Return-Path: X-Original-To: apmail-incubator-general-archive@www.apache.org Delivered-To: apmail-incubator-general-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 11227173A7 for ; Tue, 13 Jan 2015 18:01:39 +0000 (UTC) Received: (qmail 4773 invoked by uid 500); 13 Jan 2015 18:01:40 -0000 Delivered-To: apmail-incubator-general-archive@incubator.apache.org Received: (qmail 4563 invoked by uid 500); 13 Jan 2015 18:01:40 -0000 Mailing-List: contact general-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: general@incubator.apache.org Delivered-To: mailing list general@incubator.apache.org Received: (qmail 4552 invoked by uid 99); 13 Jan 2015 18:01:39 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 13 Jan 2015 18:01:39 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW X-Spam-Check-By: apache.org Received-SPF: error (athena.apache.org: local policy) Received: from [209.85.192.52] (HELO mail-qg0-f52.google.com) (209.85.192.52) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 13 Jan 2015 18:01:35 +0000 Received: by mail-qg0-f52.google.com with SMTP id i50so3321936qgf.11 for ; Tue, 13 Jan 2015 09:59:24 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=9cNf8w8XH0fA0mBjARg/vm6eGeW0YsH2SeLwcgxzI1Y=; b=jiOqIX384eDGlaI4bWQ+s6p7lXxYk4EcvGNG+PXjctL8Td31NT53MtLbD59nGsniSs 9E76IKov1dTyR35HKyIzdHnvdc8hYgxwvGds0YJNrZMXu8s4K4o4BnaAXvU5vkUwkT6I kXh0/hwkIMl3mI56Sa5s6O3DX1UTBk5elJieHTH6JzPJrVNb7r9hUglhlCgR/gR3OdBE Y2+uyEimzYUGpyngLPMFw3UV0lOcK0oK/e34mJH/KYlY3WlYXLQvy911B9/Cg25cvxNN g1jRqf3l9QtokbZniyRwFmHMV9e264HX1y1fXAVVM04Z42kvHT9jW/D3s1T+bgqYbzL5 ub1A== X-Gm-Message-State: ALoCoQkQePxSNVFAzwj75Pxkhzv9MC4z5tq1THGwVat8Dx929B8OReTPTx55oCZe8Uql13R56UzG X-Received: by 10.224.137.65 with SMTP id v1mr50481239qat.95.1421171964217; Tue, 13 Jan 2015 09:59:24 -0800 (PST) Received: from localhost.localdomain (cpe-74-138-17-157.swo.res.rr.com. [74.138.17.157]) by mx.google.com with ESMTPSA id r4sm18273002qad.32.2015.01.13.09.59.22 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 13 Jan 2015 09:59:22 -0800 (PST) Message-ID: <54B55CF7.4080400@rcbowen.com> Date: Tue, 13 Jan 2015 12:59:19 -0500 From: Rich Bowen User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0 MIME-Version: 1.0 To: general@incubator.apache.org Subject: Re: [Proposal] TinkerPop: A Graph Computing Framework [RE-SUBMISSION] References: <93C0971F-888A-425D-A7B8-B1139412BBBC@gmail.com> In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-Virus-Checked: Checked by ClamAV on apache.org On 01/10/2015 01:18 AM, Ted Dunning wrote: > > This still only has 3 committers. > > How is the project going to function with such a small group? I don't > see that there has been a realistic answer to this question. > This has been discussed by the (proposed) mentors along with the community members, and we have also identified this as a place where work needs to be done to identify what people in the community might be added to that list during incubation. We do not, however, feel that it is a barrier to entering incubation - merely something to be addressed during incubation. > > > On Fri, Jan 9, 2015 at 10:35 AM, Marko Rodriguez > wrote: > > Hello everyone, > > Over the last 2 weeks, TinkerPop's proposal has been worked on with > support from: > * David Nalley (champion) > * Rich Bowen (mentor) > * Hadrian Zbarcea (mentor) > * Daniel Gruno (mentor) > * Marko Rodriguez (submitting on behalf of TinkerPop) > > We feel it is now in prime shape from submission to vote. Enjoy!. > (URL to wiki version: > https://wiki.apache.org/incubator/TinkerPopProposal) > > > A. Abstract > > TinkerPop is a graph computing framework > written in Java. A graph > is a data > structure composed of vertices and edges and is useful for modeling > complex domains with arbitrary relations (edges, links, lines) > between entities (vertices, objects, dots). TinkerPop > provides a core API > that graph system vendors can implement. There are various types of > graph systems including in-memory graph libraries, OLTP graph > databases, and OLAP graph processors (see On Graph Computing > for more > information). Once the core interfaces are implemented, the > underlying graph system can be queried using the graph traversal > language Gremlin and processed withTinkerPop > -enabled algorithms. > For many, TinkerPop is > seen as the JDBC > of the > graph computing community. > > > B. Proposal > > TinkerPop was formed > in 2009 and is currently in the milestone series of 3.0.0. From the > start, TinkerPop has > provided its software open source and free to use for which ever > reason (commercial or otherwise). Initially the license was BSD, but > as of TinkerPop3 , the > license was changed to Apache2. The TinkerPop > team is composed of > developers, evangelists, and representatives from graph system > vendors (see TinkerPop Contributors > for > more information). TinkerPop > has done its best to > remain vendor agnostic and works closely with all vendors to ensure > that the constructs within TinkerPop > are able to > accommodate the requirements of the underlying graph system. To > date, 12 "TinkerPop > recognized" graph > system vendors provide TinkerPop > implementations. We > believe that by joining The Apache Software Foundation, our vendors, > users, and contributors will feel more comfortable in terms of legal > protected, in terms of wider-adoption, and in terms of project > stability. > > > C. Background > > TinkerPop has had > steady, active development since 2009 when it was founded. Over the > years, the Gremlin query language within TinkerPop > has been adopted by > various JVM languages and as such, there exists Gremlin-Groovy, > Gremlin-Scala, Gremlin-Clojure, Gremlin-JavaScript > , and the like. In > many ways, Gremlin is seen as a traversal style that can be readily > adopted within the programming constructs of the developer's native > language --- both on and off the JVM. TinkerPop > is not bound to the > JVM in that developers wishing to interact with a TinkerPop > -enabled graph system > can leverage Gremlin Server which provides "over the wire" > communication as well as the entry point for non-JVM language > bindings. TinkerPop is > being used is production graph-based applications around the world > and is only getting better with age. > > > D. Rationale > > The graph computing space has grown over the years to encompass > numerous graph database and graph processing systems. TinkerPop > was created as a > unifying framework for interoperability, language standardization, > and data model standardization. This framework makes it simple to > "plug and play" the back-end graph implementation without affecting > the developer's code. This is analogous to the way in which the JDBC > allows users to swap relational databases while keeping the same > programming interface. TinkerPop > also brings together > OLTP systems (graph databases) and OLAP systems (graph processors) > by providing a single query language (Gremlin) for executing graph > algorithms transparently over either type of system. The seamless > support of single-machine systems and distributed systems provides > an identical end-user experience within the boundaries of the space > and time constraints of the underlying graph system. > > > E. Initial Goals > > The goal of this proposal is to migrate TinkerPop > to The Apache Software > Foundation to > > 1. get more exposure to the project > 2. legally protect the developers and contributors of the project > 3. > ensure that TinkerPop > has a > vendor-neutral, stable home for the future > > > F. Current Status > > TinkerPop is planning > to release TinkerPop > 3.0.0.GA early 2015. We would like to release > TinkerPop 3.0.0.GA > at the Apache Software Foundation. > > > G. Meritocracy > > TinkerPop already has > an established community that values meritocracy. Anyone is welcome > to contribute to TinkerPop > and voice their > opinions/thoughts on the direction of the project. If an individual > provides beneficial pull requests, documentation updates, > theoretical ideas, etc. then they are asked to join TinkerPop > as committers. > Moreover, TinkerPop is > a business friendly community. It provides a forum where vendors > collaborate, via individual representatives, by contributing ideas, > code and content. > > We believe the values of the community align well with the ASF, and > we are willing to adapt our practices when necessary. > > > H. Community > > The TinkerPop mailing list > has 1500+ > subscribers with a flow of approximately 10 emails a day. In > addition to the initial committers there are about two dozen folks > that have contributed code to the project, and 1/2 of those are from > Graph vendors. Note that there are individuals that participate in > the TinkerPop > ecosystem by providing > language bindings and system implementations. While not contributing > to the core codebase per se, they supportTinkerPop > via their software and > lecture outreach. > > > I. Core developers > > The initial committer list is small, and we hope to grow that into a > larger, vibrant community at the Apache Software Foundation. > > > J. Alignment > > TinkerPop is licensed > Apache2. The OLAP reference implementation that distributes with > TinkerPop is based on > Hadoop and Giraph > . There has been a push from vendors and > commercial organizations interested in ensuring TinkerPop > has the legal support > of a software foundation. We believe The Apache Software Foundation > to be a great home for TinkerPop > . > > > K. Known Risks & Abandoned projects > > TinkerPop is currently > at TinkerPop 3.0.0.M6. > There is a significant amount of code developed since TinkerPop > 's inception. We have > done our best to secure CLAs from contributors. To date did not have > any legal or political issues. TinkerPop > has 12 official graph > vendors that maintain or support a TinkerPop > implementation for > their system. If, lets say, 75% of those vendors decide against > providing a TinkerPop > interface, then this > would be detrimental to TinkerPop > 's efforts. With that, > it is very important that TinkerPop > remain neutral and > engaged with vendors. > > > L. Inexperience with Open Source > > The primary developers of TinkerPop > have been producing > TinkerPop open source > code and releases in full public view since 2009 via both our GitHub > repository and our public > mailing lists. We pride ourselves in professional software, > documentation, and aesthetics. With its integration to numerous > graph systems in the market, we see TinkerPop > as a masterpiece in > the open source space. We are working with both open source and > commercial entities to ensure a solid, respected product. > > > M. Homogeneous Developers > > The initial set of committers all hail from different employers. > > > N. Reliance on Salaried Developers > > TinkerPop is open > source and no individual is paid for their contributions except for > our logo designer. All the logos and documentation graphics are > released Apache2. > > > O. Relationships with Other Apache Projects > > TinkerPop currently > leverages Hadoop, Giraph, and in the near future, will integrate > with Spark . Internally, the project > leverages Maven3, Apache Configuration, and Apache Commons. > > > P. An Excessive Fascination with the Apache Brand > > TinkerPop is > interested in The Apache Software Foundation for the legal support > and protection it can offer our developers. Numerous large software > organizations have urged TinkerPop > to join a foundation > so that they may more easily provide contributors from their > organization and moreover, maintain confidence in building products > atop TinkerPop . With > that said, TinkerPop > does respect the > Apache Software Foundation brand and believes that by joining The > Apache Software Foundation, we will further boost the recognition > and prestige of our product. Finally, note that a TinkerPop book > is slated for 2015. Combining the > Apache Software Foundation and a long awaited book should ensure a > new uptake of contributors, users, vendors, and promoters. > > > Q. Documentation > > TinkerPop takes pride > in its documentation: > > AsciiDoc > > http://www.tinkerpop.com/docs/3.0.0-SNAPSHOT/ > JavaDoc (core) > > http://www.tinkerpop.com/javadocs/3.0.0-SNAPSHOT/core/ > JavaDoc (full) > > http://www.tinkerpop.com/javadocs/3.0.0-SNAPSHOT/full/ > > > R. Initial Source > > TinkerPop is currently > hosted on GitHub : > https://github.com/tinkerpop/. > > The following repositories would like to be migrated to ASF. > > TinkerPop3 > > https://github.com/tinkerpop/tinkerpop3 > Blueprints (TinkerPop2 ) > > https://github.com/tinkerpop/blueprints > Pipes (TinkerPop2 ) > > https://github.com/tinkerpop/pipes > Frames (TinkerPop2 > > https://github.com/tinkerpop/frames > Gremlin (TinkerPop2 ) > > https://github.com/tinkerpop/gremlin > Rexster (TinkerPop2 ) > > https://github.com/tinkerpop/rexster > > > S. Source & Intellectual Property Submission Plan > > TinkerPop has required > CLAs from contributors in the past to ensure solid IP provenance. > TinkerPop plans to > submit a Software Grant for the content in the following > repositories: https://github.com/tinkerpop/tinkerpop3 > > We plan to transfer to the ASF the TinkerPop > trademark as well as > the commissioned artwork for TinkerPop > logos and the > http://tinkerpop.com and > http://tinkerpop.org domains. > > > T. External Dependencies > > TinkerPop relies on a > number of open source dependencies. We believe these to comply with > the third-party licensing guidelines. If any dependencies are unfit, > we will make the necessary changes. > > > U. Cryptography > > None. > > > V. Required Resources > > > W. Mailing Lists > > TinkerPop requests the > following mailing list: > > User Mailing List > > users@tinkerpop.incubator.apache.org > > Developer Mailing List > > dev@tinkerpop.incubator.apache.org > > Private Mailing List > > private@tinkerpop.incubator.apache.org > > Commits Mailing List > > commits@tinkerpop.incubator.apache.org > > > > X. Subversion Directory > > TinkerPop will use > subversion for it’s website and requests: > > * > https://svn.apache.org/repos/asf/incubator/tinkerpop > > > Y. Git Repository > > TinkerPop wishes to > have the following created: > > * > https://git-wip-us.apache.org/repos/asf/incubator-tinkerpop.git > > And to have all of these mirrored to Github with integration taken > care of. > > > Z. Issue Tracking > > Please help us setup a JIRA instance for both issue tracking and > code review (TINKERPOP). > > > AA. Initial Committers and Affiliations > > Marko A. Rodriguez (2009) > > Aurelius > Stephen Mallette (2011) > > Nidomics > James Thornton (2013) > > Electric Speed > > > BB. Sponsors > > * Champion: David Nalley > * Mentors: Rich Bowen, Matt Franklin, Daniel Gruno, David Nalley, > Hadrian Zbarcea > * Sponsoring Entity: We request the Incubator to sponsor this project. > > > -- Rich Bowen - rbowen@rcbowen.com - @rbowen http://apachecon.com/ - @apachecon --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org For additional commands, e-mail: general-help@incubator.apache.org