[ZF] A couple of github issues

[Marius Gedminas]

On Thu, Jan 31, 2013 at 06:14:44PM -0500, Jim Fulton wrote:
> There are a couple of issues we need to address:
> 
> 1. In github, developers can't create repos.
...
>    There are a number of ways to mitigate this.  I'll throw some out
>    for discussion:
> 
>    - use bitbucket which has saner permissions

-1

We had a vote and the majority expressed their wish to use Github.

>    - (or try to get github to fix their permissions)

+1 (but I'm not holding my breath)

>    - convert the svn repos in mass. This doesn't address new projects,
>      but we have a lot of conversions ahead of us.

+0.9 

This sounds like a lot of work, so it's not a quick solution.  Unless we
just create empty repos for existing projects and let people who care
do the conversion and push?  Eh, I'm not a fan of decoys, so -0 to this
particular idea.

>    - Write and maintain an application that authenticates contributors
>      and creates repos for them. (This will be a pain to write and
>      maintain. Not it!)

+0.2

>    - Switch to a more course-grained repository-management strategy,
>      managing multiple Python projects in a single git repo.

-1

>    - Identify some specialists and create a process other than
>      zope-dev for requesting repos.

+0.5

There was also the other suggestion by Stephan:

>    - Another option would be to make everyone an admin. Yes, I know
>      that means that anyone can add new contributors to the
>      organization but that is still better than the status quo.

+1

https://help.github.com/articles/what-are-the-different-access-permissions
says that admins "cannot add or remove users from the repositories they
admin", but they can "add and remove users from the admin team".  If I
understand that correctly, that means admins can't add new contributors,
but they can make non-admin contributors into other admins?

> 2. Converting from svn2git requires an authors.txt file.  This
>    contains svn login ids and github email addresses.  The former
>    are accessible publically via svn.zope.org and the later are
>    accessible publicly via git log.  This file isn't static, so it
>    needs to be managed via VCS.
...
>    IMO, the authors.txt file should be made available in a public
>    repo.

+1

Marius Gedminas
-- 
Lisp-style macros [...] are to C-style macros what Emacs is to cat.
                -- Jacek Generowicz
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 190 bytes
Desc: Digital signature
URL: <http://mail.zope.org/pipermail/foundation/attachments/20130201/7d033438/attachment.sig>