Re: Followup to VXQuery July 2013 report
Hi, Just to confirm several other Apache projects web site include links to nightly builds, but in most cases it's clear that it for development use, so is it OK to do like these projects do? Solr: http://wiki.apache.org/solr/NightlyBuilds JMeter: http://jmeter.apache.org/nightly.html Direcory: http://directory.apache.org/studio/nightly-builds.html Nutch: http://nutch.apache.org/nightly.html Ant: http://ant.apache.org/nightlies.html I'm asking because we may have a similar issue with the Apache Flex web site and the Apache Flex SDK installer. The last release of the Apache Flex installer allowed a user to install the nightly build, however it does default to the last official release and lists previous releases. Thanks, Justin
Write access to wiki
May I have write access to the incubator wiki (username NathanMarz) so that I can add a proposal for Storm? Thanks, Nathan
Write access to wiki
May I have write access to the incubator wiki (username NathanMarz) so that I can add a proposal for Storm? Thanks, Nathan
Re: Write access to wiki
Nathan Marz wrote: May I have write access to the incubator wiki (username NathanMarz) so that I can add a proposal for Storm? Thanks, Nathan Done. -David - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Followup to VXQuery July 2013 report
On Tue, Sep 3, 2013 at 11:42 PM, David Crossley cross...@apache.org wrote: ant elder wrote: Hi Marvin, I had a look, that README being pointed to is just build instructions on how to build the svn trunk isn't it, so not to some released artifacts. Thats allowed isn't it, i'm pretty sure other projects and podlings have done something similar anyway. Is it that the website describes it as user installation instructions rather than developer build instructions thats the issue? ...ant I reckon so. To clearly refer developers to developer resources is fine, but users no. They need to be referred to user instructions. In VXQuery's case, there's nothing to refer users to because in four years, VXQuery has never made an incubating release. If developer instructions for accessing version control are added to the website in accordance with ASF guidelines, of course that's fine -- so long as all user installation instructions are removed. Here's more background from the legal-discuss list regarding the current policy, this time from a different Board member, Doug Cutting: http://markmail.org/message/pelvob23vrzuzws5 Each PMC should attempt to ensure that every commit is in accord with Apache's intellectual property policies. Releases are a double-check of this. We hope that source code repositories are not legally considered publications, but we don't know that courts will in fact always treat them that way, so it's best to guard against that too. Note that the extra scrutiny around releases both serves to double-check (belt and suspenders) as well as to provide evidence that we do not consider the source code repository as a publication. But again, we cannot depend on others to agree with that, and must guard against other interpretations as best we can. If VXQuery finds it uncomfortable not to have anything they can show users, they can solve that by making a release. Marvin Humphrey - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Castafiore framework proposal to incubator
I think Kureem already knows the incubation process. He is looking for a java champion. Since he already has a first draft of his proposal, I asked him to copy it so people interessed could have an idea what the project is about. Sorry if my communication caused any inconvenience On Wed, Sep 4, 2013 at 8:50 AM, David Crossley cross...@apache.org wrote: Kureem Rossaye wrote: Hello community, please find below a proposal I wish to submit to the ASF. I am new here and was told that I could paste the proposal here. So here we are. That was misleading to simply say that. There is quite a process which will all be beneficial. Awaiting reply, recommendation and feedback and will be pleased to answer any questions. Please review the Incubator website. There are instructions about the process for Proposals. http://incubator.apache.org/ In the top-left see the link to the Proposal Guide. -David Thanks in advance Kind regards, Kureem Rossaye Abstract Castafiore framework is a web frameworks, fully component oriented, ajax based, one page appplication. Although the framework can be viewed as a classical component oriented web framework like GWT, it has been designed and implemented with a particular goal in mind. It is to be able to make existing javascript libraries java-able. Meaning that the framework allows to easily take a javascript library like e.g jquery ui and use the components and features via java. The integration of the javascript libraries need to be easy and natural. Actually companies like ext js and smartgwt have made their components java-able using GWT. I wish to provide an alternative to gwt that is much easier, fast, lightweight, and much more productive. Proposal Castafiore framework has been designed and implemented with the following goals in mind 1. Fully object oriented 2. Simple API that is very close to html itself We wanted an API that is closer to html markup and javascripts event model. I believe that this would help web developers easily visualize the rendering when reading source code. 3. Write a full application with only java 4. No need for compiler to convert to javascript like gwt.Javascript is rendered at runtime. 5. The same API can be used to make an software that is server centric and or client centric. Meaning that the user can make part of his application server centric and part of his application client centric. He can of course choose to make the whole application client centric or server centric depending on the requirement. All of this using the same API. 6. Low memory footprint 7. Easy packaging of application. Everything can be packaged in a single jar. This includes images, css or javascript as well 8. Same API used to create custom components. No need to external set of API or specific programming technique to create custom components. Creating a custom components should be done only the same way as writing an application. 9. No need for javascript to create custom components. 10. Although there is no need for javascript to create an application, it should be easy to integrate external javascript libraries and use them in java codes itself. This should be done is a natural way just like we would do in an HTML page. This should be like this so that javascript library authors with some java skills find it natural and easy to provide a castafiore component together with the library. e.g. The author of flexgrid should should find it easy to create a castafiore component thus making his library usable directly in java. *Actually, I wanted to create a java web framework for javascript programmers. They should find it easy and fun to integrate and distribute their js libraries as a castafiore component. They will be able to distribute their libraries as a single jar. This is very convenient for java developers to just download the jar, include in classpath, and using the library, components and feature right away in their web application in pure java. Furthermore the castafiore framework itself is very lightweight with just 2 libraries and 1 web.xml entry. Even if the java developer is not using castafiore in his project, he should find it easy to just drop the 2 libraries + web.xml entry in classpath and start using it right away. Very practical.* 1. Load external resources like css and javascript lazily and efficiently only when needed. 2. Loading of external resources can be done eagerly if the API user wish so. 3. The framework does not own the whole page. Meaning that an application created with the framework can be used in an already created page. This allows API developer to use
[PROPOSAL] Castafiore framework proposal to incubator
Hi, Indeed, I have read the incubation proposal guide. The only thing I could not figure out is how to recruit a champion. However, after re-reading the guide, I missed something. I should have prefixed the subject of the mail with [PROPOSAL]. So I am resending the proposal with the proper subject. ** PROPOSAL Abstract Castafiore framework is a web frameworks, fully component oriented, ajax based, one page appplication. Although the framework can be viewed as a classical component oriented web framework like GWT, it has been designed and implemented with a particular goal in mind. It is to be able to make existing javascript libraries java-able. Meaning that the framework allows to easily take a javascript library like e.g jquery ui and use the components and features via java. The integration of the javascript libraries need to be easy and natural. Actually companies like ext js and smartgwt have made their components java-able using GWT. I wish to provide an alternative to gwt that is much easier, fast, lightweight, and much more productive. Proposal Castafiore framework has been designed and implemented with the following goals in mind 1. Fully object oriented 2. Simple API that is very close to html itself We wanted an API that is closer to html markup and javascripts event model. I believe that this would help web developers easily visualize the rendering when reading source code. 3. Write a full application with only java 4. No need for compiler to convert to javascript like gwt.Javascript is rendered at runtime. 5. The same API can be used to make an software that is server centric and or client centric. Meaning that the user can make part of his application server centric and part of his application client centric. He can of course choose to make the whole application client centric or server centric depending on the requirement. All of this using the same API. 6. Low memory footprint 7. Easy packaging of application. Everything can be packaged in a single jar. This includes images, css or javascript as well 8. Same API used to create custom components. No need to external set of API or specific programming technique to create custom components. Creating a custom components should be done only the same way as writing an application. 9. No need for javascript to create custom components. 10. Although there is no need for javascript to create an application, it should be easy to integrate external javascript libraries and use them in java codes itself. This should be done is a natural way just like we would do in an HTML page. This should be like this so that javascript library authors with some java skills find it natural and easy to provide a castafiore component together with the library. e.g. The author of flexgrid should should find it easy to create a castafiore component thus making his library usable directly in java. *Actually, I wanted to create a java web framework for javascript programmers. They should find it easy and fun to integrate and distribute their js libraries as a castafiore component. They will be able to distribute their libraries as a single jar. This is very convenient for java developers to just download the jar, include in classpath, and using the library, components and feature right away in their web application in pure java. Furthermore the castafiore framework itself is very lightweight with just 2 libraries and 1 web.xml entry. Even if the java developer is not using castafiore in his project, he should find it easy to just drop the 2 libraries + web.xml entry in classpath and start using it right away. Very practical.* 1. Load external resources like css and javascript lazily and efficiently only when needed. 2. Loading of external resources can be done eagerly if the API user wish so. 3. The framework does not own the whole page. Meaning that an application created with the framework can be used in an already created page. This allows API developer to use the framework only for very specific purposes like for example a dynamic table, while at the same time using other web framework like struts for the other sections of the application. 4. Although a whole application can be created using pure java, the framework should be able to integrate templates. 5. By default, there should be 100% separation of logic and presentation. Meaning that the API user should be able to take an html template, and dynamise it without needing to add any modification in the template. 6. On the other hand, if an API user is more script centric, he is able to write groovy template, jstl templates or any other template engine. 7. The API user should be able to easily use any template engine he wishes easily and
[PROPOSAL] Storm for Apache Incubator
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 these organizations have built critical business applications upon Storm, and have devoted significant internal infrastructure investment in Storm. === Inexperience with Open Source === Storm has existed as a healthy
Re: [PROPOSAL] Castafiore framework proposal to incubator
H, On Wed, Sep 4, 2013 at 10:01 AM, Kureem Rossaye kur...@gmail.com wrote: ...I should have prefixed the subject of the mail with [PROPOSAL]... That's correct but looking at your proposal IMO the main problem is that it's a one-man show so far. As you already indicated, to start incubation you'll need a champion and mentors - posting your proposal here might help finding those, let's wait a bit to see if it's the case. Projects that come here with no community are usually told to first start building at least a small community elsewhere and come back here once they have demonstrated interest from more than just one author. Just posting your proposal here might prompt others to sign up as initial committers, in which case your proposal might be accepted. If too few people show interest, you'll need to try and build a community elsewhere first. For now, let's wait to see if there's interest. -Bertrand - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Storm for Apache Incubator
+1 This would be great. On 9/4/13 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 these organizations have built critical business applications upon Storm, and have devoted significant internal infrastructure
Re: [PROPOSAL] Castafiore framework proposal to incubator
Hi, Thank you, I have taken note Kureem On 4 September 2013 12:11, Bertrand Delacretaz bdelacre...@apache.orgwrote: [image: Boxbe] https://www.boxbe.com/overview This message is eligible for Automatic Cleanup! (bdelacre...@apache.org) Add cleanup rulehttps://www.boxbe.com/popup?url=https%3A%2F%2Fwww.boxbe.com%2Fcleanup%3Ftoken%3DjmwLu1YDfWxQ5axCPJYvUjyVMKJ%252FYpF5Pujp9L31edu6wlw6aB4jCm9rhPDVNzF%252B0WGrm4f0%252B8JXf3Ug%252BdRmfKUJm9ux340UDXbzJc%252B8kPCX9ANRIHNg3gvX6d80ZbeWcosvN0hAbCK3a7lO2JHM4A%253D%253D%26key%3DWDFmfps0DxXEQMh4RSkCetxIqRREWm9DCOg0BZ0ObNs%253Dtc_serial=15046274608tc_rand=77968867utm_source=stfutm_medium=emailutm_campaign=ANNO_CLEANUP_ADDutm_content=001| More infohttp://blog.boxbe.com/general/boxbe-automatic-cleanup?tc_serial=15046274608tc_rand=77968867utm_source=stfutm_medium=emailutm_campaign=ANNO_CLEANUP_ADDutm_content=001 H, On Wed, Sep 4, 2013 at 10:01 AM, Kureem Rossaye kur...@gmail.com wrote: ...I should have prefixed the subject of the mail with [PROPOSAL]... That's correct but looking at your proposal IMO the main problem is that it's a one-man show so far. As you already indicated, to start incubation you'll need a champion and mentors - posting your proposal here might help finding those, let's wait a bit to see if it's the case. Projects that come here with no community are usually told to first start building at least a small community elsewhere and come back here once they have demonstrated interest from more than just one author. Just posting your proposal here might prompt others to sign up as initial committers, in which case your proposal might be accepted. If too few people show interest, you'll need to try and build a community elsewhere first. For now, let's wait to see if there's interest. -Bertrand - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Kureem Rossaye Managing Director ArchNet ltd R. Tagore Avenue, Mesnil Mauritius Mobile :+230 7159028 / Tel :+230 6867326 Skype : arkureem http://www.archnetltd.com
Re: [PROPOSAL] Storm for Apache Incubator
Agreed. I think Storm would be a great addition to ASF. On Wed, Sep 4, 2013 at 10:12 AM, Debo Dutta (dedutta) dedu...@cisco.comwrote: +1 This would be great. On 9/4/13 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!,
Re: [PROPOSAL] Storm for Apache Incubator
+1 Great proposal and it would be a nice addition to the big data projects in the ASF. On Sep 4, 2013, at 11:19 AM, Tomaz Muraus to...@apache.org wrote: Agreed. I think Storm would be a great addition to ASF. On Wed, Sep 4, 2013 at 10:12 AM, Debo Dutta (dedutta) dedu...@cisco.comwrote: +1 This would be great. On 9/4/13 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
Re: [PROPOSAL] Storm for Apache Incubator
+1, look good. --Srinath On Wed, Sep 4, 2013 at 1:37 PM, 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 these organizations have built
Re: [PROPOSAL] Castafiore framework proposal to incubator
Hi, By the way, when you I should build a small community somewhere else before coming here, the small community can be of around how many contributors? On 4 September 2013 12:26, Kureem Rossaye kur...@gmail.com wrote: Hi, Thank you, I have taken note Kureem On 4 September 2013 12:11, Bertrand Delacretaz bdelacre...@apache.orgwrote: [image: Boxbe] https://www.boxbe.com/overview This message is eligible for Automatic Cleanup! (bdelacre...@apache.org) Add cleanup rulehttps://www.boxbe.com/popup?url=https%3A%2F%2Fwww.boxbe.com%2Fcleanup%3Ftoken%3DjmwLu1YDfWxQ5axCPJYvUjyVMKJ%252FYpF5Pujp9L31edu6wlw6aB4jCm9rhPDVNzF%252B0WGrm4f0%252B8JXf3Ug%252BdRmfKUJm9ux340UDXbzJc%252B8kPCX9ANRIHNg3gvX6d80ZbeWcosvN0hAbCK3a7lO2JHM4A%253D%253D%26key%3DWDFmfps0DxXEQMh4RSkCetxIqRREWm9DCOg0BZ0ObNs%253Dtc_serial=15046274608tc_rand=77968867utm_source=stfutm_medium=emailutm_campaign=ANNO_CLEANUP_ADDutm_content=001| More infohttp://blog.boxbe.com/general/boxbe-automatic-cleanup?tc_serial=15046274608tc_rand=77968867utm_source=stfutm_medium=emailutm_campaign=ANNO_CLEANUP_ADDutm_content=001 H, On Wed, Sep 4, 2013 at 10:01 AM, Kureem Rossaye kur...@gmail.com wrote: ...I should have prefixed the subject of the mail with [PROPOSAL]... That's correct but looking at your proposal IMO the main problem is that it's a one-man show so far. As you already indicated, to start incubation you'll need a champion and mentors - posting your proposal here might help finding those, let's wait a bit to see if it's the case. Projects that come here with no community are usually told to first start building at least a small community elsewhere and come back here once they have demonstrated interest from more than just one author. Just posting your proposal here might prompt others to sign up as initial committers, in which case your proposal might be accepted. If too few people show interest, you'll need to try and build a community elsewhere first. For now, let's wait to see if there's interest. -Bertrand - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Kureem Rossaye Managing Director ArchNet ltd R. Tagore Avenue, Mesnil Mauritius Mobile :+230 7159028 / Tel :+230 6867326 Skype : arkureem http://www.archnetltd.com -- Kureem Rossaye Managing Director ArchNet ltd R. Tagore Avenue, Mesnil Mauritius Mobile :+230 7159028 / Tel :+230 6867326 Skype : arkureem http://www.archnetltd.com
Re: [PROPOSAL] Castafiore framework proposal to incubator
Kureem, this sounds nice. As far as I understood it, once could use Castafiore in conjunction with Struts. In other terms, Castafiore could be used as a Struts plugin which then calls Struts Actions and replaces Tiles, JSP whatever. Is that correct? Cheers Am 04.09.13 10:01, schrieb Kureem Rossaye: Hi, Indeed, I have read the incubation proposal guide. The only thing I could not figure out is how to recruit a champion. However, after re-reading the guide, I missed something. I should have prefixed the subject of the mail with [PROPOSAL]. So I am resending the proposal with the proper subject. ** PROPOSAL Abstract Castafiore framework is a web frameworks, fully component oriented, ajax based, one page appplication. Although the framework can be viewed as a classical component oriented web framework like GWT, it has been designed and implemented with a particular goal in mind. It is to be able to make existing javascript libraries java-able. Meaning that the framework allows to easily take a javascript library like e.g jquery ui and use the components and features via java. The integration of the javascript libraries need to be easy and natural. Actually companies like ext js and smartgwt have made their components java-able using GWT. I wish to provide an alternative to gwt that is much easier, fast, lightweight, and much more productive. Proposal Castafiore framework has been designed and implemented with the following goals in mind 1. Fully object oriented 2. Simple API that is very close to html itself We wanted an API that is closer to html markup and javascripts event model. I believe that this would help web developers easily visualize the rendering when reading source code. 3. Write a full application with only java 4. No need for compiler to convert to javascript like gwt.Javascript is rendered at runtime. 5. The same API can be used to make an software that is server centric and or client centric. Meaning that the user can make part of his application server centric and part of his application client centric. He can of course choose to make the whole application client centric or server centric depending on the requirement. All of this using the same API. 6. Low memory footprint 7. Easy packaging of application. Everything can be packaged in a single jar. This includes images, css or javascript as well 8. Same API used to create custom components. No need to external set of API or specific programming technique to create custom components. Creating a custom components should be done only the same way as writing an application. 9. No need for javascript to create custom components. 10. Although there is no need for javascript to create an application, it should be easy to integrate external javascript libraries and use them in java codes itself. This should be done is a natural way just like we would do in an HTML page. This should be like this so that javascript library authors with some java skills find it natural and easy to provide a castafiore component together with the library. e.g. The author of flexgrid should should find it easy to create a castafiore component thus making his library usable directly in java. *Actually, I wanted to create a java web framework for javascript programmers. They should find it easy and fun to integrate and distribute their js libraries as a castafiore component. They will be able to distribute their libraries as a single jar. This is very convenient for java developers to just download the jar, include in classpath, and using the library, components and feature right away in their web application in pure java. Furthermore the castafiore framework itself is very lightweight with just 2 libraries and 1 web.xml entry. Even if the java developer is not using castafiore in his project, he should find it easy to just drop the 2 libraries + web.xml entry in classpath and start using it right away. Very practical.* 1. Load external resources like css and javascript lazily and efficiently only when needed. 2. Loading of external resources can be done eagerly if the API user wish so. 3. The framework does not own the whole page. Meaning that an application created with the framework can be used in an already created page. This allows API developer to use the framework only for very specific purposes like for example a dynamic table, while at the same time using other web framework like struts for the other sections of the application. 4. Although a whole application can be created using pure java, the framework should be able to integrate templates. 5. By default, there should be 100% separation of logic and presentation.
Re: [PROPOSAL] Castafiore framework proposal to incubator
On Wed, Sep 4, 2013 at 1:23 PM, Kureem Rossaye kur...@gmail.com wrote: ...when you I should build a small community somewhere else before coming here, the small community can be of around how many contributors?... There's no set size. For me, three contributors, along with other items that demonstrate the existence of at least an embryo of a community (blog posts, conference talks etc.) are a good starting point, but the collective appreciation of the Incubator PMC is subjective. We're basically trying to accept projects that show potential, and there are many ways to show that. -Bertrand - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Storm for Apache Incubator
+1 Jordan Zimmerman 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.
Re: [PROPOSAL] Storm for Apache Incubator
+1 (non-binding)
Re: [PROPOSAL] Storm for Apache Incubator
+1 (unbinding) Looking very good. Just wondering why there are only 7 initial committers when you say that the storm developer community has 46 members. Cheers. Reto On Wed, Sep 4, 2013 at 11:44 AM, Srinath Perera srin...@wso2.com wrote: +1, look good. --Srinath On Wed, Sep 4, 2013 at 1:37 PM, 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,
Re: [PROPOSAL] Storm for Apache Incubator
+1 Supun.. On Wed, Sep 4, 2013 at 6:28 AM, Reto Bachmann-Gmür r...@wymiwyg.com wrote: +1 (unbinding) Looking very good. Just wondering why there are only 7 initial committers when you say that the storm developer community has 46 members. Cheers. Reto On Wed, Sep 4, 2013 at 11:44 AM, Srinath Perera srin...@wso2.com wrote: +1, look good. --Srinath On Wed, Sep 4, 2013 at 1:37 PM, 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
Re: [VOTE] Release of Apache Allura (incubating) v1.0.0
Ping - just a friendly reminder that we're seeking votes on our first release here. Anything else we need to provide? On 8/28/13 6:04 PM, Cory Johns wrote: Hello, This is a call for a vote on Apache Allura 1.0.0 incubating. This is our first release. A vote was held on developer mailing list and it passed with 9 +1's, and 0 -1's or +0's (vote thread [1], discussion thread [2] which some of the votes were cast on, due to some confusion, and result thread [3]), and now requires a vote on general@incubator.apache.org. Source tar ball and signature are available at: https://dist.apache.org/repos/dist/dev/incubator/allura/ Checksums: MD5: 31b9ed4af10b28f4219c00af8592d61c allura-incubating-1.0.0.tar.gz SHA1: 0ca70edeaa497261d7f6cfbedde6cab7a20ec072 allura-incubating-1.0.0.tar.gz SHA512: 38a921da57c3e53085869aa4ea9690e11247161d6351e8235907d28f1497a597f8df7fb41326cfa1c96700a8ed7cf8b79d60520784ee465358d3047680e5 allura-incubating-1.0.0.tar.gz The release has been signed with keys (9BB3CE70 and 449C78B1): http://pgp.mit.edu:11371/pks/lookup?op=vindexsearch=0x56F0526F9BB3CE70 http://pgp.mit.edu:11371/pks/lookup?op=vindexsearch=0xDB6E071B449C78B1 Source corresponding to this release can be found at https://git-wip-us.apache.org/repos/asf?p=incubator-allura.git;a=shortlog;h=refs/tags/asf_release_1.0.0 Vote will be open for at least 1 week (4/Sep/2013 12PM IST) to allow for it being our first release. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Thanks Regards Cory Johns -- Dave Brondsema : d...@brondsema.net http://www.brondsema.net : personal http://www.splike.com : programming - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
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: [PROPOSAL] Storm for Apache Incubator
+1 binding On Wed, Sep 4, 2013 at 7:52 AM, Suresh Srinivas sur...@hortonworks.comwrote: +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
Re: [PROPOSAL] Storm for Apache Incubator
Are we voting? Regards, Alan On Sep 4, 2013, at 8:33 AM, Ted Dunning ted.dunn...@gmail.com wrote: +1 binding On Wed, Sep 4, 2013 at 7:52 AM, Suresh Srinivas sur...@hortonworks.comwrote: +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
Re: [PROPOSAL] Storm for Apache Incubator
+1 (binding) Note that I fixed a minor typo in my name on the Wiki. Regards, Arvind Prabhakar On Wed, 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
Re: [PROPOSAL] Storm for Apache Incubator
+1 (binding) -- leif - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Storm for Apache Incubator
I think that having a focused set of strong committers to start is a far better policy than including a bunch of Barneyhttp://www.barney.com/usa/index.aspcommitters. On Wed, Sep 4, 2013 at 9:39 AM, Nathan Marz nathan.m...@gmail.com wrote: That's how many people have contributed code (even just one small patch). The people on the committer list have all made significant and high quality contributions. On Sep 4, 2013, at 3:28 AM, Reto Bachmann-Gmür r...@wymiwyg.com wrote: +1 (unbinding) Looking very good. Just wondering why there are only 7 initial committers when you say that the storm developer community has 46 members. Cheers. Reto On Wed, Sep 4, 2013 at 11:44 AM, Srinath Perera srin...@wso2.com wrote: +1, look good. --Srinath On Wed, Sep 4, 2013 at 1:37 PM, 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
Re: [PROPOSAL] Storm for Apache Incubator
+1 --tim On Wed, Sep 4, 2013 at 4: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 these organizations have built critical business
Re: [PROPOSAL] Storm for Apache Incubator
That's how many people have contributed code (even just one small patch). The people on the committer list have all made significant and high quality contributions. On Sep 4, 2013, at 3:28 AM, Reto Bachmann-Gmür r...@wymiwyg.com wrote: +1 (unbinding) Looking very good. Just wondering why there are only 7 initial committers when you say that the storm developer community has 46 members. Cheers. Reto On Wed, Sep 4, 2013 at 11:44 AM, Srinath Perera srin...@wso2.com wrote: +1, look good. --Srinath On Wed, Sep 4, 2013 at 1:37 PM, 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
[VOTE] Apache Ambari 1.2.5-incubating RC1
Hi all, ambari-1.2.5-incubating-rc0 release candidate is now available. Here's a summary of what's new in Ambari 1.2.5: * Added support to setup Ganglia and Nagios HTTPS * Added support to run Ambari Server as non-root account. * Added ability to manage Kerberos Secure Cluster. * Added support to setup Ambari Server HTTPS. * Enabled Ambari Server configuration property encryption. * Added support to configure Ambari Server-Agent Two-Way SSL Communication. * Added ability to customize Dashboard Widgets. * Improved Host Checks during Install Wizard I have successfully deployed a 3-node cluster on RHEL 6.3 using the instructions available at: http://incubator.apache.org/ambari/1.2.5/installing-hadoop-using-ambari/cont ent/index.html Git source tag: https://git-wip-us.apache.org/repos/asf/incubator-ambari/repo?p=incubator-am bari.git;a=log;h=refs/tags/release-1.2.5-rc0 Staging site: http://people.apache.org/~smohanty/ambari-release-1.2.5-rc0/ PGP release keys (signed using 791FDAB0) http://pgp.mit.edu:11371/pks/lookup?op=vindexsearch=0xECFC8276791FDAB0 One can look into the issues fixed in this release at: https://issues.apache.org/jira/issues/?jql=project%20%3D%20AMBARI%20AND%20fi xVersion%20%3D%20%221.2.5%22%20AND%20status%20%3D%20Resolved%20ORDER%20BY%20 priority%20DESC Vote will be open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Here's my vote to start: +1 (binding) Sumit -- 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] Storm for Apache Incubator
Excited about Storm coming to Apache. Small comment about the mailing list, you may want to propose having: * storm-dev * storm-commits * storm-private (with moderated subscriptions) instead for starting into incubator. However, Storm has been a well known open source project, maybe it does valid to have storm-user from the beginning. But I think you may need storm-commits list to separate commits log from dev discussions. Mentors can chime in about this. Thanks, Henry On Wed, 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
Re: [PROPOSAL] Castafiore framework proposal to incubator
Nice! Have you included your proposal to the Incubator wiki? I would like to forward it to the Struts team, some might be interested. I have no time to actually code, but I might help with incubation (mentoring or championing). Before deciding on that, I would like to hear if there is interest of others here. Am 04.09.13 15:04, schrieb Kureem Rossaye: *once could use Castafiore in conjunction with Struts. In other terms, Castafiore could be used as a Struts plugin which then calls Struts Actions and replaces Tiles, JSP whatever. Is that correct?* Correct! Actually I myself did not get the idea that it could be used like that. Yes it can be used like that. Actually, a castafiore application (which can be a simple table) can be included on a page using a simple javascript or a jsp tag. So why not a struts plugin. Actually I have tried it as an echo2 framework component. It works just nice. Thanks for your interest Ragards, Kureem On 4 September 2013 15:32, Christian Grobmeier grobme...@gmail.com wrote: Kureem, this sounds nice. As far as I understood it, once could use Castafiore in conjunction with Struts. In other terms, Castafiore could be used as a Struts plugin which then calls Struts Actions and replaces Tiles, JSP whatever. Is that correct? Cheers Am 04.09.13 10:01, schrieb Kureem Rossaye: Hi, Indeed, I have read the incubation proposal guide. The only thing I could not figure out is how to recruit a champion. However, after re-reading the guide, I missed something. I should have prefixed the subject of the mail with [PROPOSAL]. So I am resending the proposal with the proper subject. ** PROPOSAL Abstract Castafiore framework is a web frameworks, fully component oriented, ajax based, one page appplication. Although the framework can be viewed as a classical component oriented web framework like GWT, it has been designed and implemented with a particular goal in mind. It is to be able to make existing javascript libraries java-able. Meaning that the framework allows to easily take a javascript library like e.g jquery ui and use the components and features via java. The integration of the javascript libraries need to be easy and natural. Actually companies like ext js and smartgwt have made their components java-able using GWT. I wish to provide an alternative to gwt that is much easier, fast, lightweight, and much more productive. Proposal Castafiore framework has been designed and implemented with the following goals in mind 1. Fully object oriented 2. Simple API that is very close to html itself We wanted an API that is closer to html markup and javascripts event model. I believe that this would help web developers easily visualize the rendering when reading source code. 3. Write a full application with only java 4. No need for compiler to convert to javascript like gwt.Javascript is rendered at runtime. 5. The same API can be used to make an software that is server centric and or client centric. Meaning that the user can make part of his application server centric and part of his application client centric. He can of course choose to make the whole application client centric or server centric depending on the requirement. All of this using the same API. 6. Low memory footprint 7. Easy packaging of application. Everything can be packaged in a single jar. This includes images, css or javascript as well 8. Same API used to create custom components. No need to external set of API or specific programming technique to create custom components. Creating a custom components should be done only the same way as writing an application. 9. No need for javascript to create custom components. 10. Although there is no need for javascript to create an application, it should be easy to integrate external javascript libraries and use them in java codes itself. This should be done is a natural way just like we would do in an HTML page. This should be like this so that javascript library authors with some java skills find it natural and easy to provide a castafiore component together with the library. e.g. The author of flexgrid should should find it easy to create a castafiore component thus making his library usable directly in java. *Actually, I wanted to create a java web framework for javascript programmers. They should find it easy and fun to integrate and distribute their js libraries as a castafiore component. They will be able to distribute their libraries as a single jar. This is very convenient for java developers to just download the jar, include in classpath, and using the library, components and feature right away in their web application in pure java. Furthermore the castafiore framework
Re: [PROPOSAL] Storm for Apache Incubator
We definitely need a storm-user list as the existing google groups mailing list for Storm is quite active. So we'll need to transition that over. I agree on adding a storm-commits list and added it to the proposal. On Wed, Sep 4, 2013 at 11:50 AM, Henry Saputra henry.sapu...@gmail.comwrote: Excited about Storm coming to Apache. Small comment about the mailing list, you may want to propose having: * storm-dev * storm-commits * storm-private (with moderated subscriptions) instead for starting into incubator. However, Storm has been a well known open source project, maybe it does valid to have storm-user from the beginning. But I think you may need storm-commits list to separate commits log from dev discussions. Mentors can chime in about this. Thanks, Henry On Wed, 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!,
Re: KEYS and keys
On 4 September 2013 02:31, Tim Williams william...@gmail.com wrote:
I notice that Chris just pointed[1] spark to the nifty keys
listing[1]. Our docs still imply manual maintenance of the typical
KEYS file[2]. Honestly, I didn't even know the ldap-driven one was
around. I assume its fair for projects to just point to the
p.a.o/keys/groups/${project}.asc file nowadays vs. copying that over
periodically to KEYS?
The KEYS file has historically been manually maintained.
As new keys are used for signing releases, they are added to the file.
However entries should not be deleted if they have ever been used to
sign a release, otherwise it may not be possible to check the sigs of
archived artifacts.
LDAP does not have all historic keys, or even all historic RMs.
So replacing the KEYS file with a copy from LDAP may lose keys needed
for validating archived files.
Directing users to the p.a.o/keys/groups/${project}.asc files should
work for current releases.
But even that has an problem - if the RM leaves a project whilst the
release is still current, the project.asc file will no longer contain
the RM's key
The problem is even worse for older releases.
People may create new keys and drop old ones which have been used for signing.
People leave a project or the ASF and the LDAP entry is changed.
I don't think the LDAP keys are really suitable for use as a KEYS file
at present.
Thanks,
--tim
[1] - http://people.apache.org/keys/group/spark.asc
[2] -
http://incubator.apache.org/guides/releasemanagement.html#distribution-signing
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Storm for Apache Incubator
What does this mean for storm contribs ( https://github.com/nathanmarz/storm-contrib)? (spouts bolts) e.g The Apache Kafka spout already it is hard to know which to use and which is best for 0.7.X and 0.8.X-betaX... Is the Apache Storm project going to help corral that or is it only for Storm core as the proposal implies with only the storm code base https://github.com/nathanmarz/storm being part of the project? A lot of traffic on the existing user list is about spouts (e.g. the Kafka Spout) and I was not sure if that would still be talked about or funneled somewhere else or what the thoughts/plans where for the parts built within Storm that are existing now? /*** Joe Stein Founder, Principal Consultant Big Data Open Source Security LLC http://www.stealth.ly Twitter: @allthingshadoop http://www.twitter.com/allthingshadoop / On Wed, Sep 4, 2013 at 4:34 PM, Nathan Marz nat...@nathanmarz.com wrote: We definitely need a storm-user list as the existing google groups mailing list for Storm is quite active. So we'll need to transition that over. I agree on adding a storm-commits list and added it to the proposal. On Wed, Sep 4, 2013 at 11:50 AM, Henry Saputra henry.sapu...@gmail.com wrote: Excited about Storm coming to Apache. Small comment about the mailing list, you may want to propose having: * storm-dev * storm-commits * storm-private (with moderated subscriptions) instead for starting into incubator. However, Storm has been a well known open source project, maybe it does valid to have storm-user from the beginning. But I think you may need storm-commits list to separate commits log from dev discussions. Mentors can chime in about this. Thanks, Henry On Wed, 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
Re: [PROPOSAL] Storm for Apache Incubator
I think that storm-kafka would make sense as a contrib module since it's widely used. I'm not sure what to do with the other storm-contrib modules. I figure the less code that's part of the initial repo the better, because there will be less contribution/legal issues to sort out. How about this - we plan to include storm-kafka under a contrib folder of the Apache Storm project (just because a lot of people depend on it), and we can pull other storm-contrib modules in if community members show initiative in working on and maintaining them? If that all sounds good I'll update the proposal accordingly. On Sep 4, 2013, at 6:41 PM, Joe Stein crypt...@gmail.com wrote: What does this mean for storm contribs ( https://github.com/nathanmarz/storm-contrib)? (spouts bolts) e.g The Apache Kafka spout already it is hard to know which to use and which is best for 0.7.X and 0.8.X-betaX... Is the Apache Storm project going to help corral that or is it only for Storm core as the proposal implies with only the storm code base https://github.com/nathanmarz/storm being part of the project? A lot of traffic on the existing user list is about spouts (e.g. the Kafka Spout) and I was not sure if that would still be talked about or funneled somewhere else or what the thoughts/plans where for the parts built within Storm that are existing now? /*** Joe Stein Founder, Principal Consultant Big Data Open Source Security LLC http://www.stealth.ly Twitter: @allthingshadoop http://www.twitter.com/allthingshadoop / On Wed, Sep 4, 2013 at 4:34 PM, Nathan Marz nat...@nathanmarz.com wrote: We definitely need a storm-user list as the existing google groups mailing list for Storm is quite active. So we'll need to transition that over. I agree on adding a storm-commits list and added it to the proposal. On Wed, Sep 4, 2013 at 11:50 AM, Henry Saputra henry.sapu...@gmail.com wrote: Excited about Storm coming to Apache. Small comment about the mailing list, you may want to propose having: * storm-dev * storm-commits * storm-private (with moderated subscriptions) instead for starting into incubator. However, Storm has been a well known open source project, maybe it does valid to have storm-user from the beginning. But I think you may need storm-commits list to separate commits log from dev discussions. Mentors can chime in about this. Thanks, Henry On Wed, 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
Re: [PROPOSAL] Storm for Apache Incubator
sounds great +1 to include storm-kafka under a contrib folder of the Apache Storm project for other modules (moving forward) based on community members showing initiative in working on and maintaing them On Wed, Sep 4, 2013 at 10:23 PM, Nathan Marz nathan.m...@gmail.com wrote: I think that storm-kafka would make sense as a contrib module since it's widely used. I'm not sure what to do with the other storm-contrib modules. I figure the less code that's part of the initial repo the better, because there will be less contribution/legal issues to sort out. How about this - we plan to include storm-kafka under a contrib folder of the Apache Storm project (just because a lot of people depend on it), and we can pull other storm-contrib modules in if community members show initiative in working on and maintaining them? If that all sounds good I'll update the proposal accordingly. On Sep 4, 2013, at 6:41 PM, Joe Stein crypt...@gmail.com wrote: What does this mean for storm contribs ( https://github.com/nathanmarz/storm-contrib)? (spouts bolts) e.g The Apache Kafka spout already it is hard to know which to use and which is best for 0.7.X and 0.8.X-betaX... Is the Apache Storm project going to help corral that or is it only for Storm core as the proposal implies with only the storm code base https://github.com/nathanmarz/storm being part of the project? A lot of traffic on the existing user list is about spouts (e.g. the Kafka Spout) and I was not sure if that would still be talked about or funneled somewhere else or what the thoughts/plans where for the parts built within Storm that are existing now? /*** Joe Stein Founder, Principal Consultant Big Data Open Source Security LLC http://www.stealth.ly Twitter: @allthingshadoop http://www.twitter.com/allthingshadoop / On Wed, Sep 4, 2013 at 4:34 PM, Nathan Marz nat...@nathanmarz.com wrote: We definitely need a storm-user list as the existing google groups mailing list for Storm is quite active. So we'll need to transition that over. I agree on adding a storm-commits list and added it to the proposal. On Wed, Sep 4, 2013 at 11:50 AM, Henry Saputra henry.sapu...@gmail.com wrote: Excited about Storm coming to Apache. Small comment about the mailing list, you may want to propose having: * storm-dev * storm-commits * storm-private (with moderated subscriptions) instead for starting into incubator. However, Storm has been a well known open source project, maybe it does valid to have storm-user from the beginning. But I think you may need storm-commits list to separate commits log from dev discussions. Mentors can chime in about this. Thanks, Henry On Wed, 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
Re: Followup to VXQuery July 2013 report
Just for the record: The website is updated (from the branch that will hopefully be released soon). Till On Sep 4, 2013, at 12:11 AM, Marvin Humphrey mar...@rectangular.com wrote: On Tue, Sep 3, 2013 at 11:42 PM, David Crossley cross...@apache.org wrote: ant elder wrote: Hi Marvin, I had a look, that README being pointed to is just build instructions on how to build the svn trunk isn't it, so not to some released artifacts. Thats allowed isn't it, i'm pretty sure other projects and podlings have done something similar anyway. Is it that the website describes it as user installation instructions rather than developer build instructions thats the issue? ...ant I reckon so. To clearly refer developers to developer resources is fine, but users no. They need to be referred to user instructions. In VXQuery's case, there's nothing to refer users to because in four years, VXQuery has never made an incubating release. If developer instructions for accessing version control are added to the website in accordance with ASF guidelines, of course that's fine -- so long as all user installation instructions are removed. Here's more background from the legal-discuss list regarding the current policy, this time from a different Board member, Doug Cutting: http://markmail.org/message/pelvob23vrzuzws5 Each PMC should attempt to ensure that every commit is in accord with Apache's intellectual property policies. Releases are a double-check of this. We hope that source code repositories are not legally considered publications, but we don't know that courts will in fact always treat them that way, so it's best to guard against that too. Note that the extra scrutiny around releases both serves to double-check (belt and suspenders) as well as to provide evidence that we do not consider the source code repository as a publication. But again, we cannot depend on others to agree with that, and must guard against other interpretations as best we can. If VXQuery finds it uncomfortable not to have anything they can show users, they can solve that by making a release. Marvin Humphrey - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Storm for Apache Incubator
+1. If you need another mentor, sign me up. On Wed, 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 these
Shepherd assignments, September 2013
Greets, Here are shepherd assignments for our September 2013 report: SHEPHERD PODLING -- Alan Cabrera Falcon Alan Cabrera MetaModel Alan Cabrera Tajo Dave FisherDrill Dave FisherS4 Matt Franklin Olingo Matt Franklin Provisionr Ross Gardler Wave Matt Hogstrom Sentry Benson Marguilies Spark Suresh Marru Allura Suresh Marru Samza Roman Shaposhnik Kalumet Roman Shaposhnik MRQL Roman Shaposhnik Streams Please add your reports to the wiki by the end of next Tuesday, September 10. I will collect all of them into a single email and send to general@incubator after the report is filed. Thanks! Marvin Humphrey - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
