Re: [Zope-CMF] A Tale of Two Repositories
Am .05.2015, 12:11 Uhr, schrieb yuppie y.2...@wcm-solutions.de: thanks for working on this issue. I'm not very happy about the proposed solution because it makes the GitHub repository the primary repository and the canonical location for bug reports. But compromises never make everybody happy. For the record, like yuppie I'm not happy with Github as the canonical repository either. Is this because it's easier to use travis-ci? Or simply because it's more convenient to have everything in one place? I'm happy about your proposal because it looks like a practicable solution everybody can live with. I can live with it because I haven't made a commit in at least two years. Charlie -- Charlie Clark Managing Director Clark Consulting Research German Office Kronenstr. 27a Düsseldorf D- 40217 Tel: +49-211-600-3657 Mobile: +49-178-782-6226 ___ Zope-CMF maillist - Zope-CMF@zope.org https://mail.zope.org/mailman/listinfo/zope-cmf See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests
Re: [Zope-CMF] A Tale of Two Repositories
Tres Seaver schreef op 14-05-15 om 21:14: Contributor Workflow: Github - Github-based contributors will follow normal Github workflow patterns: - 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 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 synchronisation. 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. Sounds good to me. -- Maurits van Rees: http://maurits.vanrees.org/ Zest Software: http://zestsoftware.nl ___ Zope-CMF maillist - Zope-CMF@zope.org https://mail.zope.org/mailman/listinfo/zope-cmf See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests
[Zope-CMF] Successful - CMF-trunk_Zope-trunk - Build # 741
CMF-trunk_Zope-trunk - Build # 741 - Successful: Check console output at https://jenkins.starzel.de/job/CMF-trunk_Zope-trunk/741/ to view the results.___ Zope-CMF maillist - Zope-CMF@zope.org https://mail.zope.org/mailman/listinfo/zope-cmf See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests
