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
Re: [VOTE] retire zeta components from incubation
On Mon, Apr 16, 2012 at 2:30 AM, Ole Marius Smestad o...@apache.org wrote: On Friday 13. April 2012 at 10:30, Julien Vermillard wrote: Hi, 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 am ambivalent about this vote, but...) I do think that this project can do nicely on github, and what Christian and Julien said about the state of community seems accurate. That being said, I also think think that James' suggestion should be considered, it doesn't seem necessary to block a release, for test infrastructure changes, which presumably can be done at a later point. We have no rush with retiring this project. If you feel that you guys want stay at the ASF no problem. In this case please lets make up a plan and set some kind of a date at which we reflect the situation again. If you want to give it another try change your vote to -1 and lets discuss it again. Surely you'll find open ears. Cheers Christian -- Regards, Ole Marius -- http://www.grobmeier.de https://www.timeandbill.de
