Malte Dik <malte....@web.de> writes: > Eric Firing wrote: > >> 2) If I understand correctly, a key question is who will have commit >> rights to the master repo on github. It seems that an exception is >> required to allow that access to more than one person. > > Multiple options (as far as I have understand github). You could use one > account with multiple ssh-keys or you can add "contributors" to the > repository > in the repositorys Admin-panel, which I haven't tried out, yet.
The github TOS allow only one person per account. I guess that's why Eric refers to an exception being required. I'm not entirely sure what Github's "public collaborator" feature means (I can only find documentation about private collaborators, which you can add if you have a paid account and a private project), but if it means push access, then I suppose it would help. >> My sense is that ideally we should have more than one person with >> that access, but far fewer people than presently have svn commit >> access. Those with access would then be asked to pull changes into >> the master from other people's clones--which would be github branches >> under their control. Sounds good to me. One possibility is to have an automated tool push reviewed and tested changes to the "official" repository, similarly to how the Android Open-Source Project uses Gerrit: http://source.android.com/source/life-of-a-patch.html The "verifier" could be just a buildbot-run script that sets the verified flag if the code passes tests. The "reviewers" could be the core developers - so instead of pulling other people's changes and pushing to the official repository, they would just flag the changes as verified, and the rest would happen automatically. But maybe that's too much overhead for a project the size of matplotlib. >> 3) Is it really a good idea to delay the release until the we make >> the github transition? Given how long it has been since a release, >> and the possibility that there will be some turbulence until we have >> had some experience with github, I think it would be better to >> release first and transition immediately afterwards. I agree that there should be a release before the transition. -- Jouni K. Seppänen http://www.iki.fi/jks ------------------------------------------------------------------------------ _______________________________________________ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
