Re: Documentation Donation
Hi, On Tue, Aug 12, 2014 at 1:32 AM, John D. Ament john.d.am...@gmail.com wrote: ...if a podling/TLP were to receive a donation of documentation from a third party, should that go through the same reviews as source code donations?... IMO yes. Flex did something like that in http://incubator.apache.org/ip-clearance/flex-adc-pmd-squiggly-fdb-tdf.html -Bertrand - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Documentation Donation
On Mon, Aug 11, 2014 at 11:38 PM, Bertrand Delacretaz bdelacre...@apache.org wrote: Hi, On Tue, Aug 12, 2014 at 1:32 AM, John D. Ament john.d.am...@gmail.com wrote: ...if a podling/TLP were to receive a donation of documentation from a third party, should that go through the same reviews as source code donations?... IMO yes. Flex did something like that in http://incubator.apache.org/ip-clearance/flex-adc-pmd-squiggly-fdb-tdf.html Yup. FWIW: I am of the same opinion. Thanks, Roman. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] Incubator exit criteria
On Mon, Aug 11, 2014 at 1:14 AM, Bertrand Delacretaz bdelacre...@apache.org wrote: On Mon, Aug 11, 2014 at 2:22 AM, Roman Shaposhnik r...@apache.org wrote: ...Including the patch below... Sorry to come in late but I had a look at [1] and it's way too complicated IMO, and I don't think the proposed patch helps with that. In general http://incubator.apache.org/ is way too verbose and hard to maintain - removing everything that is not essential would help IMO. With this in mind, I would remove almost everything from the What is retirement section and keep just A retired project is a project which has been closed down for various reasons, instead of graduating as an Apache project. It is no longer developed in the Apache Incubator and does not have any other duties. The project's code might stay available on Apache servers, if all the required IP clearance requirements have been met. Retirement is a decision of the Incubator PMC, which usually delegates it to the incubating project's mentors. The opinion of the incubating project's community should of course be taken into account, but in the end it's the Incubator PMC which makes the decision. And also keep the steps to retirement section. I totally agree with the section being overly complex to parse. I am, however, a little bit afraid of such a drastic edit ;-) Two points on that: * since I haven't seen much of complaining, can I please commit my proposed stuff and then we can pile additional edits on top of that? * re-reading those sections made me realize that we are making a distinction between two types of non-graduation: termination and retirement. The way I read it, with termination there's no code left. With retirement code is still available. Am I correct? Thanks, Roman. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] Incubator exit criteria
On Tue, Aug 12, 2014 at 9:08 AM, Roman Shaposhnik r...@apache.org wrote: ... * since I haven't seen much of complaining, can I please commit my proposed stuff and then we can pile additional edits on top of that?... Sure, my complaining is more a general issue about incubator.apache.org * re-reading those sections made me realize that we are making a distinction between two types of non-graduation: termination and retirement. The way I read it, with termination there's no code left. With retirement code is still available. Am I correct? that's too complicated, I would scratch it ;-) How many podlings retire per year? Like one or two maybe - keep it simple. -Bertrand - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Documentation Donation
On 12 August 2014 08:53, Roman Shaposhnik ro...@shaposhnik.org wrote: On Mon, Aug 11, 2014 at 11:38 PM, Bertrand Delacretaz bdelacre...@apache.org wrote: Hi, On Tue, Aug 12, 2014 at 1:32 AM, John D. Ament john.d.am...@gmail.com wrote: ...if a podling/TLP were to receive a donation of documentation from a third party, should that go through the same reviews as source code donations?... IMO yes. Flex did something like that in http://incubator.apache.org/ip-clearance/flex-adc-pmd-squiggly-fdb-tdf.html Yup. FWIW: I am of the same opinion. Documents are source code written in a natural language :-) IMO yes. Bear in mind documents are often the first thing a person sees, when looking for technology, therefore its important that they are correct. rgds jan I. Thanks, Roman. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] Incubator exit criteria
On 12 August 2014 09:38, Bertrand Delacretaz bdelacre...@apache.org wrote: On Tue, Aug 12, 2014 at 9:08 AM, Roman Shaposhnik r...@apache.org wrote: ... * since I haven't seen much of complaining, can I please commit my proposed stuff and then we can pile additional edits on top of that?... Sure, my complaining is more a general issue about incubator.apache.org * re-reading those sections made me realize that we are making a distinction between two types of non-graduation: termination and retirement. The way I read it, with termination there's no code left. With retirement code is still available. Am I correct? that's too complicated, I would scratch it ;-) How many podlings retire per year? Like one or two maybe - keep it simple. +1. and dont forget its projects leaving incubator, imho they know how we work, so simple should really do it. rgds jan I -Bertrand - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] Incubator exit criteria
On Tue, Aug 12, 2014 at 8:08 AM, Roman Shaposhnik r...@apache.org wrote: On Mon, Aug 11, 2014 at 1:14 AM, Bertrand Delacretaz bdelacre...@apache.org wrote: On Mon, Aug 11, 2014 at 2:22 AM, Roman Shaposhnik r...@apache.org wrote: ...Including the patch below... Sorry to come in late but I had a look at [1] and it's way too complicated IMO, and I don't think the proposed patch helps with that. In general http://incubator.apache.org/ is way too verbose and hard to maintain - removing everything that is not essential would help IMO. With this in mind, I would remove almost everything from the What is retirement section and keep just A retired project is a project which has been closed down for various reasons, instead of graduating as an Apache project. It is no longer developed in the Apache Incubator and does not have any other duties. The project's code might stay available on Apache servers, if all the required IP clearance requirements have been met. Retirement is a decision of the Incubator PMC, which usually delegates it to the incubating project's mentors. The opinion of the incubating project's community should of course be taken into account, but in the end it's the Incubator PMC which makes the decision. And also keep the steps to retirement section. I totally agree with the section being overly complex to parse. I am, however, a little bit afraid of such a drastic edit ;-) Two points on that: * since I haven't seen much of complaining, can I please commit my proposed stuff and then we can pile additional edits on top of that? * re-reading those sections made me realize that we are making a distinction between two types of non-graduation: termination and retirement. The way I read it, with termination there's no code left. With retirement code is still available. Am I correct? I also feel this is adding unnecessary complexity and would prefer the edits simplify rather than add more things. If you're really insisting on adding some of this text would you at least not add the following bit for now: At this point the project is expected to be put on a monthly reporting schedule and the next month's report is expected to articulate the steps and expected time frame to get to the release. In case of a clear lack of progress for straight three months the [VOTE] thread on potential retirement is expected to be started in IPMC. ...ant
[VOTE] Release Sentry incubating version 1.4.0 (rc0)
Hello IPMC, We have passed the PPMC vote for Sentry incubator release 1.4.0-rc0 with 3 +1 votes from Brock Noland, Jarek Jarcec Cecho, and Sravya Tirukkovalur. We ask for your help to vote on this incubator release. This is the incubator release of Apache Sentry, version 1.4.0-incubating. The list of fixed issues, added features and improvements can be found here: https://git-wip-us.apache.org/repos/asf?p=incubator-sentry.git;a=blob;f=CHANGELOG.txt;h=962ac73d6b091093ac9ee72b675a3de1b241d242;hb=branch-1.4.0 Source files : http://people.apache.org/~sravya/sentry-1.4.0-rc0/ Tag to be voted on is (release 1.4.0-rc0/SHA: 5e6e34202b26d7d5bc1a41e3dd4ad0cacd123e3f): https://git-wip-us.apache.org/repos/asf/incubator-sentry/repo?p=incubator-sentry.git;a=log;h=refs/tags/release-1.4.0 Sentry's KEYS containing the PGP key we used to sign the release: http://www.apache.org/dist/incubator/sentry/KEYS Note that this is a source only release and we are voting on the source (release 1.4.0-rc0/SHA: 5e6e34202b26d7d5bc1a41e3dd4ad0cacd123e3f). Vote will be open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Thank you for your prompt votes.. Thanks to Sravya for all her help and guidance... Respectfully, Sentry 1.4.0 Release Manager (Tuong Truong)
Re: Documentation Donation
On 12 August 2014 08:52, jan i j...@apache.org wrote: On 12 August 2014 08:53, Roman Shaposhnik ro...@shaposhnik.org wrote: Documents are source code written in a natural language :-) and without any tests. -- 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 Mon, Aug 11, 2014 at 6:20 PM, Hitesh Shah hit...@apache.org wrote: +1 ( non-binding ) — Hitesh On 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,
Re: [VOTE] Accept REEF into the Apache Incubator
+1 (binding) -Jake On Sat, Aug 9, 2014 at 1:40 AM, 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: [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: [VOTE] Accept REEF into the Apache Incubator
On Aug 12, 2014 7:26 PM, Suresh Srinivas sur...@hortonworks.com wrote: +1 (binding) +1 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,
Re: [VOTE] Accept REEF into the Apache Incubator
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... +1 (binding) Thanks, Roman. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] Incubator exit criteria
On 11 Aug 2014, at 10:14, Bertrand Delacretaz wrote: With this in mind, I would remove almost everything from the What is retirement section and keep just A retired project is a project which has been closed down for various reasons, instead of graduating as an Apache project. It is no longer developed in the Apache Incubator and does not have any other duties. The project's code might stay available on Apache servers, if all the required IP clearance requirements have been met. Retirement is a decision of the Incubator PMC, which usually delegates it to the incubating project's mentors. The opinion of the incubating project's community should of course be taken into account, but in the end it's the Incubator PMC which makes the decision. Interesting and I think this is really good (writes a guy who discussed the rules a lot). The problem we wanted to solve (i think) was: how can we keep our incubator list clean and be pro-active when it comes to housekeeping? If the IPMC would look at the reporting podlings each month and check if retirement is needed, then the above phrase might make perfect sense. Some might consider it unfair to be retired. In example, some projects as Wave look inactive but there is some life left. Retire or not? It's subjective. There is a good chance we keep some long-term running projects, but on the other hand... what would it matter? That being said, I would love if the other docs would get such an haircut as well. Cheers, Christian And also keep the steps to retirement section. -Bertrand [1] http://incubator.apache.org/guides/retirement.html - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org --- http://www.grobmeier.de The Zen Programmer: http://bit.ly/12lC6DL @grobmeier GPG: 0xA5CC90DB - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept REEF into the Apache Incubator
+1 -C 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 developers to
Mentor Sign off
Hi HDT! Looks like you're the last hold out. Any chance a mentor (Suresh/Roman/Chris) could review the report and sign off? John
Re: [VOTE] Release Sentry incubating version 1.4.0 (rc0)
Hi, +1 binding Checked: - release has incubating in name - signatures and hashes good - all source has correct headers - no binary files in releases (other than a few test files) - DISCLAIMER exists - LICENSE and NOTICE correct - can compile source - test pass For next release: - consider adding apache to release package name - sign package from apache account (email in signature is gmail.com) - place package in correct location not on http://people.apache.org - is year range needed in NOTICE? Thanks, Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Mentor Sign off
Sorry about that -- I reviewed their report on the ML, but somehow never got around to updating the wiki. Done! Thanks, Roman. P.S. Now reviewing the overall report... On Tue, Aug 12, 2014 at 5:23 PM, John D. Ament john.d.am...@gmail.com wrote: Hi HDT! Looks like you're the last hold out. Any chance a mentor (Suresh/Roman/Chris) could review the report and sign off? John - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
