Re: [call for review] Keeping the eZ Publish Community in the loop
On Tue, May 15, 2012 at 12:52 PM, Derick Rethans der...@apache.org wrote: On Tue, 15 May 2012, Christian Grobmeier wrote: In addition you guys need to urgently make up new mailinglists - Infra might close zeta-dev@incubator.apache.org pretty soon. There is a mailinglist already: Great :-) Thanks for the link! z...@lists.xdebug.org You can subscribe to it by sending a mail to ecar...@lists.xdebug.org with subject subscribe zeta. cheers, Derick -- http://derickrethans.nl | http://xdebug.org Like Xdebug? Consider a donation: http://xdebug.org/donate.php twitter: @derickr and @xdebug -- http://www.grobmeier.de https://www.timeandbill.de
Re: Migrating Zeta Componetns to Github
Sorry, no news arrived to my inbox. Can you ping trademarks again? Please put me on CC, if you can On Fri, May 11, 2012 at 11:05 PM, Benjamin Eberlei kont...@beberlei.de wrote: @Christian So are there any news? On Wed, Apr 25, 2012 at 2:00 AM, Benjamin Eberlei kont...@beberlei.dewrote: Hello everyone, i have just completed the migration of the Apache SVN to Github organization: Code is still pushed at the moment, these are the done tasks: https://github.com/zetacomponents * Each component is split into its own repository * Author Information has been updated on frequent committers i have found the email of (or could asked for). * composer.json was added to every project. No dependencies were defined on other components (even though could be done through DEPS) - because the Base version was never specified and such the information is incomplete anyways. Releases in the future should go and specify the dependencies of packages more explicitly. * All tags have been generated from the commit messages. * MVCTools Migration didnt work, I have to try this again. * Document has some problem with GC and is very large repo, i have to cleanup or remigrate so i didnt push to github yet. However code is not yet free for changes, we have some problems to tackle: * Do we need to adjust the headers? If yes, we should do this now using a mass-edit. Do we have to clear this with Apache legal? * Unit-tests have still to be fixed, we need a generic approach for all components for that. * I fixed the Archive component as an example: https://github.com/zetacomponents/Archive/commit/541b1faca6d63c441bead83fe8ca5d9e174afe53 Then just composer install --dev phpunit from the root of the Archive component. * All packages have to be put on packagist.org so can be used with Composer. greetings, Benjamin On Fri, Apr 20, 2012 at 1:35 PM, Benjamin Eberlei kont...@beberlei.dewrote: Repost into its own topic for better seperation: 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 -- http://www.grobmeier.de https://www.timeandbill.de
Re: Incubator PMC/Board report for May 2012 ([ppmc])
i have added a section already - please review cheers christian On Mon, Apr 30, 2012 at 7:37 PM, Marvin no-re...@apache.org wrote: Dear podling, This email was sent by an automated system on behalf of the Apache Incubator PMC. It is an initial reminder to give you plenty of time to prepare your quarterly board report. The board meeting is scheduled for Wed, 16 May 2012, 10:00:00 PST. The report for your podling will form a part of the Incubator PMC report. The Incubator PMC requires your report to be submitted 2 weeks before the board meeting, to allow sufficient time for review and submission (Wed, May 2nd). Please submit your report with sufficient time to allow the incubator PMC, and subsequently board members to review and digest. Again, the very latest you should submit your report is 2 weeks prior to the board meeting. Thanks, The Apache Incubator PMC Submitting your Report -- Your report should contain the following: * Your project name * A brief description of your project, which assumes no knowledge of the project or necessarily of its field * A list of the three most important issues to address in the move towards graduation. * Any issues that the Incubator PMC or ASF Board might wish/need to be aware of * How has the community developed since the last report * How has the project developed since the last report. This should be appended to the Incubator Wiki page at: http://wiki.apache.org/incubator/May2012 Note: This manually populated. You may need to wait a little before this page is created from a template. Mentors --- Mentors should review reports for their project(s) and sign them off on the Incubator wiki page. Signing off reports shows that you are following the project - projects that are not signed may raise alarms for the Incubator PMC. Incubator PMC -- http://www.grobmeier.de https://www.timeandbill.de
Re: [call for review] Keeping the eZ Publish Community in the loop
On Thu, Apr 26, 2012 at 9:21 PM, Benjamin Eberlei kont...@beberlei.de wrote: The naming is completely undecided yet, we have contacted apache trademarks, since we don't know how to proceed. I can confirm this has made its way into some private mailinglists and people are discussing it already. Cheers Also i agree with julien, the inactivity was the major reason to retire from ASF, since we couldnt follow procedure with quarterly reports anymore due to lack of time and didnt manage to get a first release under Apache flag out. The seperation of components into their own repositories are also done to seperate the maintained from the unmaintained ones more easily :-) On Thu, Apr 26, 2012 at 1:56 PM, Julien Vermillard jvermill...@gmail.comwrote: Hi, Even if I think it's a good idea to keep the community in the loop I would like to remeber two points : - the zeta podling retirement vote was start due to lack of progress - if you want to use the Apache/ASF word you need to contact the Apache PR for that Julien On Thu, Apr 26, 2012 at 11:35 AM, Nicolas Pastorino n...@ez.no wrote: Dear everyone, I thought it would be wise to keep the eZ Publish Community in the loop, since they are likely to be the largest share of AZC users today. Here is a small blog-post, on which I would love to have your input : https://docs.google.com/a/ez.no/document/d/1SLuBI6HQqX_PJnswCOaV6MyW2AbOd0-1wTDwhHIf3f4/edit (anyone should be able to edit it, or make remarks through comments). I hope this fits you well and I am looking forward to your feedback ! -- Nicolas -- http://www.grobmeier.de https://www.timeandbill.de
Re: [call for review] Keeping the eZ Publish Community in the loop
On Thu, Apr 26, 2012 at 9:31 PM, Benjamin Eberlei kont...@beberlei.de wrote: @Christian thats good to know, i don't get mails back from the list i sent the naming question too. Its probably summed up and sent back to this list when final decision is made? If not, Julien and I are both subscribed to the relevant lists and we will come back to you with information. But actually I expect you get a direct response from the Trademarks Officer. Cheers Christian On Thu, Apr 26, 2012 at 9:28 PM, Christian Grobmeier grobme...@gmail.comwrote: On Thu, Apr 26, 2012 at 9:21 PM, Benjamin Eberlei kont...@beberlei.de wrote: The naming is completely undecided yet, we have contacted apache trademarks, since we don't know how to proceed. I can confirm this has made its way into some private mailinglists and people are discussing it already. Cheers Also i agree with julien, the inactivity was the major reason to retire from ASF, since we couldnt follow procedure with quarterly reports anymore due to lack of time and didnt manage to get a first release under Apache flag out. The seperation of components into their own repositories are also done to seperate the maintained from the unmaintained ones more easily :-) On Thu, Apr 26, 2012 at 1:56 PM, Julien Vermillard jvermill...@gmail.comwrote: Hi, Even if I think it's a good idea to keep the community in the loop I would like to remeber two points : - the zeta podling retirement vote was start due to lack of progress - if you want to use the Apache/ASF word you need to contact the Apache PR for that Julien On Thu, Apr 26, 2012 at 11:35 AM, Nicolas Pastorino n...@ez.no wrote: Dear everyone, I thought it would be wise to keep the eZ Publish Community in the loop, since they are likely to be the largest share of AZC users today. Here is a small blog-post, on which I would love to have your input : https://docs.google.com/a/ez.no/document/d/1SLuBI6HQqX_PJnswCOaV6MyW2AbOd0-1wTDwhHIf3f4/edit (anyone should be able to edit it, or make remarks through comments). I hope this fits you well and I am looking forward to your feedback ! -- Nicolas -- http://www.grobmeier.de https://www.timeandbill.de -- http://www.grobmeier.de https://www.timeandbill.de
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: Migrating Zeta Componetns to Github
On Fri, Apr 20, 2012 at 2:58 PM, Patrick ALLAERT patrickalla...@php.net wrote: 2012/4/20 Benjamin Eberlei kont...@beberlei.de: Adding to this: I could use some help of course, so anyone also feeling to volunteer can do so. My idea was to create a repository with a bash/php script collection that does the migration and then collaborate on that until we have the final version to use. Starting point is here: https://github.com/zetacomponents/svn-git-migration I'd like to help here since I have a bit of this experience having moved eZ Publish to github. I already shared the script using a PR: https://github.com/zetacomponents/svn-git-migration/pull/1 This could help too: http://help.github.com/import-from-subversion/ cheers I also have a local users.txt containing all the information of users having committed code to ezc/zeta but since it contains e-mail addresses, I don't really know if I should push it on github and/or send it here as attachment or even using a private gist. Feel free to have suggestion. Cheers, Patrick -- 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 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
[zeta-dev] step down as a mentor
Hello guys, I am afraid that i do not find enough time anymore to actively mentor this project :-( In addition, I have so much exhausting discussion at the ASF recently, that even when I would have the time, I would not have the energy to mentor. I am aware that there are only two other mentors on this project and I will take this to general@. I will continue to stay on this list, but do not force myself to guide explicit or care on the reporting schedule. Hope you understand! Would love to see a short ACK from the other mentors to see that this project is being cared of. Cheers Christian -- http://www.grobmeier.de https://www.timeandbill.de
[zeta-dev] Zeta Components looking for a new mentor
Hello, as I intend to step down as a mentor from Zeta Components, there are only two mentors left. So this podling needs one more. Who is willing to help out? Cheers Christian -- http://www.grobmeier.de https://www.timeandbill.de
[zeta-dev] Fwd: Change in Due Dates for Board reports
FYI Can we please prepare a report for this date next month? -- Forwarded message -- From: Noel J. Bergman n...@devtech.com Date: Wed, Nov 16, 2011 at 9:47 PM Subject: Change in Due Dates for Board reports To: gene...@incubator.apache.org PLEASE NOTE! From the ASF Board: For now on, all reports to the board for review/inclusion at the board meetings will now be due 1 WEEK before the meeting. Reports submitted late will be declined and you'll need to resubmit the next month. This means that Incubator reports really need to be finished by the end of the FIRST week of the month. --- Noel - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- http://www.grobmeier.de
Re: [zeta-dev] The Piwi Framework
On Fri, Nov 4, 2011 at 11:35 AM, Fabrice PICCINALI f.piccin...@fazae.com wrote: And what about pear ? pear install zeta It is well-know, easy to use and you can have your custom depot. I always have problems with pear and would have no problem if it would go over Styx - so sooner, so better. On 04/11/2011 11:02, Christian Grobmeier wrote: On Fri, Nov 4, 2011 at 10:33 AM, Henri Bergiushenri.berg...@iki.fi wrote: On Thu, Nov 3, 2011 at 3:48 PM, Christian Grobmeiergrobme...@gmail.com wrote: But it seems, there is less interest. Don't know whats wrong, but it seems the PHP world is overloaded with frameworks. It seems, even a high quality framework as Zeta does suffer from this fact. In general, PHP has too many frameworks, and too few reusable libraries. I think for AZC it would be better to position itself as a managed collection of high-quality libraries than to try and position as a framework. After all, Zeta components can already be used outside of Zeta-managed framework code (for example, both Midgard MVC and Symfony2 have integrations with the Workflows component). +1 A similar project is commons.apache.org. It works very well. Which brings me to another point I wanted to take up. How about packaging and distributing AZC through the new Composer system? That would make the Zeta components quite accessible and easy to depend on: http://bergie.iki.fi/blog/composer_solves_the_php_code-sharing_problem/ Sounds very interesting. Will follow this project Cheers Christian Christian /Henri -- Henri Bergius Motorcycle Adventures and Free Software http://bergie.iki.fi/ Jabber: henri.berg...@gmail.com Microblogs: @bergie -- http://www.grobmeier.de
[zeta-dev] The Piwi Framework
Hello all, we, the maintainers of the Piwi Framework are currently discussing if we move to the ASF. http://code.google.com/a/apache-extras.org/p/piwi/?redir=1 As you know, I am for quite a while working in several projects of the ASF, including the incubator. For me it makes perfect sense to move therefore. In addition we have already dependencies to Zeta and would like to stick more to it. For example, Piwi has a few Dependency Injection classes we could move to Zeta. One of the problems we currently are facing is community. Piwi has only a small community, users know each one face to face. There are many strong frameworks out there, like the Zend MVC. This might be a problem Zeta Components is facing too. With moving Piwi Framework to the ASF and making it a main consumer and contributor to Zeta Components both projects might benefit. Anyway, to make this happen we need help. We are only two guys and therefore we are looking for other Apache Committers who are interested in stepping up as initial committers, mentors, champion. Please shout, if you are interested or let me know what you think abou it Cheers, Christian
Re: [zeta-dev] Incubator PMC/Board report for August 2011 (zeta-dev@incubator.apache.org)
On Fri, Aug 5, 2011 at 1:40 PM, Julien Vermillard jvermill...@gmail.com wrote: I think we should blame Holidays :) He he, month of August ... ;) August is already autumn in germany :-( No holiday feeling at my side Sir yes Sir ! ;) The wiki has been updated if there is anything incorrect/missing/unclear/whatever feel free to ping me. Have a nice day :) Excellent thanks, just signed it. I will restart the discussion on open podling status items next month, when people are back Cheers
Re: [zeta-dev] Incubator PMC/Board report for August 2011 (zeta-dev@incubator.apache.org)
Hello guys, in addition to this report, we should discuss if there are some other status items we can check off: http://incubator.apache.org/projects/zetacomponents.html Who volunteers to write the report this time? Cheers Christian On Mon, Aug 1, 2011 at 4:00 PM, no-re...@apache.org wrote: Dear Zeta Components Developers, This email was sent by an automated system on behalf of the Apache Incubator PMC. It is an initial reminder to give you plenty of time to prepare your quarterly board report. The board meeting is scheduled for Wed, 17 August 2011, 10 am Pacific. The report for your podling will form a part of the Incubator PMC report. The Incubator PMC requires your report to be submitted one week before the board meeting, to allow sufficient time for review. Please submit your report with sufficient time to allow the incubator PMC, and subsequently board members to review and digest. Again, the very latest you should submit your report is one week prior to the board meeting. Thanks, The Apache Incubator PMC Submitting your Report -- Your report should contain the following: * Your project name * A brief description of your project, which assumes no knowledge of the project or necessarily of its field * A list of the three most important issues to address in the move towards graduation. * Any issues that the Incubator PMC or ASF Board might wish/need to be aware of * How has the community developed since the last report * How has the project developed since the last report. This should be appended to the Incubator Wiki page at: http://wiki.apache.org/incubator/August2011 Note: This manually populated. You may need to wait a little before this page is created from a template. Mentors --- Mentors should review reports for their project(s) and sign them off on the Incubator wiki page. Signing off reports shows that you are following the project - projects that are not signed may raise alarms for the Incubator PMC. Incubator PMC -- http://www.grobmeier.de
[zeta-dev] Reporting time
Hello all, who will do the report this month? Its due in a few days (please mind poor mentors need a little time to review and sign off) http://wiki.apache.org/incubator/May2011 There was some cool progress on the project recently, guess this report will be fun :-) Cheers
Re: [zeta-dev] Reporting time
On Wed, May 4, 2011 at 9:19 AM, Tobias Schlitt tob...@schlitt.info wrote: Hi Jerome, On 05/04/2011 09:16 AM, Jerome Renard wrote: On Wed, May 4, 2011 at 8:20 AM, Christian Grobmeier grobme...@gmail.com wrote: who will do the report this month? Its due in a few days (please mind poor mentors need a little time to review and sign off) http://wiki.apache.org/incubator/May2011 I just updated the page, is it enough or do you need (much) more ? looks fine for me. Yap, cool thanks. I will sign it straigthaway Cheers Cheers, Toby -- Tobias Schlitt http://schlitt.info GPG Key: 0xC462BC14 Want to hire me? Need quality assurance? http://qafoo.com eZ Components are Zeta Components now! http://bit.ly/9S7zbn -- http://www.grobmeier.de
Re: [zeta-dev] License Headers
Sebastian, Who are you? Could you please have the decency of posting using a realname on this mailinglist. Thanks! Gavin is a well known and respected member of the ASF. He has around at various places and helps a lot especially on infra topics. He established the pear channel for log4php and zeta. And helped incubating log4php, creating the buildbot and much more. This page is pretty interesting if you are looking for the apache background of somebody: http://people.apache.org/committer-index.html Of course this would have not helped you now, but I thought it might be interesting anyway. Cheers
[zeta-dev] Fwd: pear channels for releases
Just in case you didn't get it (or somebody not on the committers list is interested): -- Forwarded message -- From: Gav... ga...@16degrees.com.au Date: Fri, Apr 15, 2011 at 10:07 AM Subject: pear channels for releases To: committ...@apache.org Hi All, http://pear.apache.org Those projects that can, are welcome to release PEAR packages above as part of their release process. See the site for more details. Gav... -- http://www.grobmeier.de
Re: [zeta-dev] Migration from Make to Ant
Anyway it's ASF here, let's look for consensus :) and here are my 2 cents... have used ant for long time and like it very much. Phing by the way is a php specific ant version. For log4php we have used maven with success. With its multimodules it might be a good choice for zeta also. However, I don't think make is a good choice and definitely prefer ant. I mean...make! Its so 90ties! ;-) I guess its also possible to have both build mechanisms in place? At least for a while, and then one can see how it works out. Cheers
Re: [zeta-dev] PHP based build system : Phing VS Pake
- is not XML based (Derick will appreciate that :P) probably the only one ;-) I will try to give Pake a try as soon as possible. But if one of you already has experience with Phing or Pake I would be happy to get your feedback about these tools :) I have no experience and no preference with Pake and Phing, but I could understand Phing very quickly (no surprise, as a ant user) and had some trouble to get into pake. I am still unsure on some points and could not use it straight away. You'll probably need to make a good documentation on Pake otherwise I can imagine that users who want to join the project might have some trouble. I don't see a benefit compared to the actual makefile in readability. If you say, Pake is easier - its just in the eye of the observer. this is the auto flagellation part I plead guilty for imposing Ant, the reason is that I have been using it for a couple of years already and I thought it would solve problems we got in the Makefile. But I was wrong. this was the auto flagellation part Naaa, Ant is not such bad! Trying it out was a logical consequence. It just didn't fit
Re: [zeta-dev] PHP based build system : Phing VS Pake
- is not XML based (Derick will appreciate that :P)
probably the only one ;-)
Not sure if this is a joke, but xml simply has to die (TM).
No joke. And XML has some good benefits. I don't want it to die.
Probably I am oldschool.
Not a good doc by any stretch, but to hit the ground running:
pake_desc( 'docs for the next registered task' );
pake_task( 'init-me' ); // registers task init-me
pake_desc( 'Builds the extension' );
pake_task( 'build-me', 'init-me' );
function run_init_me($task, $args=array(), $opts=array()){ echo 'hello'; }
Thanks, so far I understood - similar code can be found in the docs.
Still I cannot see why this is better than XML. But I believe its a
matter of view and taste. Maybe - if Zeta uses Pake - I will learn
more and use it myself.
Cheers
Christian
Re: [zeta-dev] Welcome: Benjamin and Jerome
Welcome guys and a lots of fun working on this great project! Cheers! On Fri, Apr 1, 2011 at 7:49 PM, Tobias Schlitt tob...@schlitt.info wrote: Hi, I'd like to officially welcome Jerome (jeromer) and Benjamin (beberlei) as Apache Zeta Components committers. We hope to increase the development team of the project further in future, in order to give it a stable basis to become a top level Apache project somewhen. Cheers, Toby -- Tobias Schlitt http://schlitt.info GPG Key: 0xC462BC14 Want to hire me? Need quality assurance? http://qafoo.com eZ Components are Zeta Components now! http://bit.ly/9S7zbn -- http://www.grobmeier.de
[zeta-dev] Re: New group in Review Board
Hello, I think the infra group is the best place to ask Cheers and have a good one too Christian On Wed, Mar 23, 2011 at 6:30 AM, Jerome Renard jerome.ren...@gmail.com wrote: Hi Christian, I just discovered that ASF provides a Review Board instance there : https://reviews.apache.org/ There is no Zeta Components group yet and it seems I can not create one. Do I have to ask Infra for a new group or do I need something else ? Have a nice day :) -- Jérôme Renard http://39web.fr | http://jrenard.info | http://twitter.com/jeromerenard -- http://www.grobmeier.de
Re: [zeta-dev] Incubator PMC/Board report for February 2011 (zeta-dev@incubator.apache.org)
Thanks Julien, would be cool if you could do it. Cheers On Thu, Feb 3, 2011 at 10:53 PM, Julien Vermillard jvermill...@gmail.com wrote: Hi I can sign it if needed Julien On Thu, Feb 3, 2011 at 12:23 PM, Christian Grobmeier grobme...@gmail.com wrote: Hello folks, is somebody taking care on the report? I am on business travel next week and may not be able to sign it. An early report would be better. Cheers, Christian On Tue, Feb 1, 2011 at 3:00 PM, no-re...@apache.org wrote: Dear Zeta Components Developers, This email was sent by an automated system on behalf of the Apache Incubator PMC. It is an initial reminder to give you plenty of time to prepare your quarterly board report. The board meeting is scheduled for Wed, 16 February 2011, 10 am Pacific. The report for your podling will form a part of the Incubator PMC report. The Incubator PMC requires your report to be submitted one week before the board meeting, to allow sufficient time for review. Please submit your report with sufficient time to allow the incubator PMC, and subsequently board members to review and digest. Again, the very latest you should submit your report is one week prior to the board meeting. Thanks, The Apache Incubator PMC Submitting your Report -- Your report should contain the following: * Your project name * A brief description of your project, which assumes no knowledge of the project or necessarily of its field * A list of the three most important issues to address in the move towards graduation. * Any issues that the Incubator PMC or ASF Board might wish/need to be aware of * How has the community developed since the last report * How has the project developed since the last report. This should be appended to the Incubator Wiki page at: http://wiki.apache.org/incubator/February2011 Note: This manually populated. You may need to wait a little before this page is created from a template. Mentors --- Mentors should review reports for their project(s) and sign them off on the Incubator wiki page. Signing off reports shows that you are following the project - projects that are not signed may raise alarms for the Incubator PMC. Incubator PMC -- http://www.grobmeier.de -- http://www.grobmeier.de
Re: [zeta-dev] Incubator PMC/Board report for February 2011 (zeta-dev@incubator.apache.org)
Hello folks, is somebody taking care on the report? I am on business travel next week and may not be able to sign it. An early report would be better. Cheers, Christian On Tue, Feb 1, 2011 at 3:00 PM, no-re...@apache.org wrote: Dear Zeta Components Developers, This email was sent by an automated system on behalf of the Apache Incubator PMC. It is an initial reminder to give you plenty of time to prepare your quarterly board report. The board meeting is scheduled for Wed, 16 February 2011, 10 am Pacific. The report for your podling will form a part of the Incubator PMC report. The Incubator PMC requires your report to be submitted one week before the board meeting, to allow sufficient time for review. Please submit your report with sufficient time to allow the incubator PMC, and subsequently board members to review and digest. Again, the very latest you should submit your report is one week prior to the board meeting. Thanks, The Apache Incubator PMC Submitting your Report -- Your report should contain the following: * Your project name * A brief description of your project, which assumes no knowledge of the project or necessarily of its field * A list of the three most important issues to address in the move towards graduation. * Any issues that the Incubator PMC or ASF Board might wish/need to be aware of * How has the community developed since the last report * How has the project developed since the last report. This should be appended to the Incubator Wiki page at: http://wiki.apache.org/incubator/February2011 Note: This manually populated. You may need to wait a little before this page is created from a template. Mentors --- Mentors should review reports for their project(s) and sign them off on the Incubator wiki page. Signing off reports shows that you are following the project - projects that are not signed may raise alarms for the Incubator PMC. Incubator PMC -- http://www.grobmeier.de
Re: [zeta-dev] Documentation
- a method that can be used to easily debug the code. ... For example, I use PersistentObject and I would like to know why the find query returns me nothing. In the documentation, there's no clue to that could help me to resolve my probleme. And also, there's no way to print the $q-getQuery() without hacking PersistentObject. Maybe we must consider the fact to create a false dependancy to Debug, disabled by default. I have no real proposal to make for debugging helpers, but am interested in any that might be given... Usually logging systems are being used. In this case log4php could generate warnings if configured. But this would require to depend on log4php. Of course zeta can provide a mock object which does nothing, in case log4php classes can not be found. This also will keep up the speed in production systems Dependency Injection can be used to inject some kind of a logging object. But... how many people are there who can use DI? Plain and simple logging will do the job for most people.
Re: [zeta-dev] Proposal: Location component
Hello, this component is currently GPL code. This is not compatible with the AL. Will this change? Are you the sole copyright holder for this component? Cheers Christian On Wed, Nov 24, 2010 at 1:03 PM, Henri Bergius ber...@apache.org wrote: Hi, As discussed in my introduction thread[1], I'd like to propose for the Midgard MVC location library[2] to be contributed to the Zeta Components stack as a new components. As a first step, here are the initial requirements for a location library. Introduction The purpose of this library is to make it easier for PHP developers to work with geolocation. Geolocation is one of the emerging trends in web development, with new possibilities rising from browser geolocation support. This library focuses on dealing with actual real-world locations and relations between them, not with map visualization. Requirements In the initial version the location library should only deal with geolocated points. To build full geoinformation systems there will be need for lines, connections and areas, but these can be added in later iterations of the library. The library should provide the following services: Spot A spot is an actual location on a map. This consists of WGS-84 latitude and longitude. Optionally spots may have an altitude, timestamp, accuracy and a human-readable description. Spot should also be able to calculate distance and direction to other spots, and to provide a bounding box around them at a given radius. For display purposes spots also need to provide a way to convert them to pretty-printed human-readable coordinates. Geocoding - Geocoding is a service for converting human-readable locations to actual coordinates (spots). There should be an interface for geocoding utilizing various online geocoding services like GeoNames and OpenStreetMap Nominatim. Users of the component should be able to create their own geocoding service implementations. Reverse geocoding - Reverse geocoding is a service for converting actual coordinates (spots) into human-readable locations. There should be an interface for reverse geocoding utilizing various online geocoding services like GeoNames and OpenStreetMap Nominatim. Users of the component should be able to create their own reverse geocoding service implementations. IP geocoding IP geocoding is a service for converting an IP address to an approximate geographical location of the network. This can be used to locate users of a website for instance, in cases where browser geolocationing is not possible. The IP geocoding interface should be able to talk to at least HostIP web service to perform geocoding. 1: http://mail-archives.apache.org/mod_mbox/incubator-zeta-dev/201011.mbox/%3caanlkti=2j_vhbrmc3x55ekkjojwtuq-=9ddms0zvn...@mail.gmail.com%3e 2: https://github.com/bergie/midgardmvc_helper_location -- http://www.grobmeier.de
Re: [zeta-dev] Draft: Status update blog entry
That'd be great. I'll try to get the wiki up for such stuff soonish, as discussed here. Did you already send an iCLA? As far as I remember I did. I know there is a page on apache.org where you can see people who sent their iCLA but I do not remember which one. Maybe Christian remembers it. Yes he does: http://people.apache.org/committer-index.html Your name is mentioned on the unlisted CLA section == your ICLA has been received Cheers
Re: [zeta-dev] Draft: Status update blog entry
I would be happy if we could provide such status updates somewhat regularly (maybe once a month?), in order to keep people informed and to attract more contributors. What do you think? Great idea! Btw, you can have an apache blog by requesting it from jira http://blogs.apache.org/ In this blog you have the chance for a preview and send the preview to the dev list were people can make suggestions or vote about. Best regards, Christian
Re: [zeta-dev] Reporting time
http://wiki.apache.org/incubator/November2010 I just added our report. Please review it. All cool, thanks and cheers Christian
Re: [zeta-dev] Reporting time
+1 I don't know if it needs a vote, but I agree with the report content. It does not need a formal vote, but its good when several people look at it and comment. Cheers Christian Regards. Thomas. 2010/11/8 Christian Grobmeier grobme...@gmail.com http://wiki.apache.org/incubator/November2010 I just added our report. Please review it. All cool, thanks and cheers Christian
[zeta-dev] Reporting time
Hello all, please don't forget Zeta needs a report pretty soon. Please have in mind mentors have to read and sign it therefore it would be good if it would be added a while before wednesday. http://wiki.apache.org/incubator/November2010 Who can write it? Best Christian
[zeta-dev] Fwd: Apache Project Branding Requirements
Hello, here are some new branding requirements we need to consider. Cheers, Christian -- Forwarded message -- From: Phil Steitz p...@steitz.com Date: Sun, Oct 17, 2010 at 8:43 PM Subject: Apache Project Branding Requirements To: Commons Developers List d...@commons.apache.org With Shane's permission, I am forwarding this so we can all join in the fun :) .. -- Dear PMCs: To better showcase our projects and the community of developers and users that all Apache projects belong to, please plan to implement the new Apache Project Branding Requirements that the ASF Brand Management team has published. http://www.apache.org/foundation/marks/pmcs Since some of these requirements for project websites are new, and many may not been clearly documented, it's expected that it may take time for projects to update their public presence to reflect the requirements. We certainly don't want to mandate technical requirements to projects, but we do believe that having some consistent elements and proper treatment of trademarks across all of our project's sites is important. snip Reporting instructions for PMC chair /snip Please email the tradema...@apache.org mailing list with all questions or suggestions (please do not reply-all, since that may include a lot of different p...@!) snip Stuff on DOAP (already done for us) /snip - Shane Curcuru VP, Brand Management, The Apache Software Foundation http://www.apache.org/foundation/ bcc: board@ - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
[zeta-dev] Thanks from Piwi
Hello guys, yesterday we have released a new version of Piwi, which includes the first classes from Zeta Components, namely UserInput for providing parameter checks. But already today I have committed the first implementation of input providers which are using ZC Document. This was a very simple task and enables Piwi to read from input sources written in Wiki, RST, fODT and docbook - you know it. Looking briefly through the other components, I see good chances for replacing some stuff from Piwi or extend the feature set. So, thanks for the good work so far and bringing ZC to Apache - ZC really helped us. Cheers, Christian
Re: [zeta-dev] Thanks from Piwi
yes of course: http://code.google.com/p/piwi/ Please note, the latest changes (input provider on document component basis) are not released yet, I added them today. Cheers Christian On Fri, Oct 15, 2010 at 1:57 PM, Maxime Thomas maxime.t...@gmail.com wrote: Cool. Do you have a link to see this ? Max 2010/10/15 Christian Grobmeier grobme...@gmail.com Hello guys, yesterday we have released a new version of Piwi, which includes the first classes from Zeta Components, namely UserInput for providing parameter checks. But already today I have committed the first implementation of input providers which are using ZC Document. This was a very simple task and enables Piwi to read from input sources written in Wiki, RST, fODT and docbook - you know it. Looking briefly through the other components, I see good chances for replacing some stuff from Piwi or extend the feature set. So, thanks for the good work so far and bringing ZC to Apache - ZC really helped us. Cheers, Christian
[zeta-dev] broken links
Hi guys, on http://incubator.apache.org/zetacomponents/documentation/install.html is a broken link at the bottom of the page. List of available components - links to void Browse the eZ Components source code online - links to ez General information page - links to ez Issues of eZ Components development are being discussed in the eZ Components developers mailinglist - links to void Cheers Christian
[zeta-dev] Website #2
Hello, on the website: http://incubator.apache.org/zetacomponents/documentation/install.html its stating you are using BSD license. This should be changed. Btw - do you prefer Jira bugs for my website comments? Cheers christian
Re: [zeta-dev] Commit access
Hello James, usually people are voted in after they have contributed to a project. In other words, you'll need to prove you have a long term interest in the project before you can join. Please read more at: http://apache.org/foundation/getinvolved.html http://www.apache.org/foundation/how-it-works.html If this is (already) the case, the PMC members will held a vote (usually done on private list). In the special case of incubator, this vote need to be ack'ed by the Incubator PMC afterwards. best regards, Christian On Wed, Oct 6, 2010 at 12:58 PM, James Pic james...@gmail.com wrote: Hello everybody, Tobias told me ask for commit access on the mailing list. I was not aware of this procedure step when i sent my iCLA a month and a half ago, so sorry for the delay. Regards James -- http://jamespic.com/contact Customer is king - Le client est roi - El cliente es rey.
Re: [zeta-dev] Commit access
Hello James, My bad, i ought to mention that i have already contributed to ez components and that i have pending contributions. Were my contributions/credits losts during the svn migration? I didn't look into SVN. I think it should be there. However, if you are already known to the Zeta people there is nothing which prevents them to discuss about your request and then vote you in. My comments were more general. Cheers, Christian
Re: [zeta-dev] Website online, help appreciated
Apache Zeta Components is an effort undergoing incubation at The Apache Software Foundation (ASF), sponsored by eZ Systems. Apache Zeta Components originally were developed by eZ Systems under the name eZ Components and was generously sponsored to the Apache Software Foundation for further development. For me it's sounding wrong, the code was *donated*, the incubation is not sponsored, or perhaps I'm missing something there. +1 donated sounds more fitting to me too. But I am not native a native speaker, as you already might have noticed :-)
Re: [zeta-dev] Contributing / ZETACOMP-8
Hello Patrick, thanks for contributing. I would like to point you to these links, which help you to understand Apache and how it all works: * http://www.apache.org/foundation/getinvolved.html * http://www.apache.org/foundation/how-it-works.html Additionally its a good idea to attach your patch to the ticket in Jira directly. Please don't forget to check the check box which allows developers to include your code. Having a signed CLA is always a good idea if you are interested in contributing more stuff. A formal application is not necessary anyway, A project elects its committers after after a contributor has shown a understanding and commitment. Best regards, Christian On Mon, Aug 23, 2010 at 10:15 AM, Patrick ALLAERT patrickalla...@php.net wrote: Hi devs, I would like to be able to contribute to the Zeta Components project as a developer. I would mainly start solving issues as well as some QA stuff like fixing tests which does not pass on every platform. My first contribution, if you accept it, would be to solve issue: ZETACOMP-8: [Archive] Double extraction causes empty file which you might review here: http://pallaert.pastebin.com/3J7duMF1 A special crafted tar is needed for this test to reproduce it. I've been able to create one which is attached to this e-mail. I have signed an Apache CLA I will send to the Foundation in the case you would accept my application. Kind regards, Patrick Allaert -- http://www.grobmeier.de
Re: [zeta-dev] Piwi and ZC (was: Re: [zeta-dev] Re: Class prefix change, was: Re: [zeta-dev] Welcome Apache Zeta Components - SVN up and running :))
sounds interesting. We already started discussing a framework component a longer time ago in eZ Components. This component was meant to provide integration for the components, like scaffolding scripts. Having a complete framework on basis of Zeta would be a step in a similar direction. if you ask me, ZC is very good because you know what it is. Looking at f. e. Cocoon which has way to much faces i always felt it does to much. However, if you like the framework - we are willing to let people in. One of our drawbacks is that we are a small team :-) On the other hand, PIWI does to much - f. e. we have implemented a small DI container. Its pretty easy and fine, but basically it would fit more at ZC than in a webframework. A webframework should only provide classes which are necessary for webworking. If there is no DI container in ZC, Piwi could contribute such a component to ZC OK would like to hear you opinions on the prefix change. We discussed this issue before actually proposing Zeta to the ASF in the round which is the PMC today. I can fully understand your arguments in favor of a class prefix change. However, we decided against. Of course, if the community desires it, we can have a vote again on this issue, but I doubt any of the PMCs will vote for a change. Thats not a problem, justed wanted to know what the status is. I wanted to avoid to start with efford and then break everything up because of class prefix change. However, I don't see it the last chance to make a change. One day, we will be in the need of releasing 2.0 versions of our components and I don't see this step too far away (maybe a year?), since PHP 5.3 establishes more and more. With this step, we can switch directly from a class prefix to namespaces, which would actually render this change superfluous. +1 Thanks for the info! Christian
Re: [zeta-dev] Reasonable restrictions of wiki use
thanks for your input. I think this is quite valuable. To which degree do we need to care about taking over stuff from the wiki into our real docs, if a user without iCLA contributed it? Let me give an example: If a user writes a short example code snippet (whatever 3-5 lines) which we would consider valuable to have in the real docs, would he need to sign an iCLA? I wouldn't worry too much about 3-5 LOC. But it might be easier on all concerned to err on the side of caution. thats surely the easier and more secure way. However, I doubt that many of our users will have signed an iCLA, so our purpose for the wiki might be lead ad absurdum somehow. Are you all speaking about signing a CLA before contributing to a wiki? I am not sure about all the legal stuff, but is it really necessary to restrict a wiki so much? For example at commons.apache.org everybody can write to a wiki. Changes are mailed to the dev list. If there is something weird devs could interact. For my taste I would keep restrictions as low as possible while having an initial frame of the content like Tobias said is a very good idea. If it does not work out well it can be changed later at any time. Christian
Re: [zeta-dev] Incubator PMC/Board report for August 2010 (zeta-dev@incubator.apache.org)
Hello, report needs to be done before Wednesday, 11 August 2010. Please have in mind that we mentors need to read and sign it off and need some time for this too :-) This is the last one in monthly period, then we have a quarterly schedule. Next one is then in november. Best regards, Christian On Sun, Aug 1, 2010 at 4:00 PM, no-re...@apache.org wrote: Dear Zeta Components Developers, This email was sent by an automated system on behalf of the Apache Incubator PMC. It is an initial reminder to give you plenty of time to prepare your quarterly board report. The board meeting is scheduled for . The report for your podling will form a part of the Incubator PMC report. The Incubator PMC requires your report to be submitted one week before the board meeting, to allow sufficient time for review. Please submit your report with sufficient time to allow the incubator PMC, and subsequently board members to review and digest. Again, the very latest you should submit your report is one week prior to the board meeting. Thanks, The Apache Incubator PMC Submitting your Report -- Your report should contain the following: * Your project name * A brief description of your project, which assumes no knowledge of the project or necessarily of its field * A list of the three most important issues to address in the move towards graduation. * Any issues that the Incubator PMC or ASF Board might wish/need to be aware of * How has the community developed since the last report * How has the project developed since the last report. This should be appended to the Incubator Wiki page at: http://wiki.apache.org/incubator/August2010 Note: This manually populated. You may need to wait a little before this page is created from a template. Mentors --- Mentors should review reports for their project(s) and sign them off on the Incubator wiki page. Signing off reports shows that you are following the project - projects that are not signed may raise alarms for the Incubator PMC. Incubator PMC
Re: [zeta-dev] SVN test import online; releases/ and release-info/?
+1 from me I also looked at the previously discussed releases directory and agree with keeping. Cheers On Wed, Jul 21, 2010 at 7:43 PM, Tobias Schlitt tob...@schlitt.info wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi all, you should be able to check out the test SVN from http://svn-master.apache.org/repos/test/gmcdonald/zeta It seems there have been some synchronization issues. Please check it out and see if everything is satisfying. I'd like to give the OK for productive import soonish. 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/ iEYEARECAAYFAkxHMdUACgkQ5bO3TcRivBSu3QCfWgJuCiL5RsVoLi7XG6xZM5Gr KygAoLICj68SCWBxiIJwoLRpjEDdjZp4 =ZFr9 -END PGP SIGNATURE-
Re: [zeta-dev] SVN import and usernames
+1 On Mon, Jul 12, 2010 at 4:02 PM, Tobias Schlitt tob...@schlitt.info wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, On 07/12/2010 03:54 PM, Tobias Schlitt wrote: Therefore, I'd suggest that we map our old users to xy-ez.no, so it is also clear that the commits were from eZ. actually, I think xy/ez.no is better, so committer names don't get confused with domain names. 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/ iEYEARECAAYFAkw7IGwACgkQ5bO3TcRivBQBPACfTGpOBwLx8HNmZE1Cn2vitdRt bTcAoLN3kyDlXT871HfuzjhJMWsiErQQ =/1cY -END PGP SIGNATURE-
Re: [zeta-dev] Fwd: Incubator PMC/Board report for July 2010 (gene...@incubator.apache.org)
Hello, I added it. Just to remind you all, reports is a project duty not a mentor duty - later the Zeta PMC will have to report to the board. So better you get used to it now. Cheers! Christian On Mon, Jul 5, 2010 at 2:52 PM, Tobias Schlitt tob...@schlitt.info wrote: On 07/02/2010 07:02 AM, Christian Grobmeier wrote: Zeta Components Zeta Components is a high-quality library of loosely-coupled PHP components. It has entered incubation on 2010-05-21. Therefore the project is still in ramp up phase. In the past month, -all Apache accounts have been created - Jira has been created - SVN repository is prepared for the import. The 3 most important issues to be tackled are: - Create initial incubating infrastructure. - Move project and community to ASF. - Get developement based in ASF moving again. At the moment the SVN export needs to be signed of from the eZ management. Once this is done, SVN can move. +1 Thx for writing it. :) Cheers, Toby
Re: [zeta-dev] Re: Incubator PMC/Board report for July 2010 (gene...@incubator.apache.org)
any comments on this one? No, it looks fine to me. Where do we send the report? the report needs to be added to the Incubator Wiki: http://wiki.apache.org/incubator/July2010 Also of interest: http://wiki.apache.org/incubator/ReportingSchedule I also recommend to subscribe to the gene...@i.a.o list were reminders are sent best regards, Christian
[zeta-dev] Fwd: Incubator PMC/Board report for July 2010 (gene...@incubator.apache.org)
Hello Zeta-Devs, report is due. Here is a proposal. Please reply with your additions. BTW, reporting is projects duty ;-) Cheers Christian Zeta Components Zeta Components is a high-quality library of loosely-coupled PHP components. It has entered incubation on 2010-05-21. Therefore the project is still in ramp up phase. In the past month, -all Apache accounts have been created - Jira has been created - SVN repository is prepared for the import. The 3 most important issues to be tackled are: - Create initial incubating infrastructure. - Move project and community to ASF. - Get developement based in ASF moving again. At the moment the SVN export needs to be signed of from the eZ management. Once this is done, SVN can move. -- Forwarded message -- From: no-re...@apache.org Date: Thu, Jul 1, 2010 at 4:00 PM Subject: Incubator PMC/Board report for July 2010 (gene...@incubator.apache.org) To: gene...@incubator.apache.org Dear Zeta Components Developers, This email was sent by an automated system on behalf of the Apache Incubator PMC. It is an initial reminder to give you plenty of time to prepare your quarterly board report. The board meeting is scheduled for . The report for your podling will form a part of the Incubator PMC report. The Incubator PMC requires your report to be submitted one week before the board meeting, to allow sufficient time for review. Please submit your report with sufficient time to allow the incubator PMC, and subsequently board members to review and digest. Again, the very latest you should submit your report is one week prior to the board meeting. Thanks, The Apache Incubator PMC Submitting your Report -- Your report should contain the following: * Your project name * A brief description of your project, which assumes no knowledge of the project or necessarily of its field * A list of the three most important issues to address in the move towards graduation. * Any issues that the Incubator PMC or ASF Board might wish/need to be aware of * How has the community developed since the last report * How has the project developed since the last report. This should be appended to the Incubator Wiki page at: http://wiki.apache.org/incubator/July2010 Note: This manually populated. You may need to wait a little before this page is created from a template. Mentors --- Mentors should review reports for their project(s) and sign them off on the Incubator wiki page. Signing off reports shows that you are following the project - projects that are not signed may raise alarms for the Incubator PMC. Incubator PMC - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
