Re: Migrating Zeta Componetns to Github

2012-05-11 Thread Christian Grobmeier
Sorry, no news arrived to my inbox. Can you ping trademarks again? Please put me on CC, if you can On Fri, May 11, 2012 at 11:05 PM, Benjamin Eberlei wrote: > @Christian So are there any news? > > On Wed, Apr 25, 2012 at 2:00 AM, Benjamin Eberlei wrote: > >> Hello everyone, >> >> i have just comp

Re: Migrating Zeta Componetns to Github

2012-05-11 Thread Benjamin Eberlei
@Christian So are there any news? On Wed, Apr 25, 2012 at 2:00 AM, Benjamin Eberlei wrote: > Hello everyone, > > i have just completed the migration of the Apache SVN to Github > organization: Code is still pushed at the moment, these are the done tasks: > > https://github.com/zetacomponents > >

Re: Migrating Zeta Componetns to Github

2012-04-24 Thread Benjamin Eberlei
Hello everyone, i have just completed the migration of the Apache SVN to Github organization: Code is still pushed at the moment, these are the done tasks: https://github.com/zetacomponents * Each component is split into its own repository * Author Information has been updated on frequent commit

Re: Migrating Zeta Componetns to Github

2012-04-20 Thread Falko Menge
On 04/20/2012 01:35 PM, Benjamin Eberlei wrote: The next step would then be that committers claim components and we determine the deprecated/abandoned/ maintained state of each of them. Every maintainer is then responsible for getting the tests back running with the new schema and adding this to

Re: Migrating Zeta Componetns to Github

2012-04-20 Thread James Pic
Do you want people to maintain their components, contribute to other's components ? If that's a need then the purpose of the migration should help this, and not just about throwing the code at github's face.

Re: Migrating Zeta Componetns to Github

2012-04-20 Thread James Pic
On Fri, Apr 20, 2012 at 2:54 PM, Patrick Allaert wrote: > > I think we should keep this thread focused on the migration of Zeta to > github. > > Feel free to change the subject to match the topic better. One of the many fantastic concepts I learned from the components project philosophy is to fir

Re: Migrating Zeta Componetns to Github

2012-04-20 Thread Christian Grobmeier
On Fri, Apr 20, 2012 at 2:58 PM, Patrick ALLAERT wrote: > 2012/4/20 Benjamin Eberlei : >> Adding to this: I could use some help of course, so anyone also feeling to >> volunteer can do so. >> >> My idea was to create a repository with a bash/php script collection that >> does the migration and the

Re: Migrating Zeta Componetns to Github

2012-04-20 Thread Patrick ALLAERT
2012/4/20 Benjamin Eberlei : > Adding to this: I could use some help of course, so anyone also feeling to > volunteer can do so. > > My idea was to create a repository with a bash/php script collection that > does the migration and then collaborate on that until we have the final > version to use.

Re: Migrating Zeta Componetns to Github

2012-04-20 Thread Patrick Allaert
2012/4/20 James Pic : > I love this idea ! Make zeta components a coding standard rather than a > centralized repo of libraries is kind of the holy grail for me ... > > In that case I only see one issue: dependency management. How should the > user specify that he wants this and that component of t

Re: Migrating Zeta Componetns to Github

2012-04-20 Thread Jérôme Vieilledent
As Daniel mentioned, Composer/Packagist is probably the best way to go. For Symfony2 users, it's even easier with deps/deps.lock files. --- Jérôme Vieilledent Software engineer eZ Systems | 26 rue de la République, 69002 Lyon, France mailto:j...@ez.no skype lolautruche | twitter @jvieilledent

Re: Migrating Zeta Componetns to Github

2012-04-20 Thread Daniel Fahlke
Am 20. April 2012 14:35 schrieb James Pic : > On Fri, Apr 20, 2012 at 2:26 PM, Derick Rethans wrote: > > > On Fri, 20 Apr 2012, James Pic wrote: > > > > > Can't apache just pass the repo to say Derick or something ? > > > > > > https://github.com/apache/zetacomponents > > > > I think we should sp

Re: Migrating Zeta Componetns to Github

2012-04-20 Thread James Pic
On Fri, Apr 20, 2012 at 2:26 PM, Derick Rethans wrote: > On Fri, 20 Apr 2012, James Pic wrote: > > > Can't apache just pass the repo to say Derick or something ? > > > > https://github.com/apache/zetacomponents > > I think we should split it up, so that we can/could orphan specific > components.

Re: Migrating Zeta Componetns to Github

2012-04-20 Thread Derick Rethans
On Fri, 20 Apr 2012, James Pic wrote: > Can't apache just pass the repo to say Derick or something ? > > https://github.com/apache/zetacomponents I think we should split it up, so that we can/could orphan specific components. I doubt anybody wants to maintain "PhpGenerator" f.e. cheers, Derick

Re: Migrating Zeta Componetns to Github

2012-04-20 Thread Derick Rethans
On Fri, 20 Apr 2012, Derick Rethans wrote: > On Fri, 20 Apr 2012, Benjamin Eberlei wrote: > > > Derick already opened an Organization on Github and I guess all current > > committers will get write access to it. > > I've also set-up a mailinglist: z...@lists.xdebug.org > > You can subscribe by

Re: Migrating Zeta Componetns to Github

2012-04-20 Thread James Pic
On Fri, Apr 20, 2012 at 2:16 PM, Derick Rethans wrote: > On Fri, 20 Apr 2012, Benjamin Eberlei wrote: > > > Derick already opened an Organization on Github and I guess all current > > committers will get write access to it. > > I've also set-up a mailinglist: z...@lists.xdebug.org > Thank you !

Re: Migrating Zeta Componetns to Github

2012-04-20 Thread James Pic
Can't apache just pass the repo to say Derick or something ? https://github.com/apache/zetacomponents

Re: Migrating Zeta Componetns to Github

2012-04-20 Thread Derick Rethans
On Fri, 20 Apr 2012, Benjamin Eberlei wrote: > Derick already opened an Organization on Github and I guess all current > committers will get write access to it. I've also set-up a mailinglist: z...@lists.xdebug.org You can subscribe by sending an email to zeta-subscr...@lists.xdebug.org cheers,

Re: Migrating Zeta Componetns to Github

2012-04-20 Thread Benjamin Eberlei
Adding to this: I could use some help of course, so anyone also feeling to volunteer can do so. My idea was to create a repository with a bash/php script collection that does the migration and then collaborate on that until we have the final version to use. Starting point is here: https://github.