Re: [RESULT] Re: [VOTE] retire zeta components from incubation
On Sun, Apr 29, 2012 at 10:42 AM, Jukka Zitting jukka.zitt...@gmail.com wrote: Hi, On Fri, Apr 20, 2012 at 4:05 PM, Julien Vermillard jvermill...@gmail.com wrote: So let's close this podling. OK. See http://incubator.apache.org/guides/retirement.html for the process to follow, including the IPMC vote to make this official. Who'll take care of this cleanup? Hi, I seen this page, I'll do the duty but next week. Julien
Re: [VOTE] retire zeta components from incubation
On Mon, Apr 16, 2012 at 6:12 PM, Benjamin Eberlei kont...@beberlei.de wrote: +1 for github On Mon, Apr 16, 2012 at 9:17 AM, Christian Grobmeier grobme...@gmail.comwrote: 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 Hi, Before closing the vote, it would be nice to have a vote of all the involved zeta commiters, if you belive this podling have a chance to regain activity and cutting release, you can vote against the retirement of apache incubator. Julien
Re: [VOTE] retire zeta components from incubation
+1 GitHub rocks your socks !
Re: [VOTE] retire zeta components from incubation
On Fri, 2012-04-13 at 10:30 +0200, Julien Vermillard wrote: Hi, Due to the reasons exposed later, and mainly due to lack of activity : [ ] +1 Retire the Zeta components project and move to another infra like github [ ] -1 Do not retire the project, because ... ±0 I do not want to vote on this because of a bunch of reasons. But since you seem to be waiting for a vote from my / our side I still send this mail. Cheers, Kore -- Kore Nordmann(GPG 0xDDC70BBB) - What I do: http://kore-nordmann.de/portfolio.html - Motivate me: http://wishlist.kore-nordmann.de/ - Hire me: http://qafoo.com/ signature.asc Description: This is a digitally signed message part
Re: [VOTE] retire zeta components from incubation
On Fri, Apr 20, 2012 at 11:19 AM, Kore Nordmann m...@kore-nordmann.de wrote: On Fri, 2012-04-13 at 10:30 +0200, Julien Vermillard wrote: Hi, Due to the reasons exposed later, and mainly due to lack of activity : [ ] +1 Retire the Zeta components project and move to another infra like github [ ] -1 Do not retire the project, because ... ±0 I do not want to vote on this because of a bunch of reasons. But since you seem to be waiting for a vote from my / our side I still send this mail. If your reasons are related to the project we are all interested in them. Cheers! Cheers, Kore -- Kore Nordmann (GPG 0xDDC70BBB) - What I do: http://kore-nordmann.de/portfolio.html - Motivate me: http://wishlist.kore-nordmann.de/ - Hire me: http://qafoo.com/ -- http://www.grobmeier.de https://www.timeandbill.de
Re: [VOTE] retire zeta components from incubation
Hi, On 04/13/2012 10:30 AM, Julien Vermillard wrote: Due to the reasons exposed later, and mainly due to lack of activity : [ ] +1 Retire the Zeta components project and move to another infra like github [ ] -1 Do not retire the project, because ... sadly, I did not find time to look into all this stuff. This also seems the reason that Zeta is dying: Time lack. I'm a bit sad, that Zeta is being closed down, but I think that it's the logical way to go. Since I won't find any time to take care for it in the near future, I cannot go any other way than vote ±0 for the retirement. If anyone feels to have the time for taking care of the project, I'd be rather happy. However, due to business reasons, I personally cannot. Benjamin just proposed to move the code to a Github organization, which I find the best solution for now. Best regards, Toby -- Tobias Schlitthttp://schlitt.infoGPG Key: 0xC462BC14 Want to hire me? Need quality assurance?http://qafoo.com eZ Components are Zeta Components now! http://bit.ly/9S7zbn
Re: [VOTE] retire zeta components from incubation
Hi, On Apr 20, 2012 11:26 AM, Tobias Schlitt tob...@schlitt.info wrote: sadly, I did not find time to look into all this stuff. This also seems the reason that Zeta is dying: Time lack. I'm a bit sad, that Zeta is being closed down, but I think that it's the logical way to go. I think the important part is that PHP is finally starting to have a reasonable infrastructure for having a proper ecosystem: * Composer for dependency handling and easy library publishing * PSR-0 for standard autoloading * GitHub for collaborative development * Travis for continuous integration These four combined make it much easier to publish simpler, more decoupled libraries that just works. Node.js has a very similar infrastructure with NPM, and there indeed this has produced hundreds of compatible modules that are widely used, and that don't need any sort of monolithic project governance structure. I think there is still a place for an effort advocating library interoperability, quality and coding standards. Zeta could be that, but it needs to be part of this new ecosystem, not something standing outside of it. Toby /Henri
Re: [VOTE] retire zeta components from incubation
Hi, Am Freitag, 20. April 2012, 11:25:20 schrieb Tobias Schlitt: Hi, [snip] sadly, I did not find time to look into all this stuff. This also seems the reason that Zeta is dying: Time lack. I'm a bit sad, that Zeta is being closed down, but I think that it's the logical way to go. Since I won't find any time to take care for it in the near future, I cannot go any other way than vote Nice to see some reactions of the core developers. Especially thanks to Toby because of the very clear words. It's really sad to see that the Zeta Components did not reached it's goals here at Apache. It's sad to see that the core committers are not able to maintain the project. It's sad to see no more development. (It's sad that I wasn't able to support the Components more.) Probably github is a better place. But I do not expect more life there. What I'm missing: - What's the future of the Components? Is it just maintenance mode? - What's the legal/license situation regarding the history/eZ Systems? - What's eZ's position? (I guess they are most interested in a clear situation of the project.) Would it be helpful to have an IRC meeting to discuss the future? (Or is it to political to speak clear words where everything is perhaps somehow logged?) Thomas
Re: [VOTE] retire zeta components from incubation
On Fri, Apr 20, 2012 at 11:36 AM, Henri Bergius henri.berg...@iki.fiwrote: Hi, On Apr 20, 2012 11:26 AM, Tobias Schlitt tob...@schlitt.info wrote: sadly, I did not find time to look into all this stuff. This also seems the reason that Zeta is dying: Time lack. I'm a bit sad, that Zeta is being closed down, but I think that it's the logical way to go. I think the important part is that PHP is finally starting to have a reasonable infrastructure for having a proper ecosystem: * Composer for dependency handling and easy library publishing * PSR-0 for standard autoloading * GitHub for collaborative development * Travis for continuous integration These four combined make it much easier to publish simpler, more decoupled libraries that just works. Node.js has a very similar infrastructure with NPM, and there indeed this has produced hundreds of compatible modules that are widely used, and that don't need any sort of monolithic project governance structure. I think there is still a place for an effort advocating library interoperability, quality and coding standards. Zeta could be that, but it needs to be part of this new ecosystem, not something standing outside of it. Good points, but don't we need to setup a light organization / project governance around this, some people that have a stake in the project and can oversee the github account[, merging pull requests], github webpages, travis setup and potentially also do some release management. For mail I guess we can use Google groups like php-fig does. Related thread on share.ez.no: http://share.ez.no/forums/general/how-is-zeta-components Toby /Henri - ar
Re: [VOTE] retire zeta components from incubation
On Fri, 20 Apr 2012, André Rømcke wrote: but don't we need to setup a light organization / project governance around this, some people that have a stake in the project and can oversee the github account[, merging pull requests], github webpages, travis setup and potentially also do some release management. What do you suggest that governance should do? For mail I guess we can use Google groups like php-fig does. Ugh, never Google Groups. I've set-up a ML as per the other thread. cheers, Derick
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
Re: [VOTE] retire zeta components from incubation
Travis seems good, no host on our side. Is there a fee or something ? Le 14 avril 2012 18:11, Jérôme Vieilledent j...@ez.no a écrit : 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 -- Maxime maxime.tho...@wascou.org | www.wascou.org | http://twitter.com/wascou
Re: [VOTE] retire zeta components from incubation
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
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
