You are viewing a plain text version of this content. The canonical link for it is here.

Posted to zeta-dev@incubator.apache.org by Benjamin Eberlei <ko...@beberlei.de> on 2012/04/20 11:35:21 UTC

Migrating Zeta Componetns to Github

Repost into its own topic for better seperation:

I volunteered to do a migration of the code to github.

I will do the following steps:

1. Do a SVN to Git migration for every component on its own. Every
component will have its own repository with issue tracker on Github.
2. Rewrite history to add composer.json files to all stable tags
3. Push to Github

Derick already opened an Organization on Github and I guess all current
committers will get write access to it.

Adding composer helps us with the deployment issue in the short term and in
the medium/long term we could maybe setup a pirum channel on github pages
to enable PEAR installation again. Composer can work with classmaps so that
the file/class layout is no problem for autoloading and components become
instantly usable by third parties.

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
travis-ci. I will attempt to do this for one component as a demonstration.

I can't give a timeframe on this but will highly prioritize this and hope
to get it done within a week.

greetings,
Benjamin

Re: Migrating Zeta Componetns to Github

Posted by Derick Rethans <de...@apache.org>.

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: zeta@lists.xdebug.org
> 
> You can subscribe by sending an email to zeta-subscribe@lists.xdebug.org

I go that wrong. It's: 

Send an e-mail to ecartis@lists.xdebug.org with subject "subscribe zeta"

cheers,
Derick

Re: Migrating Zeta Componetns to Github

Posted by Jérôme Vieilledent <jv...@ez.no>.

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:jv@ez.no
skype lolautruche | twitter @jvieilledent


Le vendredi 20 avril 2012 à 14:35, James Pic a écrit :

> On Fri, Apr 20, 2012 at 2:26 PM, Derick Rethans <derick@apache.org (mailto:derick@apache.org)> 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. I doubt anybody wants to maintain "PhpGenerator" f.e.
> >  
>  
>  
> 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 this or that version ?
>  
> What if a user wants to depend on a component in its trunk version, or even
> from his personal fork ? It should be super easy if we want people to fork
> and issue pull requests.
>  
> I am not aware that PEAR is capable of installing stuff directly from
> github, like pip does for python*. I eared compozer would be able to do
> that one day.
>  
> I think it's worth the experiment.
>  
> Regards
>  
> *
> http://blog.yourlabs.org/post/19725807220/django-pinax-virtualenv-setuptools-pip
>  
>