Re: [VOTE] Release Blur version 0.2.4-incubating RC1
Justin thank you for taking the time to evaluate the release. On Fri, Jul 17, 2015 at 10:57 PM, Tim Williams william...@gmail.com wrote: Thanks for taking the time to review Justin, we appreciate it. On Fri, Jul 17, 2015 at 8:01 PM, Justin Mclean jus...@classsoftware.com wrote: Hi, Sorry but it’s -1 (binding) until the MPL issue can be resolved / explained, other issues can be fixed next release. For the MPL issue it may be that For small amounts of source that is directly consumed by the ASF product at runtime in source form” may apply. [2] I think we just missed it, based on the example, I don't think we can use that escape-clause/rationale for its inclusion. We should take it back to the dev list at this point. I agree. I will cancel the vote and we will retry soon. Aaron For the source release I checked: - filename contains incubating - signatures and hashes good - DISCLAIMER exists - LICENSE has minor issues + MPL issue [2] - NOTICE good - Some unexpected binaries in source (see below) - All source file have headers - Can compile form source? LiCENSE is missing: - MIT licensed normalize.css (see ./apache-blur-0.2.4-incubating-src/blur-console/src/main/webapp/public/css/blurconsole.css + ./apache-blur-0.2.4-incubating-src/blur-console/src/main/webapp/libs/bootstrap/less/normalize.less) - MIT/BSD licensed polyfill (see ./docs/resources/js/respond.min.js) There is an issue with ./blur-console/src/main/webapp/libs/tagmanager/tagmanager.js as this is MPL licensed [2] which is weak copy left and considered a category B license. In this case it looks like it isn’t been handled correctly as it being included in source not binary form. I’m not sure how this should be handled given there is no compiled JS form. There are a couple of test files that contain compiled code, can this be produced via the build process? ./blur-core/src/test/resources/org/apache/blur/command/test1/test1.jar ./blur-core/src/test/resources/org/apache/blur/command/test2/test2.jar Yeah, these were just to drive some tests but I reckon we should craft another way that ships in source form. Something a little odd that caught my eye is all of the ./distribution/src/main/resources-hadoop1/notices/*.jar.src files. Is there any reason for these files to be in the source release? It look that they are used to generate the binary NOTICE file? They're sources needed to produce a [valid] binary package so it seemed reasonable to me include them. For the binary release you may want to check the LICENSE as it is identical to the source release [3]. For the binary NOTICE file a minor issue in that there is no need to repeat This product includes software developed by The Apache Software Foundation “ [4]. Re compiling from source some instructions in the README would be helpful as it seems a mvn install in the top directory may not do what is expected. (As far as I can see it seems to be doing a rat check and nothing else?) Yeah, we should add something to the README that hints at the quickstart or profiles: mvn install -Dhadoop2 Thanks again for taking your time... Thanks, --tim - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[CANCELED] [VOTE] Release Blur version 0.2.4-incubating RC1
Due to various issues we are canceling the vote for release. Aaron On Sat, Jul 18, 2015 at 5:53 PM, Aaron McCurry amccu...@gmail.com wrote: Justin thank you for taking the time to evaluate the release. On Fri, Jul 17, 2015 at 10:57 PM, Tim Williams william...@gmail.com wrote: Thanks for taking the time to review Justin, we appreciate it. On Fri, Jul 17, 2015 at 8:01 PM, Justin Mclean jus...@classsoftware.com wrote: Hi, Sorry but it’s -1 (binding) until the MPL issue can be resolved / explained, other issues can be fixed next release. For the MPL issue it may be that For small amounts of source that is directly consumed by the ASF product at runtime in source form” may apply. [2] I think we just missed it, based on the example, I don't think we can use that escape-clause/rationale for its inclusion. We should take it back to the dev list at this point. I agree. I will cancel the vote and we will retry soon. Aaron For the source release I checked: - filename contains incubating - signatures and hashes good - DISCLAIMER exists - LICENSE has minor issues + MPL issue [2] - NOTICE good - Some unexpected binaries in source (see below) - All source file have headers - Can compile form source? LiCENSE is missing: - MIT licensed normalize.css (see ./apache-blur-0.2.4-incubating-src/blur-console/src/main/webapp/public/css/blurconsole.css + ./apache-blur-0.2.4-incubating-src/blur-console/src/main/webapp/libs/bootstrap/less/normalize.less) - MIT/BSD licensed polyfill (see ./docs/resources/js/respond.min.js) There is an issue with ./blur-console/src/main/webapp/libs/tagmanager/tagmanager.js as this is MPL licensed [2] which is weak copy left and considered a category B license. In this case it looks like it isn’t been handled correctly as it being included in source not binary form. I’m not sure how this should be handled given there is no compiled JS form. There are a couple of test files that contain compiled code, can this be produced via the build process? ./blur-core/src/test/resources/org/apache/blur/command/test1/test1.jar ./blur-core/src/test/resources/org/apache/blur/command/test2/test2.jar Yeah, these were just to drive some tests but I reckon we should craft another way that ships in source form. Something a little odd that caught my eye is all of the ./distribution/src/main/resources-hadoop1/notices/*.jar.src files. Is there any reason for these files to be in the source release? It look that they are used to generate the binary NOTICE file? They're sources needed to produce a [valid] binary package so it seemed reasonable to me include them. For the binary release you may want to check the LICENSE as it is identical to the source release [3]. For the binary NOTICE file a minor issue in that there is no need to repeat This product includes software developed by The Apache Software Foundation “ [4]. Re compiling from source some instructions in the README would be helpful as it seems a mvn install in the top directory may not do what is expected. (As far as I can see it seems to be doing a rat check and nothing else?) Yeah, we should add something to the README that hints at the quickstart or profiles: mvn install -Dhadoop2 Thanks again for taking your time... Thanks, --tim - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[VOTE] Release Blur version 0.2.4-incubating RC1
Hello Incubators, We are happy to announce Blur 0.2.4-incubating is ready for release. The release artifacts can be found at this location: https://dist.apache.org/repos/dist/dev/incubator/blur/0.2.4-incubating/ The source distribution is provided by: https://dist.apache.org/repos/dist/dev/incubator/blur/0.2.4-incubating/apache-blur-0.2.4-incubating-src.tar.gz Two binary distribution is provided for user convenience: https://dist.apache.org/repos/dist/dev/incubator/blur/0.2.4-incubating/apache-blur-hadoop2-2.6.0-0.2.4-incubating-bin.tar.gz The tag in Apache Git can be found here: https://git-wip-us.apache.org/repos/asf?p=incubator-blur.git;a=tag;h=2b2fad6f4caf14c4019bba9eafb9dd62ed7cdcae The release notes are available here: https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12327386styleName=HtmlprojectId=12313721 Finally, the blur-dev@incubator [VOTE] thread can be found at this location: http://mail-archives.apache.org/mod_mbox/incubator-blur-dev/201507.mbox/%3CCAB6tTr2wKdTf8t585yvGTiqaebd_TcfnAnhdm0ZdM-YA9Jb%2BuA%40mail.gmail.com%3E Result summery: +1 (1 binding, 1 non-binding), 0 (0), -1 (0) The [VOTE] will be open for the next 72 hours --- closing Sunday (July 19th) at 9:30pm (EST). Thanks! Aaron
[RESULT] [VOTE] Release Blur version 0.2.3-incubating RC2
The VOTE passes with with a total of 5 +1 votes, 3 +1 from IPMC members and 2 +1 from PPMC members. This VOTE combines results from the blur-dev vote and the general vote. blur-dev@i.a.o results can be found here: http://mail-archives.apache.org/mod_mbox/incubator-blur-dev/201407.mbox/%3CCAB6tTr2PbONLYxkCHDZBCvp2gshQjT%3DwD%3D03_%3DHfjM1n4R0ktA%40mail.gmail.com%3E IPMC +1 votes: Tim Williams (IPMC) Patrick Hunt (IPMC) Justin Mclean (IPMC) PPMC +1 votes: Chris Rohr Aaron McCurry No -1 votes. Thank you to all that voted! Thanks, Aaron On Thu, Jul 24, 2014 at 1:50 AM, Justin Mclean jus...@classsoftware.com wrote: HI, +1 binding - vote correct (I assume so) - md5 and signatures correct - incubating in artefact name - DISCLAIMER exists - LICENSE and NOTICE correct (but a couple of minor things see below) - no binary files in source release - all source files have correct headers - can compile from source Minor things I noticed, you might (or might not) want to change these in a future release. - Apache v2 software listed in LICENSE but not required as per [1]. But having them listed does make reviewing easier, especially as you have both the MIT and Apache licensed versions of bootcamp in your source distribution. Also means you can check if Apache Thrift NOTICE has been taken into account (it has/nothing required). - bootstrap is MIT license is since 3.2.0 (I think), not 3 as mentioned in LICENSE [2], 3.x has been both Apache and MIT licensed - There's some empty files in distribution/src/main/resources-hadoop1/notices/ I assume that because the bundled software in question doesn't have a NOTICE file? - year in NOTICE is incorrect (2013 not 2014) - one or two text files don't have Apache headers (eg distribution/src/main/scripts/conf/default_zoo.cfg) Thanks, Justin 1. http://www.apache.org/dev/licensing-howto.html#alv2-dep 2. https://github.com/twbs/bootstrap/commit/cb40a2ee8c88efdec0c35adf173cc96ba25db21e - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[VOTE] Release Blur version 0.2.3-incubating RC2
We've held a vote on blur-dev to release the 0.2.3-incubating version of Apache Blur. The vote thread can be found here: http://mail-archives.apache.org/mod_mbox/incubator-blur-dev/201407.mbox/%3CCAB6tTr0kZyjp82m%3DWO%3Di_8-%3DLQV5Hz13AB6dQ0%3DrDc93iBCjeg%40mail.gmail.com%3E The vote passed with: 2 x +1 binding votes 2 x +1 non-binding votes A summary email can be found here: http://mail-archives.apache.org/mod_mbox/incubator-blur-dev/201407.mbox/%3CCAB6tTr2PbONLYxkCHDZBCvp2gshQjT%3DwD%3D03_%3DHfjM1n4R0ktA%40mail.gmail.com%3E The source and binary release artifacts can be found together with signatures here: https://dist.apache.org/repos/dist/dev/incubator/blur/0.2.3-incubating/ Please vote on this release. Thanks! Aaron
[ANNOUNCE] Apache Blur 0.2.0-incubating released
The Apache Blur team is pleased to announce the release of Blur 0.2.0-incubating. This is the first release of Apache Blur, an open source search platform capable of querying massive amounts of data at incredible speeds. Apache Blur is built on top of Apache Lucene, Apache Hadoop, Apache Thrift, and Apache ZooKeeper. The release is available here: http://www.apache.org/dyn/closer.cgi/incubator/blur/0.2.0-incubating The full change log is available here: http://incubator.apache.org/blur/docs/0.2.0/release-notes.html We welcome your help and feedback. For more information on how to report problems, and to get involved, visit the project website at http://incubator.apache.org/blur/ The Apache Blur Team Disclaimer: Apache Blur is an effort undergoing incubation at the Apache Software Foundation (ASF), sponsored by the Incubator PMC. Incubation is required of all newly accepted projects until a further review indicates that the infrastructure, communications, and decision making process have stabilized in a manner consistent with other successful ASF projects. While incubation status is not necessarily a reflection of the completeness or stability of the code, it does indicate that the project has yet to be fully endorsed by the ASF.
[RESULT] [VOTE] first release of Apache Blur (incubating)
The vote passes with 8 +1's and 0 -1's from: Binding Votes: Patrick Hunt (IPMC) Tim Williams (IPMC) Doug Cutting (IPMC) Andrei Savu (IPMC) Henry Saputra (IPMC) Non-Binding Votes: Aaron McCurry Rahul Challapalli Gagan Juneja Thanks On Tue, Sep 24, 2013 at 3:30 PM, Henry Saputra henry.sapu...@gmail.comwrote: +1 (binding) congrats! On Mon, Sep 23, 2013 at 5:50 PM, Aaron McCurry amccu...@gmail.com wrote: We've held a vote on blur-dev to release the first incubating release. The vote thread can be found here: http://mail-archives.apache.org/mod_mbox/incubator-blur-dev/201309.mbox/%3CCAB6tTr0cG%3D78nBuQHBqzKLyn4T8-4gHnmD8%2Bo8voP79qmVz2fw%40mail.gmail.com%3E The vote passed with 3 x +1 binding votes 3 x +1 non-binding votes A summary email can be found here: http://mail-archives.apache.org/mod_mbox/incubator-blur-dev/201309.mbox/%3CCAB6tTr39cN8nMQ7zmX6s9yjqk5iLS6NO4g_1_G6aiOMQu%2Bv_Hw%40mail.gmail.com%3E The source and binary release artifacts can be found together with signatures here: https://dist.apache.org/repos/dist/dev/incubator/blur/0.2.0-incubating/ Please vote on this release - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[VOTE] first release of Apache Blur (incubating)
We've held a vote on blur-dev to release the first incubating release. The vote thread can be found here: http://mail-archives.apache.org/mod_mbox/incubator-blur-dev/201309.mbox/%3CCAB6tTr0cG%3D78nBuQHBqzKLyn4T8-4gHnmD8%2Bo8voP79qmVz2fw%40mail.gmail.com%3E The vote passed with 3 x +1 binding votes 3 x +1 non-binding votes A summary email can be found here: http://mail-archives.apache.org/mod_mbox/incubator-blur-dev/201309.mbox/%3CCAB6tTr39cN8nMQ7zmX6s9yjqk5iLS6NO4g_1_G6aiOMQu%2Bv_Hw%40mail.gmail.com%3E The source and binary release artifacts can be found together with signatures here: https://dist.apache.org/repos/dist/dev/incubator/blur/0.2.0-incubating/ Please vote on this release
[VOTE] Accept Blur into the Apache Incubator
I would like to call a vote for accepting Blur for incubation in the Apache Incubator. The full proposal is available below. Please cast your vote: [ ] +1, bring Blur into Incubator [ ] +0, I don't care either way, [ ] -1, do not bring Blur into Incubator, because... This vote will be open for 72 hours and only votes from the Incubator PMC are binding. Thank you for your consideration! Aaron http://wiki.apache.org/incubator/BlurProposal = Blur Proposal = == Abstract == Blur is a search platform capable of searching massive amounts of data in a cloud computing environment. Blur leverages several existing Apache projects, including Apache Lucene, Apache Hadoop, Apache !ZooKeeper and Apache Thrift. Both bulk and near real time (NRT) updates are possible with Blur. Bulk updates are accomplished using Hadoop Map/Reduce and NRT are performed through direct Thrift calls. == Proposal == Blur is an open source search platform capable of querying massive amounts of data at incredible speeds. Rather than using the flat, document-like data model used by most search solutions, Blur allows you to build rich data models and search them in a semi-relational manner similar to joins while querying a relational database. Using Blur, you can get precise search results against terabytes of data at Google-like speeds. Blur leverages multiple open source projects including Hadoop, Lucene, Thrift and !ZooKeeper to create an environment where structured data can be transformed into an index that runs on a Hadoop cluster. Blur uses the power of Map/Reduce for bulk indexing into Blur. Server failures are handled automatically by using !ZooKeeper for cluster state and HDFS for index storage. == Background == Blur was created by Aaron !McCurry in 2010. Blur was developed to solve the challenges in dealing with searching huge quantities of data that the traditional RDBMS solutions could not cope with while still providing JOIN-like capabilities to query the data. Several other open source projects have implemented aspects of this design including elasticsearch, Katta and Apache Solr. == Rationale == There is a need for a distributed search capability within the Hadoop ecosystem. Currently, there are no other search solutions that natively leverage HDFS and the failover features of Hadoop in the same manner as the Blur project. The communities we expect to be most interested in such a project are government, health care, and other industries where scalability is a concern. We have made much progress in developing this project over the past 2 years and believe both the project and the interested communities would benefit from this work being openly available and having open development. In future versions of Blur the API will more closely follow the API’s provided in Lucene so that systems that already use Lucene can more easily scale with Blur. Blur can be viewed as a query execution engine that Lucene based solutions can utilize when scale becomes an issue. == Initial Goals == The initial goals of the project are: * To migrate the Blur codebase, issue tracking and wiki from github.com and integrate the project with the ASF infrastructure. * Add new committers to the project and grow the community in The Apache Way. == Current Status == === Meritocracy === Blur was initially developed by Aaron !McCurry in June 2010. Since then Blur has continued to evolve with the support of a small development team at Near Infinity. As a part of the Apache Software Foundation, the Apache Blur team intends to strongly encourage the community to help with and contribute to the project. Apache Blur will actively seek potential committers and help them become familiar with the codebase. === Community === A small community has developed around Blur and several project teams are currently using Blur for their big data search capability. The source code is currently available on GitHub and there is a dedicated website (blur.io) that provides an overview of the project. Blur has been shared with several members of the Apache community and has been presented at the Bay Area HUG (see http://www.meetup.com/hadoop/events/20109471/). === Core Developers === The current developers are employed by Near Infinity Corporation, but we anticipate interest developing among other companies. === Alignment === Blur is built on top of a number of Apache projects; Hadoop, Lucene, !ZooKeeper, and Thrift. It builds with Maven. During the course of Blur development, a couple of patches have been committed back to the Lucene project, including LUCENE-2205 and LUCENE-2215. Due to the strong relationship with the before mentioned Apache projects, the incubator is a good match for Blur. == Known Risks == === Orphaned Products === There is only a small risk of being orphaned. The customers that currently use Blur are committed to improving the codebase of the project due to its fulfilling needs not addressed by any other software. In addition, one
Re: [PROPOSAL] Blur for the Apache Incubator
Is there anymore feedback before I call the vote? Thanks! Aaron On Sat, Jul 14, 2012 at 11:48 AM, Dave Fisher dave2w...@comcast.net wrote: On Jul 13, 2012, at 2:23 PM, Aaron McCurry wrote: Hello! I would like to propose Blur to be an Apache Incubator project. Blur is a distributed search platform built for low latency searches over large amounts of data. Blur is scalable and fault tolerant through the use of Hadoop and ZooKeeper. Thrift is used as the RPC library and the underlying search implementation uses Lucene and the Lucene query syntax. The proposal can be found here: http://wiki.apache.org/incubator/BlurProposal I have included the contexts of the proposal below. Very cool! Regards, Dave Thanks! Aaron = Blur Proposal = == Abstract == Blur is a search platform capable of searching massive amounts of data in a cloud computing environment. Blur leverages several existing Apache projects, including Apache Lucene, Apache Hadoop, Apache !ZooKeeper and Apache Thrift. Both bulk and near real time (NRT) updates are possible with Blur. Bulk updates are accomplished using Hadoop Map/Reduce and NRT are performed through direct Thrift calls. == Proposal == Blur is an open source search platform capable of querying massive amounts of data at incredible speeds. Rather than using the flat, document-like data model used by most search solutions, Blur allows you to build rich data models and search them in a semi-relational manner similar to joins while querying a relational database. Using Blur, you can get precise search results against terabytes of data at Google-like speeds. Blur leverages multiple open source projects including Hadoop, Lucene, Thrift and !ZooKeeper to create an environment where structured data can be transformed into an index that runs on a Hadoop cluster. Blur uses the power of Map/Reduce for bulk indexing into Blur. Server failures are handled automatically by using !ZooKeeper for cluster state and HDFS for index storage. == Background == Blur was created by Aaron !McCurry in 2010. Blur was developed to solve the challenges in dealing with searching huge quantities of data that the traditional RDBMS solutions could not cope with while still providing JOIN-like capabilities to query the data. Several other open source projects have implemented aspects of this design including elasticsearch, Katta and Apache Solr. == Rationale == There is a need for a distributed search capability within the Hadoop ecosystem. Currently, there are no other search solutions that natively leverage HDFS and the failover features of Hadoop in the same manner as the Blur project. The communities we expect to be most interested in such a project are government, health care, and other industries where scalability is a concern. We have made much progress in developing this project over the past 2 years and believe both the project and the interested communities would benefit from this work being openly available and having open development. In future versions of Blur the API will more closely follow the API’s provided in Lucene so that systems that already use Lucene can more easily scale with Blur. Blur can be viewed as a query execution engine that Lucene based solutions can utilize when scale becomes an issue. == Initial Goals == The initial goals of the project are: * To migrate the Blur codebase, issue tracking and wiki from github.com and integrate the project with the ASF infrastructure. * Add new committers to the project and grow the community in The Apache Way. == Current Status == === Meritocracy === Blur was initially developed by Aaron !McCurry in June 2010. Since then Blur has continued to evolve with the support of a small development team at Near Infinity. As a part of the Apache Software Foundation, the Apache Blur team intends to strongly encourage the community to help with and contribute to the project. Apache Blur will actively seek potential committers and help them become familiar with the codebase. === Community === A small community has developed around Blur and several project teams are currently using Blur for their big data search capability. The source code is currently available on GitHub and there is a dedicated website (blur.io) that provides an overview of the project. Blur has been shared with several members of the Apache community and has been presented at the Bay Area HUG (see http://www.meetup.com/hadoop/events/20109471/). === Core Developers === The current developers are employed by Near Infinity Corporation, but we anticipate interest developing among other companies. === Alignment === Blur is built on top of a number of Apache projects; Hadoop, Lucene, !ZooKeeper, and Thrift. It builds with Maven. During the course of Blur development, a couple of patches have been committed back to the Lucene project, including LUCENE-2205 and LUCENE-2215. Due
[PROPOSAL] Blur for the Apache Incubator
Hello! I would like to propose Blur to be an Apache Incubator project. Blur is a distributed search platform built for low latency searches over large amounts of data. Blur is scalable and fault tolerant through the use of Hadoop and ZooKeeper. Thrift is used as the RPC library and the underlying search implementation uses Lucene and the Lucene query syntax. The proposal can be found here: http://wiki.apache.org/incubator/BlurProposal I have included the contexts of the proposal below. Thanks! Aaron = Blur Proposal = == Abstract == Blur is a search platform capable of searching massive amounts of data in a cloud computing environment. Blur leverages several existing Apache projects, including Apache Lucene, Apache Hadoop, Apache !ZooKeeper and Apache Thrift. Both bulk and near real time (NRT) updates are possible with Blur. Bulk updates are accomplished using Hadoop Map/Reduce and NRT are performed through direct Thrift calls. == Proposal == Blur is an open source search platform capable of querying massive amounts of data at incredible speeds. Rather than using the flat, document-like data model used by most search solutions, Blur allows you to build rich data models and search them in a semi-relational manner similar to joins while querying a relational database. Using Blur, you can get precise search results against terabytes of data at Google-like speeds. Blur leverages multiple open source projects including Hadoop, Lucene, Thrift and !ZooKeeper to create an environment where structured data can be transformed into an index that runs on a Hadoop cluster. Blur uses the power of Map/Reduce for bulk indexing into Blur. Server failures are handled automatically by using !ZooKeeper for cluster state and HDFS for index storage. == Background == Blur was created by Aaron !McCurry in 2010. Blur was developed to solve the challenges in dealing with searching huge quantities of data that the traditional RDBMS solutions could not cope with while still providing JOIN-like capabilities to query the data. Several other open source projects have implemented aspects of this design including elasticsearch, Katta and Apache Solr. == Rationale == There is a need for a distributed search capability within the Hadoop ecosystem. Currently, there are no other search solutions that natively leverage HDFS and the failover features of Hadoop in the same manner as the Blur project. The communities we expect to be most interested in such a project are government, health care, and other industries where scalability is a concern. We have made much progress in developing this project over the past 2 years and believe both the project and the interested communities would benefit from this work being openly available and having open development. In future versions of Blur the API will more closely follow the API’s provided in Lucene so that systems that already use Lucene can more easily scale with Blur. Blur can be viewed as a query execution engine that Lucene based solutions can utilize when scale becomes an issue. == Initial Goals == The initial goals of the project are: * To migrate the Blur codebase, issue tracking and wiki from github.com and integrate the project with the ASF infrastructure. * Add new committers to the project and grow the community in The Apache Way. == Current Status == === Meritocracy === Blur was initially developed by Aaron !McCurry in June 2010. Since then Blur has continued to evolve with the support of a small development team at Near Infinity. As a part of the Apache Software Foundation, the Apache Blur team intends to strongly encourage the community to help with and contribute to the project. Apache Blur will actively seek potential committers and help them become familiar with the codebase. === Community === A small community has developed around Blur and several project teams are currently using Blur for their big data search capability. The source code is currently available on GitHub and there is a dedicated website (blur.io) that provides an overview of the project. Blur has been shared with several members of the Apache community and has been presented at the Bay Area HUG (see http://www.meetup.com/hadoop/events/20109471/). === Core Developers === The current developers are employed by Near Infinity Corporation, but we anticipate interest developing among other companies. === Alignment === Blur is built on top of a number of Apache projects; Hadoop, Lucene, !ZooKeeper, and Thrift. It builds with Maven. During the course of Blur development, a couple of patches have been committed back to the Lucene project, including LUCENE-2205 and LUCENE-2215. Due to the strong relationship with the before mentioned Apache projects, the incubator is a good match for Blur. == Known Risks == === Orphaned Products === There is only a small risk of being orphaned. The customers that currently use Blur are committed to improving the codebase of the project due to its fulfilling
Request for permissions to edit Blur Proposal
I am requesting permission to be able to edit the http://wiki.apache.org/incubator/BlurProposal wiki page, so that I may respond to comments made on the proposal. My wiki id is: AaronMccurry Thanks! Aaron - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
