Hi there, I am sending this to all vegas teams in order to collect information to make decisions on how we should configure github.com for Tor teams use.
To be clear - we are not replacing hosting our own git repo for github.com.
We are considering using it as a synced repo for other means (more information below).
Please answer this as soon as you can so we can get things organized :) and projects that want to use it can move on to use it.
thanks! isabela
background:
This history goes way back then I will do in the background I am providing here. If you want to know more ping (isa or maybe irc in general cuz isa doesn't know i tall either).
To make things short, we have been investigating options to improve our workflow and volunteers workflow. Network team has being doing a lot of that and recently decided to use github.com as a solution for, between other things:
* receive and review volunteers collaborations * review long pieces of code * use travis/CI testing from github.com infra
When doing it we saw that OONI is also using github.com in their workflow. And after the network team migrated to it, stem also start using it. With that, an instance of gitlab that we had for tests (oniongit) was only being used by the UX/Services teams. To consolidate how we do things, UX/Services teams decided to move to github.com too (and we will kill oniongit).
The idea here is to have github.com for volunteers patches and some of the stuff listed above that the network team is doing (if people want them) but we will:
* keep trac as our issue tracker (so all teams will continue to use trac tickets to coordinate their work) * our real repo will always be our repo (so we can only push to master on our repo and only us can do it)
There is more to what I am saying here, more configuration details and use cases you might want to talk about. That is why I am sending this survey, to learn more from all teams.
The goal here is to organize how tor does things with github and have this option available for teams to use. If you think your team doesn't need this you can just let us know in the survey.
note: some configuration discussion is going on in this other pad: https://pad.riseup.net/p/Organizing-GitHub-and-Tor
survey:
Do you currently use github for anything? If yes, could you describe a bit how? Things like:
* What usernames your team members has on github? * What github projects is your team using? * What github repos? * Any special permissions configuration? * Do you sync what is there with tor's git? (gitweb) If so how?
If you are not using it yet, and could see a reason to start using it, please let us know:
* What would you answer for the above questions (for those who are already using it), you can write 'i would need a project named xxxx' for instance. * Is there anything else your team would need in order to be set up to use github?
isabela:
[snip]
survey:
Do you currently use github for anything? If yes, could you describe a bit how? Things like:
- What usernames your team members has on github?
- What github projects is your team using?
- What github repos?
- Any special permissions configuration?
- Do you sync what is there with tor's git? (gitweb) If so how?
As a team we don't use Github currently. There are some team members who have personal repositories on Github instead of using our own infrastructure for that, though.
If you are not using it yet, and could see a reason to start using it, please let us know:
- What would you answer for the above questions (for those who are already using it), you can write 'i would need a project named xxxx' for instance.
- Is there anything else your team would need in order to be set up to use github?
I think no one on the team is against trying it out at least. Furthermore, we have some folks who want to benefit from a good Github integration as it makes it e.g. much easier for them to contribute patches. Thus, I think we should offer that option in a way that we
a) expose our canonical Tor Browser related repos on Github (that is Torbutton, Tor Launcher, tor-browser-build, rbm, tor-browser) b) can do code reviews on Github if someone wants that c) can easily deal with pull requests against our mirrored Tor Browser repos on Github
I don't think we are at a point where we want to have a Github-only workflow just keeping the repos at out infrastructure. I fear the moment where M$ is banning Tor usage from Github for some arbitrary reason and then we are trying to scramble to our feet (assuming that all of us are actually dogfooding and are using Tor Browser/Tor to do their work). And, additionally, I at least am not convinced of using non-free tools to create free software.[1]
Georg