Opened 4 years ago

Last modified 3 months ago

#15949 needs_information defect

Can we migrate internal SVN to a document store, wiki, or set of git repositories?

Reported by: nickm Owned by: tor-gitadm
Priority: Medium Milestone:
Component: Internal Services/Service - git Version:
Severity: Normal Keywords:
Cc: mcs, ln5 Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

Here's what's in our internal SVN at the moment:

contact_info -- information on contacting various people at Tor

forms -- expense forms, timesheets, etc.

jobs -- an archive of (some) past job postings

manual_bridgedb -- a listing of bridges that we hand out by hand when asked

monthly_reports -- some old reports on what we were doing back in 2011/2012

newsleters -- some old newsletters we sent out in 2011/2012.

notes -- memoranda on some conversations and blog post drafts and whatnot.

proposals -- proposals we've made to various organizations

roadmaps -- old roadmap documentaations

supporting_organizations -- peopel who have helped us out, and what they said

tbb-qa -- information about TBB testers, information for TBB testers

todo-lists -- schedule info and todo lists for different TP members

Some of this information could become public. Some (like my home address and phone number) could go onto an internal wiki page, if we trust our ability to set that up. Some could go onto internal git repositories instead.

This is both a policy and technical issue.

Child Tickets

Change History (9)

comment:1 Changed 4 years ago by Sebastian

Happy to help with creation of the git repos (please file extra tickets once something is decided). I'm happy with the current setup, also happy with any setup that has easy offline access, but won't veto a wiki if that's easier for anyone

comment:2 Changed 4 years ago by mcs

Cc: mcs added

comment:3 Changed 4 years ago by atagar

For what it's worth a private wiki is something I've wanted on occasion too...

08:20 < atagar> (Gah, so many applications. With such a short time this is gonna be a chaotic mess.)
08:25 < atagar> It would be nice if we had a private wiki. That would help a bit.

It would help with GSoC/SoP coordination. I'm a tad wary of 'secrecy creep' where we restrict things too much. But this could be addressed by someone who cares about transparency taking a periodic audit of the pages, asking 'does this really need to be secret?'.

Anyway, just my two cents. Love to see this move forward.

comment:4 Changed 19 months ago by teor

Severity: Normal

Set all open tickets without a severity to "Normal"

comment:5 Changed 10 months ago by irl

Owner: changed from erinn, nickm, Sebastian, weasel to tor-gitadm
Status: newassigned

Setting owner to tor-gitadm as the owners that are set are not working on this currently. (Please correct me if I'm wrong).

comment:6 Changed 8 months ago by irl

Status: assignedneeds_information

I don't actually know where this internal Subversion is, or whether it is still used. Either someone knowledgable could update this ticket or we can close it due to inactivity. Maybe the internal Subversion is working just fine as a solution for the things it is used for just now.

comment:7 Changed 8 months ago by hiro

This system is used for legal documents and other related things. Some of the things mentioned in the ticket though are handled somewhere else at the moment. Not sure we should just close this. Maybe we should move it as a service ticket.

Last edited 8 months ago by hiro (previous) (diff)

comment:8 Changed 8 months ago by irl

If it is currently used, the people that are using it should be the owners of this ticket. I don't think the git team can really make any progress with this ticket as it is.

comment:9 Changed 3 months ago by irl

Cc: ln5 added

Potentially NextCloud is the answer to this ticket.

Note: See TracTickets for help on using tickets.