Re: [PROPOSAL] Storm for Apache Incubator
+1 (non-binding) Sent from phone On Sep 4, 2013, at 1:07 AM, Nathan Marz nat...@nathanmarz.com wrote: Hi everyone, I'd like to propose Storm to be an Apache Incubator project. After much thought I believe this is the right next step for the project, and I look forward to hearing everyone's thoughts and feedback! Here's a link to the proposal: https://wiki.apache.org/incubator/StormProposal The proposal is also pasted below. -Nathan = Storm Proposal = == Abstract == Storm is a distributed, fault-tolerant, and high-performance realtime computation system that provides strong guarantees on the processing of data. == Proposal == Storm is a distributed real-time computation system. Similar to how Hadoop provides a set of general primitives for doing batch processing, Storm provides a set of general primitives for doing real-time computation. Its use cases span stream processing, distributed RPC, continuous computation, and more. Storm has become a preferred technology for near-realtime big-data processing by many organizations worldwide (see a partial list at https://github.com/nathanmarz/storm/wiki/Powered-By). As an open source project, Storm’s developer community has grown rapidly to 46 members. == Background == The past decade has seen a revolution in data processing. MapReduce, Hadoop, and related technologies have made it possible to store and process data at scales previously unthinkable. Unfortunately, these data processing technologies are not realtime systems, nor are they meant to be. The lack of a Hadoop of realtime has become the biggest hole in the data processing ecosystem. Storm fills that hole. Storm was initially developed and deployed at BackType in 2011. After 7 months of development BackType was acquired by Twitter in July 2011. Storm was open sourced in September 2011. Storm has been under continuous development on its Github repository since being open-sourced. It has undergone four major releases (0.5, 0.6, 0.7, 0.8) and many minor ones. == Rationale == Storm is a general platform for low-latency big-data processing. It is complementary to the existing Apache projects, such as Hadoop. Many applications are actually exploring using both Hadoop and Storm for big-data processing. Bringing Storm into Apache is very beneficial to both Apache community and Storm community. The rapid growth of Storm community is empowered by open source. We believe the Apache foundation is a great fit as the long-term home for Storm, as it provides an established process for community-driven development and decision making by consensus. This is exactly the model we want for future Storm development. == Initial Goals == * Move the existing codebase to Apache * Integrate with the Apache development process * Ensure all dependencies are compliant with Apache License version 2.0 * Incremental development and releases per Apache guidelines == Current Status == Storm has undergone four major releases (0.5, 0.6, 0.7, 0.8) and many minor ones. Storm 0.9 is about to be released. Storm is being used in production by over 50 organizations. Storm codebase is currently hosted at github.com, which will seed the Apache git repository. === Meritocracy === We plan to invest in supporting a meritocracy. We will discuss the requirements in an open forum. Several companies have already expressed interest in this project, and we intend to invite additional developers to participate. We will encourage and monitor community participation so that privileges can be extended to those that contribute. === Community === The need for a low-latency big-data processing platform in the open source is tremendous. Storm is currently being used by at least 50 organizations worldwide (see https://github.com/nathanmarz/storm/wiki/Powered-By), and is the most starred Java project on Github. By bringing Storm into Apache, we believe that the community will grow even bigger. === Core Developers === Storm was started by Nathan Marz at BackType, and now has developers from Yahoo!, Microsoft, Alibaba, Infochimps, and many other companies. === Alignment === In the big-data processing ecosystem, Storm is a very popular low-latency platform, while Hadoop is the primary platform for batch processing. We believe that it will help the further growth of big-data community by having Hadoop and Storm aligned within Apache foundation. The alignment is also beneficial to other Apache communities (such as Zookeeper, Thrift, Mesos). We could include additional sub-projects, Storm-on-YARN and Storm-on-Mesos, in the near future. == Known Risks == === Orphaned Products === The risk of the Storm project being abandoned is minimal. There are at least 50 organizations (Twitter, Yahoo!, Microsoft, Groupon, Baidu, Alibaba, Alipay, Taobao, PARC, RocketFuel etc) are highly incentivized to continue development. Many of
Re: [VOTE] Accept Storm into the Incubator
+1 (non-binding) On Thu, Sep 12, 2013 at 12:19 PM, Doug Cutting cutt...@apache.org wrote: Discussion about the Storm proposal has subsided, issues raised now seemingly resolved. I'd like to call a vote to accept Storm as a new Incubator podling. The proposal is included below and is also at: https://wiki.apache.org/incubator/StormProposal Let's keep the vote open for four working days, until 18 September. [ ] +1 Accept Storm into the Incubator [ ] +0 Don't care. [ ] -1 Don't accept Storm because... Doug = Storm Proposal = == Abstract == Storm is a distributed, fault-tolerant, and high-performance realtime computation system that provides strong guarantees on the processing of data. == Proposal == Storm is a distributed real-time computation system. Similar to how Hadoop provides a set of general primitives for doing batch processing, Storm provides a set of general primitives for doing real-time computation. Its use cases span stream processing, distributed RPC, continuous computation, and more. Storm has become a preferred technology for near-realtime big-data processing by many organizations worldwide (see a partial list at https://github.com/nathanmarz/storm/wiki/Powered-By). As an open source project, Storm’s developer community has grown rapidly to 46 members. == Background == The past decade has seen a revolution in data processing. MapReduce, Hadoop, and related technologies have made it possible to store and process data at scales previously unthinkable. Unfortunately, these data processing technologies are not realtime systems, nor are they meant to be. The lack of a Hadoop of realtime has become the biggest hole in the data processing ecosystem. Storm fills that hole. Storm was initially developed and deployed at BackType in 2011. After 7 months of development BackType was acquired by Twitter in July 2011. Storm was open sourced in September 2011. Storm has been under continuous development on its Github repository since being open-sourced. It has undergone four major releases (0.5, 0.6, 0.7, 0.8) and many minor ones. == Rationale == Storm is a general platform for low-latency big-data processing. It is complementary to the existing Apache projects, such as Hadoop. Many applications are actually exploring using both Hadoop and Storm for big-data processing. Bringing Storm into Apache is very beneficial to both Apache community and Storm community. The rapid growth of Storm community is empowered by open source. We believe the Apache foundation is a great fit as the long-term home for Storm, as it provides an established process for community-driven development and decision making by consensus. This is exactly the model we want for future Storm development. == Initial Goals == * Move the existing codebase to Apache * Integrate with the Apache development process * Ensure all dependencies are compliant with Apache License version 2.0 * Incremental development and releases per Apache guidelines == Current Status == Storm has undergone four major releases (0.5, 0.6, 0.7, 0.8) and many minor ones. Storm 0.9 is about to be released. Storm is being used in production by over 50 organizations. Storm codebase is currently hosted at github.com, which will seed the Apache git repository. === Meritocracy === We plan to invest in supporting a meritocracy. We will discuss the requirements in an open forum. Several companies have already expressed interest in this project, and we intend to invite additional developers to participate. We will encourage and monitor community participation so that privileges can be extended to those that contribute. === Community === The need for a low-latency big-data processing platform in the open source is tremendous. Storm is currently being used by at least 50 organizations worldwide (see https://github.com/nathanmarz/storm/wiki/Powered-By), and is the most starred Java project on Github. By bringing Storm into Apache, we believe that the community will grow even bigger. === Core Developers === Storm was started by Nathan Marz at BackType, and now has developers from Yahoo!, Microsoft, Alibaba, Infochimps, and many other companies. === Alignment === In the big-data processing ecosystem, Storm is a very popular low-latency platform, while Hadoop is the primary platform for batch processing. We believe that it will help the further growth of big-data community by having Hadoop and Storm aligned within Apache foundation. The alignment is also beneficial to other Apache communities (such as Zookeeper, Thrift, Mesos). We could include additional sub-projects, Storm-on-YARN and Storm-on-Mesos, in the near future. == Known Risks == === Orphaned Products === The risk of the Storm project being abandoned is minimal. There are at least 50 organizations (Twitter, Yahoo!, Microsoft, Groupon, Baidu, Alibaba, Alipay, Taobao, PARC, RocketFuel etc)
Re: [VOTE] Release Apache Storm 0.9.1-incubating
+1 (binding) from me. Sebb, can you please answer the question related to the NOTICE file. I think while it may not be necessary to call out individual or companies contributing large portions of the code, it should not block this release and can be addressed later. On Thu, Feb 13, 2014 at 7:49 AM, P. Taylor Goetz ptgo...@gmail.com wrote: Thanks for the input! The majority of the codebase was originally developed by Nathan Marz, and it includes significant contributions from Yahoo!. The project was originally licensed under the Eclipse Public License, but has not transitioned to the Apache v2 license. If putting those attributions in the NOTICE file is not the correct thing to do, please let me know the right way to handle it. It was still 2013 when I last updated the NOTICE file. I'm not sure if that is a blocker for release or not. - Taylor On Feb 13, 2014, at 5:59 AM, sebb seb...@gmail.com wrote: On 13 February 2014 07:00, P. Taylor Goetz ptgo...@gmail.com wrote: This is a call for a vote to release Apache Storm (incubating) version 0.9.1. This will be the first release of Apache Storm. A vote was held on the developer mailing list, and passed with 9 +1 votes (6 binding, 3 non-binding), no 0 votes, and no -1 votes. Release Vote: http://mail-archives.apache.org/mod_mbox/incubator-storm-dev/201402.mbox/%3c44c5baad-0fd8-454c-84d7-c8da92442...@gmail.com%3e Release Vote Result: http://mail-archives.apache.org/mod_mbox/incubator-storm-dev/201402.mbox/%3c3a207f1c-3b07-4029-93d4-87abeb412...@gmail.com%3e The tag to be voted upon is v0.9.1-incubating: https://git-wip-us.apache.org/repos/asf?p=incubator-storm.git;a=tree;h=ffc7a81bfba60c735dd6801af4f5e8db3812658c;hb=ffc7a81bfba60c735dd6801af4f5e8db3812658c NOTICE file still refers to 2013. The NOTICE file also references software from Nathan Marz and Yahoo! However there are no corresponding licenses in the LICENSE file. Does the source *contain* software from either of the above? If so, where are the license files? If not, why are the attributions present in the NOTICE file? Remember that NL file entries are only for bits that are actually included in the distributiion. The specific source archive being voted upon can be found here: http://people.apache.org/~ptgoetz/storm/storm-0.9.1-incubating-dist-rc3/apache-storm-0.9.1-incubating-src.tar.gz Other release files, signatures and digests can be found here: http://people.apache.org/~ptgoetz/storm/storm-0.9.1-incubating-dist-rc3 The release artifacts are signed with the key available here: https://git-wip-us.apache.org/repos/asf?p=incubator-storm.git;a=blob_plain;f=KEYS;hb=22b832708295fa2c15c4f3c70ac0d2bc6fded4bd The staging repository for this release can be found here: https://repository.apache.org/content/repositories/orgapachestorm-1002/ The generated reports and documentation for this release can be found here: http://people.apache.org/~ptgoetz/storm/storm-0.9.1-incubating-report-rc3 Please vote on releasing this package as Apache Storm 0.9.1-incubating. This vote will be open for at least 72 hours. [ ] +1 Release this package as Apache Storm 0.9.1-incubating [ ] 0 No opinion [ ] -1 Do not release this package because ... Thanks, Apache Storm Team - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- http://hortonworks.com/download/ -- CONFIDENTIALITY NOTICE NOTICE: This message is intended for the use of the individual or entity to which it is addressed and may contain information that is confidential, privileged and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, you are hereby notified that any printing, copying, dissemination, distribution, disclosure or forwarding of this communication is strictly prohibited. If you have received this communication in error, please contact the sender immediately and delete it from your system. Thank You.
Re: [VOTE] Accept Stratosphere into the incubator
+1 On Thu, Apr 10, 2014 at 10:42 AM, Alan Gates ga...@hortonworks.com wrote: Based on the results of the discussion thread ( http://mail-archives.apache.org/mod_mbox/incubator-general/201403.mbox/%3CCE562EE9-968C-420E-A719-8C08CDAC99F8%40hortonworks.com%3Ein particular notice the discussion on name change in the disucssion ), I would like to call a vote on accepting Stratosphere into the incubator. [ ] +1 Accept Stratosphere into the Incubator [ ] +0 Indifferent to the acceptance of Stratosphere [ ] -1 Do not accept Stratosphere because ... The vote will be open until Monday April 14 18:00 UTC. https://wiki.apache.org/incubator/StratosphereProposal = Stratosphere = == Abstract == Stratosphere is an open source system for parallel data analysis. Stratosphere deeply integrates MapReduce and database technologies to provide expressive and optimizable programming interfaces and at the same time efficient and scalable execution. == Proposal == Stratosphere is an open source system for expressive, declarative, fast, and efficient data analysis. Stratosphere combines the scalability and programming flexibility of distributed MapReduce-like platforms with the efficiency, out-of-core execution, and query optimization capabilities found in parallel databases. == Background == There is currently a need for general-purpose cluster computing platforms that are compatible with the Hadoop ecosystem, are more efficient, easier to use, and can support more applications than Hadoop MapReduce, but are not restricted to a specific data model and language (such as the relational model and a variant of SQL). Stratosphere fulfils these needs. Stratosphere exposes expressive APIs in Java and Scala (conceptually similar to Spark, Cascading, Scalding) that allow arbitrary user-defined functions in the same language and data model that the program is written in. Stratosphere programs pass through a cost-based optimizer that finds the best execution path for these programs depending on the data and cluster characteristics. The design and implementation of Stratosphere is based on research that generalizes query optimizers in relational databases. Stratosphere has a distributed runtime that is architected upon the principles of parallel databases, providing true pipelining (a basis for stream processing) and efficient out-of-core algorithms for grouping, sorting, joining, and aggregating data. Stratosphere provides first-class support for iterative algorithms via a built-in iterate operator, covering Machine Learning and graph analysis use cases. It achieves performance similar to Apache Giraph without being a specialized graph processing system. Stratosphere has undergone three major releases (v0.1, v0.2, v0.4) and some minor ones. == Rationale == Stratosphere started out in 2008 as a research project by the Technical University of Berlin, the Humboldt University of Berlin, and the Hasso Plattner Institute, and has received subsequent funding from the German Research Council, the European Institute of Innovation and Technology, the European Commision, and industry. The traction of Stratosphere has by far exceeded our initial expectations, and we are therefore seeking an organizational long-term home for Stratosphere beyond the University walls that will house and further encourage contributors from companies and other organizations that are interested in Stratosphere. We believe that the Apache Software Foundation is the ideal home for Stratosphere. Stratosphere integrates with several existing Apache projects, such as HDFS, YARN, HBase, and Avro. The team is familiar with the Apache processes and fully subscribes to the Apache mission. One of the proposing members is a long-time Apache contributor and PMC member. == Initial Goals == * Move the existing codebase to Apache * Integrate with the Apache development process * Ensure all dependencies are compliant with Apache License version 2.0 * Incremental development and releases per Apache guidelines == Current Status == === Meritocracy === Stratosphere operated on meritocratic principles from the get go. The initial project proposal submitted to the German Research Council in 2008 stated that all code developed in the project will be released as open source under the Apache 2 license. Currently, all the discussions pertaining to Stratosphere development are public on [[ https://github.com/stratosphere/stratosphere|GitHub]] and our [[ https://groups.google.com/forum/#!forum/stratosphere-dev|mailing list]]. The current incubation proposal includes the major code contributors to Stratosphere. Several additional people have worked on the Stratosphere codebase for research prototypes and industry use cases and would be interested in becoming committers. We are starting with a small committer group and we plan to add additional committers following an open merit-based decision process
Re: [ANNOUNCE] Ashutosh Chauhan joins the IPMC
Congrats Ashutosh! Welcome to IPMC. Sent from phone On Apr 11, 2014, at 5:56 PM, Roman Shaposhnik r...@apache.org wrote: Hi! an ASF member Ashutosh Chauhan has volunteered recently to join the Incubator PMC. Ashutosh comes to the Incubator with a background in an impressive variety of Hadoop ecosystem projects: Datafu, HCatalog, Hive, Pig, and Tez. An experience that should have prepared him well for helping future podlings. Welcome, Ashutosh! Great to have you on board! Thanks, Roman. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- CONFIDENTIALITY NOTICE NOTICE: This message is intended for the use of the individual or entity to which it is addressed and may contain information that is confidential, privileged and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, you are hereby notified that any printing, copying, dissemination, distribution, disclosure or forwarding of this communication is strictly prohibited. If you have received this communication in error, please contact the sender immediately and delete it from your system. Thank You. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept Slider into the incubator
+1 (binding) On Thu, Apr 17, 2014 at 6:01 AM, Steve Loughran ste...@hortonworks.comwrote: I'd like to call a vote on accepting Slider into the incubator https://wiki.apache.org/incubator/SliderProposal [ ] +1 Accept Slider into the Incubator [ ] +0 Indifferent to the acceptance of Slider [ ] -1 Do not accept Slider because ... The vote will be open until Thursday April 24 13:00 UTC -Steve -- CONFIDENTIALITY NOTICE NOTICE: This message is intended for the use of the individual or entity to which it is addressed and may contain information that is confidential, privileged and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, you are hereby notified that any printing, copying, dissemination, distribution, disclosure or forwarding of this communication is strictly prohibited. If you have received this communication in error, please contact the sender immediately and delete it from your system. Thank You. -- http://hortonworks.com/download/ -- CONFIDENTIALITY NOTICE NOTICE: This message is intended for the use of the individual or entity to which it is addressed and may contain information that is confidential, privileged and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, you are hereby notified that any printing, copying, dissemination, distribution, disclosure or forwarding of this communication is strictly prohibited. If you have received this communication in error, please contact the sender immediately and delete it from your system. Thank You.
Re: [VOTE] Accept Optiq into the incubator
+1 (binding) On Fri, May 9, 2014 at 11:03 AM, Ashutosh Chauhan hashut...@apache.orgwrote: Based on the results of the discussion thread ( http://mail-archives.apache.org/mod_mbox/incubator-general/201404.mbox/%3CCA%2BFBdFQA4TghLRdh9GgDKaMtKLQHxE_QZV%3DoZ7HfiDSA_jyqwg%40mail.gmail.com%3E ), I would like to call a vote on accepting Optiq into the incubator. [ ] +1 Accept Optiq into the Incubator [ ] +0 Indifferent to the acceptance of Stratosphere [ ] -1 Do not accept Optiq because ... The vote will be open until Tuesday May 13 18:00 UTC. https://wiki.apache.org/incubator/OptiqProposal = Optiq = == Abstract == Optiq is a framework that allows efficient translation of queries involving heterogeneous and federated data. == Proposal == Optiq is a highly customizable engine for parsing and planning queries on data in a wide variety of formats. It allows database-like access, and in particular a SQL interface and advanced query optimization, for data not residing in a traditional database. == Background == Databases were traditionally engineered in a monolithic stack, providing a data storage format, data processing algorithms, query parser, query planner, built-in functions, metadata repository and connectivity layer. They innovate in some areas but rarely in all. Modern data management systems are decomposing that stack into separate components, separating data, processing engine, metadata, and query language support. They are highly heterogeneous, with data in multiple locations and formats, caching and redundant data, different workloads, and processing occurring in different engines. Query planning (sometimes called query optimization) has always been a key function of a DBMS, because it allows the implementors to introduce new query-processing algorithms, and allows data administrators to re-organize the data without affecting applications built on that data. In a componentized system, the query planner integrates the components (data formats, engines, algorithms) without introducing unncessary coupling or performance tradeoffs. But building a query planner is hard; many systems muddle along without a planner, and indeed a SQL interface, until the demand from their customers is overwhelming. There is an opportunity to make this process more efficient by creating a re-usable framework. == Rationale == Optiq allows database-like access, and in particular a SQL interface and advanced query optimization, for data not residing in a traditional database. It is complementary to many current Hadoop and NoSQL systems, which have innovative and performant storage and runtime systems but lack a SQL interface and intelligent query translation. Optiq is already in use by several projects, including Apache Drill, Apache Hive and Cascading Lingual, and commercial products. Optiq's architecture consists of: An extensible relational algebra. * SPIs (service-provider interfaces) for metadata (schemas and tables), planner rules, statistics, cost-estimates, user-defined functions. * Built-in sets of rules for logical transformations and common data-sources. * Two query planning engines driven by rules, statistics, etc. One engine is cost-based, the other rule-based. * Optional SQL parser, validator and translator to relational algebra. * Optional JDBC driver. == Initial Goals == The initial goals are be to move the existing codebase to Apache and integrate with the Apache development process. Once this is accomplished, we plan for incremental development and releases that follow the Apache guidelines. As we move the code into the org.apache namespace, we will restructure components as necessary to allow clients to use just the components of Optiq that they need. A version 1.0 release, including pre-built binaries, will foster wider adoption. == Current Status == Optiq has had over a dozen minor releases over the last 18 months. Its core SQL parser and validator, and its planning engine and core rules, are mature and robust and are the basis for several production systems; but other components and SPIs are still undergoing rapid evolution. === Meritocracy === We plan to invest in supporting a meritocracy. We will discuss the requirements in an open forum. We encourage the companies and projects using Optiq to discuss their requirements in an open forum and to participate in development. We will encourage and monitor community participation so that privileges can be extended to those that contribute. Optiq's pluggable architecture encourages developers to contribute extensions such as adapters for data sources, new planning rules, and better statistics and cost-estimation functions. We look forward to fostering a rich ecosystem of extensions. === Community === Building a data management system requires a high degree of technical skill, and correspondingly, the community of developers directly using Optiq
Re: [VOTE] Release Apache Storm 0.9.2-incubating
Taylor, thanks for making 0.9.2 available. I did some preliminary tests and looked through the artifacts. +1 (binding) from me for the release. On Mon, Jun 23, 2014 at 11:00 AM, Alan Cabrera l...@toolazydogs.com wrote: Only IPMC members' votes are binding until the podling is out of the incubator. This release will need at least 3 of those votes. However, any IPMC +1 votes will carry over to this current vote. If I counted correctly, this release has one from the earlier vote plus mine. I think it needs one more IPMC member's vote. Regards, Alan On Jun 22, 2014, at 1:47 PM, P. Taylor Goetz ptgo...@gmail.com wrote: Alan, That was the result of the PPMC vote on the dev@ list. Arvind is a mentor. -Taylor On Jun 22, 2014, at 2:51 PM, Alan Cabrera l...@toolazydogs.com wrote: I'm looking at the release vote result and I'm seeing only one binding vote from a IPMC member. Am I comparing the vote results against the wrong IPMC roster? http://people.apache.org/committers-by-project.html#incubator-pmc Regards, Alan P.S. Apologies if this is a duplicate email. On Jun 19, 2014, at 11:37 AM, P. Taylor Goetz ptgo...@apache.org wrote: This is a call for a vote to release Apache Storm (incubating) version 0.9.2. This will be the 2nd release of Apache Storm. A vote was held on the developer mailing list, and passed with 3 binding +1 votes, no 0 votes, and no -1 votes. Release vote: http://mail-archives.apache.org/mod_mbox/incubator-storm-dev/201406.mbox/%3c5045a732-a2f6-4a12-a57f-c330d9e9e...@gmail.com%3e Release vote result: http://mail-archives.apache.org/mod_mbox/incubator-storm-dev/201406.mbox/%3c0f81f852-eeb9-4025-80ab-1f0e92470...@gmail.com%3e The full list of changes in this release: https://git-wip-us.apache.org/repos/asf?p=incubator-storm.git;a=blob;f=CHANGELOG.md;h=95024dad910d12eb3e14772f46a2d28675669b61;hb=24d4a14de310cbbfebdc4a50d8cc9d86f9943087 The tag to be voted upon is v0.9.2-incubating: https://git-wip-us.apache.org/repos/asf?p=incubator-storm.git;a=tree;h=24d4a14de310cbbfebdc4a50d8cc9d86f9943087;hb=24d4a14de310cbbfebdc4a50d8cc9d86f9943087 The specific source archive being voted upon can be found here: http://people.apache.org/~ptgoetz/storm-0.9.2-incubating/apache-storm-0.9.2-incubating-src.tar.gz Other release files, signatures and digests can be found here: http://people.apache.org/~ptgoetz/storm-0.9.2-incubating/ The release artifacts are signed with the key available here: https://git-wip-us.apache.org/repos/asf?p=incubator-storm.git;a=blob_plain;f=KEYS;hb=22b832708295fa2c15c4f3c70ac0d2bc6fded4bd The staging repository for this release can be found here: https://repository.apache.org/content/repositories/orgapachestorm-1008 The generated reports and documentation for this release can be found here: http://people.apache.org/~ptgoetz/storm-0.9.2-incubating/report/ Please vote on releasing this package as Apache Storm 0.9.2-incubating. This vote will be open for at least 72 hours. [ ] +1 Release this package as Apache Storm 0.9.2-incubating [ ] 0 No opinion [ ] -1 Do not release this package because … Thanks, Taylor - 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://hortonworks.com/download/ -- CONFIDENTIALITY NOTICE NOTICE: This message is intended for the use of the individual or entity to which it is addressed and may contain information that is confidential, privileged and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, you are hereby notified that any printing, copying, dissemination, distribution, disclosure or forwarding of this communication is strictly prohibited. If you have received this communication in error, please contact the sender immediately and delete it from your system. Thank You.
Re: [VOTE] Accept REEF into the Apache Incubator
+1 (binding) On Fri, Aug 8, 2014 at 10:40 PM, Byung-Gon Chun bgc...@gmail.com wrote: Hi, Thanks for participating in the proposal discussion on REEF. The discussion has calmed. I would like to call a vote for acceptance of REEF into the Apache Incubator. The proposal is attached below, and it is also available at https://wiki.apache.org/incubator/ReefProposal Let's keep this vote open for three business days, closing the voting on August 11, 11:59PM (PDT). [] +1 Accept REEF into the Incubator [] 0 Don't care [] -1 Don't accept REEF because... Thanks! -Gon -- Byung-Gon Chun # REEFProposal - Incubator # Abstract REEF (Retainable Evaluator Execution Framework) is a scale-out computing fabric that eases the development of Big Data applications on top of resource managers such as Apache YARN and Mesos. # Proposal REEF is a Big Data system that makes it easy to implement scalable, fault-tolerant runtime environments for a range of data processing models (e.g., graph processing and machine learning) on top of resource managers such as Apache YARN and Mesos. REEF provides capabilities to run multiple heterogeneous frameworks and workflows of those efficiently. Additionally, REEF contains two libraries that are of independent value: Wake is an event-based-programming framework inspired by Rx and SEDA. Tang is a dependency injection framework inspired by Google Guice, but designed specifically for configuring distributed systems. # Background The resource management layer such as Apache YARN and Mesos has emerged as a critical layer in the new scale-out data processing stack; resource managers assume the responsibility of multiplexing a cluster of shared-nothing machines across heterogeneous applications. They operate behind an interface for leasing containers - a slice of a machine’s resources - to computations in an elastic fashion. However, building data processing frameworks directly on this layer comes at a high cost: each framework must tackle the same challenges (e.g., fault-tolerance, task scheduling and coordination) and reimplement common mechanisms (e.g., caching, bulk transfers). REEF provides a reusable control-plane for scheduling and coordinating task-level work on cluster resource managers. The REEF design enables sophisticated optimizations, such as container re-use and data caching, and facilitates workflows that span multiple frameworks. Examples include pipelining data between different operators in a relational system, retaining state across iterations in iterative or recursive data flow, and passing the result of a MapReduce job to a Machine Learning computation. # Rationale Since REEF is a library that makes it easy to write distributed applications on top of Apache YARN or Mesos, the Apache Software Foundation is the perfect home for hosting REEF. # Current Status REEF has been developed mostly by Microsoft, UCLA and the Seoul National University. The REEF codebase is open-sourced under Apache License 2.0 and is currently hosted in a public repository at github.com. # Meritocracy We plan to build a strong open community by following the Apache meritocracy principles. We will work with those who contribute significantly to the project and invite them to be its committers. # Community REEF is currently being used internally at Microsoft. Also, SK Telecom builds their data analytics infrastructure on top of REEF in collaboration with Seoul National University. We hope to extend our contributor base by becoming an Apache incubator project. REEF will attract developers who are interested in creating common building blocks for simplifying the development of large-scale big data applications. # Core Developers Core developers are engineers from Microsoft, Purestorage, UCB, UCLA, UW and Seoul National University. # Alignment REEF depends on many Apache projects and dependencies. REEF is built on resource managers such as Apache YARN and Apache Mesos. REEF also uses HDFS as a distributed storage layer. # Known Risks ## Orphaned Products The risk of REEF being orphaned is small because Microsoft products are built on REEF. The core REEF developers continue to work on REEF at Microsoft, UCLA, and Seoul National University. The REEF project is gaining interest from other institutions to be used as their infrastructure. ## Inexperience with Open Source Several core developers have experience with open source development. REEF committers will be guided by the mentors with strong Apache open source project backgrounds. ## Homogeneous Developers The initial committers include developers from several institutions including Microsoft, Purestorage, UCB, UCLA, and Seoul National University. ## Reliance on Salaried Developers Developers from Microsoft are paid to work on REEF. Since the work is used internally at Microsoft, Microsoft will keep supporting the
Re: [Proposal] Taverna workflow
This is an exciting project. If you you need a volunteer, I am available. My interests are from my close participation in related projects - Hadoop, Falcon, and Storm. On Tue, Sep 23, 2014 at 5:43 AM, Stian Soiland-Reyes soiland-re...@cs.manchester.ac.uk wrote: I hereby present the Apache Incubator proposal for the project Taverna. Also available in rich text in the Taverna wiki (with more hyperlinks!): http://dev.mygrid.org.uk/wiki/display/developer/Taverna+incubator+proposal (Could someone grant me access to edit the Incubator wiki pages? My wiki username is soilandreyes) # Abstract Taverna is an open source and domain-independent suite of tools used to design and execute data-driven workflows. # Proposal The Taverna suite includes: * Taverna Workbench, a Java-based desktop application for graphically composing, editing and executing workflows of distributed web services and local tools * Taverna Commandline Tool which allows repeated execution of parameterized workflow definitions * Taverna Server provides a REST and SOAP API for executing workflows * Taverna Player is a Ruby-based web interface towards the Server, providing a high-level view of workflow executions and their results, and allows further integrations with Ruby on Rails applications. Taverna can browse and combine different service types, allowing workflows to integrate steps of arbitrary REST and SOAP web services with command line tools (local and SSH), scripts (Beanshell, R, Jython) and finally visualize the results. The goal of the Taverna suite is to help researchers to access distributed datasets and processing capabilities by the construction of pipelines, and also to simplify the execution of these pipelines in various environments. The Taverna suite of products is already successful and in wide-use across different domains. The software is currently licensed as LGPL 2.1, with copyright owned by University of Manchester. External contributors have all signed Apache-like CLAs. # Background Taverna workflows coordinate inputs and outputs between computational processes and Web Services. The workflow is designed in a graphical interface which shows the workflow as a series of boxes and arrows; representing processes and their data connections. The different processes in a workflow can be command line tools, REST and WSDL Web Services; which are used for combining steps such as data acquisition, filtering, cleaning, integrating, analysis and visualization. Taverna calls these processes services, as they generally are provided by remote (third-party) servers. These kind of computational workflows, also known as pipelines and dataflows, focus on the movement of data rather than the execution order of the underlying processes. Features such as implicit iterations (where an input list of values causes multiple process executions) and parallel invocations (independent processes are executed as soon as their data is available) are intrinsic to a dataflow system, not requiring any particular constructs by the workflow designer. As a visual programming environment, workflows aids collaboration and reuse of workflows. At the highest level, a workflow represents the conceptual level of an analysis, allowing understanding, discussion and communication of the overall analysis protocol. More detail can be revealed and modified for individual steps. At the individual process level, the workflow defines execution specifics such as operations, parameters and command line tools. Sharing of the workflow definitions allows re-use and re-purposing of the computational analysis. During workflow execution, provenance can be collected from every step, allowing deep inspection of intermediate values for the purpose of debugging and validation. # Rationale There is a strong need to lower the barrier of entry to datasets and computational resources widely available on the Internet, to increase their use by researchers who understand the computational steps needed to produce their results, but who are not necessarily expert programmers. Taverna has already shown its success and popularity in a wide range of scientific disciplines. # Initial Goals * Transition mailing lists to Apache (keep existing subscribers, but invite more) * Taverna developer workshop (2014-10-30) * Prepare git repositories for move: * Update headers/metadata to indicate Apache License 2.0 * Restructure git repositories * Rename Maven groupIds to org.apache.taverna.* * Rename packages to org.apache.taverna.* * Move Github repositories to Apache git * Automated builds in Apache's Jenkins * Update to latest releases of Apache dependencies * Propose updated release testing procedure under Apache * Moved Website and documentation We intend to only release the current development version Taverna 3.x http://www.taverna.org.uk/developers/work-in-progress/taverna-3/ under
Re: [VOTE] Accept Lens into the Apache Incubator (earlier called Grill)
+1 (binding) Sent from phone On Oct 8, 2014, at 12:20 PM, Joe Brockmeier j...@zonker.net wrote: On Mon, Oct 6, 2014, at 06:51 AM, Sharad Agarwal wrote: [ ] +1 accept Lens in the Incubator +1 (binding) Best, jzb -- Joe Brockmeier j...@zonker.net Twitter: @jzb http://www.dissociatedpress.net/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- CONFIDENTIALITY NOTICE NOTICE: This message is intended for the use of the individual or entity to which it is addressed and may contain information that is confidential, privileged and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, you are hereby notified that any printing, copying, dissemination, distribution, disclosure or forwarding of this communication is strictly prohibited. If you have received this communication in error, please contact the sender immediately and delete it from your system. Thank You. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept Taverna into the Apache Incubator
+1 (binding) Sent from phone On Oct 16, 2014, at 3:43 PM, Andy Seaborne a...@apache.org wrote: [ ] +1 accept Taverna in the Incubator [ ] ±0 [ ] -1 because... +1 (binding) Andy - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- CONFIDENTIALITY NOTICE NOTICE: This message is intended for the use of the individual or entity to which it is addressed and may contain information that is confidential, privileged and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, you are hereby notified that any printing, copying, dissemination, distribution, disclosure or forwarding of this communication is strictly prohibited. If you have received this communication in error, please contact the sender immediately and delete it from your system. Thank You. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept HTrace into the Apache Incubator
+1 (binding) On Wed, Nov 5, 2014 at 11:16 AM, Roman Shaposhnik r...@apache.org wrote: Following the discussion earlier in the thread: http://s.apache.org/Dk7 I would like to call a VOTE for accepting HTrace as a new incubator project. The proposal is available at: https://wiki.apache.org/incubator/HTraceProposal Vote is open until at least Sunday, 9th November 2014, 23:59:00 UTC [ ] +1 accept Lens in the Incubator [ ] ±0 [ ] -1 because... - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- http://hortonworks.com/download/ -- CONFIDENTIALITY NOTICE NOTICE: This message is intended for the use of the individual or entity to which it is addressed and may contain information that is confidential, privileged and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, you are hereby notified that any printing, copying, dissemination, distribution, disclosure or forwarding of this communication is strictly prohibited. If you have received this communication in error, please contact the sender immediately and delete it from your system. Thank You.
Re: [VOTE] Graduation of Apache Falcon from the Incubator
+1 (binding) On Wed, Nov 5, 2014 at 5:48 AM, Jean-Baptiste Onofré j...@nanthrax.net wrote: Hi all, We wrapped up the vote on the Apache Falcon dev list in which the community expressed its desire to graduate to a top-level project. The vote has passed with: 13 binding +1 votes 8 non-binding +1 votes no 0 or -1 vote This is the Incubator vote to decide if Apache Falcon should graduate from the Incubator. Please see the resolution later in this e-mail. This vote is open for at least 72 hours. [ ] +1 Graduate Apache Falcon from the Incubator. [ ] +0 Don't care. [ ] -1 Don't graduate Apache Falcon from the Incubator because ... Thanks, Regards JB resolution WHEREAS, the Board of Directors deems it to be in the best interests of the Foundation and consistent with the Foundation's purpose to establish a Project Management Committee charged with the creation and maintenance of open-source software, for distribution at no charge to the public, related to Big Data management platform covering data pipelines, data motion, data lifecycle management, data discovery governance NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the Apache Falcon Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Falcon Project be and hereby is responsible for the creation and maintenance of software related to interactive analysis of large-scale datasets; and be it further RESOLVED, that the office of Vice President, Apache Falcon be and hereby is created, the person holding such office to serve at the direction of the Board of Directors as the chair of the Apache Falcon Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Falcon Project; and be it further RESOLVED, that the persons listed immediately below be and hereby are appointed to serve as the initial members of the Apache Falcon Project: * Srikanth Sundarrajan sriksun at apache dot org * Venkatesh Seetharam venkatesh at apache dot org * Shwetha GS shwethags at apache dot org * Shaik Idris shaikidris at apache dot org * Sanjay Radia sanjay at apache dot org * Sharad Agarwal sharad at apache dot org * Amareshwari SR amareshwari at apache dot org * Samarth Gupta samarthg at apache dot org * Rishu Mehrothra rishumehrothra at apache dot org * Arpit Gupta arpit at apache dot org * Suhas Vasu suhas.vasu at apache dot org * Jean-Baptiste Onofré jbonofre at apache dot org * Ruslan Ostafiychuk rostafiychuk at apache dot org * Raghav Kumar Gautam raghav at apache dot org NOW, THEREFORE, BE IT FURTHER RESOLVED, that Srikanth Sundarrajan be appointed to the office of Vice President, Apache Falcon, to serve in accordance with and subject to the direction of the Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed; and be it further RESOLVED, that the Apache Falcon Project be and hereby is tasked with the migration and rationalization of the Apache Incubator Falcon podling; and be it further RESOLVED, that all responsibilities pertaining to the Apache Incubator Falcon podling encumbered upon the Apache Incubator Project are hereafter discharged. -- 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 -- http://hortonworks.com/download/ -- CONFIDENTIALITY NOTICE NOTICE: This message is intended for the use of the individual or entity to which it is addressed and may contain information that is confidential, privileged and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, you are hereby notified that any printing, copying, dissemination, distribution, disclosure or forwarding of this communication is strictly prohibited. If you have received this communication in error, please contact the sender immediately and delete it from your system. Thank You.
Re: [VOTE] Release Apache Ranger 0.4.0 (incubating) - (formally known as Apache Argus)
+1 (binding) On Thursday, November 13, 2014, Selvamohan Neethiraj sneet...@apache.org wrote: The Apache Ranger community has voted on and approved a proposal to release Apache Ranger 0.4.0 (incubating). This will be our first release since the project entered incubation in July 2014 as Apache Argus and then, got it renamed as Apache Ranger. The ranger-0.4.0-rc3 release candidate is now available with the following artifacts up for a project vote : Git tag for the release: https://git-wip-us.apache.org/repos/asf?p=incubator-argus.git;a=shortlog;h=refs/tags/ranger-0.4.0-rc3 Source release: http://people.apache.org/~sneethir/ranger/ranger-0.4.0-rc3/ranger-0.4.0-rc3.tar.gz Source release verification: PGP Signature: http://people.apache.org/~sneethir/ranger/ranger-0.4.0-rc3/ranger-0.4.0-rc3.tar.gz.asc MD5/SHA Hash: http://people.apache.org/~sneethir/ranger/ranger-0.4.0-rc3/ranger-0.4.0-rc3.tar.gz.mds Keys to verify the signature of the release artifact are available at: https://people.apache.org/keys/group/argus.asc Build verification steps can be found at: http://argus.incubator.apache.org/quick_start_guide.html The vote will be open for at least 72 hours or until necessary number of votes are reached. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Here is my +1 (non binding) Thanks Selva- -- Sent from a mobile device -- CONFIDENTIALITY NOTICE NOTICE: This message is intended for the use of the individual or entity to which it is addressed and may contain information that is confidential, privileged and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, you are hereby notified that any printing, copying, dissemination, distribution, disclosure or forwarding of this communication is strictly prohibited. If you have received this communication in error, please contact the sender immediately and delete it from your system. Thank You.
Re: [VOTE] accept NiFi into the incubator
+1 On Fri, Nov 21, 2014 at 10:55 AM, Benson Margulies bimargul...@gmail.com wrote: http://wiki.apache.org/incubator/NiFiProposal has elicited a cheerful and positive conversation, so I offer this vote. Vote will be open for the usual 72 hours ... Here is my [+1] -- http://hortonworks.com/download/ -- CONFIDENTIALITY NOTICE NOTICE: This message is intended for the use of the individual or entity to which it is addressed and may contain information that is confidential, privileged and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, you are hereby notified that any printing, copying, dissemination, distribution, disclosure or forwarding of this communication is strictly prohibited. If you have received this communication in error, please contact the sender immediately and delete it from your system. Thank You.
Re: [VOTE] Release Falcon version 0.6-incubating
+1 (binding) On Fri, Nov 28, 2014 at 11:11 PM, Seetharam Venkatesh venkat...@innerzeal.com wrote: Hello folks, This is a call for a vote on Apache Falcon 0.6 incubating release. A vote was held on developer mailing list and it passed with 10 +1's. Vote thread: http://s.apache.org/YwI Results thread: http://s.apache.org/8Pq The source tarball (*.tar.gz), signature (*.asc), checksum (*.md5, *.sha): http://people.apache.org/~venkatesh/falcon-0.6-incubating-rc1/source/ The SHA1 checksum of the archive is 2060489fc68b273560e0ea783318fa3fad3b19cb The commit id (e2482b8b24ce27bd3caa9e7aa96be67e945eff57) to ve voted upon: https://git-wip-us.apache.org/repos/asf?p=incubator-falcon.git;a=commit;h=e2482b8b24ce27bd3caa9e7aa96be67e945eff57 The tag to be voted upon: https://git-wip-us.apache.org/repos/asf?p=incubator-falcon.git;a=tag;h=refs/tags/release-0.6-rc1 The list of fixed issues: https://git-wip-us.apache.org/repos/asf?p=incubator-falcon.git;a=blob;f=CHANGES.txt;h=2b131c0e5c2dcb98ddd40f680ff688b0b018998c;hb=e2482b8b24ce27bd3caa9e7aa96be67e945eff57 The release has been signed through key(42C7A5EA): http://pgp.mit.edu:11371/pks/lookup?op=vindexsearch=0x1B16738C42C7A5EA Keys to verify the signature of the release artifact are available at: http://www.apache.org/dist/incubator/falcon/KEYS PGP release keys: http://pgp.mit.edu/pks/lookup?op=vindexsearch=0x1B16738C42C7A5EA Note that this is a source only release and we are voting on the source. Checksums: SHA1 (release-0.6-incubating-rc1 / SHA: 2060489fc68b273560e0ea783318fa3fad3b19cb) MD5 (apache-falcon-0.6-incubating-sources.tar.gz) = cccf15351e1de32e4738d6f067025819 Vote will be open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) +1 from my side for the release. Thanks! -- Regards, Venkatesh “Perfection (in design) is achieved not when there is nothing more to add, but rather when there is nothing more to take away.” - Antoine de Saint-Exupéry -- http://hortonworks.com/download/ -- CONFIDENTIALITY NOTICE NOTICE: This message is intended for the use of the individual or entity to which it is addressed and may contain information that is confidential, privileged and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, you are hereby notified that any printing, copying, dissemination, distribution, disclosure or forwarding of this communication is strictly prohibited. If you have received this communication in error, please contact the sender immediately and delete it from your system. Thank You.
Re: [Proposal] TinkerPop: A Graph Computing Framework
+1 Thanks for the proposal. In Apache Falcon we use Blueprints. I am happy to see TinkerPop moving to ASF. Let me know if you need a mentor. On Wed, Dec 17, 2014 at 11:09 AM, Marko Rodriguez okramma...@gmail.com wrote: Hello, My name is Marko A. Rodriguez and am a co-founder of TinkerPop ( http://tinkerpop.com). There has been positive pressure on us (both internally and externally) to move TinkerPop to The Apache Foundation. This email contains our proposal and I, on behalf of TinkerPop, thank you for spending your time reading it. Take care, Marko. http://markorodriguez.com *A. Abstract* TinkerPop is a graph computing framework written in Java -- http://tinkerpop.com. TinkerPop started in 2009 and is currently in the milestone series of 3.0.0. Graph system vendors such as in-memory graph libraries, OLTP graph databases, and OLAP graph processors can provide a TinkerPop implementation ( http://markorodriguez.com/2013/01/09/on-graph-computing/). Once the core TinkerPop interfaces are implemented, the underlying graph system can be queried using the graph traversal language Gremlin. TinkerPop was designed to be used at any scale and as such, can be leveraged by both single-server and multi-machine compute clusters. For many, TinkerPop is seen as the JDBC of the graph computing community ( http://en.wikipedia.org/wiki/Java_Database_Connectivity). *B. Proposal* Since its inception in 2009, TinkerPop has been open source, free to use. Initially the license was BSD, but as of TinkerPop3, the license is Apache2. The TinkerPop team is composed of developers as well as representatives from numerous graph system vendors ( http://www.tinkerpop.com/docs/3.0.0-SNAPSHOT/#tinkerpop-contributors). TinkerPop has done its best to remain vendor agnostic and works closely with vendors to ensure that the constructs within TinkerPop are able to accommodate the requirements of the underlying graph system. To date, over 12 graph system vendors provide TinkerPop implementations. We believe that by joining The Apache Foundation, our vendors, users, and contributors will feel more comfortable in terms of legal protected, in terms of wider-adoption, and in terms of project stability. *C. Background* TinkerPop was founded in 2009 and has had steady, active development since. Over the years, the Gremlin query language within TinkerPop has been adopted by various JVM languages and as such, there exists Gremlin-Groovy, Gremlin-Scala, Gremlin-Clojure, Gremlin-JavaScript, and the like. In many ways, Gremlin is seen as a traversal language style that can be readily adopted by developers --- on and off the JVM. TinkerPop is not bound to the JVM in that developers wishing to interact with a TinkerPop-enabled graph system can leverage Gremlin Server which provides over the wire communication as well as the entry point for non-JVM language bindings. TinkerPop is being used is production graph-based applications around the world and is only getting better with age. *D. Rationale* The graph computing space has grown over the years to encompass numerous graph database and graph processing systems. TinkerPop was created as a unifying framework for interoperability, language standardization, and data model standardization. This framework makes it simple to plug and play the back-end graph implementation without affecting the developer's code. This is analogous to the way in which JDBC allows users to swap relational databases while keeping the same programming interface. TinkerPop also brings together OLTP systems (graph databases) and OLAP systems (graph processors) by providing a single query language, Gremlin, for executing graph algorithms transparently over either type of system. Finally, TinkerPop unifies single-machine systems and distributed systems, presenting an identical user experience within the boundaries of the computational space and time constraints of the underlying graph system. *E. Initial Goals* The goal of this proposal is to migrate TinkerPop to The Apache Foundation to 1.) get more exposure to the project and 2.) legally protect the developers and contributors of TinkerPop. *F. Current Status* TinkerPop is planning to release TinkerPop 3.0.0.GA early 2015 -- January or February. We would like to release TinkerPop 3.0.0.GA under The Apache Foundation. *G. Meritocracy* Anyone is welcome to join TinkerPop as a contributor. If an individual provides successful code updates, documentation updates, etc. then they are asked to join TinkerPop contributors. Once inside TinkerPop, they are able to voice their opinions/thoughts on the direction of the project. Moreover, TinkerPop actively seeks vendors who leverage TinkerPop in their offering to place a representative on TinkerPop contributors who can speak on behalf of their organization as it relates to the requirements of their graph system.
Re: [VOTE] Accept Apache Atlas into Apache Incubator
orphaned. A prototype of Atlas is in use and being actively developed by several companies and have vested interest in its continued vitality and adoption. === Inexperience with Open Source === Many of the core developers are PMC and committers of Apache. Harish Butani is PMC Apache Hive, Venkatesh Seetharam is PMC on Apache Falcon and Apache Knox, Shwetha GS is PMC on Apache Falcon and Apache Oozie committer. === Homogeneous Developers === The current core developers are from diverse set of organizations such as Hortonworks, Aetna, JPMC, Merck, SAS, Schlumberger and Target. We expect to quickly establish a developer community that includes contributors from additional organizations post incubation. === Reliance on Salaried Developers === Currently, most developers are paid to do work on Atlas but few are contributing in their spare time. However, once the project has a community built around it post incubation, we expect to get additional committers and developers from outside the current core developers. === Relationships with Other Apache Products === Atlas is going to be used by the users of Apache Hadoop and the Hadoop ecosystem in general – particularly with Apache Falcon and Apache Ranger for rationalizing data lifecycle and security policies respectively. === A Excessive Fascination with the Apache Brand === While we respect the reputation of the Apache brand and have no doubts that it will attract contributors and users, our interest is primarily to give Atlas a solid home as an open source project following an established development model. We have also given reasons in the Rationale and Alignment sections. == Documentation == http://people.apache.org/~venkatesh/atlas/ == Initial Source == The source is currently hosted at: http://people.apache.org/~venkatesh/atlas/ == Source and Intellectual Property Submission Plan == The complete Atlas code is under Apache Software License 2. == External Dependencies == The dependencies all have Apache compatible licenses. These include BSD, MIT licensed dependencies. == Cryptography == None == Required Resources == === Mailing lists === * atlas-dev AT incubator DOT apache DOT org * atlas-commits AT incubator DOT apache DOT org * atlas-private AT incubator DOT apache DOT org === Subversion Directory === Git is the preferred source control system: git://git.apache.org/atlas === Issue Tracking === JIRA Atlas == Initial Committers == * Venkatesh Seetharam (venkatesh AT apache DOT org) * Harish Butani (rhbutani AT apache DOT org) * Shwetha Shivalingamurthy (shwethags AT apache DOT org) * Jon Maron (jmaron AT hortonworks DOT com) * Andrew Ahn (aahn AT hortonworks DOT com) * David Kaspar (david DOT kaspar AT merck DOT com) * Ivo Lasek (ivo DOT lasek AT merck DOT com) * Dennis Fusaro (fusarod AT aetna DOT com) * Chris Hyzer (hyzerc AT aetna DOT com) * Daniel Markwat (markwatd AT aetna DOT com) * Greg Senia (seniag AT aetna DOT com) * James Vollmer (james DOT vollmer AT target DOT com) * Aaron Dossett (aaron DOT dossett AT target DOT com) * Mitch Schussler(Mitch DOT Schussler AT jpmorgan DOT com) * Viswanath Avasarala (VAvasarala AT SLB dot com) * Anil Varma (AVarma AT SLB dot com) * Barbara Stortz (Barbara DOT stortz AT sap DOT com) * Srikanth Sundarrajan (sriksun AT apache DOT org) * Suresh Srinivas (suresh AT hortonworks DOT org) * Venkat Ranganathan (vranganathan AT hortonworks DOT com) == Affiliations == * Venkatesh Seetharam (Hortonworks) * Harish Butani (Hortonworks) * Swetha Shivalingamurthy (Hortonworks) * Jon Maron (Hortonworks) * Andrew Ahn (Hortonworks) * David Kasper (Merck) * Ivo Lasek (Merck) * Dennis Fusaro (Aetna) * Chris Hyzer (Aetna) * Daniel Markwat (Aetna) * Greg Senia (Aetna) * James Vollmer (Target) * Aaron Dossett (Target) * Schussler, Mitch (JPMC) * Viswanath Avasarala (Schlumberger) * Anil Varma (Schlumberger) * Barbara Stortz (SAP) * Srikanth Sundarrajan (InMobi) * Suresh Srinivas (Hortonworks) * Venkat Ranganathan (Hortonworks) == Sponsors == === Champion === * Jitendra Nath Pandey (jitendra AT apache DOT org) === Nominated Mentors === * Arun Murthy (acmurthy AT apache DOT org) * Chris Douglas (cdouglas AT apache DOT org) * Jakob Homan (jghoman AT apache DOT org) * Vinod Kumar Vavilapalli (vinodkv AT apache DOT org) === Sponsoring Entity === Incubator PMC -- Regards, Venkatesh “Perfection (in design) is achieved not when there is nothing more to add, but rather when there is nothing more to take away.” - Antoine de Saint-Exupéry - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
