Re: [RESULT] Re: [VOTE] retire zeta components from incubation
On Sun, Apr 29, 2012 at 10:42 AM, Jukka Zitting wrote: > Hi, > > On Fri, Apr 20, 2012 at 4:05 PM, Julien Vermillard > 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: [RESULT] Re: [VOTE] retire zeta components from incubation
Hi, On Fri, Apr 20, 2012 at 4:05 PM, Julien Vermillard 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? BR, Jukka Zitting
[RESULT] Re: [VOTE] retire zeta components from incubation
So let's close the vote : +1 binding : grobmeier, beberlei, derick, jpic, oms, rolandb, +0 binding : kore, toby -1 none So let's close this podling. Julien On Fri, Apr 13, 2012 at 10:30 AM, 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 ... > > This vote is open for the next 72 hours. > Julien
Re: [VOTE] retire zeta components from incubation
On Fri, Apr 20, 2012 at 2:31 PM, Derick Rethans wrote: > 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? > Quality control ! If someone has a lib that matches the components coding standards and license, i say let it be an official component. We've seen **many** components made by non core developers that were great and never got into the components project, although they were totally worth it (well designed, 100% documented, 100% tested, etc, etc). If the components project did accept them then it would not have died like this. All this plan would need is a standard for deployment that encourages forking and rolling releases. The strength of the components is actually the talented people that are or were behind it. Their experience and altruism. The code itself is just a demonstration of how to do a library right. Just my 2cent
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 Fri, Apr 20, 2012 at 11:36 AM, Henri Bergius wrote: > Hi, > > On Apr 20, 2012 11:26 AM, "Tobias Schlitt" 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
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
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 On Fri, Apr 20, 2012 at 11:36 AM, Henri Bergius wrote: > Hi, > > On Apr 20, 2012 11:26 AM, "Tobias Schlitt" 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, On Apr 20, 2012 11:26 AM, "Tobias Schlitt" 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, 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
On Fri, Apr 20, 2012 at 11:19 AM, Kore Nordmann 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
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
+1 GitHub rocks your socks !
Re: [VOTE] retire zeta components from incubation
On Mon, Apr 16, 2012 at 6:12 PM, Benjamin Eberlei wrote: > +1 for github > > On Mon, Apr 16, 2012 at 9:17 AM, Christian Grobmeier > wrote: > >> On Mon, Apr 16, 2012 at 2:30 AM, Ole Marius Smestad >> 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 for github On Mon, Apr 16, 2012 at 9:17 AM, Christian Grobmeier wrote: > On Mon, Apr 16, 2012 at 2:30 AM, Ole Marius Smestad > 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
On Mon, Apr 16, 2012 at 2:30 AM, Ole Marius Smestad 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
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. -- Regards, Ole Marius
Re: [VOTE] retire zeta components from incubation
We also talked few months ago about extra tools for code reviewing. Do we still need them or GitHub is ok on that ? What do you think ? Le 15 avril 2012 10:26, Jérôme Vieilledent a écrit : > No, as far as I know there is no fee but donation is of course encouraged > ;-) > > --- > 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 dimanche 15 avril 2012 à 10:21, Maxime Thomas a écrit : > > > Travis seems good, no host on our side. > > Is there a fee or something ? > > > > Le 14 avril 2012 18:11, Jérôme Vieilledent mailto: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 > > > > > > > -- Maxime maxime.tho...@wascou.org | www.wascou.org | http://twitter.com/wascou
Re: [VOTE] retire zeta components from incubation
Guys as much as I appreciate the progressive discussions on Github- can we please VOTE on this thread and use another mailing thread for discussions? It makes it almost impossible for Julien to count the votes. Thanks! 2012/4/15 Jérôme Vieilledent : > No, as far as I know there is no fee but donation is of course encouraged ;-) > > --- > 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 dimanche 15 avril 2012 à 10:21, Maxime Thomas a écrit : > >> Travis seems good, no host on our side. >> Is there a fee or something ? >> >> Le 14 avril 2012 18:11, Jérôme Vieilledent mailto: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 >> >> > > -- http://www.grobmeier.de https://www.timeandbill.de
Re: [VOTE] retire zeta components from incubation
No, as far as I know there is no fee but donation is of course encouraged ;-) --- 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 dimanche 15 avril 2012 à 10:21, Maxime Thomas a écrit : > Travis seems good, no host on our side. > Is there a fee or something ? > > Le 14 avril 2012 18:11, Jérôme Vieilledent mailto: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
Travis seems good, no host on our side. Is there a fee or something ? Le 14 avril 2012 18:11, Jérôme Vieilledent 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
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 > > > > >
Re: [VOTE] retire zeta components from incubation
On Sat, 14 Apr 2012, Gaetano Giunta wrote: > 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. Pull requests do, but cherry picking is a hack! > 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? I can easily host the mailinglist and set-up a mantis project for it. cheers, Derick -- http://derickrethans.nl | http://xdebug.org Like Xdebug? Consider a donation: http://xdebug.org/donate.php twitter: @derickr and @xdebug
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
Seems pretty obvious +1 David Neilsen | 07 834 3366 | PANmedia ® 2012/4/14 Philippe VINCENT-ROYOL > +1 github > > -- > Philippe VINCENT-ROYOL > > > Le vendredi 13 avril 2012 à 18:55, Ronan Guilloux a écrit : > > > +1 > > & github FTW > > > > -- > > Ronan Guilloux > > > > > > >
Re: [VOTE] retire zeta components from incubation
+1 github -- Philippe VINCENT-ROYOL Le vendredi 13 avril 2012 à 18:55, Ronan Guilloux a écrit : > +1 > & github FTW > > -- > Ronan Guilloux > >
Re: [VOTE] retire zeta components from incubation
+1 & github FTW -- Ronan Guilloux
Re: [VOTE] retire zeta components from incubation
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. cheers, Derick -- http://derickrethans.nl | http://xdebug.org Like Xdebug? Consider a donation: http://xdebug.org/donate.php twitter: @derickr and @xdebug
Re: [VOTE] retire zeta components from incubation
James, On Fri, Apr 13, 2012 at 11:56 AM, James Pic wrote: > Shouldn't we consider rolling back the unit tests updates ? That would > unlock the release process. we have suggested to retire this podling because of the lack of activity. If the committers tell us they want to continue with it and try to build a community - fine. But so far you are the only committer who has even responded to this proposal. This makes me feel this podling is dead. Please convince me that people will come back to here, then I will gladly change my +1 to a -1. Cheers Christian > > Regards -- http://www.grobmeier.de https://www.timeandbill.de
Re: [VOTE] retire zeta components from incubation
+1 2012/4/13 James Pic > Shouldn't we consider rolling back the unit tests updates ? That would > unlock the release process. > > Regards > -- Maxime maxime.tho...@wascou.org | www.wascou.org | http://twitter.com/wascou
Re: [VOTE] retire zeta components from incubation
Shouldn't we consider rolling back the unit tests updates ? That would unlock the release process. Regards
Re: [VOTE] retire zeta components from incubation
On Fri, Apr 13, 2012 at 10:44 AM, Luc Chase wrote: > What are the general advantages of keeping this project on Apache? This question has raised many flamewars - you'll find many blogs out there on "comparing" Github to ASF. Search for "ASF considered harmful" and the replies from Jim Jagielski. In short: Apache is around community and the people (slogan: community over code). Additionally there is a foundation which protects people before legal problems. Github is a source code hoster like Google Code. You can build a community there too, but it is not the focus. Its more a great tool. In the case of Zeta this project has failed to build up a community. Therefore it does not really match to the ASF and it might happen that people are more excited about Zeta when it goes to Github. Not every project does find a good home here - sadly. Cheers Christian > On Apr 13, 2012 9:35 AM, "Christian Grobmeier" wrote: > >> > [X] +1 Retire the Zeta components project and move to another infra >> like github >> >> :-( >> >> Please note, if somebody is interested to fork this project later, SVN >> will stay (readonly). More information on the retirement process can >> be found here: >> http://incubator.apache.org/guides/retirement.html >> >> >> >> -- >> http://www.grobmeier.de >> https://www.timeandbill.de >> -- http://www.grobmeier.de https://www.timeandbill.de
Re: [VOTE] retire zeta components from incubation
+1 On Github we could add the docs here via github pages (static) and wiki. Same for issue tracker. --- 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 vendredi 13 avril 2012 à 10:40, Philipp Kamps a écrit : > Let's define retire. Moving the code to github. But what about > documentation, website, mailing lists etc > > On Fri, Apr 13, 2012 at 10:30 AM, Julien Vermillard > mailto:jvermill...@gmail.com)> 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 ... > > > > This vote is open for the next 72 hours. > > Julien > > > > >
Re: [VOTE] retire zeta components from incubation
What are the general advantages of keeping this project on Apache? On Apr 13, 2012 9:35 AM, "Christian Grobmeier" wrote: > > [X] +1 Retire the Zeta components project and move to another infra > like github > > :-( > > Please note, if somebody is interested to fork this project later, SVN > will stay (readonly). More information on the retirement process can > be found here: > http://incubator.apache.org/guides/retirement.html > > > > -- > http://www.grobmeier.de > https://www.timeandbill.de >
Re: [VOTE] retire zeta components from incubation
Philipp On Fri, Apr 13, 2012 at 10:40 AM, Philipp Kamps wrote: > Let's define retire. Moving the code to github. But what about > documentation, website, mailing lists etc See the complete guide: http://incubator.apache.org/guides/retirement.html Basically SVN is readonly then, project is not actively maintained anymore. If somebody wants to revive the project at the ASF later, he can (with a vote on gneerals list). > > On Fri, Apr 13, 2012 at 10:30 AM, 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 ... >> >> This vote is open for the next 72 hours. >> Julien -- http://www.grobmeier.de https://www.timeandbill.de
Re: [VOTE] retire zeta components from incubation
Let's define retire. Moving the code to github. But what about documentation, website, mailing lists etc On Fri, Apr 13, 2012 at 10:30 AM, 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 ... > > This vote is open for the next 72 hours. > Julien
Re: [VOTE] retire zeta components from incubation
> [X] +1 Retire the Zeta components project and move to another infra like > github :-( Please note, if somebody is interested to fork this project later, SVN will stay (readonly). More information on the retirement process can be found here: http://incubator.apache.org/guides/retirement.html -- http://www.grobmeier.de https://www.timeandbill.de
Re: [VOTE] retire zeta components from incubation
Am 13. April 2012 10:30 schrieb Julien Vermillard : > 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 ... > > This vote is open for the next 72 hours. > Julien > +1 (+1 for github/git based infra)
[VOTE] retire zeta components from incubation
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 ... This vote is open for the next 72 hours. Julien
Re: Retire Zeta Components?
+1 for GitHub Am 10.04.2012 16:19, schrieb David Neilsen: > Sad but true. > > David Neilsen | 07 834 3366 | PANmedia ® > > > On Wed, Apr 11, 2012 at 12:08 AM, Julien Vermillard > wrote: > >> On Sun, Apr 8, 2012 at 12:48 PM, Philippe Vincent-Royol >> wrote: >>> Hi Christian, >>> >>> >>> 2012/4/8 Christian Grobmeier >>> Hello folks, i have not seen any substantial changes to ZC for weeks. There were no additions to the community (in fact, substractions, given the recent email from jerome), no commits, no email activity. This project seems pretty dead for me. >>> I'm sorry to say that but i confirm that ZC is a dead project. >>> >>> The ASF is about community; ZC has none and it is very unlikely it will >> get one. How are your feelings against this? I think Github would make more sense for Zeta Components. >>> >>> +1 for github >>> >>> In France, except ezpublish users, nobody knows ZC.. they work on >> Symfony2 >>> or Zend so... >>> One of the biggest blockers I have seen at this project is the missing release. Maybe you want to give it another try, with releasing single components (like in commons.apache.org). This will need some time too - do the committers of this project have any plans to make further steps in the Zeta direction? Cheers Christian >> >> 1+ due to the lack of activity and no real perspective on a first release. >> >> Julien >> >
Re: Retire Zeta Components?
Sad but true. David Neilsen | 07 834 3366 | PANmedia ® On Wed, Apr 11, 2012 at 12:08 AM, Julien Vermillard wrote: > On Sun, Apr 8, 2012 at 12:48 PM, Philippe Vincent-Royol > wrote: > > Hi Christian, > > > > > > 2012/4/8 Christian Grobmeier > > > >> Hello folks, > >> > >> i have not seen any substantial changes to ZC for weeks. There were no > >> additions to the community (in fact, substractions, given the recent > >> email from jerome), no commits, no email activity. This project seems > >> pretty dead for me. > >> > >> > > I'm sorry to say that but i confirm that ZC is a dead project. > > > > The ASF is about community; ZC has none and it is very unlikely it will > get > >> one. > >> > >> How are your feelings against this? I think Github would make more > >> sense for Zeta Components. > >> > > > > +1 for github > > > > In France, except ezpublish users, nobody knows ZC.. they work on > Symfony2 > > or Zend so... > > > >> > >> One of the biggest blockers I have seen at this project is the missing > >> release. Maybe you want to give it another try, with releasing single > >> components (like in commons.apache.org). This will need some time too > >> - do the committers of this project have any plans to make further > >> steps in the Zeta direction? > >> > >> Cheers > >> Christian > > 1+ due to the lack of activity and no real perspective on a first release. > > Julien >
Re: Retire Zeta Components?
On Sun, Apr 8, 2012 at 12:48 PM, Philippe Vincent-Royol wrote: > Hi Christian, > > > 2012/4/8 Christian Grobmeier > >> Hello folks, >> >> i have not seen any substantial changes to ZC for weeks. There were no >> additions to the community (in fact, substractions, given the recent >> email from jerome), no commits, no email activity. This project seems >> pretty dead for me. >> >> > I'm sorry to say that but i confirm that ZC is a dead project. > > The ASF is about community; ZC has none and it is very unlikely it will get >> one. >> >> How are your feelings against this? I think Github would make more >> sense for Zeta Components. >> > > +1 for github > > In France, except ezpublish users, nobody knows ZC.. they work on Symfony2 > or Zend so... > >> >> One of the biggest blockers I have seen at this project is the missing >> release. Maybe you want to give it another try, with releasing single >> components (like in commons.apache.org). This will need some time too >> - do the committers of this project have any plans to make further >> steps in the Zeta direction? >> >> Cheers >> Christian 1+ due to the lack of activity and no real perspective on a first release. Julien
Re: Retire Zeta Components?
Hi Christian, 2012/4/8 Christian Grobmeier > Hello folks, > > i have not seen any substantial changes to ZC for weeks. There were no > additions to the community (in fact, substractions, given the recent > email from jerome), no commits, no email activity. This project seems > pretty dead for me. > > I'm sorry to say that but i confirm that ZC is a dead project. The ASF is about community; ZC has none and it is very unlikely it will get > one. > > How are your feelings against this? I think Github would make more > sense for Zeta Components. > +1 for github In France, except ezpublish users, nobody knows ZC.. they work on Symfony2 or Zend so... > > One of the biggest blockers I have seen at this project is the missing > release. Maybe you want to give it another try, with releasing single > components (like in commons.apache.org). This will need some time too > - do the committers of this project have any plans to make further > steps in the Zeta direction? > > Cheers > Christian > > -- > http://www.grobmeier.de > https://www.timeandbill.de > -- Philippe VINCENT-ROYOL
Retire Zeta Components?
Hello folks, i have not seen any substantial changes to ZC for weeks. There were no additions to the community (in fact, substractions, given the recent email from jerome), no commits, no email activity. This project seems pretty dead for me. The ASF is about community; ZC has none and it is very unlikely it will get one. How are your feelings against this? I think Github would make more sense for Zeta Components. One of the biggest blockers I have seen at this project is the missing release. Maybe you want to give it another try, with releasing single components (like in commons.apache.org). This will need some time too - do the committers of this project have any plans to make further steps in the Zeta direction? Cheers Christian -- http://www.grobmeier.de https://www.timeandbill.de
