Facebook page for Zeta Components
Hi, I'd like to create a page on Facebook for the Zeta Components project and wanted to ask if there is anything special to keep in mind (except the official branding guidelines)? I assume that I'm allowed to claim an official Facebook page in the name of Zeta? 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 - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Links error in ZetaComponents pages
Hi Cyrille, On 11/04/2010 10:51 AM, cyrille giquello wrote: In pages http://incubator.apache.org/zetacomponents/community/index.html http://incubator.apache.org/zetacomponents/documentation/install.html links about mailing lists are broken. thanks for the info, I just fixed the problems. 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 - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Zeta license changes
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi! Of intuition I posted this message to legal-discusss@, but Gavin corrected me, that incubator-general is the right place to go. So, sorry for my re-post here. I'm on fixing license headers and stuff for the Zeta Components project and want to re-confirm that I got everything right. The Zeta project has been developed under the hood of eZ Systems AS (http://ez.no) previously and code drop was signed last week. - From http://www.apache.org/legal/src-headers.html I understand that we now process as follows: - - Remove all copyright notices from source files - - Add Apache License 2.0 header to every source file - - Add a NOTICE file that notices the copyright of eZ Systems Is that the correct procedure? Or do we need to follow the steps for Treatment of Third-Party Works and keep the current copyright info inside the source files? Thanks in advance, Toby - -- Tobias Schlitt tob...@schlitt.info GPG Key: 0xC462BC14 a passion for php http://schlitt.info/opensource eZ Components are Zeta Components now! http://bit.ly/9S7zbn -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkxPybYACgkQ5bO3TcRivBSbKACeLM3X9jaTXeeOeAciNQ/btirb sVoAniUZ7P7gz1g63qTzpaU1/hF73dNh =cE5W -END PGP SIGNATURE- - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [zeta] Mailinglist moderators
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Christian, On 05/25/2010 07:51 AM, Christian Grobmeier wrote: i just created the project status page (still needs to be synced). Next step would be to create the necessary mailinglists and transfer all communications to there. We need minimum 3 moderators for those lists, so all you Zeta guys, who is volunteering? please add all initial commiters as moderators for the list. As soon as the lists are setup, I will post to our old lists in order to move communication. Find our email addresses below: Derick Rethans e...@derickrethans.nl Kore Nordmann m...@kore-nordmann.de Tobias Schlitt tob...@schlitt.info Sebastian Bergmann s...@sebastian-bergmann.de Ole Marius Smestad o...@ez.no Roland Benedetti r...@ez.no Thanks, Toby - -- Tobias Schlitt tob...@schlitt.info GPG Key: 0xC462BC14 a passion for php http://schlitt.info/opensource eZ Components are Zeta Components now! http://bit.ly/9S7zbn -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkv7Z6EACgkQ5bO3TcRivBTNtwCfa3JbGzs97h34civDVi8fmORA U7cAniFB72hF+KbI/9VcieL3O2wLfydq =ujN6 -END PGP SIGNATURE- - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[RESULT][VOTE] Accept Zeta Components into the incubator
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I'm happy to colse this vote with the result of Zeta Components being accepted for incubation. Summary of the vote: +1: 11 (7 binding, 2 memberships pending) - -1:0 0: 0 Bertrand Delacretaz (*) Chris A. Mattmann (*) Christian Grobmeier(**) Donald Woods (*) Jean-Frederic Clere Julien Vermillard (**) Mohammad Nour El-Din Niclas Hedhman (*) Nicolas Pastorino Noel J. Bergmann (*) Paul Borgermans (* = binding, ** = IPMC membership not verified, yet). You can find the original call for votes here: http://mail-archives.apache.org/mod_mbox/incubator-general/201005.mbox/%3c4bf17b68.5020...@schlitt.info%3e We'll start setting up the podling with our mentors after the weekend, i.e. on Tuesday. Thanks for your support, regards, Toby - -- Tobias Schlitt tob...@schlitt.info GPG Key: 0xC462BC14 a passion for php http://schlitt.info/opensource eZ Components are Zeta Components now! http://bit.ly/9S7zbn -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkv2jlAACgkQ5bO3TcRivBT2wACfa+Xb2SaF9Uh+6nEZ401b1Su+ eToAn26HebX7F8/KyI0PASO+RxkS+O1M =vZq7 -END PGP SIGNATURE- - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Zeta proposal - Next steps
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Bertrand, hi all, On 05/08/2010 05:45 PM, Bertrand Delacretaz wrote: On Sat, May 8, 2010 at 1:32 PM, Gav... ga...@16degrees.com.au wrote: ...I've shown my support for Christian, we just need to wait for the Incubator PMC chair to approve or not, and he is on his holidays currently I believe IMO the decision is made by a vote of the Incubator PMC members, it's not just the chair's decision. I just started the vote on the incubator private, it's open for 72 hours at least so we should have an answer for Christian by Wednesday morning. As Julien is an ASF member, his Incubator PMC membership is just a formality - Noel as the PMC chair must forward the request to the board when he's back, which should be later this weekend. So I guess we should be ready to vote on the Zeta proposal by Wednesday. In the meantime, Zeta committers who don't have an iCLA on file [1] should send it, that will save time if/when the project is accepted. I don't think there's more that can be done at this point to save time. are there any news regarding the acceptance of our mentors? Thanks, Toby - -- Tobias Schlitt tob...@schlitt.info GPG Key: 0xC462BC14 a passion for php http://schlitt.info/opensource eZ Components are Zeta Components now! http://bit.ly/9S7zbn -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkvw3wIACgkQ5bO3TcRivBTofACfenywSimxxR05jymQa5n/nygQ swIAoKGWovGB5ZefIGayY9QNocxhFLS9 =eYVZ -END PGP SIGNATURE- - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Zeta proposal - Next steps
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Bertrand, On 05/17/2010 11:30 AM, Bertrand Delacretaz wrote: On Mon, May 17, 2010 at 8:15 AM, Tobias Schlitt tob...@schlitt.info wrote: On 05/08/2010 05:45 PM, Bertrand Delacretaz wrote: ...I guess we should be ready to vote on the Zeta proposal by Wednesday. In the meantime, Zeta committers who don't have an iCLA on file [1] should send it, that will save time if/when the project is accepted. I don't think there's more that can be done at this point to save time. are there any news regarding the acceptance of our mentors?... This took a bit more time than expected, and I forgot the required delay once the board acknowledges a new Incubator PMC member [1] - taking this into account we'll have a final answer tomorrow at 4PM. So as not to keep you waiting longer, I think you can go ahead with the vote, and mention pending Incubator PMC membership confirmation for Julien and Christian as mentors. Cool, looking forward to it. Is the a document defining how a call for votes should look like, except for the subject prefix [VOTE]? Thanks, Toby - -- Tobias Schlitt tob...@schlitt.info GPG Key: 0xC462BC14 a passion for php http://schlitt.info/opensource eZ Components are Zeta Components now! http://bit.ly/9S7zbn -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkvxDmoACgkQ5bO3TcRivBSkCwCdExf3mBg8Rf5d7DceHkevmqje Rx8AniLiA2u7XSUbw+6sy5i3N1zkHjka =kzaC -END PGP SIGNATURE- - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[VOTE] Accept Zeta Components into the incubator
. Community = eZ Components was mainly developed by the core team of lately 4 employees of eZ Systems. During the past 5 years, 10 employees contributed actively to the project. In addition, 18 external contributors signed the CLA and actively provided patches or full components to the project. The project maintains a vital open source community, with currently more than 15 people active on the development mailinglist, discussing and contributing. In addition, there is an active IRC channel, which counts between 20 and 40 people and is used for support and technical discussions. We are sure that this community will stay with the project, if it moves to the ASF, and that there is growing potential from the PHP users community. Especially when people realize that the project is no more a product of eZ Systems, but a fully independent OSS project. eZ Systems plans to integrate the components provided by the Zeta project further into their product eZ Publish. Therefore, the company also plans to have their developers contribute further. This includes bug fixes, feature additions and potentially new components. In addition to that, there is a vital community of partners and open source contributors around eZ System's product eZ Publish. These parties already make heavy use of eZ Components and will continue to use it as Zeta Components, since the project provides essential building blocks for eZ Publish development. While some of them already contribute to the project, it is expected, that contributions and participation from this community grow in the future. Beside that, the contributors are willing to represent and evangelize the project at open source events and to attract new contributors. Core Developers === Zeta has four core developers by now, which all have a degree in computer science and are long time members of the open source community around PHP. As there are: Derick Rethans: Derick works on the core and multiple extensions for the PHP language itself. In addition, he is the creator of the widely used Xdebug PHP debugging extension [8]. Sebastian Bergmann: As the creator and maintainer of PHPUnit [9], Sebastian is head of development of this de-facto standard for unit testing in the PHP world. Kore Nordmann: Kore Nordmann maintains several open source projects, for example Arbit [10], a PHP based issue tracking and project management system. Beside that, he regularly contributes to various other projects in the PHP world. Tobias Schlitt: As a long time member of the PEAR project [11], the standard PHP code collection, Tobias has brought experiences in software architecture and PHP development. Beside his work on Zeta, he contributes to various other open source projects and is a maintainer of Planet PHP [12]. Alignment = The Zeta project fits especially into the ASF for its meritocratic development approach and the target of having a very permissive license. There is currently only one component in Zeta interacting with an ASF project: The Search component supports Solr as a backend. However, PHP is a project that is quite close to the ASF and many applications written on basis of Zeta will run in an Apache web server. In addition, some employees of eZ Systems also contribute to other ASF projects. Jerome Renard maintains some custom Apache server modules and contributed bug reports and patches in the past. Paul Borgermanns contributes to Solr and Tika. - --- Known Risks - --- In following, we try to analyze the risks for the Zeta project. Orphaned Products = The Zeta project has been developed for the past 5 years under the name eZ Components. There is a vital and active community around it. While the core development team has been paid for development in the past, they did that also with their heart and soul and will therefore not allow the project of becoming orphan. eZ Systems will continue to use the project in its main product (eZ Publish) and even plans to extend the usage. To realize this, eZ Systems will make its developers contribute to the project. The project is in use by many PHP companies and in open source projects like Arbit. In addition, 2 of the core developers plan to found a company and to build their business model onto this project, among others. Chances that development of Zeta will die away in the future are therefore rare. Inexperience with Open Source = The project exists since 5 years as an open source project and one reason for putting it into the ASF is to keep it this way. All core developers have long time experiences in leading and contributing to various open source projects. eZ Systems is an open source company and its business model is fully built upon OSS. Homogeneous Developers == 3 of the 4 core developers of Zeta reside in Germany, but work for 2 different companies. One of them resides in London, UK. eZ Systems is located in Norway
Re: Zeta proposal - Next steps
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi all, On 05/08/2010 05:45 PM, Bertrand Delacretaz wrote: On Sat, May 8, 2010 at 1:32 PM, Gav... ga...@16degrees.com.au wrote: ...I've shown my support for Christian, we just need to wait for the Incubator PMC chair to approve or not, and he is on his holidays currently I believe IMO the decision is made by a vote of the Incubator PMC members, it's not just the chair's decision. I just started the vote on the incubator private, it's open for 72 hours at least so we should have an answer for Christian by Wednesday morning. As Julien is an ASF member, his Incubator PMC membership is just a formality - Noel as the PMC chair must forward the request to the board when he's back, which should be later this weekend. So I guess we should be ready to vote on the Zeta proposal by Wednesday. In the meantime, Zeta committers who don't have an iCLA on file [1] should send it, that will save time if/when the project is accepted. I don't think there's more that can be done at this point to save time. are there any news in this direction? Regards, Toby - -- Tobias Schlitt tob...@schlitt.info GPG Key: 0xC462BC14 a passion for php http://schlitt.info/opensource eZ Components are Zeta Components now! http://bit.ly/9S7zbn -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkvs8jYACgkQ5bO3TcRivBQ+FwCZARoSfT25s0qROHWwqpQB0Wi1 kNgAn2scWQ+QRHXzTnsJ27sT4Xno2SYh =+zoJ -END PGP SIGNATURE- - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Zeta proposal - Next steps
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, we gathered 3 mentors by our call for mentors here on the list and private contact to Apache members. These are: - - Christian Grobmeier (not ASF member) - - Julien Vermillard (ASF member) - - Craig L Russell (ASF member) Is there a need for more mentors (e.g. a specially experienced one)? If not, what would be the next step? Is it calling for votes here on the list? If yes, who is in charge of this, one of the project members or a mentor? Thanks in advance for your support, regards, Toby - -- Tobias Schlitt tob...@schlitt.info GPG Key: 0xC462BC14 a passion for php http://schlitt.info/opensource eZ Components are Zeta Components now! http://bit.ly/9S7zbn -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkvkJT0ACgkQ5bO3TcRivBTnaACgrUBQHVMHD6ZUNWkGYY/dk4bZ Y24AoKxerLobJH9ZLllsZ22ZvWOMkAuX =0BVF -END PGP SIGNATURE- - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Zeta proposal - Next steps
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Jean-Frederic, On 05/07/2010 05:05 PM, jean-frederic clere wrote: On 05/07/2010 04:35 PM, Tobias Schlitt wrote: we gathered 3 mentors by our call for mentors here on the list and private contact to Apache members. These are: Sorry according to http://incubator.apache.org/incubation/Incubation_Policy.html#Mentor he should be in the Incubator PMC. ah, sorry, I misread this paragraph. I thought only 1 mentor must be a member of the IPMC. Craig is already member of the IPMC and he is mentoring several projects, so he is the wise guy in our mentor team. Julien applied for becoming a member of the IPMC, so we'll need to wait for this to happen. He is also an ASF member. Christian is not an ASF member, but applied also for becoming an IPMC member. So, we need to wait and see now, how the applications of them proceed. Is there anything, we as the proposing project, can do in the meantime? Anything else to prepare? Thanks for your advice, regards, Toby - -- Tobias Schlitt tob...@schlitt.info GPG Key: 0xC462BC14 a passion for php http://schlitt.info/opensource eZ Components are Zeta Components now! http://bit.ly/9S7zbn -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkvkQVUACgkQ5bO3TcRivBTZqgCgrWUhy6Nz+AC6Yd6DAURFegnd WrwAn3YCmDRx5zK1QbVFo/8WEuzu94Vz =sGCu -END PGP SIGNATURE- - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Call for mentors: Zeta Components
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Craig, On 05/02/2010 12:22 AM, Craig L Russell wrote: This project seems to have a lot of interest but a lack of mentors. I'm willing to be a third mentor to help the podling get started, assuming that others can carry the bulk of the mentoring responsibility. good news, thanks! :) I started a list of volunteered members in the proposal and added Christian, Julien and you to it. http://wiki.apache.org/incubator/ZetaComponentsProposal#Volunteered_Mentors Would be cool to get one or two people on board, to relieve some load from you people. Cheers, Toby - -- Tobias Schlitt tob...@schlitt.info GPG Key: 0xC462BC14 a passion for php http://schlitt.info/opensource eZ Components are Zeta Components now! http://bit.ly/9S7zbn -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkvdG4cACgkQ5bO3TcRivBSryACfYYcmWNYojRgjOKi7LKiPpI3p NhIAn0o0eeBU43OedbLM938kTtbO+XH0 =LXGo -END PGP SIGNATURE- - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Call for mentors: Zeta Components
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Julien, On 05/01/2010 02:02 PM, Julien Vermillard wrote: I was contacted by a Zeta components contributor, I'm no experienced mentor, but I'm ASF member. I can help mentoring if needed. that is fantastic news, thanks a lot! :) Hope we can push things further now. Great stuff, regards, Toby - -- Tobias Schlitt tob...@schlitt.info GPG Key: 0xC462BC14 a passion for php http://schlitt.info/opensource eZ Components are Zeta Components now! http://bit.ly/9S7zbn -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkvcjJ4ACgkQ5bO3TcRivBRUKwCfUpuKcGw/2EUY9xiSzJnlcyd/ h40AoKZmHeLmPuEYyTCNZ6UOwntML90D =+bdV -END PGP SIGNATURE- - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Call for mentors: Zeta Components
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Christian, On 04/30/2010 05:12 PM, Christian Grobmeier wrote: However, we are still missing mentors to push this proposal forward. Could anybody please raise his hand for this position? I can assure you, we are really low maintenance. :) I am willing to help here. Unfortunatly I am not on the IPMC - I have sent an e-mail for addition, but no response yet. However, I am PMC and Dev on the Log4PHP project and would like to learn more about Zeta. I am also looking for the chance to stick with the project even after mentoring phase. thanks. It's good to see at least somebody stepping up. :) However, I think we need an ASF member as the primary mentor. Are you a member, yet? Regards, Toby - -- Tobias Schlitt tob...@schlitt.info GPG Key: 0xC462BC14 a passion for php http://schlitt.info/opensource eZ Components are Zeta Components now! http://bit.ly/9S7zbn -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkvbGjYACgkQ5bO3TcRivBTO3gCgu6fHGCunATA+KRxzOPdM+1QO d5IAnjdWDk+mFYlanbaw8ScYtE6TS+Ep =Cep4 -END PGP SIGNATURE- - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Call for mentors: Zeta Components
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi all, there was lots of positive feedback on our proposal to incubate Zeta Components [1]. We sorted out some smaller issues and I think the proposal is pretty complete now. Find the current state here: http://wiki.apache.org/incubator/ZetaComponentsProposal However, we are still missing mentors to push this proposal forward. Could anybody please raise his hand for this position? I can assure you, we are really low maintenance. :) In addition, I want to kindly ask the IPMC to sponsor our project. Thanks in advance, cheers, Toby - -- Tobias Schlitt tob...@schlitt.info GPG Key: 0xC462BC14 a passion for php http://schlitt.info/opensource eZ Components are Zeta Components now! http://bit.ly/9S7zbn -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkvUo0QACgkQ5bO3TcRivBTEuwCgoF3L3GRYAzsScK4IABZq1BYi nXAAn30Cohx7gkFsg1TOvQPGdVhmuwZe =7DGO -END PGP SIGNATURE- - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Zeta Components - Further comments?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Leo, On 04/23/2010 12:40 AM, Leo Simons wrote: On 4/22/10 10:21 AM, Tobias Schlitt wrote: I updated the proposal to reflect the objections regarding the infrastructure. Our questions regarding the import of our SVN history has been cleared. Are there further comments, suggestions, objections? Very nicely written proposal, well done! Looks like an interesting project to bring into the apache fold - some more PHP sounds like a good idea :) thanks, that sounds very motivating. :) It looks like you now need to sign up some mentors after which your proposal would be ready for a vote. I actually expected that some mentors would volunteer during the discussion here. The incubator docs state that Mentors are chosen by the Sponsor. I assumed that the Incubator PMC would be our sponsor. Is there a certain process we need to trigger, like asking the Incubator PMC for sponsoring or asking for mentors on the list? Regards, Toby - -- Tobias Schlitt tob...@schlitt.info GPG Key: 0xC462BC14 a passion for php http://schlitt.info/opensource Member of the eZ Components project http://components.ez.no -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkvRdmEACgkQ5bO3TcRivBS4YACdEj4qqcufFpOOC8TkaL+zpRul z68AoLLWf9wQUPnHg0ufNJF5lpjq6Q54 =i/mO -END PGP SIGNATURE- - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Zeta Components - Further comments?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi all, I updated the proposal to reflect the objections regarding the infrastructure. Our questions regarding the import of our SVN history has been cleared. Are there further comments, suggestions, objections? Thanks a lot for your feedback, regards, Toby - -- Tobias Schlitt tob...@schlitt.info GPG Key: 0xC462BC14 a passion for php http://schlitt.info/opensource Member of the eZ Components project http://components.ez.no -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkvQFTEACgkQ5bO3TcRivBRi1gCcC1ICCxETmbbZEDDPPYR0EvPL B8QAmgM4ahqOzSL5Z4j1djauwMzZniXw =S254 -END PGP SIGNATURE- - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Zeta Components - Further comments?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Christian, On 04/22/2010 12:30 PM, Christian Grobmeier wrote: I updated the proposal to reflect the objections regarding the infrastructure. Our questions regarding the import of our SVN history has been cleared. Are there further comments, suggestions, objections? I read it again and like the update. Only: Required Resources The current project infrastructure is hosted by eZ Systems, but this should change. The project can be fully hosted on its own servers, sponsored by some of the core contributors. However, for reliability reasons, there are some services which we would want to have hosted by the ASF I find a little confusing meanwhile - i think its outdated but are there any other services we need to speak off? If SVN, Hudson, Jira and the Website is hosted on ASF servers then all critical services are there and the paragraph can be rephrased. I know you plan to run an own CI server - but is there any other stuff? Thanks for the hint. I rephrased this section to clear it up. We require inside ASF: - - SVN - - mailinglists - - issue tracker - - website The CI stuff is secondary to get started, since we will also have external CI. We can take care of that as soon as we are incubated, I think. Regards, Toby - -- Tobias Schlitt tob...@schlitt.info GPG Key: 0xC462BC14 a passion for php http://schlitt.info/opensource Member of the eZ Components project http://components.ez.no -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkvQOScACgkQ5bO3TcRivBSelwCeOkq4q/OKtJlyK6mo5UEkkjS3 T2IAn0Avp5m9KE4lcHW6zReT3BG0ucwu =BUUN -END PGP SIGNATURE- - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Zeta Components - Further comments?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, On 04/22/2010 02:43 PM, Gav... wrote: snip The CI stuff is secondary to get started, since we will also have external CI. We can take care of that as soon as we are incubated, I think. Incubation periods vary, it could be 3 months, 6, a year, two, no one knows for sure. Certainly not a blocker for starting incubation though. Once incubation has started, you can detail all your CI needs to the builds@ list and we'll see what can be done, or you can detail them now and I can give you an idea. I think we should do that on the builds@ list later, since I'm not sure how to exactly do CI with our stuff in ASF environment, yet. We have a custom test suite, based on PHPUnit, and require some PHP extensions to be available for testing certain features and other stuff. Thanks for the offer. :) Cheers, Toby - -- Tobias Schlitt tob...@schlitt.info GPG Key: 0xC462BC14 a passion for php http://schlitt.info/opensource Member of the eZ Components project http://components.ez.no -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkvQXMkACgkQ5bO3TcRivBRlWACgvTV1Md88I5/tao8joeS7wO7h RRwAn2+pZdjiUA/UaQaCirPNeP6xqJbL =n5KS -END PGP SIGNATURE- - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Zeta Components
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Justin, On 04/21/2010 08:26 AM, Justin Erenkrantz wrote: On Mon, Apr 19, 2010 at 6:52 AM, Tobias Schlitt tob...@schlitt.info wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi all, please find below our proposal for Zeta Components. The proposal is also available in the wiki: http://wiki.apache.org/incubator/ZetaComponentsProposal Sorry that I don't have time to review the proposal yet, but I did see: http://css.dzone.com/articles/ez-components-php-library It might be good to reach out to the author to clarify that you haven't joined Apache just yet. =) For reference, the publicity/branding rules for podlings are at: http://incubator.apache.org/guides/branding.html sorry, if some people misunderstood our situation. I will take care about that. Regards, Toby - -- Tobias Schlitt tob...@schlitt.info GPG Key: 0xC462BC14 a passion for php http://schlitt.info/opensource Member of the eZ Components project http://components.ez.no -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkvOqvkACgkQ5bO3TcRivBQeawCfcFAzy0o8zoPSuBj734uF6WHy vrwAnjtbFucrpulHxnhjHTpFIC4+eora =Z0n2 -END PGP SIGNATURE- - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Zeta Components (issue tracker)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi all, we talked a bit about the issue tracker stuff and came to the conclusion that we'd go with Jira. The point of having issues central in ASF infra is quite striking and we agree here, that we don't want issues to be tracked on an external server. For the CI we will mostly likely want to setup Hudson inside ASF and will most probably setup Arbit for it on an external server. More CI cannot hurt, can it? ;) I updated our proposal in the wiki accordingly: http://wiki.apache.org/incubator/ZetaComponentsProposal I read on the infra pages, that our website is required to be generated static HTML content. This is fine for us, since the desired systems does basically do this. But I wounder how really dynamic stuff is handeled here? E.g. having a blog is possible with static HTML, but what about comment functionality? Regards, Toby - -- Tobias Schlitt tob...@schlitt.info GPG Key: 0xC462BC14 a passion for php http://schlitt.info/opensource Member of the eZ Components project http://components.ez.no -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkvO1ZEACgkQ5bO3TcRivBThIQCgrdkAjAbxxsYS3vEKCrSHcnO1 sBcAn3G26zmBZw9HhJodn6c3k5R2klJO =fPJv -END PGP SIGNATURE- - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Zeta Components (issue tracker)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, On 04/21/2010 12:43 PM, Daniel S. Haischt wrote: actually blogs are done using apache roller as you may figure from the below URL. On Wed, Apr 21, 2010 at 12:40 PM, Bertrand Delacretaz bdelacre...@apache.org wrote: On Wed, Apr 21, 2010 at 12:38 PM, Tobias Schlitt tob...@schlitt.info wrote: ...I read on the infra pages, that our website is required to be generated static HTML content. This is fine for us, since the desired systems does basically do this. But I wounder how really dynamic stuff is handeled here? E.g. having a blog is possible with static HTML, but what about comment functionality?... Projects can have blogs with comments under http://blogs.apache.org/ For other dynamic stuff, projects can use zones: http://www.apache.org/dev/solaris-zones.html ok, then we need to deal with this in some way. Details can be figured out later, I guess. ;) Regards, Toby - -- Tobias Schlitt tob...@schlitt.info GPG Key: 0xC462BC14 a passion for php http://schlitt.info/opensource Member of the eZ Components project http://components.ez.no -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkvO1ycACgkQ5bO3TcRivBRCdgCfVxE4i84ROhYp7Mirk3K0C+nS n0AAoLGQOsWB40NHNkvGpjEV65kJXC2b =blV+ -END PGP SIGNATURE- - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Zeta Components
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Bertrand, On 04/20/2010 01:16 PM, Bertrand Delacretaz wrote: On Tue, Apr 20, 2010 at 1:07 PM, Erik Abele erikab...@apache.org wrote: On Apr 19, 2010, at 15:52, Tobias Schlitt wrote: http://wiki.apache.org/incubator/ZetaComponentsProposal +1! Yeah, I know it's long but any other opinions? Just finished reading it, big +1, cool to see more php stuff at Apache. Being mostly clueless about PHP I'm curious about how such modules would be released. Does the usual model of a downloadable archive that includes NOTICE/LICENSE files apply, or would Zeta components mostly be released through a module distribution server like http://pear.php.net/ ? Our current release model involves component based releases whenever a component has something to release. These releases by now happen through a PEAR channel server. In addition to that, we released a full package release every 6 months as a downloadable archive. It needs to be discussed, if this release model satisfies Apache release processes. Every component package contains its own documentation and also some of the typical meta info files, in our case CREDITS, DESCRIPION and ChangeLog. That'd mean in the future we'd also package the Apache meta data files with the components. As all components are included in a full package, these files would be included there as well. Regards, Toby - -- Tobias Schlitt tob...@schlitt.info GPG Key: 0xC462BC14 a passion for php http://schlitt.info/opensource Member of the eZ Components project http://components.ez.no -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkvNj18ACgkQ5bO3TcRivBRCFwCfVLp9VPCmSWRN2ditG6gMLhvK m0EAoK6J+i0E8q8G4ujAwNzD3CVVYt6x =MWyn -END PGP SIGNATURE- - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Zeta Components
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Christian, On 04/20/2010 01:14 PM, Christian Grobmeier wrote: An excellent well thought out, complete proposal, with none of the usual copying of previous proposals with a bit of tweaking. Just one note: Required Resources The current project infrastructure is hosted by eZ Systems, but this should change. The project can be fully hosted on its own servers, sponsored by some of the core contributors. However, for reliability reasons, there are some services which we would want to have hosted by the ASF. I think the complete project should be hosted on apache servers we would be happy to host our infrastructure on Apache servers. Especially for SVN and the mailinglists. We have kind of an issue in direction of the issue tracking software. None of the 4 core developers is really happy with Jira or Bugzilla. Our current idea is to use Arbit [1], an issue tracking and project management solution based on Zeta. This tool also includes facilities for continuous integration, which is quite vital for us. Arbit is also build on basis of CouchDB, which is an Apache project. Is it possible to use Arbit instead of the standard issue trackers provided by Apache? Regards, Toby [1] http://arbitracker.org - -- Tobias Schlitt tob...@schlitt.info GPG Key: 0xC462BC14 a passion for php http://schlitt.info/opensource Member of the eZ Components project http://components.ez.no -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkvNkGAACgkQ5bO3TcRivBR0VgCdGckfm8CC00ii1UYc0rgpxBqs mSsAn3Kl3L88tYjNjjBHFnGtHgAunKd+ =T9aP -END PGP SIGNATURE- - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Zeta Components
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, On 04/20/2010 01:34 PM, Christian Grobmeier wrote: I think the complete project should be hosted on apache servers Is it possible to use Arbit instead of the standard issue trackers provided by Apache? Currently only bugzilla and jira is used in apache world. The use of Arbit needs to be discussed with the infra team. I am not sure if this will happen so easily For integration, there are several continuus integration server around. Its cruise control, buildbot (Log4PHP uses buildbot for example) and i think Gump around. Other might exist but I am not sure. Again, if someelse is necessary this is a dicussion with infra team would it be problematic if issue tracking / CI would be hosted on a dedicated server outside Apache? Kore Nordmann and me would happily sponsor this server. The reasons we want to use Arbit instead of the other solutions is simple: 1. Since Arbit is driven by some of the core contributors of Zeta, we can patch new features into it right away, as we need them. 2. Arbit is built upon Zeta Components and eating our own dog food is just fair. 3. We have experience with other CI solutions (CruiseControl) and it's always been a hassle to fully integrate the metrics we wanted to have. 4. CI of Zeta consumes quite some ressources. 1-2 GB of RAM consumption is not seldom. A dedicated server for this purpose would ensure we do not disturb other services. Regards, Toby - -- Tobias Schlitt tob...@schlitt.info GPG Key: 0xC462BC14 a passion for php http://schlitt.info/opensource Member of the eZ Components project http://components.ez.no -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkvNn2MACgkQ5bO3TcRivBTviACgl7IGNA6EfJjbn1G0PfDQTyf8 1UgAmwXVyShx6rgBi/KLYh+QJRnYAKem =0fWA -END PGP SIGNATURE- - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Zeta Components
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 04/20/2010 02:48 PM, Christian Grobmeier wrote: would it be problematic if issue tracking / CI would be hosted on a dedicated server outside Apache? Kore Nordmann and me would happily sponsor this server. I am not a decision maker, but I would think that CI is no problem. I mean, it uses code from Apache SVN and there is no documentation which is cirtical for the project on it. If it breaks or gets lost or developers leave the project there is nearly no harm done because one can set up another CI server. In Log4PHP we had a cruisecontrol server from one of the developers until we moved to buildbot. I think we could have stayed there. On issues i think is more problematic. This is information critical to a project and I believe it needs to be stored somewhere on Apache servers. But there is always the chance to speak with infra if we are able to install Arbit there. Is this a incubation blocker for Zeta? If not we should proceed with this process and then ask infra, otherwise we need to clarify now. I don't think this should be an incubation blocker, although some of us have really strong feelings against Jira and even stronger against Bugzilla. Therefore, if we can sort out this stuff before, it's good. :) Regards, Toby - -- Tobias Schlitt tob...@schlitt.info GPG Key: 0xC462BC14 a passion for php http://schlitt.info/opensource Member of the eZ Components project http://components.ez.no -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkvNo4YACgkQ5bO3TcRivBTgFACfQAViNCh5iP/0Flf266Emr2Fb 9q4An1VY2EjuesDwZH/uT1BVinMvL0B9 =r/8F -END PGP SIGNATURE- - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[PROPOSAL] Zeta Components
, if it moves to the ASF, and that there is growing potential from the PHP users community. Especially when people realize that the project is no more a product of eZ Systems, but a fully independent OSS project. eZ Systems plans to integrate the components provided by the Zeta project further into their product eZ Publish. Therefore, the company also plans to have their developers contribute further. This includes bug fixes, feature additions and potentially new components. In addition to that, there is a vital community of partners and open source contributors around eZ System's product eZ Publish. These parties already make heavy use of eZ Components and will continue to use it as Zeta Components, since the project provides essential building blocks for eZ Publish development. While some of them already contribute to the project, it is expected, that contributions and participation from this community grow in the future. Beside that, the contributors are willing to represent and evangelize the project at open source events and to attract new contributors. Core Developers === Zeta has four core developers by now, which all have a degree in computer science and are long time members of the open source community around PHP. As there are: Derick Rethans Derick works on the core and multiple extensions for the PHP language itself. In addition, he is the creator of the widely used Xdebug PHP debugging extension [12]_. Sebastian Bergmann As the creator and maintainer of PHPUnit [13]_, Sebastian is head of development of this de-facto standard for unit testing in the PHP world. Kore Nordmann Kore Nordmann maintains several open source projects, for example Arbit [14]_, a PHP based issue tracking and project management system. Beside that, he regularly contributes to various other projects in the PHP world. Tobias Schlitt As a long time member of the PEAR project [15]_, the standard PHP code collection, Tobias has brought experiences in software architecture and PHP development. Beside his work on Zeta, he contributes to various other open source projects and is a maintainer of Planet PHP [16]_. Alignment = The Zeta project fits especially into the ASF for its meritocratic development approach and the target of having a very permissive license. There is currently only one component in Zeta interacting with an ASF project: The Search component supports Solr as a backend. However, PHP is a project that is quite close to the ASF and many applications written on basis of Zeta will run in an Apache web server. In addition, some employees of eZ Systems also contribute to other ASF projects. Jerome Renard maintains some custom Apache server modules and contributed bug reports and patches in the past. Paul Borgermanns contributes to Solr and Tinka. - --- Known Risks - --- In following, we try to analyze the risks for the Zeta project. Orphaned Products = The Zeta project has been developed for the past 5 years under the name eZ Components. There is a vital and active community around it. While the core development team has been paid for development in the past, they did that also with their heart and soul and will therefore not allow the project of becoming orphan. eZ Systems will continue to use the project in its main product (eZ Publish) and even plans to extend the usage. To realize this, eZ Systems will make its developers contribute to the project. The project is in use by many PHP companies and in open source projects like Arbit. In addition, 2 of the core developers plan to found a company and to build their business model onto this project, among others. Chances that development of Zeta will die away in the future are therefore rare. Inexperience with Open Source = The project exists since 5 years as an open source project and one reason for putting it into the ASF is to keep it this way. All core developers have long time experiences in leading and contributing to various open source projects. eZ Systems is an open source company and its business model is fully built upon OSS. Homogeneous Developers == 3 of the 4 core developers of Zeta reside in Germany, but work for 2 different companies. One of them resides in London, UK. eZ Systems is located in Norway and has a vital community of partners and contributors among Europe and even world wide. All parties involved in the project are looking forward to new team members from all over the world. Reliance on Salaried Developers === The four core contributors were paid for working on the project in the past 5 years. However, their intention to work on the project on a not salaried basis is clear and strong, as can be seen by the efforts put into the project becoming independent. eZ Systems might pay developers for working on Zeta in the future. Two of the core
