Re: [VOTE] Apache Spark for the Incubator
+1 (binding) Greetings, Marcel - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept Apache MetaModel into the Apache incubator
+1 (binding) Good luck guys! Greetings, Marcel - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Apache Spark for the Incubator
On Sat, Jun 8, 2013 at 4:55 PM, Mattmann, Chris A (398J) wrote: > Note: we discussed adding Roman before the VOTE and it was > fine with the incoming Spark community, so Roman is now on > the wiki for the proposal. > > In case this changes anyone's VOTE on the VOTE thread, feel > free to speak up or change your VOTE. Otherwise, nothing else > to see here folks. +1 for the original proposal. +0.9 for the new proposal. Yes, I expect you to tally my vote that way. :) Next time, please be more careful when starting a VOTE and please don't change the proposal text in the middle of a vote. Personnel issues in proposals have caused significant problems in the past. That's unlikely to happen in this case, but I want to register my protest now because it might save us hundreds or thousands of emails in the future. Good luck, Spark! Marvin Humphrey - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Apache Spark for the Incubator
+1 (non binding)... This is great news!. thanks, Thilina On Sat, Jun 8, 2013 at 10:50 PM, Alan Cabrera wrote: > +1 binding > > > Regards, > Alan > > On Jun 7, 2013, at 10:34 PM, "Mattmann, Chris A (398J)" < > chris.a.mattm...@jpl.nasa.gov> wrote: > > > Hi Folks, > > > > OK discussion has died down, time to VOTE to accept Spark into the > > Apache Incubator. I'll let the VOTE run for at least a week. > > > > So far I've heard +1s from the following folks, so no need for them > > to VOTE again unless they want to change their VOTE: > > > > +1 > > > > Chris Mattmann* > > Konstantin Boudnik > > Henry Saputra* > > Reynold Xin > > Pei Chen > > Roman Shaposhnik* > > Suresh Marru* > > > > * -indicates IPMC > > > > [ ] +1 Accept Spark into the Apache Incubator. > > [ ] +0 Don't care. > > [ ] -1 Don't accept Spark into the Apache Incubator because.. > > > > Proposal text is below. > > > > === Abstract === > > Spark is an open source system for large-scale data analysis on clusters. > > > > === Proposal === > > Spark is an open source system for fast and flexible large-scale data > > analysis. Spark provides a general purpose runtime that supports > > low-latency execution in several forms. These include interactive > > exploration of very large datasets, near real-time stream processing, and > > ad-hoc SQL analytics (through higher layer extensions). Spark interfaces > > with HDFS, HBase, Cassandra and several other storage storage layers, and > > exposes APIs in Scala, Java and Python. > > Background > > Spark started as U.C. Berkeley research project, designed to efficiently > > run machine learning algorithms on large datasets. Over time, it has > > evolved into a general computing engine as outlined above. Spark¹s > > developer community has also grown to include additional institutions, > > such as universities, research labs, and corporations. Funding has been > > provided by various institutions including the U.S. National Science > > Foundation, DARPA, and a number of industry sponsors. See: > > https://amplab.cs.berkeley.edu/sponsors/ for full details. > > > > === Rationale === > > As the number of contributors to Spark has grown, we have sought for a > > long-term home for the project, and we believe the Apache foundation > would > > be a great fit. Spark is a natural fit for the Apache foundation: Spark > > already interoperates with several existing Apache projects (HDFS, HBase, > > Hive, Cassandra, Avro and Flume to name a few). The Spark team is > familiar > > with the Apache process and and subscribes to the Apache mission - the > > team includes multiple Apache committers already. Finally, joining Apache > > will help coordinate the development effort of the growing number of > > organizations which contribute to Spark. > > > > == Initial Goals == > > The initial goals will most likely be to move the existing codebase to > > Apache and integrate with the Apache development process. Furthermore, we > > plan for incremental development, and releases along with the Apache > > guidelines. > > > > === Current Status === > > == Meritocracy == > > The Spark project already operates on meritocratic principles. Today, > > Spark has several developers and has accepted multiple major patches from > > outside of U.C. Berkeley. While this process has remained mostly informal > > (we do not have an official committer list), an implicit organization > > exists in which individuals who contribute major components act as > > maintainers for those modules. If accepted, the Spark project would > > include several of these participants as committers from the onset. We > > will work to identify all committers and PPMC members for the project and > > to operate under the ASF meritocratic principles. > > > > === Community === > > Acceptance into the Apache foundation would bolster the already strong > > user and developer community around Spark. That community includes dozens > > of contributors from several institutions, a meetup group with several > > hundred members, and an active mailing list composed of hundreds of > users. > > Core Developers > > The core developers of our project are listed in our contributors and > > initial PPMC below. Though many exist at UC Berkeley, there is a > > representative cross sampling of other organizations including > Quantifind, > > Microsoft, Yahoo!, ClearStory Data, Bizo, Intel, Tagged and Webtrends. > > > > > > === Alignment === > > Our proposed effort aligns with several ongoing BIGDATA and U.S. National > > priority funding interests including the NSF and its Expeditions program, > > and the DARPA XDATA project. Our industry partners and collaborators are > > well aligned with our code base. > > > > There are also a number of related Apache projects and dependencies, that > > will be mentioned in the Relationships with Other Apache products > section. > > > > == Known Risks == > > > > === Orphaned Products === > > Given the current level of investment in Spark - the risk
Re: [VOTE] Accept Apache MetaModel into the Apache incubator
+1 - binding Regards, Alan On Jun 6, 2013, at 3:30 PM, Henry Saputra wrote: > Hi All, > > I'd like to call a VOTE for acceptance of MetaModel into the Apache > incubator. > The vote will close on June 12, 2013 at 6:00 PM (PST). > > [] +1 Accept MetaModel into the Apache incubator > [] +0 Don't care. > [] -1 Don't accept MetaModel into the incubator because... > > Full proposal is pasted at the bottom on this email, and the corresponding > wiki > is: > http://wiki.apache.org/incubator/MetaModelProposal. > > Only VOTEs from Incubator PMC members are binding, but all are welcome to > express their thoughts. > > Thanks, > > Henry Saputra > Champion for Apache MetaModel > > > P.S. Here's my +1 (binding) > > > - > > = MetaModel – uniform data access across datastores = > > Proposal for Apache Incubator > > == Abstract == > > MetaModel is a data access framework, providing a common interface for > exploration and querying of different types of datastores. > > == Proposal == > > MetaModel provides a uniform meta-model for exploring and querying the > structure of datastores, covering but not limited to relational databases, > various data file formats, NoSQL databases, Salesforce.com, SugarCRM and > more. The scope of the project is to stay domain-agnostic, so the > meta-model will be concerned with schemas, tables, columns, rows, > relationships etc. > > On top of this meta-model a rich querying API is provided which resembles > SQL, but built using compiler-checked Java language constructs. For > datastores that do not have a native SQL-compatible query engine, the > MetaModel project also includes an abstract Java-based query engine > implementation which individual datastore-modules can adapt to fit the > concrete datastore. > > === Background === > > The MetaModel project was initially developed by eobject.dk to service the > DataCleaner application (http://datacleaner.org). The main requirement was > to perform data querying and modification operations on a wide range of > quite different datastores. Furthermore a programmatic query model was > needed in order to allow different components to influence the query plan. > > In 2009, Human Inference acquired the eobjects projects including > MetaModel. Since then MetaModel has been put to extensive use in the Human > Inference products. The open source nature of the project was reinforced, > leading to a significant growth in the community. > > MetaModel has successfully been used in a number of other open source > projects as well as mission critical commercial software from Human > Inference. Currently MetaModel is hosted at http://metamodel.eobjects.org. > > === Rationale === > > Different types of datastores have different characteristics, which always > lead to the interfaces for these being different from one another. > Standards like JDBC and the SQL language attempt to standardize data > access, but for some datastore types like flat files, spreadsheets, NoSQL > databases and more, such standards are not even implementable. > > Specialization in interfaces obviously has merit for optimized usage, but > for integration tools, batch applications and or generic data modification > tools, this myriad of specialized interfaces is a big pain. Furthermore, > being able to query every datastore with a basic set of SQL-like features > can be a great productivity boost for a wide range of applications. > > === Initial goals === > > MetaModel is already a stable project, so initial goals are more oriented > towards an adaption to the Apache ecosystem than about functional changes. > > We are constantly adding more datastore types to the portfolio, but the > core modules have not had drastic changes for some time. > > Our focus will be on making ties with other Apache projects (such as POI, > Gora, HBase and CouchDB) and potentially renaming the ‘MetaModel’ project > to something more rememberable. > This includes comply with Apache Software Foundation license for third > party dependencies. > > == Current status == > > === Meritocracy === > > We intend to do everything we can to encourage a meritocracy in the > development of MetaModel. Currently most important development and design > decisions have been made at Human Inference, but with an open window for > anyone to participate on mailing lists and discussion forums. We believe > that the approach going forward should be more encouraging by sharing all > the design ideas and discussions in the open, not only just the topics that > have been “dragged” into the open by third parties. We believe that > meritocracy will be further stimulated by granting the control of the > project to an independent committee. > > === Community === > > The community around MetaModel already exists, but we believe it will grow > substantially by becoming an Apache project. With MetaModel used in a wide > range of both open and closed source appli
Re: [VOTE] Apache Spark for the Incubator
+1 binding Regards, Alan On Jun 7, 2013, at 10:34 PM, "Mattmann, Chris A (398J)" wrote: > Hi Folks, > > OK discussion has died down, time to VOTE to accept Spark into the > Apache Incubator. I'll let the VOTE run for at least a week. > > So far I've heard +1s from the following folks, so no need for them > to VOTE again unless they want to change their VOTE: > > +1 > > Chris Mattmann* > Konstantin Boudnik > Henry Saputra* > Reynold Xin > Pei Chen > Roman Shaposhnik* > Suresh Marru* > > * -indicates IPMC > > [ ] +1 Accept Spark into the Apache Incubator. > [ ] +0 Don't care. > [ ] -1 Don't accept Spark into the Apache Incubator because.. > > Proposal text is below. > > === Abstract === > Spark is an open source system for large-scale data analysis on clusters. > > === Proposal === > Spark is an open source system for fast and flexible large-scale data > analysis. Spark provides a general purpose runtime that supports > low-latency execution in several forms. These include interactive > exploration of very large datasets, near real-time stream processing, and > ad-hoc SQL analytics (through higher layer extensions). Spark interfaces > with HDFS, HBase, Cassandra and several other storage storage layers, and > exposes APIs in Scala, Java and Python. > Background > Spark started as U.C. Berkeley research project, designed to efficiently > run machine learning algorithms on large datasets. Over time, it has > evolved into a general computing engine as outlined above. Spark¹s > developer community has also grown to include additional institutions, > such as universities, research labs, and corporations. Funding has been > provided by various institutions including the U.S. National Science > Foundation, DARPA, and a number of industry sponsors. See: > https://amplab.cs.berkeley.edu/sponsors/ for full details. > > === Rationale === > As the number of contributors to Spark has grown, we have sought for a > long-term home for the project, and we believe the Apache foundation would > be a great fit. Spark is a natural fit for the Apache foundation: Spark > already interoperates with several existing Apache projects (HDFS, HBase, > Hive, Cassandra, Avro and Flume to name a few). The Spark team is familiar > with the Apache process and and subscribes to the Apache mission - the > team includes multiple Apache committers already. Finally, joining Apache > will help coordinate the development effort of the growing number of > organizations which contribute to Spark. > > == Initial Goals == > The initial goals will most likely be to move the existing codebase to > Apache and integrate with the Apache development process. Furthermore, we > plan for incremental development, and releases along with the Apache > guidelines. > > === Current Status === > == Meritocracy == > The Spark project already operates on meritocratic principles. Today, > Spark has several developers and has accepted multiple major patches from > outside of U.C. Berkeley. While this process has remained mostly informal > (we do not have an official committer list), an implicit organization > exists in which individuals who contribute major components act as > maintainers for those modules. If accepted, the Spark project would > include several of these participants as committers from the onset. We > will work to identify all committers and PPMC members for the project and > to operate under the ASF meritocratic principles. > > === Community === > Acceptance into the Apache foundation would bolster the already strong > user and developer community around Spark. That community includes dozens > of contributors from several institutions, a meetup group with several > hundred members, and an active mailing list composed of hundreds of users. > Core Developers > The core developers of our project are listed in our contributors and > initial PPMC below. Though many exist at UC Berkeley, there is a > representative cross sampling of other organizations including Quantifind, > Microsoft, Yahoo!, ClearStory Data, Bizo, Intel, Tagged and Webtrends. > > > === Alignment === > Our proposed effort aligns with several ongoing BIGDATA and U.S. National > priority funding interests including the NSF and its Expeditions program, > and the DARPA XDATA project. Our industry partners and collaborators are > well aligned with our code base. > > There are also a number of related Apache projects and dependencies, that > will be mentioned in the Relationships with Other Apache products section. > > == Known Risks == > > === Orphaned Products === > Given the current level of investment in Spark - the risk of the project > being abandoned is minimal. There are several constituents who are highly > incentivized to continue development. The U.C. Berkeley AMPLab relies on > Spark as a platform for a large number of long-term research projects. > Several companies have build verticalized products which are tightly > dependent on Spark. Other companies have dev
Re: June report
I'm off by a week. No buttoning until next week. On Fri, Jun 7, 2013 at 7:00 PM, Benson Margulies wrote: > I'll button it up in the middle of tomorrow some time. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Apache Spark for the Incubator
+1 (binding) Ralph On Jun 7, 2013, at 10:34 PM, Mattmann, Chris A (398J) wrote: > Hi Folks, > > OK discussion has died down, time to VOTE to accept Spark into the > Apache Incubator. I'll let the VOTE run for at least a week. > > So far I've heard +1s from the following folks, so no need for them > to VOTE again unless they want to change their VOTE: > > +1 > > Chris Mattmann* > Konstantin Boudnik > Henry Saputra* > Reynold Xin > Pei Chen > Roman Shaposhnik* > Suresh Marru* > > * -indicates IPMC > > [ ] +1 Accept Spark into the Apache Incubator. > [ ] +0 Don't care. > [ ] -1 Don't accept Spark into the Apache Incubator because.. > > Proposal text is below. > > === Abstract === > Spark is an open source system for large-scale data analysis on clusters. > > === Proposal === > Spark is an open source system for fast and flexible large-scale data > analysis. Spark provides a general purpose runtime that supports > low-latency execution in several forms. These include interactive > exploration of very large datasets, near real-time stream processing, and > ad-hoc SQL analytics (through higher layer extensions). Spark interfaces > with HDFS, HBase, Cassandra and several other storage storage layers, and > exposes APIs in Scala, Java and Python. > Background > Spark started as U.C. Berkeley research project, designed to efficiently > run machine learning algorithms on large datasets. Over time, it has > evolved into a general computing engine as outlined above. Spark¹s > developer community has also grown to include additional institutions, > such as universities, research labs, and corporations. Funding has been > provided by various institutions including the U.S. National Science > Foundation, DARPA, and a number of industry sponsors. See: > https://amplab.cs.berkeley.edu/sponsors/ for full details. > > === Rationale === > As the number of contributors to Spark has grown, we have sought for a > long-term home for the project, and we believe the Apache foundation would > be a great fit. Spark is a natural fit for the Apache foundation: Spark > already interoperates with several existing Apache projects (HDFS, HBase, > Hive, Cassandra, Avro and Flume to name a few). The Spark team is familiar > with the Apache process and and subscribes to the Apache mission - the > team includes multiple Apache committers already. Finally, joining Apache > will help coordinate the development effort of the growing number of > organizations which contribute to Spark. > > == Initial Goals == > The initial goals will most likely be to move the existing codebase to > Apache and integrate with the Apache development process. Furthermore, we > plan for incremental development, and releases along with the Apache > guidelines. > > === Current Status === > == Meritocracy == > The Spark project already operates on meritocratic principles. Today, > Spark has several developers and has accepted multiple major patches from > outside of U.C. Berkeley. While this process has remained mostly informal > (we do not have an official committer list), an implicit organization > exists in which individuals who contribute major components act as > maintainers for those modules. If accepted, the Spark project would > include several of these participants as committers from the onset. We > will work to identify all committers and PPMC members for the project and > to operate under the ASF meritocratic principles. > > === Community === > Acceptance into the Apache foundation would bolster the already strong > user and developer community around Spark. That community includes dozens > of contributors from several institutions, a meetup group with several > hundred members, and an active mailing list composed of hundreds of users. > Core Developers > The core developers of our project are listed in our contributors and > initial PPMC below. Though many exist at UC Berkeley, there is a > representative cross sampling of other organizations including Quantifind, > Microsoft, Yahoo!, ClearStory Data, Bizo, Intel, Tagged and Webtrends. > > > === Alignment === > Our proposed effort aligns with several ongoing BIGDATA and U.S. National > priority funding interests including the NSF and its Expeditions program, > and the DARPA XDATA project. Our industry partners and collaborators are > well aligned with our code base. > > There are also a number of related Apache projects and dependencies, that > will be mentioned in the Relationships with Other Apache products section. > > == Known Risks == > > === Orphaned Products === > Given the current level of investment in Spark - the risk of the project > being abandoned is minimal. There are several constituents who are highly > incentivized to continue development. The U.C. Berkeley AMPLab relies on > Spark as a platform for a large number of long-term research projects. > Several companies have build verticalized products which are tightly > dependent on Spark. Other companies have devoted signif
Re: [VOTE] Accept Apache BeanShell in the Incubator
+1 (binding) Ralph On Jun 3, 2013, at 6:02 AM, Mattmann, Chris A (398J) wrote: > +1 (binding). > > Cheers, > Chris > > ++ > Chris Mattmann, Ph.D. > Senior Computer Scientist > NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA > Office: 171-266B, Mailstop: 171-246 > Email: chris.a.mattm...@nasa.gov > WWW: http://sunset.usc.edu/~mattmann/ > ++ > Adjunct Assistant Professor, Computer Science Department > University of Southern California, Los Angeles, CA 90089 USA > ++ > > > > > > > -Original Message- > From: Simone Tripodi > Reply-To: "general@incubator.apache.org" > Date: Friday, May 24, 2013 12:23 AM > To: "general@incubator.apache.org" > Subject: [VOTE] Accept Apache BeanShell in the Incubator > >> Dear ASF members, >> >> We would like to propose BeanShell for the incubator. >> >> The proposal draft is available at: >> https://wiki.apache.org/incubator/BeanShellProposal, >> follows below the proposal >> >> Open is open for at least 72h and closes approximately on May 27th at >> 8:20am GMT >> >> [ ] +1 accept BeanShell in the Incubator >> [ ] +/-0 >> [ ] -1 because (provide a reason) >> >> Many thanks in advance, all the best! >> -Simo >> >> http://people.apache.org/~simonetripodi/ >> http://simonetripodi.livejournal.com/ >> http://twitter.com/simonetripodi >> http://www.99soft.org/ >> >> ~~ >> ~ >> >> = BeanShell = >> == Abstract == >> The following proposal is about BeanShell, see JSR-274: The BeanShell >> Scripting Language implementation. >> >> == Proposal == >> BeanShell is a small, free, embeddable Java source interpreter with >> object scripting language features, written in Java. BeanShell >> dynamically executes standard Java syntax and extends it with common >> scripting conveniences such as loose types, commands, and method >> closures like those in Perl and JavaScript. >> Users can use BeanShell interactively for Java experimentation and >> debugging as well as to extend your applications in new ways. >> Scripting Java lends itself to a wide variety of applications >> including rapid prototyping, user scripting extension, rules engines, >> configuration, testing, dynamic deployment, embedded systems, and even >> Java education. >> BeanShell is small and embeddable, so users can call BeanShell from >> Java applications to execute Java code dynamically at run-time or to >> provide extensibility in applications. Alternatively, users can use >> standalone BeanShell scripts to manipulate Java applications; working >> with Java objects and APIs dynamically. Since BeanShell is written in >> Java and runs in the same VM as application, users can freely pass >> references to "live" objects into scripts and return them as results. >> >> == Background == >> BeanShell is a long living project born in the 2000 thanks to Patrick >> Niemeyer initial effort, who is still maintaining the project, with >> the help of Daniel Leuck and contributions voluntarily sent by users. >> >> == Rationale == >> Currently there are no projects hosted by the ASF focused on providing >> JSR-274 implementation, moving the existing BeanShell project under >> the Apache umbrella would mean the ASF provides the JSR-274 reference >> implementation. >> >> = Current Status = >> == Meritocracy == >> The historical BeanShell team believes in meritocracy and always acted >> as a community. Mailing list, open issue tracker and other >> communication channels have always been adopted since its first >> release. The adoption in a larger community, such as Apache, is the >> natural evolution for BeanShell. Moreover, the Apache standards will >> enforce the existing BeanShell community practices and will be a >> foundation for future committers involvement. >> >> == Core Developers == >> In alphabetical order: >> >> * Daniel Leuck , >> * Patrick Niemeyer >> * Pedro Giffuni >> * Simone Tripodi >> >> == Alignment == >> Main aim of the project is to develop and maintain a fully flavored >> JSR-274 implementation that can be used by other Apache projects that >> need a Java Scripting Language. >> >> = Known Risks = >> == Orphaned Products == >> The increasing number of BeanShell adopters and the raising interest >> for the JSR-274 technology let us believe that there is a minimal risk >> for this work to being abandoned from the community. >> >> Moreover, BeanShell has been already used by the following projects for >> years: >> >> * Apache OpenOffice >> * Apache Maven >> * Apache JMeter >> >> == 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
Re: [PROPOSAL] Apache Spark for the Incubator
Note: we discussed adding Roman before the VOTE and it was fine with the incoming Spark community, so Roman is now on the wiki for the proposal. In case this changes anyone's VOTE on the VOTE thread, feel free to speak up or change your VOTE. Otherwise, nothing else to see here folks. Cheers, Chris ++ Chris Mattmann, Ph.D. Senior Computer Scientist NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA Office: 171-266B, Mailstop: 171-246 Email: chris.a.mattm...@nasa.gov WWW: http://sunset.usc.edu/~mattmann/ ++ Adjunct Assistant Professor, Computer Science Department University of Southern California, Los Angeles, CA 90089 USA ++ -Original Message- From: Roman Shaposhnik Date: Saturday, June 8, 2013 3:03 PM To: jpluser Subject: Re: [PROPOSAL] Apache Spark for the Incubator >On Mon, Jun 3, 2013 at 6:40 PM, Mattmann, Chris A (398J) > wrote: >> Hi Roman, I've conferred with the incoming Spark community and we are >> happy to have you >> as a mentor for the project. >> >> Feel free to add yourself to the wiki proposal. > >Great news! Done. > >Thanks, >Roman. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Apache HotdoG interest?
ACK go for it ++ Chris Mattmann, Ph.D. Senior Computer Scientist NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA Office: 171-266B, Mailstop: 171-246 Email: chris.a.mattm...@nasa.gov WWW: http://sunset.usc.edu/~mattmann/ ++ Adjunct Assistant Professor, Computer Science Department University of Southern California, Los Angeles, CA 90089 USA ++ -Original Message- From: Adam Estrada Date: Saturday, June 8, 2013 3:18 PM To: jpluser Cc: "general@incubator.apache.org" Subject: Re: Apache HotdoG interest? >+1 this sounds great! If I get an ACK, I will add myself to the project >wiki ASAP! > > >Thanks in advance, >Adam. > > > > >On Wed, Jun 5, 2013 at 10:51 AM, Mattmann, Chris A (398J) > wrote: > >Hey Adam, > >I noticed you were interested in Apache HotdoG -- would you like >to join the project as an initial committer and PPMC member? I know >you are interested in being a mentor; which requires you to be a >member of the IPMC which at present you are not. > >That being said there is nothing stopping you from doing "mentor"-ish >roles and tasks. Meaning, you can still help out with IPMC HotdoG >reporting (should the project be accepted into the Incubator after >our restarted VOTE and after we get a 3rd mentor from the IPMC to >sign up ;) ); with the community for HotdoG and bringing new contributors >to it; and of course with the code! > >Demonstration of these types of qualities is precisely the types of >things we look for in a mentor and an IPMC member and there is nothing >stopping you from doing that to help out HotdoG. Suggestion: > >(if the rest of the Hotdog community members have no objection; >which are present during discussion they have not) > >1. Adam adds himself as PPMC member and committer to: >http://wiki.apache.org/incubator/HotdoGProposal > > >2. Should HotdoG be accepted as Apache Incubator project; Adam >does mentor roles and participates that way. > >Adam that sound good? > >Thanks for your interest! > >Cheers, >Chris > > >++ >Chris Mattmann, Ph.D. >Senior Computer Scientist >NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA >Office: 171-266B, Mailstop: 171-246 >Email: chris.a.mattm...@nasa.gov >WWW: http://sunset.usc.edu/~mattmann/ >++ >Adjunct Assistant Professor, Computer Science Department >University of Southern California, Los Angeles, CA 90089 USA >++ > > > > > > > > > - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Apache Spark for the Incubator
+1 On 6/7/13 10:34 PM, "Mattmann, Chris A (398J)" wrote: >Hi Folks, > >OK discussion has died down, time to VOTE to accept Spark into the >Apache Incubator. I'll let the VOTE run for at least a week. > >So far I've heard +1s from the following folks, so no need for them >to VOTE again unless they want to change their VOTE: > >+1 > >Chris Mattmann* >Konstantin Boudnik >Henry Saputra* >Reynold Xin >Pei Chen >Roman Shaposhnik* >Suresh Marru* > >* -indicates IPMC > >[ ] +1 Accept Spark into the Apache Incubator. >[ ] +0 Don't care. >[ ] -1 Don't accept Spark into the Apache Incubator because.. > >Proposal text is below. > >=== Abstract === >Spark is an open source system for large-scale data analysis on clusters. > >=== Proposal === >Spark is an open source system for fast and flexible large-scale data >analysis. Spark provides a general purpose runtime that supports >low-latency execution in several forms. These include interactive >exploration of very large datasets, near real-time stream processing, and >ad-hoc SQL analytics (through higher layer extensions). Spark interfaces >with HDFS, HBase, Cassandra and several other storage storage layers, and >exposes APIs in Scala, Java and Python. >Background >Spark started as U.C. Berkeley research project, designed to efficiently >run machine learning algorithms on large datasets. Over time, it has >evolved into a general computing engine as outlined above. Spark¹s >developer community has also grown to include additional institutions, >such as universities, research labs, and corporations. Funding has been >provided by various institutions including the U.S. National Science >Foundation, DARPA, and a number of industry sponsors. See: >https://amplab.cs.berkeley.edu/sponsors/ for full details. > >=== Rationale === >As the number of contributors to Spark has grown, we have sought for a >long-term home for the project, and we believe the Apache foundation would >be a great fit. Spark is a natural fit for the Apache foundation: Spark >already interoperates with several existing Apache projects (HDFS, HBase, >Hive, Cassandra, Avro and Flume to name a few). The Spark team is familiar >with the Apache process and and subscribes to the Apache mission - the >team includes multiple Apache committers already. Finally, joining Apache >will help coordinate the development effort of the growing number of >organizations which contribute to Spark. > >== Initial Goals == >The initial goals will most likely be to move the existing codebase to >Apache and integrate with the Apache development process. Furthermore, we >plan for incremental development, and releases along with the Apache >guidelines. > >=== Current Status === >== Meritocracy == >The Spark project already operates on meritocratic principles. Today, >Spark has several developers and has accepted multiple major patches from >outside of U.C. Berkeley. While this process has remained mostly informal >(we do not have an official committer list), an implicit organization >exists in which individuals who contribute major components act as >maintainers for those modules. If accepted, the Spark project would >include several of these participants as committers from the onset. We >will work to identify all committers and PPMC members for the project and >to operate under the ASF meritocratic principles. > >=== Community === >Acceptance into the Apache foundation would bolster the already strong >user and developer community around Spark. That community includes dozens >of contributors from several institutions, a meetup group with several >hundred members, and an active mailing list composed of hundreds of users. >Core Developers >The core developers of our project are listed in our contributors and >initial PPMC below. Though many exist at UC Berkeley, there is a >representative cross sampling of other organizations including Quantifind, >Microsoft, Yahoo!, ClearStory Data, Bizo, Intel, Tagged and Webtrends. > > >=== Alignment === >Our proposed effort aligns with several ongoing BIGDATA and U.S. National >priority funding interests including the NSF and its Expeditions program, >and the DARPA XDATA project. Our industry partners and collaborators are >well aligned with our code base. > >There are also a number of related Apache projects and dependencies, that >will be mentioned in the Relationships with Other Apache products section. > >== Known Risks == > >=== Orphaned Products === >Given the current level of investment in Spark - the risk of the project >being abandoned is minimal. There are several constituents who are highly >incentivized to continue development. The U.C. Berkeley AMPLab relies on >Spark as a platform for a large number of long-term research projects. >Several companies have build verticalized products which are tightly >dependent on Spark. Other companies have devoted significant internal >infrastructure investment in Spark. > >=== Inexperience with Open Source === >Spark has existed as a healthy open
Re: [VOTE] Apache Spark for the Incubator
+1 (non-binding) -- Hitesh On Jun 7, 2013, at 10:34 PM, Mattmann, Chris A (398J) wrote: > Hi Folks, > > OK discussion has died down, time to VOTE to accept Spark into the > Apache Incubator. I'll let the VOTE run for at least a week. > > So far I've heard +1s from the following folks, so no need for them > to VOTE again unless they want to change their VOTE: > > +1 > > Chris Mattmann* > Konstantin Boudnik > Henry Saputra* > Reynold Xin > Pei Chen > Roman Shaposhnik* > Suresh Marru* > > * -indicates IPMC > > [ ] +1 Accept Spark into the Apache Incubator. > [ ] +0 Don't care. > [ ] -1 Don't accept Spark into the Apache Incubator because.. > > Proposal text is below. > > === Abstract === > Spark is an open source system for large-scale data analysis on clusters. > > === Proposal === > Spark is an open source system for fast and flexible large-scale data > analysis. Spark provides a general purpose runtime that supports > low-latency execution in several forms. These include interactive > exploration of very large datasets, near real-time stream processing, and > ad-hoc SQL analytics (through higher layer extensions). Spark interfaces > with HDFS, HBase, Cassandra and several other storage storage layers, and > exposes APIs in Scala, Java and Python. > Background > Spark started as U.C. Berkeley research project, designed to efficiently > run machine learning algorithms on large datasets. Over time, it has > evolved into a general computing engine as outlined above. Spark¹s > developer community has also grown to include additional institutions, > such as universities, research labs, and corporations. Funding has been > provided by various institutions including the U.S. National Science > Foundation, DARPA, and a number of industry sponsors. See: > https://amplab.cs.berkeley.edu/sponsors/ for full details. > > === Rationale === > As the number of contributors to Spark has grown, we have sought for a > long-term home for the project, and we believe the Apache foundation would > be a great fit. Spark is a natural fit for the Apache foundation: Spark > already interoperates with several existing Apache projects (HDFS, HBase, > Hive, Cassandra, Avro and Flume to name a few). The Spark team is familiar > with the Apache process and and subscribes to the Apache mission - the > team includes multiple Apache committers already. Finally, joining Apache > will help coordinate the development effort of the growing number of > organizations which contribute to Spark. > > == Initial Goals == > The initial goals will most likely be to move the existing codebase to > Apache and integrate with the Apache development process. Furthermore, we > plan for incremental development, and releases along with the Apache > guidelines. > > === Current Status === > == Meritocracy == > The Spark project already operates on meritocratic principles. Today, > Spark has several developers and has accepted multiple major patches from > outside of U.C. Berkeley. While this process has remained mostly informal > (we do not have an official committer list), an implicit organization > exists in which individuals who contribute major components act as > maintainers for those modules. If accepted, the Spark project would > include several of these participants as committers from the onset. We > will work to identify all committers and PPMC members for the project and > to operate under the ASF meritocratic principles. > > === Community === > Acceptance into the Apache foundation would bolster the already strong > user and developer community around Spark. That community includes dozens > of contributors from several institutions, a meetup group with several > hundred members, and an active mailing list composed of hundreds of users. > Core Developers > The core developers of our project are listed in our contributors and > initial PPMC below. Though many exist at UC Berkeley, there is a > representative cross sampling of other organizations including Quantifind, > Microsoft, Yahoo!, ClearStory Data, Bizo, Intel, Tagged and Webtrends. > > > === Alignment === > Our proposed effort aligns with several ongoing BIGDATA and U.S. National > priority funding interests including the NSF and its Expeditions program, > and the DARPA XDATA project. Our industry partners and collaborators are > well aligned with our code base. > > There are also a number of related Apache projects and dependencies, that > will be mentioned in the Relationships with Other Apache products section. > > == Known Risks == > > === Orphaned Products === > Given the current level of investment in Spark - the risk of the project > being abandoned is minimal. There are several constituents who are highly > incentivized to continue development. The U.C. Berkeley AMPLab relies on > Spark as a platform for a large number of long-term research projects. > Several companies have build verticalized products which are tightly > dependent on Spark. Other companies have devote
