Re: [DISCUSS] Trafodion Incubation Proposal
Bit belated... I'd be happy and honored to be a mentor for Trafodian. -- Lars From: Stack To: general@incubator.apache.org Sent: Friday, May 8, 2015 2:59 PM Subject: [DISCUSS] Trafodion Incubation Proposal I would like to start up a discussion on Trafodion joining the ASF as an incubating project. Trafodion is a webscale SQL-on-Hadoop solution that enables transactional or operational workloads on Hadoop, . The proposal is available on the wiki here: https://wiki.apache.org/incubator/TrafodionProposal#preview The proposal text is also attached to the end of this email. Trafodion is a rich, storied SQL engine that has recently been ported to run on HBase and Hadoop. I think it would make for a fine addition to the Apache family of projects It would be good to hear what others think. Thank you in advance for giving the proposal a read. Yours, St.Ack Trafodion Apache Incubator Proposal Abstract Trafodion is a webscale SQL-on-Hadoop solution enabling transactional or operational workloads on Hadoop. Proposal Apache Trafodion builds on the scalability, elasticity, and flexibility of Hadoop. Trafodion extends Hadoop to provide guaranteed transactional integrity, enabling new kinds of big data applications to run on Hadoop. Key features of Apache Trafodion include: * Full-functioned ANSI SQL language support * JDBC/ODBC connectivity for Linux/Windows clients * Distributed ACID transaction protection across multiple statements, tables and rows * Performance improvements for OLTP workloads with compile-time and run-time optimizations * Support for large data sets using a parallel-aware query optimizer * ANSI SQL security and data integrity constraints including referential integrity Hewlett-Packard Company submits this proposal to donate its Apache License, Version 2.0 open source project known as Trafodion, its source code, documentation, and web site content to the Apache Software Foundation in order to build an open source community Background Trafodion is an open source project sponsored by HP, incubated at HP Labs and HP-IT, to develop an enterprise-class SQL-on-Hadoop solution targeting big data transactional or operational workloads. HP publically announced the open source project and uploaded the source code to GitHub in June 2014. The SQL compiler, optimizer and executor components of Trafodion have a rich heritage. Under development since 1993, they were released as commercial closed source software in various flavors such as HP NonStop SQL/MX and HP Neoview. NonStop SQL/MX was designed for online transaction processing on HP’s NonStop (formerly Tandem) fault-tolerant servers and is known for its high availability, scalability, and performance. Hundreds of companies and thousands of servers are running mission-critical applications today on NonStop SQL/MX. In addition, much of these components today are running internal to HP as the core of its Enterprise Data Warehouse (EDW), managing over a PB of data. Starting in 2013, the software was modified to run on HBase and a new distributed transaction manager was written to run as an HBase co-processor. Unlike most NOSQL and other SQL-on-Hadoop open source projects, Trafodion provides comprehensive ANSI SQL language support including full-functioned data definition (DDL), data manipulation (DML), transaction control (TCL) and database utility support. Trafodion provides comprehensive and standard SQL data manipulation support including SELECT, INSERT, UPDATE, DELETE, and UPSERT/MERGE syntax with language options including join variants, unions, where predicates, aggregations (group by and having), sort ordering, sampling, correlated and nested sub-queries, cursors, and many SQL functions. Utilities are provided for updating table statistics used by the optimizer for costing (i.e. selectivity/cardinality estimates) plan alternatives, for displaying the chosen SQL execution plan, plan shaping, backup and restoring the database, data loading and unloading, and a command line utility for interfacing with the database engine. Explicit control statements are provided to allow applications to define transaction boundaries and to abort transactions when warranted, including BEGIN WORK, COMMIT WORK, ROLLBACK WORK and SET TRANSACTION. Trafodion supports ANSI’s grant/revoke semantics to define user and role privileges in terms of managing and accessing the database objects. Rationale The name “Trafodion” (the Welsh word for transactions, pronounced “Tra-vod-eee-on”) was chosen specifically to emphasize the differentiation that Trafodion provides in closing a critical gap in the Hadoop ecosystem. Trafodion builds on the scalability, elasticity, and flexibility of Hadoop. Trafodion extends Hadoop to provide guaranteed transactional integrity, enabling new kinds of big data applications to run on Hadoop. Current Status HP released the Trafodion code under the Apache License, Version 2, in June of 2014. Since that time, we have had
Re: [VOTE] Apache Drill 0.6.0-incubating release
+1 (binding) - Downloaded bin and -src tarballs. - Not knowing much about the internals of Drill (yet), I poked around in the tarballs, looks all good. - Ran some of the examples. - All looks good. Packaging is clean. Few comments: - I would probably prefer the documentation to be part of either the bin or src tarball, seems that should be part of the distribution. - The documentation on https://cwiki.apache.org/confluence/display/DRILL/Apache+Drill+in+10+Minutes#ApacheDrillin10Minutes-StartDrill is a bit outdated (refers to release 0.4.0 at points) As for the Java8/Unittest failure discussion. IMHO a release does not need to be free of bugs (that's not actually possible anyway), it just means it is useful "snaphot" of the software. In any case this is an important discussion to have. (As the HBase 0.94 release manager I introduced a strict monthly release cadence and we found that far more useful then getting all the last fixes in - those just have to wait a month. Only for critical correctness issues did I delay a release for a few days. Obviously that is just my opinion.) Thanks. -- Lars From: Ted Dunning To: "general@incubator.apache.org" Sent: Wednesday, October 8, 2014 12:52 PM Subject: Re: [VOTE] Apache Drill 0.6.0-incubating release +1 (binding) I have downloaded the code, compiled and run the tests. I also checked all checksums, and verified the signatures. I also verified that the signing key was signed by people I trust (and indeed, by me as well) and correctly propagated to the gpg key servers. I also reviewed in both the source and binary that the various notices, licenses and dependency lists appear to be correct. The license files also appear to be correct and include the correct attributions. I have previously checked that the list of dependencies and attributions was both correct and complete and since these are generated automatically, I did not specifically check them again. Moreover, the dependencies have not changed so this gives even higher confidence in this assessment. It should be noted that Drill as a project has been able to produce several high quality releases in a row with different release managers. Moreover, Drill has invested in documentation to help train release managers to help grow the community. On Tue, Oct 7, 2014 at 8:41 AM, jan i wrote: > Hi. > > I have had a look at your release and it looks good, I could not find any > formal errors. > > But I took a closer look at the release vote thread, because a failing unit > test is a serious bad quality signal for me. > > Whenever I test new software, I download it, build it, then run all test > cases to secure I got it build correctly, where I assume I have made > something wrong if a test case fails. > > Apache is known for quality software and I think we all want to keep that > image. I am sure the project does not take quality lightly, but the > attitude "can be fixed later" especially with unit tests is to me not a > good policy. > > If the software only runs with 1.7 and not higher, then why not make a > simple startup version check, then there would be no problem (of course its > even better to solve the problem). I just wonder how this error will affect > people using the project. > > It seems (from the vote thread) you already have solved the problem, but > dont want to wait for a respin, can you please at least explain why the > project is under such a time constraint, that 72 hours is too long to wait > to make good quality. > > I wanted to give the release a -1 but decided to give > > -0 binding. > > in the hope the PMC will go for quality and voluntary respin the release. > > rgds > jan i > > > > On 7 October 2014 07:09, Steven Phillips wrote: > > > In case there is any confusion, the first email sent out in this thread > had > > the wrong vote count. The second one has the correct count: > > > > +9 binding > > +3 non-binding > > > > I should also mention there was one -0 (binding). This was due to unit > test > > failures when using java 1.8. Jiras were filed, and the fix will be > > included in the next release, not this one. > > > > On Sun, Oct 5, 2014 at 11:14 AM, Steven Phillips wrote: > > > > > I would like to present the Apache Drill 0.6.0-incubating release to > > > the general incubator list for a vote. This set of artifacts have > passed > > > our drill-dev vote and incorporate a number of improvements with over > 30 > > > JIRAs closed in the last month. > > > > > > The vote thread can be found here: > > > http://mail-archives.apache.org/mod_mbox/incubator-drill-dev/201410.mbox/%3CCAA_-67fAJFB20wGX462wm7BYvoSy3PvydCPgY9uNSEj3HpQRmg%40mail.gmail.com%3E > > > > > > The vote passed with: > > > +9 binding > > > +3 non-binding > > > > > > You can find the artifacts for the release at this location: > > http://people.apache.org/~smp/apache-drill-0.6.0.rc0/ > > > > > > I look forward to your feedback. > > > > > > Thanks, > > > Stev
Re: [VOTE] Graduation of Apache Phoenix from the Incubator
+1 From: James Taylor To: general@incubator.apache.org Sent: Wednesday, April 30, 2014 10:44 PM Subject: [VOTE] Graduation of Apache Phoenix from the Incubator Hi everyone, The Apache Phoenix podling has has discussed and voted to graduate from the incubator with 22 +1 votes, 5 of which were IPMC vote [1]. We've made three releases, increased our contributor and committer list [2], and have an active, thriving community. Please VOTE below on the graduation of Apache Phoenix from the Incubator. The graduation resolution is pasted below. The VOTE will be open for at least 72 hours: [ ] +1 Graduate Apache Phoenix from the Incubator. [ ] +0 Don't care. [ ] -1 Don't graduate Apache Phoenix from the Incubator because [1] http://mail-archives.apache.org/mod_mbox/incubator-phoenix-dev/201405.mbox/%3CCAAF1JdgX_0nc7hgSrx9v1wJGKG0C3LBjO2ceZpGYsW1Z%3DsSaYw%40mail.gmail.com%3E [2] https://incubator.apache.org/projects/phoenix.html X. Establish the Apache Phoenix Project WHEREAS, the Board of Directors deems it to be in the best interests of the Foundation and consistent with the Foundation's purpose to establish a Project Management Committee charged with the creation and maintenance of open-source software, for distribution at no charge to the public, related to a SQL database for NoSQL data stores such as Apache HBase. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the "Apache Phoenix Project", be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Phoenix Project be and hereby is responsible for the creation and maintenance of software related to a SQL database for NoSQL data stores such as Apache HBase; and be it further RESOLVED, that the office of "Vice President, Apache Phoenix" be and hereby is created, the person holding such office to serve at the direction of the Board of Directors as the chair of the Apache Phoenix Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Phoenix Project; and be it further RESOLVED, that the persons listed immediately below be and hereby are appointed to serve as the initial members of the Apache Phoenix Project: * Andrew Purtell * Anoop Sam John * Devaraj Das * Eli Levine * Enis Soztutar * Gabriel Reid * James R. Taylor * Jeffrey Zhong * Jesse Yates * Lars Hofhansl * Maryann Xue * Michael Stack * Mujtaba Chohan * Nick Dimiduk * Ramkrishna Vasudevan * Simon Toens * Steven Noels NOW, THEREFORE, BE IT FURTHER RESOLVED, that James R. Taylor be appointed to the office of Vice President, Apache Phoenix, to serve in accordance with and subject to the direction of the Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed; and be it further RESOLVED, that the initial Apache Phoenix PMC be and hereby is tasked with the creation of a set of bylaws intended to encourage open development and increased participation in the Apache Phoenix Project; and be it further RESOLVED, that the Apache Phoenix Project be and hereby is tasked with the migration and rationalization of the Apache Incubator Phoenix podling; and be it further RESOLVED, that all responsibilities pertaining to the Apache Incubator Phoenix podling encumbered upon the Apache Incubator Project are hereafter discharged.
Re: [VOTE] Release of Apache Phoenix 3.0.0 incubating RC3
+1 (binding) - promoting my +1 from the Phoenix dev list. -- Lars From: James Taylor To: general@incubator.apache.org Sent: Monday, March 31, 2014 10:40 PM Subject: [VOTE] Release of Apache Phoenix 3.0.0 incubating RC3 Hi everyone, This is a call for a vote on Apache Phoenix 3.0.0 incubating RC3. Phoenix is a SQL query engine for Apache HBase, a NoSQL data store. It is accessed as a JDBC driver and enables querying and managing HBase tables using SQL. This is the next major release of Phoenix compatible with the 0.94 branch of Apache HBase and will be our second release in the incubator. The release includes both a source-only release and a convenience binary release. New features include: - Equi-joins through broadcast hash join - Shared tables over same physical HBase table - Read-only and updatable views - Multi-tenancy - JDBC ARRAY type - Sequence creation and usage The dev list thread for the passing vote (8 +1s with 2 IPMC votes) can be found at: http://mail-archives.apache.org/mod_mbox/incubator-phoenix-dev/201404.mbox/%3CCAAF1JdiaQHkaT7FeMW9R343j4mbZLOr0Qxn2ZeP9EoXVv4%3DGZQ%40mail.gmail.com%3E The source tarball, including signatures, digests, etc can be found at: https://dist.apache.org/repos/dist/dev/incubator/phoenix/phoenix-3.0.0-incubating-rc3/src/ The binary artifacts can be found at: https://dist.apache.org/repos/dist/dev/incubator/phoenix/phoenix-3.0.0-incubating-rc3/bin/ Release artifacts are signed with the following key: https://people.apache.org/keys/committer/mujtaba.asc KEYS file available here: https://dist.apache.org/repos/dist/release/incubator/phoenix/KEYS The hash and tag to be voted on: https://git-wip-us.apache.org/repos/asf?p=incubator-phoenix.git;a=commit;h=363e71bfd7cf6576657dddb484c6a48de9b8de61 https://git-wip-us.apache.org/repos/asf?p=incubator-phoenix.git;a=tag;h=refs/tags/v3.0.0-incubating-rc3 For information about the contents of this release see: https://git-wip-us.apache.org/repos/asf?p=incubator-phoenix.git;a=log;h=refs/tags/v3.0.0-incubating-rc3 Vote will be open for at least 72 hours. Please vote: [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Thanks, The Apache Phoenix Team
Re: [VOTE] Graduation of Apache Spark from the Incubator
I agree with Marvin. In addition I find it odd to rely in two sources of truth (and two sets of infrastructure, etc) as far as code goes just so we do code reviews on GitHub. Anybody who wants to commit now needs to have both the Github repo and the Apache repo cloned; you can merge a pull request on GitHub, as that is not authoritative source control. Github will be behind sometimes, etc, etc. What if there are issues with Github (unlikely, I know, but would be out of Apache's control)? Can't we add necessary Apache Infrastructure? Would Apache be able to get a free GitHub license - ala Jira - to run it as part of Apache (or maybe buy a license)? On the Phoenix mailing Gerret was mentioned for git-style code review. -- Lars From: Marvin Humphrey To: "general@incubator.apache.org" Sent: Thursday, February 6, 2014 9:53 AM Subject: Re: [VOTE] Graduation of Apache Spark from the Incubator On Thu, Feb 6, 2014 at 9:08 AM, Michael Joyce wrote: > How is doing a review on Github any different than doing a review on Review > Board? One is captured to Apache controlled channels and the other is not. > If there's concern that work on Github isn't being adequately mirrored on > the mailing lists then that sounds like an Infra problem to me. It's not an Infra problem. It's the problem of any PMC which fails to ensure that all of its communications are properly archived. If anyone here is interested in contributing towards this feature, I encourage you to subscribe to the infrastructure-dev@apache list. I also encourage everyone to ponder carefully: * How to ensure that no information is lost when capturing communications in GitHub channels through notifications to our dev lists. * The impact of adding GitHub integration features on long-term ASF Infra labor costs. > There are plenty of hooks [1] that makes this easy to do and, if I'm not > mistaken, pull requests through Github are already supposed to mail dev@. That's right. I've actually worked on the specific hook that does that[1][2]. > I would assume that any comment on them should as well. Why would you "assume" that GitHub comments are being mailed to dev lists? They are not. Every Apache PMC member is tasked with oversight of their project, and that includes ensuring that all decisions happen on the dev list and are properly documented. It is not enough to "assume" that Infra is taking care of archival -- ensuring that the archival actually happens is the PMC's direct responsibility. Marvin Humphrey [1] https://issues.apache.org/jira/browse/INFRA-4651 [2] Thread on legal-discuss@apache: http://s.apache.org/Nhx - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Hoya Proposal
I should we shouldn't rule out a name just because the English pronunciation is similar to another project. Will people really confuse Apache Hyena and Apache Jena? Would have to be a face-to-face conversation or a recording where either party do not really know what they are talking about. That said, "Hoya" seems like a fine name to me as well. I do wonder whether it is a large enough project to be standalone (rather then being folded into either Hadoop or HBase). Just my $0.02. -- Lars From: Andy Seaborne To: general@incubator.apache.org Sent: Tuesday, January 14, 2014 4:03 AM Subject: Re: Hoya Proposal As a project name "Jena" has been in use for the project for about 13 years now. 1.0 was 9 Jan 2001. A mere 983K (zipped). The discussion is about Hyena for Hoya. Andy On 13/01/14 23:38, sebb wrote: > Jenny ? > > On 13 January 2014 22:21, Ted Dunning wrote: >> Too many people will read that as Jena, the city in Thuringia. >> >> https://en.wikipedia.org/wiki/Jena >> >> -1 >> >> >> >> >> On Mon, Jan 13, 2014 at 1:57 PM, Andy Seaborne wrote: >> >>> On 13/01/14 20:25, Bertrand Delacretaz wrote: >>> On Mon, Jan 13, 2014 at 5:36 PM, Bertrand Delacretaz wrote: > On Mon, Jan 13, 2014 at 3:33 PM, Steve Loughran > wrote: > >> ...What do people think about a project name "Hyena"? It's close >> enough, lives >> in the savannah... >> > > I think it's too close to http://jena.apache.org/ > to be clear, this is a strong -1 from me, having confusing project names inside Apache is not ok. Hyena and Jena sound exactly the same in several languages, unfortunately. >>> >>> The "j-e-n" in "Jena" is like "Jen-kins" or "Gen-er-al". >>> >>> It is derived from "Jennifer" >>> >>> http://en.wikipedia.org/wiki/Jennifer_%28given_name%29 >>> >>> which is often, but not here, with "nn": >>> >>> http://en.wikipedia.org/wiki/Jenna >>> >>> Andy >>> >>> -Bertrand >>> >>> >>> - >>> 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 > - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: January 2014 Incubator report timeline
Thanks Marvin, my username is LarsHofhansl Thanks. -- Lars From: Marvin Humphrey To: "general@incubator.apache.org" ; lars hofhansl Sent: Wednesday, January 8, 2014 3:38 AM Subject: Re: January 2014 Incubator report timeline On Tue, Jan 7, 2014 at 11:30 PM, lars hofhansl wrote: > Belated +1 from me as well. Thanks, I've added it. For future reference, what's your username for the Incubator wiki (not Apache ID)? We should whitelist you now so that next month you can participate in the report editing process directly. Marvin Humphrey - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: January 2014 Incubator report timeline
Belated +1 from me as well. From: Marvin Humphrey To: "general@incubator.apache.org" Sent: Tuesday, January 7, 2014 5:24 PM Subject: Re: January 2014 Incubator report timeline On Tue, Jan 7, 2014 at 3:49 PM, Stack wrote: > I went ahead and added up the Phoenix report (I removed us from the > non-reporters list -- smile). Great, thanks! > I did not know what to fill in for the 'signed-off by' list so left it > blank. It's a list of Mentors who have seen the report and approved it. I took the liberty of filling in the checkboxes for Enis Sözutar and Devaraj Das because they both sent +1 emails to dev@phoenix.incubator. > Let me go ping our Shepherd for this period; hopefully he is just as > forgiving of our late submission. The main thing we need shepherds for is to signal the IPMC when all Mentors have gone missing and a podling is adrift. The secondary function of providing outsider feedback can be helpful, but it's best not to add commentary late in the process because we want to give the podling the chance to respond if necessary. Clearly the Mentors for Phoenix are engaged, and I plan to file the Incubator report tomorrow regardless. Marvin Humphrey - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Subscribtion at the private list
I'd volunteer. What does it involve? Of course I am new here. Thanks. -- Lars From: Jukka Zitting To: general Sent: Thursday, December 19, 2013 8:29 PM Subject: Re: Subscribtion at the private list Hi, On Thu, Dec 19, 2013 at 1:20 AM, Raphael Bircher wrote: > I'm still not subscribed at the private incubator list. I was sending a > request, but for some reasons, I'm not registred yet. Can someone help me to > get on the private list. Thanks! I checked through the backlog of recent subscription requests and approved the new IPMC members. Welcome! Apologies for the delay. It seems like we need a few new moderators for private@incubator. Any volunteers? BR, Jukka Zitting - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Subscribtion at the private list
I have the same issue (tried multiple time for a week). Will do the same. From: David Crossley To: general@incubator.apache.org Sent: Wednesday, December 18, 2013 11:29 PM Subject: Re: Subscribtion at the private list Raphael Bircher wrote: > Hi all > > I'm still not subscribed at the private incubator list. I was sending a > request, but for some reasons, I'm not registred yet. Can someone help > me to get on the private list. Thanks! Gee, that is not good. If you still get no result, perhaps try contacting the moderators directly at private-owner@i.a.o -David > Greetings Raphael - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Enable Release Checklist Experiment
+1 From: Marvin Humphrey To: "general@incubator.apache.org" Sent: Friday, December 13, 2013 12:59 PM Subject: [VOTE] Enable Release Checklist Experiment Greetings, As the next step in our ongoing efforts to reform the release voting process, I propose that we run an experiment allowing the PPMC members of select podlings to earn binding votes under limited circumstances by completing a release checklist. For participating podlings, the Incubator's release management guide... http://incubator.apache.org/guides/releasemanagement.html ... would be supplanted by the following documents: http://incubator.apache.org/guides/release_manifest.txt http://incubator.apache.org/guides/release.html The scope of this VOTE is limited to approving the following patch to our policy page: https://paste.apache.org/k4vJ Here is the patch content minus markup: 2013 Alternate Release Voting Process Select podlings pre-cleared by a majority vote of the IPMC MAY participate in an alternate release voting process: Should a Podling decide it wishes to perform a release, the Podling SHALL hold a vote on the Podling's dev list and create a permanently archived Release Manifest as described in the Experimental Release Guide. At least three +1 votes from PPMC members are required (see the Apache Voting Process page). If the majority of PPMC votes is positive, then the Podling SHALL send a summary of that vote to the Incubator's general list and formally request the Incubator PMC approve such a release. Formal approval requires three binding +1 votes and more positive than negative votes. Votes cast by members of the Incubator PMC are always binding. For all releases after the first, votes cast by members of the PPMC are binding if a Mentor approves the Release Manifest. Please note that the proposed change is both incremental and reversible: * It is incremental because podlings must be opted in by vote of the IPMC to participate. * It is reversible because once the experiment has run its course the policy change can be reverted with zero impact through lazy consensus. Those who may have questions about the legitimacy of allowing binding votes from non-IPMC members should see this post from Roy Fielding: http://s.apache.org/v7 Please vote: [ ] +1 Yes, apply the patch enabling the experiment. [ ] -1 No, do not apply the patch enabling the experiment. This majority VOTE will run for 7 days and will close at 13:00 PST on Friday, December 20, 2013. Votes cast by members of the Incubator PMC are binding. Here is my own +1. Marvin Humphrey - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Phoenix for incubator project
ion format, interoperability between them will take a big step forward. In addition, we plan to explore providing lower level APIs for other products such as Apache Drill to plug into when querying HBase data so that they get the performance benefits of using Phoenix. A Excessive Fascination with the Apache Brand Phoenix is already a healthy and relatively well known open source project. This proposal is not for the purpose of generating publicity. Rather, the primary benefits to joining Apache are those outlined in the Rationale section. Documentation Additional documentation on Phoenix may be found on its github website: Phoenix overview: https://github.com/forcedotcom/phoenix/blob/master/README.md Phoenix wiki: https://github.com/forcedotcom/phoenix/wiki Phoenix road map: https://github.com/forcedotcom/phoenix/wiki#roadmap Phoenix issue tracking: https://github.com/forcedotcom/phoenix/issues?direction=desc&sort=updated&state=open Phoenix codebase: https://github.com/forcedotcom/phoenix Phoenix SQL language reference: http://forcedotcom.github.io/phoenix/ Phoenix performance: https://github.com/forcedotcom/phoenix/wiki/Performance#phoenix-vs-related-products User group: https://groups.google.com/group/phoenix-hbase-user Initial Source The Phoenix codebase is currently hosted on Github: https://github.com/forcedotcom/phoenix. Source and Intellectual Property Submission Plan Currently, the Phoenix codebase is distributed under a BSD license. Upon entering Apache, the Phoenix license will be migrated to the Apache 2.0 License. External Dependencies Beyond relying on Apache HBase, Phoenix has the following external dependencies: ANTLR 3.5 (BSD license: http://www.antlr3.org/license.html) Sqlline 1.1.2 (BSD license: https://github.com/julianhyde/sqlline/blob/master/LICENSE) Open CSV 2.3 (Apache 2.0 license) Upon acceptance to the incubator, we would begin a thorough analysis of all transitive dependencies to verify this information and introduce license checking into the build and release process by integrating with Apache Rat. Required Resources Mailing list We will migrate the existing Phoenix mailing lists as follows: phoenix-hbase-u...@googlegroups.com --> us...@phoenix.incubator.apache.org phoenix-hbase-...@googlegroups.com --> d...@phoenix.incubator.apache.org priv...@phoenix.incubator.apache.org for IPMC members comm...@phoenix.incubator.apache.org The latter is to be consistent with the new PIAO naming scheme for podlings. Source control The Phoenix team would like to use Git for source control, due to our current use of Git. We request a writeable Git repo for Phoenix, and mirroring to be set up to Github through INFRA. Issue Tracking Phoenix currently uses the github issue tracking system associated with its github repo: https://github.com/forcedotcom/phoenix/issues?direction=desc&sort=updated&state=open. We will migrate to the Apache JIRA: http://issues.apache.org/jira/browse/PHOENIX Other Resources Jenkins/Hudson for builds and test running. Wiki for documentation purposes Blog to improve project dissemination Initial Committers James Taylor Mujtaba Chohan Jesse Yates Eli Levine Simon Toens Maryann Xue Anoop Sam John Ramkrishna S Vasudevan Jeffrey Zhong Nick Dimiduk Affiliations The initial committers are from three organizations: Salesforce.com, Intel, and Hortonworks. James Taylor (Salesforce.com) Mujtaba Chohan (Salesforce.com) Jesse Yates (Salesforce.com) Eli Levine (Salesforce.com) Simon Toens (Salesforce.com) Maryann Xue (Intel) Anoop Sam John (Intel) Ramkrishna S Vasudevan (Intel) Jeffrey Zhong (Hortonworks) Nick Dimiduk (Hortonworks) Sponsors Champion Michael Stack Nominated Mentors Michael Stack Lars Hofhansl Andrew Purtell Devaraj Das Enis Soztutar Steven Noels Sponsoring Entity The Apache Incubator
Re: [VOTE] Phoenix for Apache Incubator
This is not an official vote, is it? In any case. +1 -- Lars From: Ravi Kiran To: general@incubator.apache.org Sent: Tuesday, December 3, 2013 8:37 AM Subject: [VOTE] Phoenix for Apache Incubator +1 An exciting project which we are currently evaluating at Evolv. Looking forward for its incubation at Apache. Regards Ravi
