Re: [Zope-CMF] A Tale of Two Repositories

2015-06-08 Thread Maurits van Rees
Tres Seaver schreef op 26-05-15 om 03:10: I have cloned the root CMF buildout repository to Git, and pushed to Github[1] and Launchpad[2]. This one was involved enough that I'd like some extra eyeballs on it before clearing out the SVN 'trunk': in particular, I think it is possilbe that some

Re: [Zope-CMF] A Tale of Two Repositories

2015-05-25 Thread Tres Seaver
I have cloned the root CMF buildout repository to Git, and pushed to Github[1] and Launchpad[2]. This one was involved enough that I'd like some extra eyeballs on it before clearing out the SVN 'trunk': in particular, I think it is possilbe that some of the historical changes (removing the

Re: [Zope-CMF] A Tale of Two Repositories

2015-05-22 Thread Tres Seaver
On 05/14/2015 03:14 PM, Tres Seaver wrote: Proposed Github-Launchpad Workflow for CMF == A Tale of Two Repositories -- .. blockquote:: It was the best of times, it was the worst of times, it was the age of wisdom,

Re: [Zope-CMF] A Tale of Two Repositories

2015-05-22 Thread Tres Seaver
Products.CMFTopic is now moved to Github / Launchpad: $ svn log -r HEAD \ svn+ssh://svn.zope.org/repos/main/Products.CMFTopic/trunk r130523 | tseaver | 2015-05-22 19:01:00 -0400 (Fri, 22 May 2015) | 8 lines Note source

Re: [Zope-CMF] A Tale of Two Repositories

2015-05-22 Thread Tres Seaver
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Products.DCWorkflow now moved to Github/Launchpad: $ svn log -r HEAD / svn+ssh://svn.zope.org/repos/main/Products.DCWorkflow/trunk - r130527 | tseaver | 2015-05-22 21:02:17

Re: [Zope-CMF] A Tale of Two Repositories

2015-05-22 Thread Tres Seaver
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Products.CMFCore is now moved to Github / Launchpad: $ svn log -r HEAD \ svn+ssh://svn.zope.org/repos/main/Products.CMFCore/trunk - r130521 | tseaver | 2015-05-22 17:04:03

Re: [Zope-CMF] A Tale of Two Repositories

2015-05-22 Thread Tres Seaver
Products.CMFDefault is now moved to Github / Launchpad: $ svn log -r HEAD \ svn+ssh://svn.zope.org/repos/main/Products.CMFDefault/trunk r130522 | tseaver | 2015-05-22 18:45:38 -0400 (Fri, 22 May 2015) | 8 lines Note

Re: [Zope-CMF] A Tale of Two Repositories

2015-05-16 Thread Tres Seaver
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 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 patterns: - Fork the repository

Re: [Zope-CMF] A Tale of Two Repositories

2015-05-16 Thread Tres Seaver
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 05/15/2015 07:55 AM, Charlie Clark wrote: 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

Re: [Zope-CMF] A Tale of Two Repositories

2015-05-15 Thread Charlie Clark
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.

Re: [Zope-CMF] A Tale of Two Repositories

2015-05-15 Thread Maurits van Rees
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