Re: [VOTE] Release ManifoldCF 0.3-incubating?
+1 ...ant On Mon, Sep 19, 2011 at 2:22 PM, Karl Wright daddy...@gmail.com wrote: If I count correctly, we still need one more binding +1. ManifoldCF only has two mentors, so this vote will have to come from incubator community at large. But we'd also love to have a third mentor! Karl On Fri, Sep 16, 2011 at 8:34 AM, Jukka Zitting jukka.zitt...@gmail.com wrote: Hi, On Tue, Sep 13, 2011 at 7:33 PM, Karl Wright daddy...@gmail.com wrote: The ManifoldCF community has voted to release ManifoldCF 0.3-incubating RC1. Now it is your turn to vote! You can pick up the artifact at http://people.apache.org/~kwright, or if you want to look at the svn tag it's at https://svn.apache.org/repos/asf/incubator/lcf/tags/release-0.3-incubating-RC1. +1 looks good BR, Jukka Zitting - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[RESULT][VOTE] Kalumet to join Incubator
Hello, The vote has passed with the following result : + 1 (binding) : Jean-Baptiste Onofré, Alan D. Cabrera, Marcel Offermans, Brett Porter, Mohammad Nour El-Din, Olivier Lamy + 1 (non binding) : Simone Tripodi, Joey Echeverria, David Blevins, Henri Gomez, Ashish Paliwal, Jamie Mark Goodyear, foxmask (no real name sorry :-), Terri-Lynn Rimmer, It looks the vote is fine : now time to hack :-). I will proceed with all the various tasks (ml creation, jira etc...) later this week. Thanks, -- Olivier Lamy Talend : http://talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [RESULT][VOTE] Kalumet to join Incubator
Hi, thanks all for your votes. I gonna work with Olivier to create and import the resources. Regards JB On 09/20/2011 09:56 AM, Olivier Lamy wrote: Hello, The vote has passed with the following result : + 1 (binding) : Jean-Baptiste Onofré, Alan D. Cabrera, Marcel Offermans, Brett Porter, Mohammad Nour El-Din, Olivier Lamy + 1 (non binding) : Simone Tripodi, Joey Echeverria, David Blevins, Henri Gomez, Ashish Paliwal, Jamie Mark Goodyear, foxmask (no real name sorry :-), Terri-Lynn Rimmer, It looks the vote is fine : now time to hack :-). I will proceed with all the various tasks (ml creation, jira etc...) later this week. Thanks, -- Jean-Baptiste Onofré jbono...@apache.org http://blog.nanthrax.net Talend - http://www.talend.com - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Your CCLA sent to Apache Secretary
Dear Shanti Subramanyan, This message acknowledges receipt of the following document, which has been filed in the Apache Software Foundation records: CCLA from Sun Microsystems, Inc. for Web2.0kit aka Olio Craig L Russell Secretary, Apache Software Foundation - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[RESULT][VOTE] Release ManifoldCF 0.3-incubating?
Three binding +1's, 72 hours. Vote passes! A big thanks to all that voted too... ;-) Karl - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[ANNOUNCE] Announcing general availability of Apache ManifoldCF 0.3-incubating!
Thanks to all who put time and effort into this release! The site and download mirrors should update in a day or so, but if you cannot wait, you can download the release in the interim from http://www.apache.org/dist/incubator/manifoldcf. Karl - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Kalumet to join Incubator
+1 (binding) On Mon, Sep 19, 2011 at 9:51 PM, Mohammad Nour El-Din nour.moham...@gmail.com wrote: +1 (binding) On Mon, Sep 19, 2011 at 4:23 PM, trimmer one.pro.gram...@gmail.com wrote: +1 (non-binding) Cheers, Terri-Lynn Rimmer -- View this message in context: http://old.nabble.com/-VOTE--Kalumet-to-join-Incubator-tp32453584p32495487.html Sent from the Apache Incubator - General mailing list archive at Nabble.com. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Thanks - Mohammad Nour Life is like riding a bicycle. To keep your balance you must keep moving - Albert Einstein - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Kalumet to join Incubator
hmm looks like I'm late :) good luck any way On Tue, Sep 20, 2011 at 10:53 AM, Julien Vermillard jvermill...@gmail.com wrote: +1 (binding) On Mon, Sep 19, 2011 at 9:51 PM, Mohammad Nour El-Din nour.moham...@gmail.com wrote: +1 (binding) On Mon, Sep 19, 2011 at 4:23 PM, trimmer one.pro.gram...@gmail.com wrote: +1 (non-binding) Cheers, Terri-Lynn Rimmer -- View this message in context: http://old.nabble.com/-VOTE--Kalumet-to-join-Incubator-tp32453584p32495487.html Sent from the Apache Incubator - General mailing list archive at Nabble.com. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Thanks - Mohammad Nour Life is like riding a bicycle. To keep your balance you must keep moving - Albert Einstein - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Kalumet to join Incubator
+1 (binding) Tommaso 2011/9/20 Julien Vermillard jvermill...@gmail.com +1 (binding) On Mon, Sep 19, 2011 at 9:51 PM, Mohammad Nour El-Din nour.moham...@gmail.com wrote: +1 (binding) On Mon, Sep 19, 2011 at 4:23 PM, trimmer one.pro.gram...@gmail.com wrote: +1 (non-binding) Cheers, Terri-Lynn Rimmer -- View this message in context: http://old.nabble.com/-VOTE--Kalumet-to-join-Incubator-tp32453584p32495487.html Sent from the Apache Incubator - General mailing list archive at Nabble.com. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Thanks - Mohammad Nour Life is like riding a bicycle. To keep your balance you must keep moving - Albert Einstein - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[DISCUSS] DirectMemory to join the Apache Incubator
Hi all guys, I would like to propose DirectMemory, a Java OpenSource multi-layered cache implementation featuring off-heap memory storage (a-la Terracotta BigMemory) originally developed by Raffaele P. Guidi on GitHub[1], to be an Apache Incubator project. For those interested on knowing more about DirectMemory, you can read Raffaele's related blog[2]. Here's a link to the proposal in the Incubator wiki[3] where we started collecting all needed info. As you will note, the list of mentors is in need of some volunteers, so if you find this interesting, feel free to sign up or let us know you are interested :). Hope to read from you soon, thanks in advance and have a nice day! All the best, Simo [1] https://github.com/raffaeleguidi/DirectMemory [2] http://raffaeleguidi.wordpress.com/ [3] http://wiki.apache.org/incubator/DirectMemoryProposal http://people.apache.org/~simonetripodi/ http://www.99soft.org/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] DirectMemory to join the Apache Incubator
Thanks, Simone for your introduction and support. To help evaluation I would add that there's also some more information in the project wiki at https://github.com/raffaeleguidi/DirectMemory/wiki and that I'm here to answer all of your questions in detail as well. Thanks for your, Raffaele On Tue, Sep 20, 2011 at 11:48 AM, Simone Tripodi simonetrip...@apache.orgwrote: Hi all guys, I would like to propose DirectMemory, a Java OpenSource multi-layered cache implementation featuring off-heap memory storage (a-la Terracotta BigMemory) originally developed by Raffaele P. Guidi on GitHub[1], to be an Apache Incubator project. For those interested on knowing more about DirectMemory, you can read Raffaele's related blog[2]. Here's a link to the proposal in the Incubator wiki[3] where we started collecting all needed info. As you will note, the list of mentors is in need of some volunteers, so if you find this interesting, feel free to sign up or let us know you are interested :). Hope to read from you soon, thanks in advance and have a nice day! All the best, Simo [1] https://github.com/raffaeleguidi/DirectMemory [2] http://raffaeleguidi.wordpress.com/ [3] http://wiki.apache.org/incubator/DirectMemoryProposal http://people.apache.org/~simonetripodi/ http://www.99soft.org/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Moving the incubator web site to the CMS
On 20 September 2011 04:24, David Crossley cross...@apache.org wrote: sebb wrote: Mohammad Nour El-Din sebb wrote: Also, what about clutch? That currently depends on being able to read some XML files. Although I have another long term idea for that, but it can be updated to read the relevant pages of Incubator CMS, and I am also very willing to help in that. Parts of Clutch have been modified at various occasions to gather its data and hints from other places. It currently gets facts from http://wiki.apache.org/incubator/ReportingSchedule and from the xml source for http://incubator.apache.org/projects/ Then it tries to get some hints from the xml source of each podling status page. Then it uses those gathered hints to detect whether the various project resources are available. After the move to CMS, it could parse the generated html instead. As Sebb indicates, the Markdown source files would not be easy. I think we should base clutch on a separate simple summary file, which is then used to create various aspects of the CMS site, as well as being used for other purpose. The CMS syntax is very flexible, and harder to parse. Having a purpose-designed podling status file would make Clutch's job much easier, as well as being easier to edit. For example, now when a podling graduates, the entry has to be moved from one section to another. A dedicated status file would just required changing the status entry. Yes. However, could we please make it so that that summary file is separate to Clutch. Agreed. The summary file needs other reasons for being, which might also encourage it to be well-maintained. My intention was originally for it to be the source of the projects page, i.e. it would be directly updated by podlings, and used to generate the projects index page and the RHS links. One file to update instead of two, though podlings would still need to update their own pages as at present. It would need to contain the following as a minimum: Project Description Apache Sponsor Mentors Started [Ended] Status If it's decided to use DOAPs for individual podling status pages, then the description and perhaps other fields could be automatically taken from the DOAP and merged into the summary file. It might even be possible to create the entire file from the DOAPs, but it might still be useful to list the podling names as a cross-check, and for historic projects it would be easier not to have to create DOAPS. It would then only be necessary to update the summary file when the podling status changed: creation, graduation, retirement or hibernation, assuming that is not done in the DOAP files themselves. I am running low on volunteer time, but will attempt to adjust Clutch to follow the CMS changes, taking small steps where possible. Once the new file format is decided, futher changes to Clutch should be minimal. -David - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] DirectMemory to join the Apache Incubator
That sounds like a really exciting project to bring to Apache. I'd be happy to volunteer as a mentor if you need one, with the so many existing ASF committors and members part of the project i expect incubation should go pretty smoothly. ...ant On Tue, Sep 20, 2011 at 10:48 AM, Simone Tripodi simonetrip...@apache.org wrote: Hi all guys, I would like to propose DirectMemory, a Java OpenSource multi-layered cache implementation featuring off-heap memory storage (a-la Terracotta BigMemory) originally developed by Raffaele P. Guidi on GitHub[1], to be an Apache Incubator project. For those interested on knowing more about DirectMemory, you can read Raffaele's related blog[2]. Here's a link to the proposal in the Incubator wiki[3] where we started collecting all needed info. As you will note, the list of mentors is in need of some volunteers, so if you find this interesting, feel free to sign up or let us know you are interested :). Hope to read from you soon, thanks in advance and have a nice day! All the best, Simo [1] https://github.com/raffaeleguidi/DirectMemory [2] http://raffaeleguidi.wordpress.com/ [3] http://wiki.apache.org/incubator/DirectMemoryProposal http://people.apache.org/~simonetripodi/ http://www.99soft.org/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] DirectMemory to join the Apache Incubator
On Tue, Sep 20, 2011 at 12:24 PM, ant elder ant.el...@gmail.com wrote: That sounds like a really exciting project to bring to Apache. I'd be happy to volunteer as a mentor if you need one, with the so many existing ASF committors and members part of the project i expect incubation should go pretty smoothly. I agree, this is an exciting project. There are many people comfortable with the incubation process, but I think the others will welcome you helping as mentor as I do. Please sign up to the proposal :-) Cheers Christian ...ant On Tue, Sep 20, 2011 at 10:48 AM, Simone Tripodi simonetrip...@apache.org wrote: Hi all guys, I would like to propose DirectMemory, a Java OpenSource multi-layered cache implementation featuring off-heap memory storage (a-la Terracotta BigMemory) originally developed by Raffaele P. Guidi on GitHub[1], to be an Apache Incubator project. For those interested on knowing more about DirectMemory, you can read Raffaele's related blog[2]. Here's a link to the proposal in the Incubator wiki[3] where we started collecting all needed info. As you will note, the list of mentors is in need of some volunteers, so if you find this interesting, feel free to sign up or let us know you are interested :). Hope to read from you soon, thanks in advance and have a nice day! All the best, Simo [1] https://github.com/raffaeleguidi/DirectMemory [2] http://raffaeleguidi.wordpress.com/ [3] http://wiki.apache.org/incubator/DirectMemoryProposal http://people.apache.org/~simonetripodi/ http://www.99soft.org/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- http://www.grobmeier.de - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] DirectMemory to join the Apache Incubator
Thanks for your feedback Ant, we are more than happy to have you onboard, glad to hear you are interested! I'm going to add you in the mentors list :) If there is someone in the existing list that want to step-up as mentor, feel free to do it! I suggest that Christian and Olivier are excellent candidates :) Simo http://people.apache.org/~simonetripodi/ http://www.99soft.org/ On Tue, Sep 20, 2011 at 12:24 PM, ant elder ant.el...@gmail.com wrote: That sounds like a really exciting project to bring to Apache. I'd be happy to volunteer as a mentor if you need one, with the so many existing ASF committors and members part of the project i expect incubation should go pretty smoothly. ...ant On Tue, Sep 20, 2011 at 10:48 AM, Simone Tripodi simonetrip...@apache.org wrote: Hi all guys, I would like to propose DirectMemory, a Java OpenSource multi-layered cache implementation featuring off-heap memory storage (a-la Terracotta BigMemory) originally developed by Raffaele P. Guidi on GitHub[1], to be an Apache Incubator project. For those interested on knowing more about DirectMemory, you can read Raffaele's related blog[2]. Here's a link to the proposal in the Incubator wiki[3] where we started collecting all needed info. As you will note, the list of mentors is in need of some volunteers, so if you find this interesting, feel free to sign up or let us know you are interested :). Hope to read from you soon, thanks in advance and have a nice day! All the best, Simo [1] https://github.com/raffaeleguidi/DirectMemory [2] http://raffaeleguidi.wordpress.com/ [3] http://wiki.apache.org/incubator/DirectMemoryProposal http://people.apache.org/~simonetripodi/ http://www.99soft.org/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] DirectMemory to join the Apache Incubator
On Tue, Sep 20, 2011 at 3:54 PM, ant elder ant.el...@gmail.com wrote: That sounds like a really exciting project to bring to Apache. I'd be happy to volunteer as a mentor if you need one, with the so many existing ASF committors and members part of the project i expect incubation should go pretty smoothly. ...ant Agree, I have been watching this project on github for a while. Seems like a nice extension to JCS (http://commons.apache.org/jcs/) thanks ashish - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] DirectMemory to join the Apache Incubator
If there is someone in the existing list that want to step-up as mentor, feel free to do it! I suggest that Christian and Olivier are excellent candidates :) oh yes, I will add my name there later too Cheers Simo http://people.apache.org/~simonetripodi/ http://www.99soft.org/ On Tue, Sep 20, 2011 at 12:24 PM, ant elder ant.el...@gmail.com wrote: That sounds like a really exciting project to bring to Apache. I'd be happy to volunteer as a mentor if you need one, with the so many existing ASF committors and members part of the project i expect incubation should go pretty smoothly. ...ant On Tue, Sep 20, 2011 at 10:48 AM, Simone Tripodi simonetrip...@apache.org wrote: Hi all guys, I would like to propose DirectMemory, a Java OpenSource multi-layered cache implementation featuring off-heap memory storage (a-la Terracotta BigMemory) originally developed by Raffaele P. Guidi on GitHub[1], to be an Apache Incubator project. For those interested on knowing more about DirectMemory, you can read Raffaele's related blog[2]. Here's a link to the proposal in the Incubator wiki[3] where we started collecting all needed info. As you will note, the list of mentors is in need of some volunteers, so if you find this interesting, feel free to sign up or let us know you are interested :). Hope to read from you soon, thanks in advance and have a nice day! All the best, Simo [1] https://github.com/raffaeleguidi/DirectMemory [2] http://raffaeleguidi.wordpress.com/ [3] http://wiki.apache.org/incubator/DirectMemoryProposal http://people.apache.org/~simonetripodi/ http://www.99soft.org/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- http://www.grobmeier.de - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] DirectMemory to join the Apache Incubator
Hi Ashish, JCS is indeed in the field of interest of DirectMemory, we intend to provide support for 3rd parties as much as possible! Thanks for your feedback! Simo http://people.apache.org/~simonetripodi/ http://www.99soft.org/ On Tue, Sep 20, 2011 at 12:29 PM, Ashish paliwalash...@gmail.com wrote: On Tue, Sep 20, 2011 at 3:54 PM, ant elder ant.el...@gmail.com wrote: That sounds like a really exciting project to bring to Apache. I'd be happy to volunteer as a mentor if you need one, with the so many existing ASF committors and members part of the project i expect incubation should go pretty smoothly. ...ant Agree, I have been watching this project on github for a while. Seems like a nice extension to JCS (http://commons.apache.org/jcs/) thanks ashish - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] DirectMemory to join the Apache Incubator
oh yes, I will add my name there later too Cheers I can take care of it, doing it right now ;) Simo http://people.apache.org/~simonetripodi/ http://www.99soft.org/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] DirectMemory to join the Apache Incubator
2011/9/20 Simone Tripodi simonetrip...@apache.org: Thanks for your feedback Ant, we are more than happy to have you onboard, glad to hear you are interested! I'm going to add you in the mentors list :) If there is someone in the existing list that want to step-up as mentor, feel free to do it! I suggest that Christian and Olivier are excellent candidates :) Done :-) Very nice project proposal ! Simo http://people.apache.org/~simonetripodi/ http://www.99soft.org/ On Tue, Sep 20, 2011 at 12:24 PM, ant elder ant.el...@gmail.com wrote: That sounds like a really exciting project to bring to Apache. I'd be happy to volunteer as a mentor if you need one, with the so many existing ASF committors and members part of the project i expect incubation should go pretty smoothly. ...ant On Tue, Sep 20, 2011 at 10:48 AM, Simone Tripodi simonetrip...@apache.org wrote: Hi all guys, I would like to propose DirectMemory, a Java OpenSource multi-layered cache implementation featuring off-heap memory storage (a-la Terracotta BigMemory) originally developed by Raffaele P. Guidi on GitHub[1], to be an Apache Incubator project. For those interested on knowing more about DirectMemory, you can read Raffaele's related blog[2]. Here's a link to the proposal in the Incubator wiki[3] where we started collecting all needed info. As you will note, the list of mentors is in need of some volunteers, so if you find this interesting, feel free to sign up or let us know you are interested :). Hope to read from you soon, thanks in advance and have a nice day! All the best, Simo [1] https://github.com/raffaeleguidi/DirectMemory [2] http://raffaeleguidi.wordpress.com/ [3] http://wiki.apache.org/incubator/DirectMemoryProposal http://people.apache.org/~simonetripodi/ http://www.99soft.org/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Olivier Lamy Talend : http://talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] DirectMemory to join the Apache Incubator
On Tue, Sep 20, 2011 at 5:48 AM, Simone Tripodi simonetrip...@apache.org wrote: Hi all guys, I would like to propose DirectMemory, a Java OpenSource multi-layered cache implementation featuring off-heap memory storage (a-la Terracotta BigMemory) originally developed by Raffaele P. Guidi on GitHub[1], to be an Apache Incubator project. For those interested on knowing more about DirectMemory, you can read Raffaele's related blog[2]. Here's a link to the proposal in the Incubator wiki[3] where we started collecting all needed info. As you will note, the list of mentors is in need of some volunteers, so if you find this interesting, feel free to sign up or let us know you are interested :). Hope to read from you soon, thanks in advance and have a nice day! All the best, Simo Hi Simo, well done, a couple questions: - the proposal doesn't have a champion, wouldn't that be you? - are the core developers listed actively committing code to the project? I like it, happy to help mentor if needed... Thanks, --tim - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] DirectMemory to join the Apache Incubator
Hi Tim! :) thanks for your interest and glad to add you in the mentors list, going to add you as soon as I replied to the email, welcome!!! Please read inline answers for your questions: - the proposal doesn't have a champion, wouldn't that be you? The main concern is that I'm not a champion :P Anyway if no one else would like to do it, I would be very nice to do it, but I would prefere if more experienced people like Christian or Olivier would do it - are the core developers listed actively committing code to the project? Nope, DirectMemory is an effort that Raffaele is doing in his spare-time, we joined him because we all met on twitter speaking about his project and proposed him to donate to the ASF. Thanks for your message! Simo http://people.apache.org/~simonetripodi/ http://www.99soft.org/ On Tue, Sep 20, 2011 at 1:28 PM, Tim Williams william...@gmail.com wrote: On Tue, Sep 20, 2011 at 5:48 AM, Simone Tripodi simonetrip...@apache.org wrote: Hi all guys, I would like to propose DirectMemory, a Java OpenSource multi-layered cache implementation featuring off-heap memory storage (a-la Terracotta BigMemory) originally developed by Raffaele P. Guidi on GitHub[1], to be an Apache Incubator project. For those interested on knowing more about DirectMemory, you can read Raffaele's related blog[2]. Here's a link to the proposal in the Incubator wiki[3] where we started collecting all needed info. As you will note, the list of mentors is in need of some volunteers, so if you find this interesting, feel free to sign up or let us know you are interested :). Hope to read from you soon, thanks in advance and have a nice day! All the best, Simo Hi Simo, well done, a couple questions: - the proposal doesn't have a champion, wouldn't that be you? - are the core developers listed actively committing code to the project? I like it, happy to help mentor if needed... Thanks, --tim - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] DirectMemory to join the Apache Incubator
- the proposal doesn't have a champion, wouldn't that be you? The main concern is that I'm not a champion :P Anyway if no one else would like to do it, I would be very nice to do it, but I would prefere if more experienced people like Christian or Olivier would do it Actually you (Simone) have already played the role of a champion:The Champion assists the candidate on their initial submission to a Sponsor. http://incubator.apache.org/incubation/Roles_and_Responsibilities.html#Champion But if you don't want to do it, I have no problem if you would add me to that section. The part of the Champion is already nearly done, so... - are the core developers listed actively committing code to the project? Speaking for myself, I currently have no time to commit java code, but I am willing to do lend a hand probably with site generation, mvn, and what comes along and does not require me to dig to deep into code, until i have some free time again. Cheers - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] DirectMemory to join the Apache Incubator
Dankeshön Christian, actually you are taking care more than me to looking for the sponsor, so Champion is the place you deserve :) I'm going to add you there :) Alles gute! Simo Actually you (Simone) have already played the role of a champion:The Champion assists the candidate on their initial submission to a Sponsor. http://incubator.apache.org/incubation/Roles_and_Responsibilities.html#Champion But if you don't want to do it, I have no problem if you would add me to that section. The part of the Champion is already nearly done, so... http://people.apache.org/~simonetripodi/ http://www.99soft.org/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Confusion: Sponsoring entity and Champions
Hi, I was looking into that: http://incubator.apache.org/incubation/Roles_and_Responsibilities.html#Sponsor And thought, if an upcoming podling is deciding to become a TLD it should ask the board to sponsor it. Now I have been told from Andrus that this is not the case and usually the Incubator is sponsoring TLD projects. I find this paragraph very misleading - is it just me? If (and I assume he is) Andrus is right, how is the way to have the Incubator as a sponsor? Just asking? Just adding to the proposal? If this is the case, then is Champion obsolete? Actually I was always doubting this role a bit. Cheers, Christian - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Confusion: Sponsoring entity and Champions
Hi, On Tue, Sep 20, 2011 at 5:18 PM, Christian Grobmeier grobme...@gmail.com wrote: I was looking into that: http://incubator.apache.org/incubation/Roles_and_Responsibilities.html#Sponsor And thought, if an upcoming podling is deciding to become a TLD it should ask the board to sponsor it. Now I have been told from Andrus that this is not the case and usually the Incubator is sponsoring TLD projects. Yes, as I said on the board list I don't remember the board sponsoring incubating projects recently. ...how is the way to have the Incubator as a sponsor? Just asking? Just adding to the proposal? ... Yes, just add it and people will complain if they see a problem. ...If this is the case, then is Champion obsolete? Actually I was always doubting this role a bit The champion is a person, while the sponsor is a PMC - what makes you think the champion role is obsolete? -Bertrand - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Confusion: Sponsoring entity and Champions
The default sponsor is the incubator PMC. if you just put that in a proposal and offer it up, it just happens. Board sponsorship happens for 'special' circumstances (like OO), and I don't pretend to understand why it's important. On Tue, Sep 20, 2011 at 11:33 AM, Bertrand Delacretaz bdelacre...@apache.org wrote: Hi, On Tue, Sep 20, 2011 at 5:18 PM, Christian Grobmeier grobme...@gmail.com wrote: I was looking into that: http://incubator.apache.org/incubation/Roles_and_Responsibilities.html#Sponsor And thought, if an upcoming podling is deciding to become a TLD it should ask the board to sponsor it. Now I have been told from Andrus that this is not the case and usually the Incubator is sponsoring TLD projects. Yes, as I said on the board list I don't remember the board sponsoring incubating projects recently. ...how is the way to have the Incubator as a sponsor? Just asking? Just adding to the proposal? ... Yes, just add it and people will complain if they see a problem. ...If this is the case, then is Champion obsolete? Actually I was always doubting this role a bit The champion is a person, while the sponsor is a PMC - what makes you think the champion role is obsolete? -Bertrand - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Confusion: Sponsoring entity and Champions
And thought, if an upcoming podling is deciding to become a TLD it should ask the board to sponsor it. Now I have been told from Andrus that this is not the case and usually the Incubator is sponsoring TLD projects. Yes, as I said on the board list I don't remember the board sponsoring incubating projects recently. thanks for repeating it here, b/c i realized i was not subscribed yet (fixed it now, but missed your reply) ...how is the way to have the Incubator as a sponsor? Just asking? Just adding to the proposal? ... Yes, just add it and people will complain if they see a problem. OK will do. ...If this is the case, then is Champion obsolete? Actually I was always doubting this role a bit The champion is a person, while the sponsor is a PMC - what makes you think the champion role is obsolete? What actually does a Champion do? Docs say he helps with finding a sponsor... A project can put the name Incubator as a sponsor as you said and see what happens. If somebody thinks on general@ a project fits perfectly to another one, then he probably says it. Therefore I really don't see the need for a role like a champion. If you ask me, I would delete the whole champion thing from the docs and rephrase the link I sent to: ask an existing project to sponsor you or put incubator into the sponsoring section. Learning the apache way is what mentors usually help with Christian -Bertrand - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- http://www.grobmeier.de - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Confusion: Sponsoring entity and Champions
On Tue, Sep 20, 2011 at 5:35 PM, Benson Margulies bimargul...@gmail.com wrote: The default sponsor is the incubator PMC. if you just put that in a proposal and offer it up, it just happens. Board sponsorship happens for 'special' circumstances (like OO), and I don't pretend to understand why it's important. This makes it even more confusing to me. It is really overengineered ;-) On Tue, Sep 20, 2011 at 11:33 AM, Bertrand Delacretaz bdelacre...@apache.org wrote: Hi, On Tue, Sep 20, 2011 at 5:18 PM, Christian Grobmeier grobme...@gmail.com wrote: I was looking into that: http://incubator.apache.org/incubation/Roles_and_Responsibilities.html#Sponsor And thought, if an upcoming podling is deciding to become a TLD it should ask the board to sponsor it. Now I have been told from Andrus that this is not the case and usually the Incubator is sponsoring TLD projects. Yes, as I said on the board list I don't remember the board sponsoring incubating projects recently. ...how is the way to have the Incubator as a sponsor? Just asking? Just adding to the proposal? ... Yes, just add it and people will complain if they see a problem. ...If this is the case, then is Champion obsolete? Actually I was always doubting this role a bit The champion is a person, while the sponsor is a PMC - what makes you think the champion role is obsolete? -Bertrand - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- http://www.grobmeier.de - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Confusion: Sponsoring entity and Champions
IMO the champion helps clarify the incubator process up to acceptance of the podling into the incubator. For example the champion for Wicket was not a singular person, but both Alex Karasulu and Upayavira were both very instrumental in smoothing our transition into the incubator. general@ can be very confusing and sometimes even hostile towards new podlings. Having a champion watching out for the podling is rather useful. Martijn On Tue, Sep 20, 2011 at 5:43 PM, Christian Grobmeier grobme...@gmail.com wrote: And thought, if an upcoming podling is deciding to become a TLD it should ask the board to sponsor it. Now I have been told from Andrus that this is not the case and usually the Incubator is sponsoring TLD projects. Yes, as I said on the board list I don't remember the board sponsoring incubating projects recently. thanks for repeating it here, b/c i realized i was not subscribed yet (fixed it now, but missed your reply) ...how is the way to have the Incubator as a sponsor? Just asking? Just adding to the proposal? ... Yes, just add it and people will complain if they see a problem. OK will do. ...If this is the case, then is Champion obsolete? Actually I was always doubting this role a bit The champion is a person, while the sponsor is a PMC - what makes you think the champion role is obsolete? What actually does a Champion do? Docs say he helps with finding a sponsor... A project can put the name Incubator as a sponsor as you said and see what happens. If somebody thinks on general@ a project fits perfectly to another one, then he probably says it. Therefore I really don't see the need for a role like a champion. If you ask me, I would delete the whole champion thing from the docs and rephrase the link I sent to: ask an existing project to sponsor you or put incubator into the sponsoring section. Learning the apache way is what mentors usually help with Christian -Bertrand - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- http://www.grobmeier.de - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Become a Wicket expert, learn from the best: http://wicketinaction.com - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Confusion: Sponsoring entity and Champions
On Tue, Sep 20, 2011 at 5:46 PM, Martijn Dashorst martijn.dasho...@gmail.com wrote: IMO the champion helps clarify the incubator process up to acceptance of the podling into the incubator. For example the champion for Wicket was not a singular person, but both Alex Karasulu and Upayavira were both very instrumental in smoothing our transition into the incubator. general@ can be very confusing and sometimes even hostile towards new podlings. Having a champion watching out for the podling is rather useful Agreed, IMO the role of the champion is to help the podling get started (which might include help find a sponsor, mentors etc) and they might only follow things from afar once that's done. It's different from a mentor who's supposed to stay active until graduation, but in some cases the role/people overlap, without problems. -Bertrand - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] S4 for the Apache Incubator
There are currently only 2 mentors volunteering to help out (Owen and myself), would be great to have 3+ -- any IPMC members out there that could help with the mentoring effort? Regards, Patrick On Mon, Sep 19, 2011 at 10:53 PM, Vinod Kumar Vavilapalli vino...@hortonworks.com wrote: On Mon, Sep 19, 2011 at 10:43 PM, Flavio Junqueira f...@s4.io wrote: To give you an idea of what we have in mind, here are a few points: - Monitor Nodes and PEs. - Ability to query specific PE instance variables. - Add remove nodes. - Monitor logs. - Monitor CPU/Memory usage per node. - Load/unload apps. It does look like some of the resource management can be offloaded to YARN. In general, it sounds right to assess if it is viable to use YARN for S4 cluster management and we would appreciate your help. If it is ok with you, I'd rather not include it in the proposal, though, since it is an issue we could consider independently of the project going into incubator. Let me know if you agree. Definitely. Thanks, +Vinod - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Confusion: Sponsoring entity and Champions
On Tue, Sep 20, 2011 at 5:56 PM, Bertrand Delacretaz bdelacre...@apache.org wrote: On Tue, Sep 20, 2011 at 5:46 PM, Martijn Dashorst martijn.dasho...@gmail.com wrote: IMO the champion helps clarify the incubator process up to acceptance of the podling into the incubator. For example the champion for Wicket was not a singular person, but both Alex Karasulu and Upayavira were both very instrumental in smoothing our transition into the incubator. general@ can be very confusing and sometimes even hostile towards new podlings. Having a champion watching out for the podling is rather useful Agreed, IMO the role of the champion is to help the podling get started (which might include help find a sponsor, mentors etc) and they might only follow things from afar once that's done. So, why do we need a role for that? I rarely see the call We need a champion on the mailinglsit. So I assume that these persons are somehow connected to the project before. Or they read the draft-proposal and contact people directly. At the moment it looks as it is required to have a Champion. I don't think so. It should be optional, if we really need such a role. I still doubt. Instead, a Champion is more or less the first mentor a project has. It should be called Mentor (or initial mentor) to avoid to much unnecessary terms. In fact, with DirectMemory I have felt it led all to more confusion than it was helpful. Help finding a sponsor - default sponsor is Incubator PMC. There is no real need of it. Help finding mentors - an email to general usually is enough to make people act. Cheers, Christian It's different from a mentor who's supposed to stay active until graduation, but in some cases the role/people overlap, without problems. -Bertrand - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- http://www.grobmeier.de - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Refactoring Sponsor Paragraph
Hi, as already mentioned I find this paragraph very confusing: http://incubator.apache.org/incubation/Roles_and_Responsibilities.html#Sponsor I propose to change it to the text below. Basically I have left out the Sponsoring entity Board, because the board does not sponsor an Podling from the beginning as I have learned. Please see below. Best regards, Christian Sponsor The Sponsor [definition] is the entity within the ASF that makes the determination that a candidate would make a worthy addition to the ASF, and agrees to take on the candidate in question should it complete the incubation process. A Sponsor will be one of: A Top Level Project within the ASF. In this case, the project in question has agreed that the candidate is a good fit for their project, and will take on the candidate as a sub-project upon successful completion of Incubation. The Incubator PMC. In this case, the Incubator PMC agrees that the project in question will make a good addition to the ASF, but there is no clear owner of the candidate should it successfully complete incubation. An incubation exit requirement for such candidates will be the identification (and successfuly lobbying) of an owner entity - either the Board (and the candidate will be a TLP) or another project. Note that a Sponsor is more than just a final resting place for a candidate that successfully completes incubation. The Sponsor, by taking on a candidate, is indicating that they believe the candidate will make a worthy addition to the ASF, and takes responsibility for assisting the podling through the Incubation process. The Sponsor is therefore expected to be actively involved in the incubation process and assist where necessary, giving the podling the best possible chance of success. In addition, an entity that is a Top Level Project should be involved in the Candidate's incubation in order to educate the Candidate about practices that are specific to that TLP and about other relevant projects within the TLP. However, while the Sponsor is expected to be actively involved, it is formally represented by the Mentors. The Mentors are the individuals accountable to the Incubator PMC for ensuring the incubation process is correctly followed. In cases where the Mentors are not fulfilling their responsibilities, the Sponsor (in particular its Chair) will be expected to remedy the situation. Responsibilities of the Sponsor to provide initial approval for a Canidate to be accepted as a Podling to nominate Mentors for the incubation process - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] S4 for the Apache Incubator
Happy to help mentor S4. Arun On Sep 20, 2011, at 9:13 AM, Patrick Hunt wrote: There are currently only 2 mentors volunteering to help out (Owen and myself), would be great to have 3+ -- any IPMC members out there that could help with the mentoring effort? Regards, Patrick On Mon, Sep 19, 2011 at 10:53 PM, Vinod Kumar Vavilapalli vino...@hortonworks.com wrote: On Mon, Sep 19, 2011 at 10:43 PM, Flavio Junqueira f...@s4.io wrote: To give you an idea of what we have in mind, here are a few points: - Monitor Nodes and PEs. - Ability to query specific PE instance variables. - Add remove nodes. - Monitor logs. - Monitor CPU/Memory usage per node. - Load/unload apps. It does look like some of the resource management can be offloaded to YARN. In general, it sounds right to assess if it is viable to use YARN for S4 cluster management and we would appreciate your help. If it is ok with you, I'd rather not include it in the proposal, though, since it is an issue we could consider independently of the project going into incubator. Let me know if you agree. Definitely. Thanks, +Vinod - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] S4 for the Apache Incubator
Thanks, Arun. I'm happy to have you on board! -Flavio On Sep 20, 2011, at 6:55 PM, Arun C Murthy wrote: Happy to help mentor S4. Arun On Sep 20, 2011, at 9:13 AM, Patrick Hunt wrote: There are currently only 2 mentors volunteering to help out (Owen and myself), would be great to have 3+ -- any IPMC members out there that could help with the mentoring effort? Regards, Patrick On Mon, Sep 19, 2011 at 10:53 PM, Vinod Kumar Vavilapalli vino...@hortonworks.com wrote: On Mon, Sep 19, 2011 at 10:43 PM, Flavio Junqueira f...@s4.io wrote: To give you an idea of what we have in mind, here are a few points: - Monitor Nodes and PEs. - Ability to query specific PE instance variables. - Add remove nodes. - Monitor logs. - Monitor CPU/Memory usage per node. - Load/unload apps. It does look like some of the resource management can be offloaded to YARN. In general, it sounds right to assess if it is viable to use YARN for S4 cluster management and we would appreciate your help. If it is ok with you, I'd rather not include it in the proposal, though, since it is an issue we could consider independently of the project going into incubator. Let me know if you agree. Definitely. Thanks, +Vinod - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Confusion: Sponsoring entity and Champions
On Tue, Sep 20, 2011 at 5:46 PM, Christian Grobmeier grobme...@gmail.com wrote: On Tue, Sep 20, 2011 at 5:56 PM, Bertrand Delacretaz bdelacre...@apache.org wrote: On Tue, Sep 20, 2011 at 5:46 PM, Martijn Dashorst martijn.dasho...@gmail.com wrote: IMO the champion helps clarify the incubator process up to acceptance of the podling into the incubator. For example the champion for Wicket was not a singular person, but both Alex Karasulu and Upayavira were both very instrumental in smoothing our transition into the incubator. general@ can be very confusing and sometimes even hostile towards new podlings. Having a champion watching out for the podling is rather useful Agreed, IMO the role of the champion is to help the podling get started (which might include help find a sponsor, mentors etc) and they might only follow things from afar once that's done. So, why do we need a role for that? I rarely see the call We need a champion on the mailinglsit. So I assume that these persons are somehow connected to the project before. Or they read the draft-proposal and contact people directly. I suspect that they often contact people directly At the moment it looks as it is required to have a Champion. I don't think so. It should be optional, if we really need such a role. I still doubt. Instead, a Champion is more or less the first mentor a project has. It should be called Mentor (or initial mentor) to avoid to much unnecessary terms. IIRC separating these roles allowed specialists to navigate the podling approval process without having to make a long commitment. Our documentation for this process seems ok now. So maybe champions are no longer needed. Robert - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[VOTE] S4 to join the Incubator
It's been a nearly a week since the S4 proposal was submitted for discussion. A few questions were asked, and the proposal was clarified in response. Sufficient mentors have volunteered. I thus feel we are now ready for a vote. The latest proposal can be found at the end of this email and at: http://wiki.apache.org/incubator/S4Proposal The discussion regarding the proposal can be found at: http://s.apache.org/RMU Please cast your votes: [ ] +1 Accept S4 for incubation [ ] +0 Indifferent to S4 incubation [ ] -1 Reject S4 for incubation This vote will close 72 hours from now. Thanks, Patrick -- = S4 Proposal = == Abstract == S4 (Simple Scalable Streaming System) is a general-purpose, distributed, scalable, partially fault-tolerant, pluggable platform that allows programmers to easily develop applications for processing continuous, unbounded streams of data. == Proposal == S4 is a software platform written in Java. Clients that send and receive events can be written in any programming language. S4 also includes a collection of modules called Processing Elements (or PEs for short) that implement basic functionality and can be used by application developers. In S4, keyed data events are routed with affinity to Processing Elements (PEs), which consume the events and do one or both of the following: (1) ''emit'' one or more events which may be consumed by other PEs, (2) ''publish'' results. The architecture resembles the Actors model, providing semantics of encapsulation and location transparency, thus allowing applications to be massively concurrent while exposing a simple programming interface to application developers. To drive adoption and increase the number of contributors to the project, we may need to prioritize the focus based on feedback from the community. We believe that one of the top priorities and driving design principle for the S4 project is to provide a simple API that hides most of the complexity associated with distributed systems and concurrency. The project grew out of the need to provide a flexible platform for application developers and scientists that can be used for quick experimentation and production. S4 differs from existing Apache projects in a number of fundamental ways. Flume is an Incubator project that focuses on log processing, performing lightweight processing in a distributed fashion and accumulating log data in a centralized repository for batch processing. S4 instead performs all stream processing in a distributed fashion and enables applications to form arbitrary graphs to process streams of events. We see Flume as a complementary project. We also expect S4 to complement Hadoop processing and in some cases to supersede it. Kafka is another Incubator project that focuses on processing large amounts of stream data. The design of Kafka, however, follows the pub-sub paradigm, which focuses on delivering messages containing arbitrary data from source processes (publishers) to consumer processes (subscribers). Compared to S4, Kafka is an intermediate step between data generation and processing, while S4 is itself a platform for processing streams of events. S4 overall addresses a need of existing applications to process streams of events beyond moving data to a centralized repository for batch processing. It complements the features of existing Apache projects, such as Hadoop, Flume, and Kafka, by providing a flexible platform for distributed event processing. == Background == S4 was initially developed at Yahoo! Labs starting in 2008 to process user feedback in the context of search advertising. The project was licensed under the Apache License version 2.0 in October 2010. The project documentation is currently available at http://s4.io . == Rationale == Stream computing has been growing steadily over the last 20 years. However, recently there has been an explosion in real-time data sources including the Web, sensor networks, financial securities analysis and trading, traffic monitoring, natural language processing of news and social data, and much more. As Hadoop evolved as a standard open source solution for batch processing of massive data sets, there is no equivalent community supported open source platform for processing data streams in real-time. While various research projects have evolved into proprietary commercial products, S4 has the potential to fill the gap. Many projects that require a scalable stream processing architecture currently use Hadoop by segmenting the input stream into data batches. This solution is not efficient, results in high latency, and introduces unnecessary complexity. The S4 design is primarily driven by large scale applications for data mining and machine learning in a production environment. We think that the S4 design is surprisingly flexible and lends itself to run in large clusters built with commodity hardware. S4 enables application programmers to focus more on the application and less on
Re: Confusion: Sponsoring entity and Champions
On 20 September 2011 18:50, Robert Burrell Donkin robertburrelldon...@gmail.com wrote: On Tue, Sep 20, 2011 at 5:46 PM, Christian Grobmeier grobme...@gmail.com wrote: On Tue, Sep 20, 2011 at 5:56 PM, Bertrand Delacretaz bdelacre...@apache.org wrote: On Tue, Sep 20, 2011 at 5:46 PM, Martijn Dashorst martijn.dasho...@gmail.com wrote: IMO the champion helps clarify the incubator process up to acceptance of the podling into the incubator. For example the champion for Wicket was not a singular person, but both Alex Karasulu and Upayavira were both very instrumental in smoothing our transition into the incubator. general@ can be very confusing and sometimes even hostile towards new podlings. Having a champion watching out for the podling is rather useful Agreed, IMO the role of the champion is to help the podling get started (which might include help find a sponsor, mentors etc) and they might only follow things from afar once that's done. So, why do we need a role for that? I rarely see the call We need a champion on the mailinglsit. So I assume that these persons are somehow connected to the project before. Or they read the draft-proposal and contact people directly. I suspect that they often contact people directly At the moment it looks as it is required to have a Champion. I don't think so. It should be optional, if we really need such a role. I still doubt. Instead, a Champion is more or less the first mentor a project has. It should be called Mentor (or initial mentor) to avoid to much unnecessary terms. IIRC separating these roles allowed specialists to navigate the podling approval process without having to make a long commitment. Our documentation for this process seems ok now. So maybe champions are no longer needed. If there is no Champion, who is responsible for driving the process forward initially? Once the PPMC is up and running, that becomes less of an issue. Do PPMCs have chairs? If not, then maybe the Champion fulfils that role until eventual graduation; otherwise they fulfil the role until the PPMC elects a chair. Robert - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Confusion: Sponsoring entity and Champions
On Tue, Sep 20, 2011 at 12:46 PM, Christian Grobmeier grobme...@gmail.com wrote: On Tue, Sep 20, 2011 at 5:56 PM, Bertrand Delacretaz bdelacre...@apache.org wrote: On Tue, Sep 20, 2011 at 5:46 PM, Martijn Dashorst martijn.dasho...@gmail.com wrote: IMO the champion helps clarify the incubator process up to acceptance of the podling into the incubator. For example the champion for Wicket was not a singular person, but both Alex Karasulu and Upayavira were both very instrumental in smoothing our transition into the incubator. general@ can be very confusing and sometimes even hostile towards new podlings. Having a champion watching out for the podling is rather useful Agreed, IMO the role of the champion is to help the podling get started (which might include help find a sponsor, mentors etc) and they might only follow things from afar once that's done. So, why do we need a role for that? I rarely see the call We need a champion on the mailinglsit. So I assume that these persons are somehow connected to the project before. Or they read the draft-proposal and contact people directly. At the moment it looks as it is required to have a Champion. I don't think so. It should be optional, if we really need such a role. It seems to that it is a mostly pre-incubation job in only certain projects. But it seems useful that one person would step forth and claim to be the champion of bringing a certain project to the ASF and [implicitly] agree to pushing down any artificial process hurdles. It seems like we've had such hurdles and brave champions in the past but I'm too lazy to dig right now... --tim - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] S4 to join the Incubator
Great project. +1 (non-binding) On Tue, Sep 20, 2011 at 1:56 PM, Patrick Hunt ph...@apache.org wrote: It's been a nearly a week since the S4 proposal was submitted for discussion. A few questions were asked, and the proposal was clarified in response. Sufficient mentors have volunteered. I thus feel we are now ready for a vote. The latest proposal can be found at the end of this email and at: http://wiki.apache.org/incubator/S4Proposal The discussion regarding the proposal can be found at: http://s.apache.org/RMU Please cast your votes: [ ] +1 Accept S4 for incubation [ ] +0 Indifferent to S4 incubation [ ] -1 Reject S4 for incubation This vote will close 72 hours from now. Thanks, Patrick -- = S4 Proposal = == Abstract == S4 (Simple Scalable Streaming System) is a general-purpose, distributed, scalable, partially fault-tolerant, pluggable platform that allows programmers to easily develop applications for processing continuous, unbounded streams of data. == Proposal == S4 is a software platform written in Java. Clients that send and receive events can be written in any programming language. S4 also includes a collection of modules called Processing Elements (or PEs for short) that implement basic functionality and can be used by application developers. In S4, keyed data events are routed with affinity to Processing Elements (PEs), which consume the events and do one or both of the following: (1) ''emit'' one or more events which may be consumed by other PEs, (2) ''publish'' results. The architecture resembles the Actors model, providing semantics of encapsulation and location transparency, thus allowing applications to be massively concurrent while exposing a simple programming interface to application developers. To drive adoption and increase the number of contributors to the project, we may need to prioritize the focus based on feedback from the community. We believe that one of the top priorities and driving design principle for the S4 project is to provide a simple API that hides most of the complexity associated with distributed systems and concurrency. The project grew out of the need to provide a flexible platform for application developers and scientists that can be used for quick experimentation and production. S4 differs from existing Apache projects in a number of fundamental ways. Flume is an Incubator project that focuses on log processing, performing lightweight processing in a distributed fashion and accumulating log data in a centralized repository for batch processing. S4 instead performs all stream processing in a distributed fashion and enables applications to form arbitrary graphs to process streams of events. We see Flume as a complementary project. We also expect S4 to complement Hadoop processing and in some cases to supersede it. Kafka is another Incubator project that focuses on processing large amounts of stream data. The design of Kafka, however, follows the pub-sub paradigm, which focuses on delivering messages containing arbitrary data from source processes (publishers) to consumer processes (subscribers). Compared to S4, Kafka is an intermediate step between data generation and processing, while S4 is itself a platform for processing streams of events. S4 overall addresses a need of existing applications to process streams of events beyond moving data to a centralized repository for batch processing. It complements the features of existing Apache projects, such as Hadoop, Flume, and Kafka, by providing a flexible platform for distributed event processing. == Background == S4 was initially developed at Yahoo! Labs starting in 2008 to process user feedback in the context of search advertising. The project was licensed under the Apache License version 2.0 in October 2010. The project documentation is currently available at http://s4.io . == Rationale == Stream computing has been growing steadily over the last 20 years. However, recently there has been an explosion in real-time data sources including the Web, sensor networks, financial securities analysis and trading, traffic monitoring, natural language processing of news and social data, and much more. As Hadoop evolved as a standard open source solution for batch processing of massive data sets, there is no equivalent community supported open source platform for processing data streams in real-time. While various research projects have evolved into proprietary commercial products, S4 has the potential to fill the gap. Many projects that require a scalable stream processing architecture currently use Hadoop by segmenting the input stream into data batches. This solution is not efficient, results in high latency, and introduces unnecessary complexity. The S4 design is primarily driven by large scale applications for data mining and machine learning in a production environment. We think that
Re: [VOTE] S4 to join the Incubator
+1 On Wed, Sep 21, 2011 at 2:26 AM, Patrick Hunt ph...@apache.org wrote: It's been a nearly a week since the S4 proposal was submitted for discussion. A few questions were asked, and the proposal was clarified in response. Sufficient mentors have volunteered. I thus feel we are now ready for a vote. The latest proposal can be found at the end of this email and at: http://wiki.apache.org/incubator/S4Proposal The discussion regarding the proposal can be found at: http://s.apache.org/RMU Please cast your votes: [ ] +1 Accept S4 for incubation [ ] +0 Indifferent to S4 incubation [ ] -1 Reject S4 for incubation This vote will close 72 hours from now. Thanks, Patrick -- = S4 Proposal = == Abstract == S4 (Simple Scalable Streaming System) is a general-purpose, distributed, scalable, partially fault-tolerant, pluggable platform that allows programmers to easily develop applications for processing continuous, unbounded streams of data. == Proposal == S4 is a software platform written in Java. Clients that send and receive events can be written in any programming language. S4 also includes a collection of modules called Processing Elements (or PEs for short) that implement basic functionality and can be used by application developers. In S4, keyed data events are routed with affinity to Processing Elements (PEs), which consume the events and do one or both of the following: (1) ''emit'' one or more events which may be consumed by other PEs, (2) ''publish'' results. The architecture resembles the Actors model, providing semantics of encapsulation and location transparency, thus allowing applications to be massively concurrent while exposing a simple programming interface to application developers. To drive adoption and increase the number of contributors to the project, we may need to prioritize the focus based on feedback from the community. We believe that one of the top priorities and driving design principle for the S4 project is to provide a simple API that hides most of the complexity associated with distributed systems and concurrency. The project grew out of the need to provide a flexible platform for application developers and scientists that can be used for quick experimentation and production. S4 differs from existing Apache projects in a number of fundamental ways. Flume is an Incubator project that focuses on log processing, performing lightweight processing in a distributed fashion and accumulating log data in a centralized repository for batch processing. S4 instead performs all stream processing in a distributed fashion and enables applications to form arbitrary graphs to process streams of events. We see Flume as a complementary project. We also expect S4 to complement Hadoop processing and in some cases to supersede it. Kafka is another Incubator project that focuses on processing large amounts of stream data. The design of Kafka, however, follows the pub-sub paradigm, which focuses on delivering messages containing arbitrary data from source processes (publishers) to consumer processes (subscribers). Compared to S4, Kafka is an intermediate step between data generation and processing, while S4 is itself a platform for processing streams of events. S4 overall addresses a need of existing applications to process streams of events beyond moving data to a centralized repository for batch processing. It complements the features of existing Apache projects, such as Hadoop, Flume, and Kafka, by providing a flexible platform for distributed event processing. == Background == S4 was initially developed at Yahoo! Labs starting in 2008 to process user feedback in the context of search advertising. The project was licensed under the Apache License version 2.0 in October 2010. The project documentation is currently available at http://s4.io . == Rationale == Stream computing has been growing steadily over the last 20 years. However, recently there has been an explosion in real-time data sources including the Web, sensor networks, financial securities analysis and trading, traffic monitoring, natural language processing of news and social data, and much more. As Hadoop evolved as a standard open source solution for batch processing of massive data sets, there is no equivalent community supported open source platform for processing data streams in real-time. While various research projects have evolved into proprietary commercial products, S4 has the potential to fill the gap. Many projects that require a scalable stream processing architecture currently use Hadoop by segmenting the input stream into data batches. This solution is not efficient, results in high latency, and introduces unnecessary complexity. The S4 design is primarily driven by large scale applications for data mining and machine learning in a production environment. We think that the S4 design is surprisingly
Re: [VOTE] S4 to join the Incubator
On Tue, Sep 20, 2011 at 4:56 PM, Patrick Hunt ph...@apache.org wrote: [ ] +1 Accept S4 for incubation [ ] +0 Indifferent to S4 incubation [ ] -1 Reject S4 for incubation +1 Cheers, Phil - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] S4 to join the Incubator
+1 (binding) Arun On Sep 20, 2011, at 1:56 PM, Patrick Hunt wrote: It's been a nearly a week since the S4 proposal was submitted for discussion. A few questions were asked, and the proposal was clarified in response. Sufficient mentors have volunteered. I thus feel we are now ready for a vote. The latest proposal can be found at the end of this email and at: http://wiki.apache.org/incubator/S4Proposal The discussion regarding the proposal can be found at: http://s.apache.org/RMU Please cast your votes: [ ] +1 Accept S4 for incubation [ ] +0 Indifferent to S4 incubation [ ] -1 Reject S4 for incubation This vote will close 72 hours from now. Thanks, Patrick -- = S4 Proposal = == Abstract == S4 (Simple Scalable Streaming System) is a general-purpose, distributed, scalable, partially fault-tolerant, pluggable platform that allows programmers to easily develop applications for processing continuous, unbounded streams of data. == Proposal == S4 is a software platform written in Java. Clients that send and receive events can be written in any programming language. S4 also includes a collection of modules called Processing Elements (or PEs for short) that implement basic functionality and can be used by application developers. In S4, keyed data events are routed with affinity to Processing Elements (PEs), which consume the events and do one or both of the following: (1) ''emit'' one or more events which may be consumed by other PEs, (2) ''publish'' results. The architecture resembles the Actors model, providing semantics of encapsulation and location transparency, thus allowing applications to be massively concurrent while exposing a simple programming interface to application developers. To drive adoption and increase the number of contributors to the project, we may need to prioritize the focus based on feedback from the community. We believe that one of the top priorities and driving design principle for the S4 project is to provide a simple API that hides most of the complexity associated with distributed systems and concurrency. The project grew out of the need to provide a flexible platform for application developers and scientists that can be used for quick experimentation and production. S4 differs from existing Apache projects in a number of fundamental ways. Flume is an Incubator project that focuses on log processing, performing lightweight processing in a distributed fashion and accumulating log data in a centralized repository for batch processing. S4 instead performs all stream processing in a distributed fashion and enables applications to form arbitrary graphs to process streams of events. We see Flume as a complementary project. We also expect S4 to complement Hadoop processing and in some cases to supersede it. Kafka is another Incubator project that focuses on processing large amounts of stream data. The design of Kafka, however, follows the pub-sub paradigm, which focuses on delivering messages containing arbitrary data from source processes (publishers) to consumer processes (subscribers). Compared to S4, Kafka is an intermediate step between data generation and processing, while S4 is itself a platform for processing streams of events. S4 overall addresses a need of existing applications to process streams of events beyond moving data to a centralized repository for batch processing. It complements the features of existing Apache projects, such as Hadoop, Flume, and Kafka, by providing a flexible platform for distributed event processing. == Background == S4 was initially developed at Yahoo! Labs starting in 2008 to process user feedback in the context of search advertising. The project was licensed under the Apache License version 2.0 in October 2010. The project documentation is currently available at http://s4.io . == Rationale == Stream computing has been growing steadily over the last 20 years. However, recently there has been an explosion in real-time data sources including the Web, sensor networks, financial securities analysis and trading, traffic monitoring, natural language processing of news and social data, and much more. As Hadoop evolved as a standard open source solution for batch processing of massive data sets, there is no equivalent community supported open source platform for processing data streams in real-time. While various research projects have evolved into proprietary commercial products, S4 has the potential to fill the gap. Many projects that require a scalable stream processing architecture currently use Hadoop by segmenting the input stream into data batches. This solution is not efficient, results in high latency, and introduces unnecessary complexity. The S4 design is primarily driven by large scale applications for data mining and machine learning in a production environment. We think that the S4 design
Re: [VOTE] S4 to join the Incubator
+1 Otis Sematext :: http://sematext.com/ :: Solr - Lucene - Nutch Lucene ecosystem search :: http://search-lucene.com/ From: Patrick Hunt ph...@apache.org To: general@incubator.apache.org Sent: Tuesday, September 20, 2011 4:56 PM Subject: [VOTE] S4 to join the Incubator It's been a nearly a week since the S4 proposal was submitted for discussion. A few questions were asked, and the proposal was clarified in response. Sufficient mentors have volunteered. I thus feel we are now ready for a vote. The latest proposal can be found at the end of this email and at: http://wiki.apache.org/incubator/S4Proposal The discussion regarding the proposal can be found at: http://s.apache.org/RMU Please cast your votes: [ ] +1 Accept S4 for incubation [ ] +0 Indifferent to S4 incubation [ ] -1 Reject S4 for incubation This vote will close 72 hours from now. Thanks, Patrick -- = S4 Proposal = == Abstract == S4 (Simple Scalable Streaming System) is a general-purpose, distributed, scalable, partially fault-tolerant, pluggable platform that allows programmers to easily develop applications for processing continuous, unbounded streams of data. == Proposal == S4 is a software platform written in Java. Clients that send and receive events can be written in any programming language. S4 also includes a collection of modules called Processing Elements (or PEs for short) that implement basic functionality and can be used by application developers. In S4, keyed data events are routed with affinity to Processing Elements (PEs), which consume the events and do one or both of the following: (1) ''emit'' one or more events which may be consumed by other PEs, (2) ''publish'' results. The architecture resembles the Actors model, providing semantics of encapsulation and location transparency, thus allowing applications to be massively concurrent while exposing a simple programming interface to application developers. To drive adoption and increase the number of contributors to the project, we may need to prioritize the focus based on feedback from the community. We believe that one of the top priorities and driving design principle for the S4 project is to provide a simple API that hides most of the complexity associated with distributed systems and concurrency. The project grew out of the need to provide a flexible platform for application developers and scientists that can be used for quick experimentation and production. S4 differs from existing Apache projects in a number of fundamental ways. Flume is an Incubator project that focuses on log processing, performing lightweight processing in a distributed fashion and accumulating log data in a centralized repository for batch processing. S4 instead performs all stream processing in a distributed fashion and enables applications to form arbitrary graphs to process streams of events. We see Flume as a complementary project. We also expect S4 to complement Hadoop processing and in some cases to supersede it. Kafka is another Incubator project that focuses on processing large amounts of stream data. The design of Kafka, however, follows the pub-sub paradigm, which focuses on delivering messages containing arbitrary data from source processes (publishers) to consumer processes (subscribers). Compared to S4, Kafka is an intermediate step between data generation and processing, while S4 is itself a platform for processing streams of events. S4 overall addresses a need of existing applications to process streams of events beyond moving data to a centralized repository for batch processing. It complements the features of existing Apache projects, such as Hadoop, Flume, and Kafka, by providing a flexible platform for distributed event processing. == Background == S4 was initially developed at Yahoo! Labs starting in 2008 to process user feedback in the context of search advertising. The project was licensed under the Apache License version 2.0 in October 2010. The project documentation is currently available at http://s4.io . == Rationale == Stream computing has been growing steadily over the last 20 years. However, recently there has been an explosion in real-time data sources including the Web, sensor networks, financial securities analysis and trading, traffic monitoring, natural language processing of news and social data, and much more. As Hadoop evolved as a standard open source solution for batch processing of massive data sets, there is no equivalent community supported open source platform for processing data streams in real-time. While various research projects have evolved into proprietary commercial products, S4 has the potential to fill the gap. Many projects that require a scalable stream processing architecture currently use Hadoop by segmenting the input stream into data batches. This solution is not efficient, results in high latency, and introduces unnecessary complexity. The S4 design is
Re: [DISCUSS] DirectMemory to join the Apache Incubator
Oh I hope this gets into ASF. I mentioned DirectMemory on one of the Apache MLs the other day in the context of somebody at Facebook? or Cloudera? working on something very similar for another ASF project maybe HBase. Just mentioning it. Otis Sematext :: http://sematext.com/ :: Solr - Lucene - Nutch Lucene ecosystem search :: http://search-lucene.com/ From: Simone Tripodi simonetrip...@apache.org To: general@incubator.apache.org Sent: Tuesday, September 20, 2011 5:48 AM Subject: [DISCUSS] DirectMemory to join the Apache Incubator Hi all guys, I would like to propose DirectMemory, a Java OpenSource multi-layered cache implementation featuring off-heap memory storage (a-la Terracotta BigMemory) originally developed by Raffaele P. Guidi on GitHub[1], to be an Apache Incubator project. For those interested on knowing more about DirectMemory, you can read Raffaele's related blog[2]. Here's a link to the proposal in the Incubator wiki[3] where we started collecting all needed info. As you will note, the list of mentors is in need of some volunteers, so if you find this interesting, feel free to sign up or let us know you are interested :). Hope to read from you soon, thanks in advance and have a nice day! All the best, Simo [1] https://github.com/raffaeleguidi/DirectMemory [2] http://raffaeleguidi.wordpress.com/ [3] http://wiki.apache.org/incubator/DirectMemoryProposal http://people.apache.org/~simonetripodi/ http://www.99soft.org/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
September 2011 Incubator Board
The flood of Hadoop related projects continues with new Incubator projects: * HMS (now Ambari), a monitoring, administration and lifecycle management project for Apache Hadoop clusters * Accumulo, a sorted, distributed key/value store based on Google's BigTable design, and built on top of Hadoop, Zookeeper, and Thrift were voted to start Incubation, along with: * Kalumet, a complete environment manager and deployer including J2EE environments (application servers, applications, etc), softwares, and resources. Other projects under discussion: * S4 (Simple Scalable Streaming System), a general-purpose, distributed, scalable, partially fault-tolerant, pluggable platform that allows programmers to easily develop applications for processing continuous, unbounded streams of data. OGNL should be moving to Apache Commons. --- Ambari (was HMS) Ambari is monitoring, administration and lifecycle management project for Apache Hadoop clusters. * Incubating since 30 August 2011. * Changed name to Ambari over trademark concerns. * In process of moving onto Apache infrastructure: * Jira and subversion created. * Mailing lists requested (6 Sep), but not created. * Confluence requested (6 Sep), but not created * Committer accounts created. * Working on initial code import and code grant. BeanValidation Bean Validation was accepted into Incubator on 1 March 2010. The Bean Validation project is an implementation of the Java EE Bean Validation JSR303 specification. There are no other important issues open before a possible graduation. Actually the project is discussing its graduation as TLP or into Apache Commons, as natural successor of Commons Validator. Any issues that the Incubator PMC or ASF Board might wish/need to be aware of * none How has the community developed since the last report * Users community activity is stable, users slightly decreased the activity of filling issues on JIRA and asking questions, we suppose codebase/provided documentation start being mature enough to satisfy users needs. How has the project developed since the last report. * Started a 'extras' module development where putting validators not included in the JSR303 spec. * planning the development for implementing next JSR330 spec version. Bigtop Bigtop is a project for the development of native packaging and stack tests of the Hadoop ecosystem. Bigtop entered incubation on June 20, 2011. Primary issues blocking graduation: * Need for increased diversity and additional committers. * Incubating release including testing framework. * Incorporation of functional stack testing. Issues which Incubator PMC and/or ASF Board might need/wish to be aware of: * Due to limitations in available platforms on Apache Jenkins infrastructure and need for VM spin-up/spin-down for tests, we are working directly with OSUOSL on build/test setup. Community development since last report: * Community meetup held August 18th, with mentors and committers alike. Project development since last report: * 0.1.0-incubating released. * Website created. * Additional component project (Mahout) added. * Supported platforms voted on. * Initial implementation of package validation tests implemented and live. Deft Deft is a non-blocking, asynchronous, event driven high performance web framework running on the JVM. Issues before graduation * Project rename (Deft seems to be trademarked) * Put together a first incubation release * Find new committers The PPMC has discussed that we probably need to rename Deft. The reason for this is to avoid future complication because of trademarks associated with Deft. No significant change has been noticed regarding the Apache Deft community. The Apache Deft web page is up and running (still a lot of documentation to be done). Etch Etch was accepted into Incubator on 2 September 2008. Etch is a cross-platform, language- and transport-independent framework for building and consuming network services. The Etch toolset includes a network service description language, a compiler, and binding libraries for a variety of programming languages. - Etch binding-cpp is currently in development and some parts of the basic framework (OS abstraction layer, collection types, basic Etch components) are already implemented and available in the trunk - A new developer Martin Veith from the BMW Car IT provided a lot of patches and some documentation stuff - Fixed some smaller bugs in the C, Java and C# bindings - The new Apache Etch website is nearly complete http://etch.staging.apache.org/etch/ and will be migrated to the public area while the next weeks. A detailed Etch documentation will be converted afterwards (Docbook PDF and HTML) - Community ramp up a little bit and we hope to get a better grounding future tasks: - Prepare next release and publish it - Migrate to new Apache Etch CMS - Further development of the
RE: Accumulo incubator proposal: Statement of Concern
No... Knowing Noel, he was not opening anything. He was speaking to general principles about how the Incubator works. +1 --- Noel - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] S4 to join the Incubator
+1 (non-binding) On Tue, Sep 20, 2011 at 4:56 PM, Patrick Hunt ph...@apache.org wrote: It's been a nearly a week since the S4 proposal was submitted for discussion. A few questions were asked, and the proposal was clarified in response. Sufficient mentors have volunteered. I thus feel we are now ready for a vote. The latest proposal can be found at the end of this email and at: http://wiki.apache.org/incubator/S4Proposal The discussion regarding the proposal can be found at: http://s.apache.org/RMU Please cast your votes: [ ] +1 Accept S4 for incubation [ ] +0 Indifferent to S4 incubation [ ] -1 Reject S4 for incubation This vote will close 72 hours from now. Thanks, Patrick -- = S4 Proposal = == Abstract == S4 (Simple Scalable Streaming System) is a general-purpose, distributed, scalable, partially fault-tolerant, pluggable platform that allows programmers to easily develop applications for processing continuous, unbounded streams of data. == Proposal == S4 is a software platform written in Java. Clients that send and receive events can be written in any programming language. S4 also includes a collection of modules called Processing Elements (or PEs for short) that implement basic functionality and can be used by application developers. In S4, keyed data events are routed with affinity to Processing Elements (PEs), which consume the events and do one or both of the following: (1) ''emit'' one or more events which may be consumed by other PEs, (2) ''publish'' results. The architecture resembles the Actors model, providing semantics of encapsulation and location transparency, thus allowing applications to be massively concurrent while exposing a simple programming interface to application developers. To drive adoption and increase the number of contributors to the project, we may need to prioritize the focus based on feedback from the community. We believe that one of the top priorities and driving design principle for the S4 project is to provide a simple API that hides most of the complexity associated with distributed systems and concurrency. The project grew out of the need to provide a flexible platform for application developers and scientists that can be used for quick experimentation and production. S4 differs from existing Apache projects in a number of fundamental ways. Flume is an Incubator project that focuses on log processing, performing lightweight processing in a distributed fashion and accumulating log data in a centralized repository for batch processing. S4 instead performs all stream processing in a distributed fashion and enables applications to form arbitrary graphs to process streams of events. We see Flume as a complementary project. We also expect S4 to complement Hadoop processing and in some cases to supersede it. Kafka is another Incubator project that focuses on processing large amounts of stream data. The design of Kafka, however, follows the pub-sub paradigm, which focuses on delivering messages containing arbitrary data from source processes (publishers) to consumer processes (subscribers). Compared to S4, Kafka is an intermediate step between data generation and processing, while S4 is itself a platform for processing streams of events. S4 overall addresses a need of existing applications to process streams of events beyond moving data to a centralized repository for batch processing. It complements the features of existing Apache projects, such as Hadoop, Flume, and Kafka, by providing a flexible platform for distributed event processing. == Background == S4 was initially developed at Yahoo! Labs starting in 2008 to process user feedback in the context of search advertising. The project was licensed under the Apache License version 2.0 in October 2010. The project documentation is currently available at http://s4.io . == Rationale == Stream computing has been growing steadily over the last 20 years. However, recently there has been an explosion in real-time data sources including the Web, sensor networks, financial securities analysis and trading, traffic monitoring, natural language processing of news and social data, and much more. As Hadoop evolved as a standard open source solution for batch processing of massive data sets, there is no equivalent community supported open source platform for processing data streams in real-time. While various research projects have evolved into proprietary commercial products, S4 has the potential to fill the gap. Many projects that require a scalable stream processing architecture currently use Hadoop by segmenting the input stream into data batches. This solution is not efficient, results in high latency, and introduces unnecessary complexity. The S4 design is primarily driven by large scale applications for data mining and machine learning in a production environment. We think that the S4 design is
Re: [VOTE] S4 to join the Incubator
+1 (non-binding) +Vinod On Wed, Sep 21, 2011 at 2:26 AM, Patrick Hunt ph...@apache.org wrote: It's been a nearly a week since the S4 proposal was submitted for discussion. A few questions were asked, and the proposal was clarified in response. Sufficient mentors have volunteered. I thus feel we are now ready for a vote. The latest proposal can be found at the end of this email and at: http://wiki.apache.org/incubator/S4Proposal The discussion regarding the proposal can be found at: http://s.apache.org/RMU Please cast your votes: [ ] +1 Accept S4 for incubation [ ] +0 Indifferent to S4 incubation [ ] -1 Reject S4 for incubation This vote will close 72 hours from now. Thanks, Patrick -- = S4 Proposal = == Abstract == S4 (Simple Scalable Streaming System) is a general-purpose, distributed, scalable, partially fault-tolerant, pluggable platform that allows programmers to easily develop applications for processing continuous, unbounded streams of data. == Proposal == S4 is a software platform written in Java. Clients that send and receive events can be written in any programming language. S4 also includes a collection of modules called Processing Elements (or PEs for short) that implement basic functionality and can be used by application developers. In S4, keyed data events are routed with affinity to Processing Elements (PEs), which consume the events and do one or both of the following: (1) ''emit'' one or more events which may be consumed by other PEs, (2) ''publish'' results. The architecture resembles the Actors model, providing semantics of encapsulation and location transparency, thus allowing applications to be massively concurrent while exposing a simple programming interface to application developers. To drive adoption and increase the number of contributors to the project, we may need to prioritize the focus based on feedback from the community. We believe that one of the top priorities and driving design principle for the S4 project is to provide a simple API that hides most of the complexity associated with distributed systems and concurrency. The project grew out of the need to provide a flexible platform for application developers and scientists that can be used for quick experimentation and production. S4 differs from existing Apache projects in a number of fundamental ways. Flume is an Incubator project that focuses on log processing, performing lightweight processing in a distributed fashion and accumulating log data in a centralized repository for batch processing. S4 instead performs all stream processing in a distributed fashion and enables applications to form arbitrary graphs to process streams of events. We see Flume as a complementary project. We also expect S4 to complement Hadoop processing and in some cases to supersede it. Kafka is another Incubator project that focuses on processing large amounts of stream data. The design of Kafka, however, follows the pub-sub paradigm, which focuses on delivering messages containing arbitrary data from source processes (publishers) to consumer processes (subscribers). Compared to S4, Kafka is an intermediate step between data generation and processing, while S4 is itself a platform for processing streams of events. S4 overall addresses a need of existing applications to process streams of events beyond moving data to a centralized repository for batch processing. It complements the features of existing Apache projects, such as Hadoop, Flume, and Kafka, by providing a flexible platform for distributed event processing. == Background == S4 was initially developed at Yahoo! Labs starting in 2008 to process user feedback in the context of search advertising. The project was licensed under the Apache License version 2.0 in October 2010. The project documentation is currently available at http://s4.io . == Rationale == Stream computing has been growing steadily over the last 20 years. However, recently there has been an explosion in real-time data sources including the Web, sensor networks, financial securities analysis and trading, traffic monitoring, natural language processing of news and social data, and much more. As Hadoop evolved as a standard open source solution for batch processing of massive data sets, there is no equivalent community supported open source platform for processing data streams in real-time. While various research projects have evolved into proprietary commercial products, S4 has the potential to fill the gap. Many projects that require a scalable stream processing architecture currently use Hadoop by segmenting the input stream into data batches. This solution is not efficient, results in high latency, and introduces unnecessary complexity. The S4 design is primarily driven by large scale applications for data mining and machine learning in a production environment. We think that the S4
