Re: [VOTE] retire zeta components from incubation
About CI, we could use Travis. It works perfectly with Github and PHPUnit. Several PHP projects already use it --- 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 Le samedi 14 avril 2012 à 18:04, Gaetano Giunta a écrit : Derick Rethans wrote: On Fri, 13 Apr 2012, Julien Vermillard wrote: Due to the reasons exposed later, and mainly due to lack of activity : [X] +1 Retire the Zeta components project and move to another infra like github I think it'd work better on github, but still, there needs to be a release at some point. I think github is ok for hosting the code. Pull requests and cherry-picks rock. And moving to git can have some nice PR. Things I'm a bit worried about is the rest of infrastructure: - github tracker is really de suck (imho of course) - where do we move the ml? - build/ci servers Bye Gaetano cheers, Derick
Github tools and discussions
Hi As Christian asked for, here's the github thread :). For CI : Travis should be OK. It's very well integrated with Github. We also talked few months ago about extra tools for code reviewing. For people that have push access to the repository, it is possible to do internal pull requests (ie. from a branch to master). It's then possible to discuss, comment line by line, just like any other PR. About the issue tracker, I think Github is sufficient, but of course we could have another stuff. Github has a lot of service hooks to link external tools like Mantis (or even Jira since Zeta is full Open Source) --- 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: Github tools and discussions
Some people at eZ engineering do it. We still don't have clear responsibilities for that. This is currently in discussion with the community project board. The best would be to have 1 or 2 persons being the entry point and pinging the right people then. Le lundi 16 avril 2012, Maxime Thomas a écrit : @Jerome Vieilledent : How do you manage that at eZ ? 2012/4/15 David Neilsen da...@panmedia.co.nz javascript:; Whos going to be responsible for managing pull requests? David Neilsen | 07 834 3366 | PANmedia ® 2012/4/15 Jérôme Vieilledent j...@ez.no javascript:; Hi As Christian asked for, here's the github thread :). For CI : Travis should be OK. It's very well integrated with Github. We also talked few months ago about extra tools for code reviewing. For people that have push access to the repository, it is possible to do internal pull requests (ie. from a branch to master). It's then possible to discuss, comment line by line, just like any other PR. About the issue tracker, I think Github is sufficient, but of course wer could have another stuff. Github has a lot of service hooks to link external tools like Mantis (or even Jira since Zeta is full Open Source)s --- Jérôme Vieilledent Software engineer eZ Systems | 26 rue de la République, 69002 Lyon, France mailto:j...@ez.no javascript:; skype lolautruche | twitter @jvieilledent -- Maxime maxime.tho...@wascou.org javascript:; | www.wascou.org | http://twitter.com/wascou
