Re: [VOTE] Accept Blur into the Apache Incubator
+1 On Sun, Jul 22, 2012 at 4:40 PM, Sajeevan Achuthan achuthan.sajee...@gmail.com wrote: +1 On 22 July 2012 14:40, Doug Cutting cutt...@gmail.com wrote: +1 Doug On Jul 20, 2012 9:43 AM, Aaron McCurry amccu...@gmail.com wrote: I would like to call a vote for accepting Blur for incubation in the Apache Incubator. The full proposal is available below. Please cast your vote: [ ] +1, bring Blur into Incubator [ ] +0, I don't care either way, [ ] -1, do not bring Blur into Incubator, because... This vote will be open for 72 hours and only votes from the Incubator PMC are binding. Thank you for your consideration! Aaron http://wiki.apache.org/incubator/BlurProposal = Blur Proposal = == Abstract == Blur is a search platform capable of searching massive amounts of data in a cloud computing environment. Blur leverages several existing Apache projects, including Apache Lucene, Apache Hadoop, Apache !ZooKeeper and Apache Thrift. Both bulk and near real time (NRT) updates are possible with Blur. Bulk updates are accomplished using Hadoop Map/Reduce and NRT are performed through direct Thrift calls. == Proposal == Blur is an open source search platform capable of querying massive amounts of data at incredible speeds. Rather than using the flat, document-like data model used by most search solutions, Blur allows you to build rich data models and search them in a semi-relational manner similar to joins while querying a relational database. Using Blur, you can get precise search results against terabytes of data at Google-like speeds. Blur leverages multiple open source projects including Hadoop, Lucene, Thrift and !ZooKeeper to create an environment where structured data can be transformed into an index that runs on a Hadoop cluster. Blur uses the power of Map/Reduce for bulk indexing into Blur. Server failures are handled automatically by using !ZooKeeper for cluster state and HDFS for index storage. == Background == Blur was created by Aaron !McCurry in 2010. Blur was developed to solve the challenges in dealing with searching huge quantities of data that the traditional RDBMS solutions could not cope with while still providing JOIN-like capabilities to query the data. Several other open source projects have implemented aspects of this design including elasticsearch, Katta and Apache Solr. == Rationale == There is a need for a distributed search capability within the Hadoop ecosystem. Currently, there are no other search solutions that natively leverage HDFS and the failover features of Hadoop in the same manner as the Blur project. The communities we expect to be most interested in such a project are government, health care, and other industries where scalability is a concern. We have made much progress in developing this project over the past 2 years and believe both the project and the interested communities would benefit from this work being openly available and having open development. In future versions of Blur the API will more closely follow the API’s provided in Lucene so that systems that already use Lucene can more easily scale with Blur. Blur can be viewed as a query execution engine that Lucene based solutions can utilize when scale becomes an issue. == Initial Goals == The initial goals of the project are: * To migrate the Blur codebase, issue tracking and wiki from github.com and integrate the project with the ASF infrastructure. * Add new committers to the project and grow the community in The Apache Way. == Current Status == === Meritocracy === Blur was initially developed by Aaron !McCurry in June 2010. Since then Blur has continued to evolve with the support of a small development team at Near Infinity. As a part of the Apache Software Foundation, the Apache Blur team intends to strongly encourage the community to help with and contribute to the project. Apache Blur will actively seek potential committers and help them become familiar with the codebase. === Community === A small community has developed around Blur and several project teams are currently using Blur for their big data search capability. The source code is currently available on GitHub and there is a dedicated website (blur.io) that provides an overview of the project. Blur has been shared with several members of the Apache community and has been presented at the Bay Area HUG (see http://www.meetup.com/hadoop/events/20109471/). === Core Developers === The current developers are employed by Near Infinity Corporation, but we anticipate interest developing among other companies. === Alignment === Blur is built on top of a number of Apache projects; Hadoop, Lucene, !ZooKeeper, and Thrift. It builds with Maven. During the course of Blur development, a couple of patches have been committed back to the Lucene project,
[RESULT] Re: [VOTE] retire zeta components from incubation
Here the results for retiring the zeta components podling. 6 binding +1 : Jukka Zitting, Bertrand Delacretaz, Ralph Goers, Julien Vermillard, Alan D. Cabrera, Matthew B. Franklin Julien On Sat, May 5, 2012 at 5:19 PM, Alan D. Cabrera l...@toolazydogs.com wrote: +1 binding Regards, Alan On May 3, 2012, at 1:12 AM, Julien Vermillard wrote: Hi, As discussed earlier the Zeta components community has voted to retire the project. Following the retirement guide [1], I now call the Incubator PMC to vote on confirming this decision. This vote is open for the next 72 hours. [ ] +1 Retire the Zeta components project [ ] -1 Do not retire the project, because ... [1] http://incubator.apache.org/guides/retirement.html Cheers, Julien -- Forwarded message -- From: Julien Vermillard jvermill...@gmail.com Date: Fri, Apr 20, 2012 at 3:05 PM Subject: [RESULT] Re: [VOTE] retire zeta components from incubation To: zeta-...@incubator.apache.org Cc: general@incubator.apache.org So let's close the vote : +1 binding : grobmeier, beberlei, derick, jpic, oms, rolandb, +0 binding : kore, toby -1 none So let's close this podling. Julien - 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: [VOTE] retire zeta components from incubation
Here my vote : +1 (binding) On Thu, May 3, 2012 at 2:36 PM, Ralph Goers ralph.go...@dslextreme.com wrote: +1 (binding) Ralph On May 3, 2012, at 1:12 AM, Julien Vermillard wrote: Hi, As discussed earlier the Zeta components community has voted to retire the project. Following the retirement guide [1], I now call the Incubator PMC to vote on confirming this decision. This vote is open for the next 72 hours. [ ] +1 Retire the Zeta components project [ ] -1 Do not retire the project, because ... [1] http://incubator.apache.org/guides/retirement.html Cheers, Julien -- Forwarded message -- From: Julien Vermillard jvermill...@gmail.com Date: Fri, Apr 20, 2012 at 3:05 PM Subject: [RESULT] Re: [VOTE] retire zeta components from incubation To: zeta-...@incubator.apache.org Cc: general@incubator.apache.org So let's close the vote : +1 binding : grobmeier, beberlei, derick, jpic, oms, rolandb, +0 binding : kore, toby -1 none So let's close this podling. Julien - 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
[VOTE] retire zeta components from incubation
Hi, As discussed earlier the Zeta components community has voted to retire the project. Following the retirement guide [1], I now call the Incubator PMC to vote on confirming this decision. This vote is open for the next 72 hours. [ ] +1 Retire the Zeta components project [ ] -1 Do not retire the project, because ... [1] http://incubator.apache.org/guides/retirement.html Cheers, Julien -- Forwarded message -- From: Julien Vermillard jvermill...@gmail.com Date: Fri, Apr 20, 2012 at 3:05 PM Subject: [RESULT] Re: [VOTE] retire zeta components from incubation To: zeta-...@incubator.apache.org Cc: general@incubator.apache.org So let's close the vote : +1 binding : grobmeier, beberlei, derick, jpic, oms, rolandb, +0 binding : kore, toby -1 none So let's close this podling. Julien - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [RESULT] Re: [VOTE] retire zeta components from incubation
On Sun, Apr 29, 2012 at 10:42 AM, Jukka Zitting jukka.zitt...@gmail.com wrote: Hi, On Fri, Apr 20, 2012 at 4:05 PM, Julien Vermillard jvermill...@gmail.com wrote: So let's close this podling. OK. See http://incubator.apache.org/guides/retirement.html for the process to follow, including the IPMC vote to make this official. Who'll take care of this cleanup? Hi, I seen this page, I'll do the duty but next week. Julien - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[RESULT] Re: [VOTE] retire zeta components from incubation
So let's close the vote : +1 binding : grobmeier, beberlei, derick, jpic, oms, rolandb, +0 binding : kore, toby -1 none So let's close this podling. Julien On Fri, Apr 13, 2012 at 10:30 AM, Julien Vermillard jvermill...@gmail.com wrote: Hi, Due to the reasons exposed later, and mainly due to lack of activity : [ ] +1 Retire the Zeta components project and move to another infra like github [ ] -1 Do not retire the project, because ... This vote is open for the next 72 hours. Julien - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Graduate ACE from the Apache Incubator
+1 binding On Friday, November 18, 2011, Alan D. Cabrera l...@toolazydogs.com wrote: +1 binding Regards, Alan On Nov 17, 2011, at 2:42 AM, Marcel Offermans wrote: In my opinion, ACE is ready to begin the process of graduating from the Apache Incubator to a Top Level Project. Since joining the incubator in in May 2009 we've added 4 new committers (12 in total now) from diverse organizations and did a release in May this year to demonstrate we follow the Apache guidelines. We've shown an ability to self-govern using accepted Apache practices and ACE continues to attract new contributors and users. The first step is to vote as a community, demonstrating that ACE is ready and willing to graduate. Once this vote is succesful we create a board resolution proposal or Charter and start a vote on the general incubator list. The full process is described at http://incubator.apache.org/guides/graduation.html#toplevel The vote is open for at least 72 hours. Greetings, Marcel - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [RESULT][VOTE] accept DirectMemory as new Apache Incubator podling
BTW my vote was binding :) On Wed, Oct 5, 2011 at 10:54 AM, Simone Tripodi simonetrip...@apache.org wrote: Good morning all guys, Since 72 hours passed I'm declaring this vote as closed and passed with the following resolution: 13 positive binding votes: * Christian Grobmeier * Jean-Baptiste Onofré * Tim Williams * Davanum Srinivas * Ralph Goers * Niklas Gustavsson * Sylvain Wallez * Chris Mattmann * Olivier Lamy * Tommaso Teofili * Anthony Elder * Arun C Murthy * Bertrand Delacretaz 3 positive members votes: * Simone Tripodi * Simone Gianni * Otis Gospodnetic 5 positive community votes: * Maurizio Cucchiara * Ashish * Joey Echeverria * Julien Vermillard * Vinod Kumar Vavilapalli Welcome DirectMemory to join the Apache Incubator! Thanks everybody take part to the proposal review and vote, have a nice day! All the best, Simo http://people.apache.org/~simonetripodi/ http://www.99soft.org/ On Tue, Oct 4, 2011 at 11:30 AM, Bertrand Delacretaz bdelacre...@apache.org wrote: On Sun, Oct 2, 2011 at 9:36 AM, Simone Tripodi simonetrip...@apache.org wrote: I'm now calling a formal VOTE on the DirectMemory proposal... +1 -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 - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] accept DirectMemory as new Apache Incubator podling
+1 (binding) On Sun, Oct 2, 2011 at 4:32 PM, Ralph Goers ralph.go...@dslextreme.com wrote: +1 (binding) Ralph On Oct 2, 2011, at 12:36 AM, Simone Tripodi wrote: Hi all guys, I'm now calling a formal VOTE on the DirectMemory proposal located here: http://wiki.apache.org/incubator/DirectMemoryProposal Proposal text copied at the bottom of this email. VOTE close on Tuesday, October 4, early 7:30 AM CET. Please VOTE: [ ] +1 Accept DirectMemory into the Apache Incubator [ ] +0 Don't care [ ] -1 Don't Accept DirectMemory into the Apache Incubator because... Thanks in advance for participating! All the best, have a nice day, Simo P.S. Here's my +1 http://people.apache.org/~simonetripodi/ http://www.99soft.org/ = DirectMemory = == Abstract == The following proposal is about Apache !DirectMemory, a Java !OpenSource multi-layered cache implementation featuring off-heap memory storage (a-la Terracotta !BigMemory) to enable caching of Java objects without degrading JVM performance == Proposal == !DirectMemory's main purpose is to to act as a second level cache (after a heap based one) able to store large amounts of data without filling up the Java heap and thus avoiding long garbage collection cycles. Although serialization has a runtime cost store/retrieve operations are in the sub-millisecond range being pretty acceptable in every usage scenario even as a first level cache and, most of all, outperforms heap storage when the count of the entries goes over a certain amount. !DirectMemory implements cache eviction based on a simple LFU (Least Frequently Used) algorythm and also on item expiration. Included in the box is a small set of utility classes to easily handle off-heap memory buffers. == Background == !DirectMemory is a project was born in the 2010 thanks to Raffaele P. Guidi initial effort under [[https://github.com/raffaeleguidi/!DirectMemory/|GitHub]] and already licensed under the Apache License 2.0. == Rationale == The rationale behind !DirectMemory is bringing off-heap caching to the open source world, empowering FOSS developers and products with a tool that enables breaking the heap barrier and override the JVM garbage collection mechanism collection - which could be useful in scenarios where RAM needs are over the usual limits (more than 8, 12, 24gb) and to ease usage of off-heap memory in general = Current Status = == Meritocracy == As a majority of the initial project members are existing ASF committers, we recognize the desirability of running the project as a meritocracy. We are eager to engage other members of the community and operate to the standard of meritocracy that Apache emphasizes; we believe this is the most effective method of growing our community and enabling widespread adoption. == Core Developers == In alphabetical order: * Christian Grobmeier grobmeier at apache dot org * Maurizio Cucchiara mcucchiara at apache dot org * Olivier Lamy olamy at apache dot org * Raffaele P. Guidi raffaele dot p dot guidi at gmail dot com * Simone Gianni simoneg at apache dot org * Simone Tripodi simonetripodi at apache dot org * Tommaso Teofili tommaso at apache dot org == Alignment == The purpose of the project is to develop and maintain !DirectMemory implementation that can be used by other Apache projects. = Known Risks = == Orphaned Products == !DirectMemory does not have any reported production usage, yet, but is getting traction with developers and being evaluated by potential users and thus the risks of it being orphaned are minimal == Inexperience with Open Source == All of the committers have experience working in one or more open source projects inside and outside ASF. == Homogeneous Developers == The list of initial committers are geographically distributed across the Europe with no one company being associated with a majority of the developers. Many of these initial developers are experienced Apache committers already and all are experienced with working in distributed development communities. == Reliance on Salaried Developers == To the best of our knowledge, none of the initial committers are being paid to develop code for this project. == Relationships with Other Apache Products == !DirectMemory fits naturally in the ASF because it could be successfully employed together with a large number of ASF products ranging from JCS - as a new cache region between the heap and indexed file ones, to ORM systems like Cayenne (i.e. replacing current OSCache based implementation), Apache JDO and JPA implementations and also java based databases (i.e. Derby) and all systems managing large amounts of data from Hadoop to Cassandra == A Excessive Fascination with the Apache Brand == While the Apache Software Foundation would be a good home for the !DirectMemory project it already has some traction and it could live on its own - however we see reciprocal benefits for both the ASF
Re: [VOTE] S4 to join the Incubator
+1 (binding) On Wed, Sep 21, 2011 at 12:05 PM, Flavio Junqueira f...@s4.io wrote: Thanks for pointing it out, Bertrand. I have just fixed it on the wiki. -Flavio On Sep 21, 2011, at 10:51 AM, Bertrand Delacretaz wrote: On Tue, Sep 20, 2011 at 10:56 PM, Patrick Hunt ph...@apache.org wrote: ...Please cast your votes: [ X] +1 Accept S4 for incubation ... * Matthieu Morel (mm at s4 dot io) * Anish Nair (an at s4 dot com)... Shouldn't that be s4 dot io instead? -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 - 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] Accumulo to join the Incubator
On Fri, Sep 9, 2011 at 6:22 PM, Doug Cutting cutt...@apache.org wrote: It's been a week since the Accumulo 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/AccumuloProposal The discussion regarding the proposal can be found at: http://s.apache.org/oi Please cast your votes: [ ] +1 Accept Accumulo for incubation [ ] +0 Indifferent to Accumulo incubation [ ] -1 Reject Accumulo for incubation +1 binding - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Deft for incubation
On Thu, Jul 7, 2011 at 4:17 PM, Alan D. Cabrera l...@toolazydogs.com wrote: It would be nice, very nice indeed, if this happened. It is not a MUST. :) Regards, Alan +1 :) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Deft to join the incubator
+1 (Binding) On Tue, Jul 5, 2011 at 12:35 PM, Niklas Gustavsson nik...@protocol7.com wrote: Hi, With three mentors graciously signed up and the discussion around the proposal settling, it's time for a vote on Deft joining the incubator. The latest proposal can be found below, or in the wiki: http://wiki.apache.org/incubator/DeftProposal For discussions: http://www.mail-archive.com/general@incubator.apache.org/msg29659.html Please cast your votes: [ ] +1 Accept Deft for incubation [ ] +0 Indifferent to Deft incubation [ ] -1 Reject Deft for incubation Vote will be running for 72 hours. /niklas = Deft Proposal = == Abstract == Deft is a non-blocking, asynchronous, event driven high performance web framework running on the JVM. == Proposal == Deft is a web framework that makes using it feel a bit like ordinary Java servlets, but with additional tools and optimizations to take advantage of the underlying non-blocking infrastructure. The framework is distinct from most mainstream Java web server frameworks because it is non-blocking and reasonably fast. It's ideal for real-time web services because it can support thousands of simultaneous idle connections. Key features: * Optimized for thousands of simultaneous connections * Using pure Java NIO (java.nio java.nio.channels) * Asynchronous (nonblocking I/O) * Event driven == Background == Deft was initially inspired by Facebook's (actually !FriendFeed's ) Tornado open source project. Tornado is written in python and was open sourced by Facebook September 2009. Deft was started in October 2010 by Roger Schildmeijer and Jim Petersson, since then, a number of other developers (from different parts of the world) have submitted patches to the project. External contributors have also been involved in the pre-commit review process that Deft has adopted from Apache Cassandra. Currently the project is hosted on github and has 134 watchers and 19 forks. == Rationale == The goals of the project are very much aligned with the goals of the Apache Software Foundation. i.e there is interest in (continuing to) foster a collaborative, consensus based development process, using an open and pragmatic software license, and a desire to create high quality software that leads the way in its field. == Initial Goals == Even though the basic functionality is in place we would like to see the following features included in future releases: * More third party libraries that works within Deft's IOLoop * Https support for the async http client * Optimized buffer usage in the async socket abstraction * Template engine * Chunked transfer-encoding * Websockets * Https support * Improved Http 1.1 compliance = Current Status = == Meritocracy == Deft has been an open source project since day one. The project has transformed from being primarily a two person led (and funded) project to one with a number of diverse participants. Any potentially controversial architecture change is discussed on the public mailing list. Development has been coordinated primarily through a mailing list, pull requests and with some IRC. == Community == Building an active open source community will be one of Deft's top priority. The amount of interest in the project from social networks (like twitter and github) and individual developers and users suggests a strong community will develop once the framework to support one is in place. Currently the Deft community exists out of the core developers, and the users integration Deft in an end-user products (the actual number is unknown). == Core Developers == * Roger Schildmeijer * Jim Petersson * Johnathan Meehan * Nicholas Whitehead * Séven Le Mesle Other contributors to the project include: William Edwards, Jacob Kristhammar, Rickard Böttcher, ilmich, 1730wang (Nemo), Khaled Essghaier, Mikael Piotrowski == Alignment == Deft is a web framework with a strong focus on speed and asynchronous principles. Some parts of Deft are a complex (especiallt the asynchronous parts) and it makes sense to have a supporting/developing community. Apache provides a solid base with established processes and rules to create such community. == Known Risks == === Inexperience with Open Source === The current code that has been developed for Deft is open sourced under the Apache 2.0 license. The majority of the initial developers of Deft are familiar with the Apache model for open-source development. === Orphaned Products === All participants are active users and contributors to open source. One of them (Roger Schildmeijer) has experience as a contributor on the Apache Cassandra open source project. === Homogeneous Developers === Deft's initial set of committers include people that have a strong JVM background, and are spread over a number of countries and different employers. === Reliance on Salaried Developers === None of the developers
Re: [PROPOSAL] Deft for incubation
On Mon, Jul 4, 2011 at 8:59 PM, Roger Schildmeijer schildmei...@gmail.com wrote: Hi again, Been examining the asyncweb project in more details (atleast the asyncweb.client and asyncwebserver components). Below is my notes (simple draft). asyncweb notes -client module * https support for Deft's AHC (AsynchronousHttpClient) could borrow some details from asyncweb (o.a.asyncweb.client.SimpleTrustManagerFactory) * Improve the http request decoding (org.apache.ahc.codec.HttpDecoder, eg. decode[line, status, header, cookie]) -server module * like the simple and elegant design of o.a.asyncweb.server.resolver.ServiceResolver (and its concrete impl., eg. PatternMatchResolver (comparable to Deft's Capturing groups) and ExactMatchURIServiceResolver) * o.a.asyncweb.server.HttpClientListener (interface with callbacks clientDisconnected, clientIdle, register listeners on HttpServiceContext). I like the idea. Useful for comet/longpoll (could be worth to add to Deft). Conclusion: Ofcourse there are overlaps between the two projects. I agree with Emanuel Emmanuel Lécharny regarding that It's almost as difficult to write from scratch some piece of code than to reuse some other with lost support... Deft is built (tightly integrated) around the event-loop (org.deftserver.io.IOLoop) which the modules (e.g the web server component and the async http client) heavily depend upon. Asyncweb is built on top of the Apache MINA network framework and to merge these two project (Asyncweb and deft) is non trivial, therefor I propose we don't. Also, I guess asyncweb was abandoned for a reason? Took a look at Deft, I know well AsyncWeb, and the two projects are really similar. AsyncWeb was abandoned for some weird community issues (the merge of MINA and AsyncWeb communities was badly managed) and because it's much funnier to redo an HTTP from scratch than taking back and abandoned project :) We are currently recoding MINA from scratch (v3.0) so we can share ideas about asynchronous API for network operations, perf tests, etc.. I think the two projects should stay in touch and share background ideas. Julien - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept OpenOffice.org for incubation
+1 (binding) On Sat, Jun 11, 2011 at 6:44 AM, ant elder ant.el...@gmail.com wrote: I'm an Incubator PMC member so have a binding vote, but I'm also an IBM employee, on this vote I abstain. ...ant On Fri, Jun 10, 2011 at 5:02 PM, Sam Ruby ru...@intertwingly.net wrote: *** Please change your Subject: line for any [DISCUSSION] of this [VOTE] As the discussions on the OpenOfficeProposal threads seem to be winding down, I would like to initiate the vote to accept OpenOffice.org as an Apache Incubator project. At the end of this mail, I've put a copy of the current proposal. Here is a link to the document in the wiki: http://wiki.apache.org/incubator/OpenOfficeProposal?action=recallrev=207 As the proposal discussion threads are numerous, I encourage people to scan and review the archives for this month: http://mail-archives.apache.org/mod_mbox/incubator-general/201106.mbox/browser Please cast your votes: [ ] +1 Accept OpenOffice.org for incubation [ ] +0 Indifferent to OpenOffice.org incubation [ ] -1 Reject OpenOffice.org for incubation This vote will close 72 hours from now. - Sam Ruby = OpenOffice.org - An open productivity environment = == Abstract == !OpenOffice.org is comprised of six personal productivity applications: a word processor (and its web-authoring component), spreadsheet, presentation graphics, drawing, equation editor, and database. !OpenOffice.org is released on Windows, Solaris, Linux and Macintosh operation systems, with more [[http://porting.openoffice.org/|communities]] joining, including a mature [[http://porting.openoffice.org/freebsd/|FreeBSD port]]. !OpenOffice.org is localized, supporting over 110 languages worldwide. == Proposal == Apache !OpenOffice.org will continue the mission pursued by the !OpenOffice.org project while under the sponsorship of Sun and Oracle, namely: To create, as a community, the leading international office suite that will run on all major platforms and provide access to all functionality and data through open-component based APIs and an XML-based file format. In addition to to building the !OpenOffice.org product, as an end-user facing product with many existing individual and corporate users, this project will also be active in supporting end-users via tutorials, user forums, document template repositories, etc. The project will also work to further enable !OpenOffice.org to be used as a programmable module in document automation scenarios. == Background == !OpenOffice.org was launched as an open source project by Sun Microsystems in June 2000. !OpenOffice.org was originally developed under the name of StarOffice by Star Division, a German company, which was acquired by Sun Microsystems in 1999. Sun released this as open source in 2000. !OpenOffice.org is the leading alternative to MS-Office available. Its most recent major version, the 3.x series saw over [[http://www.webmasterpro.de/portal/news/2010/02/05/international-openoffice-market-shares.html|100 million downloads]] in its first year. The [[http://www.webmasterpro.de/portal/news/2010/02/05/international-openoffice-market-shares.html|most recent estimates]] suggest a market share on the order of 8-15%. The !OpenOffice source is written in C++ and delivers language-neutral and scriptable functionality. This source technology introduces the next-stage architecture, allowing use of the suite elements as separate applications or as embedded components in other applications. Numerous other features are also present including XML-based file formats based on the vendor-neutral !OpenDocument Format (ODF) standard from OASIS and other resources. == Rationale == !OpenOffice.org core development would continue at Apache following the contribution by Oracle, in accordance with Apache bylaws and its usual open development processes. Both Oracle and ASF agree that the !OpenOffice.org development community, previously fragmented, would re-unite under ASF to ensure a stable and long term future for OpenOffice.org. ASF would enable corporate, non-profit, and volunteer stakeholders to contribute code in a collaborative fashion. Supporting tooling projects will accompany the !OpenOffice.org contribution, providing APIs for extending and customizing !OpenOffice.org. Both !OpenOffice.org and the related tooling projects support the OASIS Open Document Format, and will attract an ecosystem of developers, ISVs and Systems Integrators. ODF ensures the users of !OpenOffice.org and related solutions will own their document data, and be free to choose the application or solution that best meets their requirements. The !OpenOffice.org implementation will serve as a reference implementation of the Open Document Format standard. = Current Status = == Meritocracy == We understand the intention and value of meritocracy at Apache. We are particularly gratified to learn, during the discussion on this proposal, that
Re: [VOTE] Accept Sqoop for Incubation
+1 (binding), Agreeing with Chris, looks awesome ! On Wed, Jun 8, 2011 at 5:39 AM, arv...@cloudera.com arv...@cloudera.com wrote: As there are no active discussions on the [PROPOSAL] thread for a few days now, I will like to initiate the vote to accept Sqoop as an Apache Incubator project. The proposal discussion thread and full text of the proposal can be found at the following locations: Discussion Thread: http://www.mail-archive.com/general@incubator.apache.org/msg27726.html Proposal: http://wiki.apache.org/incubator/SqoopProposal Please cast your votes: [ ] +1 Accept Sqoop for incubation [ ] +0 Indifferent to Sqoop incubation [ ] -1 Reject Sqoop for incubation This vote will close 72 hours from now. Thanks and Regards, Arvind Prabhakar - 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] Flume to join the Incubator.
+1 (binding) and good luck :) On Wed, Jun 8, 2011 at 1:22 PM, Sanjiva Weerawarana sanj...@opensource.lk wrote: +1 (non-binding). On Wed, Jun 8, 2011 at 10:08 AM, Jonathan Hsieh j...@cloudera.com wrote: Hi all, Since there have been no new conversations on this Flume [PROPOSAL] thread, I'd like to call a vote. At the end of this mail, I've put a copy of the current proposal. Here is a link to the document in the wiki: http://wiki.apache.org/incubator/FlumeProposal And here is a link to the discussion thread: http://www.mail-archive.com/general@incubator.apache.org/msg27722.html Please cast your votes: [ ] +1 Accept Flume for incubation [ ] +0 Indifferent to Flume incubation [ ] -1 Reject Flume for incubation This vote will close 72 hours from now. Thanks, Jon. = Flume - A Distributed Log Collection System = == Abstract == Flume is a distributed, reliable, and available system for efficiently collecting, aggregating, and moving large amounts of log data to scalable data storage systems such as Apache Hadoop's HDFS. == Proposal == Flume is a distributed, reliable, and available system for efficiently collecting, aggregating, and moving large amounts of log data from many different sources to a centralized data store. Its main goal is to deliver data from applications to Hadoop’s HDFS. It has a simple and flexible architecture for transporting streaming event data via flume nodes to the data store. It is robust and fault-tolerant with tunable reliability mechanisms that rely upon many failover and recovery mechanisms. The system is centrally configured and allows for intelligent dynamic management. It uses a simple extensible data model that allows for lightweight online analytic applications. It provides a pluggable mechanism by which new sources, destinations, and analytic functions which can be integrated within a Flume pipeline. == Background == Flume was initially developed by Cloudera to enable reliable and simplified collection of log information from many distributed sources. It was later open-sourced by Cloudera on GitHub as an Apache 2.0 licensed project in June 2010. During this time Flume has been formally released five times as versions 0.9.0 (June 2010), 0.9.1 (Aug 2010), 0.9.1u1 (Oct 2010), 0.9.2 (Nov 2010), and 0.9.3 (Feb 2011). These releases are also distributed by Cloudera as source and binaries along with enhancements as part of Cloudera Distribution including Apache Hadoop (CDH). == Rationale == Collecting log information in a data center in a timely, reliable, and efficient manner is a difficult challenge but important because when aggregated and analyzed, log information can yield valuable business insights. We believe that users and operators need a manageable systematic approach for log collection that simplifies the creation, the monitoring, and the administration of reliable log data pipelines. Oftentimes today, this collection is attempted by periodically shipping data in batches and by using potentially unreliable and inefficient ad-hoc methods. Log data is typically generated in various systems running within a data center that can range from a few machines to hundreds of machines. In aggregate, the data acts like a large-volume continuous stream with contents that can have highly-varied format and highly-varied content. The volume and variety of raw log data makes Apache Hadoop's HDFS file system an ideal storage location before the eventual analysis. Unfortunately, HDFS has limitations with regards to durability as well as scaling limitations when handling a large number of low-bandwidth connections or small files. Similar technical challenges are also suffered when attempting to write data to other data storage services. Flume addresses these challenges by providing a reliable, scalable, manageable, and extensible solution. It uses a streaming design for capturing and aggregating log information from varied sources in a distributed environment and has centralized management features for minimal configuration and management overhead. == Initial Goals == Flume is currently in its first major release with a considerable number of enhancement requests, tasks, and issues recorded towards its future development. The initial goal of this project will be to continue to build community in the spirit of the Apache Way, and to address the highly requested features and bug-fixes towards the next dot release. Some goals include: * To stand up a sustaining Apache-based community around the Flume codebase. * Implementing core functionality of a usable highly-available Flume master. * Performance, usability, and robustness improvements. * Improving the ability to monitor and diagnose problems as data is transported. * Providing a centralized place for contributed connectors and related projects. = Current Status = == Meritocracy == Flume was
Re: [italo.vign...@documentfoundation.org: Re: OpenOffice and the ASF]
On Sun, Jun 5, 2011 at 6:11 AM, Shane Curcuru a...@shanecurcuru.org wrote: Louis Suarez-Potts wrote: ...snip... * Apache Foundation owns the trademark to OOo? ...snip... The ASF has a recorded Software Grant that includes the trademark along with a specific list of source code files. I have not yet seen the specific grant of the trademark itself at the ASF yet (i.e. legal documents officially transferring ownership within the USPTO here in the US). As best I understand, the ASF does not currently own the trademark, but the intent of both Oracle and the ASF is that the trademark will be transferred to the ASF once the appropriate legal paperwork is completed. I presume, and will follow up, to ensure this includes the graphical logo with the seagulls. Question: is anyone here aware of any registrations of OpenOffice.org or the logo or other related marks in other countries besides the US? - Shane Curcuru VP, Brand Management, The Apache Software Foundation http://www.apache.org/foundation/marks/ For those interested: http://tarr.uspto.gov/servlet/tarr?regser=serialentry=78581289 http://tarr.uspto.gov/servlet/tarr?regser=serialentry=77021413 Hi I found it in the E.U. database, look like it's registered (with the logo). You can check there searching openoffice (can't paste result url..) : http://tmview.europa.eu/tmview/basicSearch.html http://oami.europa.eu/CTMOnline/RequestManager/en_SearchBasic Julien - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Recuse as mentor?
On Sat, Jun 4, 2011 at 9:31 AM, Christian Grobmeier grobme...@gmail.com wrote: If people want, I will happily remove myself as mentor. This is supposed to be fun and at least *somewhat* fulfilling... I consider you an very important part of this process. Even when you have said something wrong or have made a wrong decision (i don't know one) you are still doing a great job. It is a very hot discussion with tons of e-mails and mistakes do happen. Others do their mistakes too. Speaking for myself, I am very glad you have this role and would kindly ask you to continue. Cheers Christian +1 Nothing to add :) Julien - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: OpenOffice.org Apache Incubator Proposal: Splitting^H^H^H^H^H^H^H^H^HREUNITING the Community?
On Saturday, June 4, 2011, Florian Effenberger flo...@documentfoundation.org wrote: Hi Robert, I'm still reading a few messages and trying to reply to them, but wanted to join in here: Robert Burrell Donkin wrote on 2011-06-04 09.14: The TDF is in no position to accept a major donation of either copyright or code today. Apache is. Why? Can you elaborate? In short : taxes (US taxes) saving donnating stuff to non profit org. Julien - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Kitty to Enter the Incubator
+1 - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept Zeta Components into the incubator
Here my +1 On Mon, May 17, 2010 at 8:37 PM, Bertrand Delacretaz bdelacre...@apache.org wrote: On Mon, May 17, 2010 at 7:22 PM, Tobias Schlitt tob...@schlitt.info wrote: ...Please vote on the acceptance of Zeta Components for incubation at the Apache Incubator... +1, bring Zeta into Incubator -Bertrand BTW, very happy to see a project name starting with Z, we'll have the whole alphabet now ;-) - 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: Zeta proposal - Next steps
On Fri, May 7, 2010 at 6:57 PM, Christian Grobmeier grobme...@gmail.com wrote: Sorry according to http://incubator.apache.org/incubation/Incubation_Policy.html#Mentor he should be in the Incubator PMC. ah, sorry, I misread this paragraph. I thought only 1 mentor must be a member of the IPMC. Christian is not an ASF member, but applied also for becoming an IPMC member. I have no feedback so far from the IPMC. If this doesn't change I cannot help on mentoring - but I will enjoy helping on the mailing list and such. Looks like there is a lot of latency from the IPMC. Julien - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Call for mentors: Zeta Components
On Sat, May 1, 2010 at 1:56 PM, Bertrand Delacretaz bdelacre...@apache.org wrote: Hi, On Sat, May 1, 2010 at 1:16 PM, Daniel S. Haischt daniel.hais...@googlemail.com wrote: ...Btw, in the first place you confused me a bit using the term member but pointing to the committers list :) ASF members are called out here - http://www.apache.org/foundation/members.html ASF committers are called out here - http://people.apache.org/committers.html Ah sorry - I usually use Jim's list where members are shown in bold, not sure if the other one is updated as often as Jim's (but members don't change that often, granted). Can every committer become a mentor of a podling? From the roles responsibilities document I read this All Mentors must be members of the Incubator PMC In general and IMO the Incubator PMC requires at least one member and one experienced mentor (who can be the same person) for a new podling. Committers can be Incubator PMC members, but that's not an ideal situation, IIRC because committers don't have access to some foundation information - maybe someone can explain more, I don't remember the details here. That being said, if you'd like to be a member and you're an experienced committer, feel free to apply. It can take up to 1-2 weeks for the Incubator PMC to answer I think, as we usually do a bit of research on the candidates ASF-wide or other experience. -Bertrand I was contacted by a Zeta components contributor, I'm no experienced mentor, but I'm ASF member. I can help mentoring if needed. Julien - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
