-----BEGIN PGP SIGNED MESSAGE-----
On 05/15/2015 07:07 AM, Maurits van Rees wrote:
> Tres Seaver schreef op 14-05-15 om 21:14:
>> Contributor Workflow: Github -----------------------------
>> Github-based contributors will follow normal Github workflow
>> - Fork the repository of interest via the Github UI.
> If they have contributor acccess to the original repository, they can
> of course create a branch in this original github repository.
I class "contributor" as distinct from "maintainer", based on exactly
those rights, although we might want to adopt a pattern where even
maintainers function as though they were contributors, submitting pull
requests for review by another maintainer.
> I was going to say: "the same is true for Launchpad," but on Launchpad
> we should of course not do any manual changes to the original
> repository, because it is meant to be only touched by the automatic
I don't have enough Git-fu to work out how to automate two-way
synchronization, which is why I described having the LP repository be a
>> The Launchpad repository will be synched automatically, whether by
>> the cron job or by the built-in Launchpad mirroring.
> Does anyone know if we can make the Launchpad repository read-only
> except for the synchronization? This would prevent accidental
> commits. Well, I guess the access rights can be tweaked. If the repo
> can only be written to by one Zope Foundation or CMF account, this
> would prevent accidental commits by individual contributors.
If Launchpad supports it, then having the commit rights restricted to the
mirroring process would be great.
> Sounds good to me.
Tres Seaver +1 540-429-0999 tsea...@palladion.com
Palladion Software "Excellence by Design" http://palladion.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
-----END PGP SIGNATURE-----
Zope-CMF maillist - Zope-CMF@zope.org
See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests