On Apr 10, 2011, at 12:58 PM, Martin v. Löwis wrote: >> The one question that comes to mind is how will repo write >> permissions be handled/shared between all our repos? With the recent >> policy of granting Jython committers cpython commit access if they >> want it, sharing the permissions wouldn't be a problem. In turn we >> like the idea of reciprocating commit rights to Jython back to >> cpython committers. > > In the past, granting permissions generously wasn't a problem as long > as users where aware what repositories they are allowed to commit to. > There isn't a true push log at this point (IIUC), but at least for > cpython, we can audit what changes have been pushed by what user through > the commit emails. > As it is always possible to revert undesired changes, and to revoke > privileges that are abused, there is no reason to technically enforce > access control. > > IOW, cpython committers just shouldn't push to Jython's repository, > and vice versa, except for a good reason. > > Ultimately, it's up to Georg and Antoine to decide whether they want > to accept the load. One option would be to grant a Jython developer > control to account management - preferably a single person, who would > then also approve/apply changes to the hooks.
That could be me. If this would mean creating an account for me on python.org so I could handle the majority of the maintenance instead of Georg & Antoine, I'd be up for that. -- Philip Jenvey _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com