Differences between revisions 20 and 21
Revision 20 as of 2015-01-07 03:09:30
Size: 11682
Comment:
Revision 21 as of 2015-01-08 00:57:19
Size: 11251
Comment: Updates to the tinkerpop proposal
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
= Apache Tinkerpop Proposal =
Line 3: Line 4:
=== A. Abstract === == A. Abstract ==
Line 7: Line 8:
=== B. Proposal === == B. Proposal ==
Line 11: Line 12:
=== C. Background === == C. Background ==
Line 13: Line 14:
TinkerPop was founded in 2009 and has had steady, active development since. 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. 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.
Line 15: Line 16:
=== D. Rationale === == D. Rationale ==
Line 19: Line 20:
=== E. Initial Goals === == E. Initial Goals ==
Line 21: Line 22:
The goal of this proposal is to migrate TinkerPop to The Apache Software Foundation to 1.) get more exposure to the project and 2.) legally protect the developers and contributors of TinkerPop. The goal of this proposal is to migrate TinkerPop to The Apache Software Foundation to
 #
get more exposure to the project and
 #
legally protect the developers and contributors of TinkerPop
 # ensure that TinkerPop has a vendor-neutral, stable home for the future
Line 23: Line 27:
=== F. Current Status === == F. Current Status ==
Line 25: Line 29:
TinkerPop is planning to release TinkerPop 3.0.0.GA early 2015. We would like to release TinkerPop 3.0.0.GA under The Apache Software Foundation. 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.
Line 27: Line 31:
=== G. Meritocracy === == G. Meritocracy ==
Line 30: Line 34:
Line 32: Line 37:
=== H. Community === == H. Community ==
Line 34: Line 39:
The [[https://groups.google.com/forum/#!forum/gremlin-users|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 support TinkerPop via their software and lecture outreach.  The [[https://groups.google.com/forum/#!forum/gremlin-users|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 support TinkerPop via their software and lecture outreach.
Line 36: Line 41:
=== I. Core developers === == I. Core developers ==
Line 38: Line 43:
The initial committer list is small, and we hope to grow that into a larger, vibrant community at the Apache Software Foundation.   The initial committer list is small, and we hope to grow that into a larger, vibrant community at the Apache Software Foundation.
Line 40: Line 45:
=== J. Alignment === == J. Alignment ==
Line 44: Line 49:
=== K. Known Risks & Abandoned projects === == K. Known Risks & Abandoned projects ==
Line 46: Line 51:
TinkerPop is currently at TinkerPop 3.0.0.M6. By joining The Apache Software Foundation, there is a significant amount of code and time that has passed since TinkerPop's inception. However, we have done our best to secure CLAs from contributors and to date, have not been involved in 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. 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.
Line 48: Line 53:
=== L. Inexperience with Open Source === == L. Inexperience with Open Source ==
Line 50: Line 55:
The primary developers of TinkerPop have been providing TinkerPop code and releases open source and 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 a open source technology --- working with both open source and commercial entities to ensure a solid, respected product. 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.
Line 52: Line 57:
=== M. Homogeneous Developers === == M. Homogeneous Developers ==
Line 54: Line 59:
The initial set of committers all hail from different employers.  The initial set of committers all hail from different employers.
Line 56: Line 61:
=== N. Reliance on Salaried Developers === == N. Reliance on Salaried Developers ==
Line 60: Line 65:
=== O. Relationships with Other Apache Projects === == O. Relationships with Other Apache Projects ==
Line 64: Line 69:
=== P. An Excessive Fascination with the Apache Brand === == P. An Excessive Fascination with the Apache Brand ==
Line 66: Line 71:
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 [[http://www.tinkerpopbook.com/|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. 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 [[http://www.tinkerpopbook.com/|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.
Line 68: Line 73:
=== Q. Documentation === == Q. Documentation ==
Line 76: Line 81:
=== R. Initial Source === == R. Initial Source ==
Line 80: Line 85:
=== S. Source & Intellectual Property Submission Plan === == S. Source & Intellectual Property Submission Plan ==
Line 84: Line 89:
We plan to transfer to the ASF the TinkerPop trademark as well as the commissioned artwork for TinkerPop logos and the http://tinkerpop.com domain. 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.
Line 86: Line 91:
=== T. External Dependencies === == T. External Dependencies ==
Line 88: Line 93:
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 work to remove them. 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.
Line 90: Line 95:
=== U. Cryptography === == U. Cryptography ==
Line 94: Line 99:
=== V. Required Resources ===

The only resource we see moving forward and if Apache wishes, is to fund our logo designer when we need a logo. We currently spend about $500 a year on logos. Please look through our documentation to see how much we love giving character to our work. If this is not something that Apache can do, then we will continue funding the creation of our artwork as we have done in the past.
== V. Required Resources ==
Line 100: Line 103:
|| User Mailing List || gremlin-users@googlegroups.com (mirrored by users@tinkerpop.incubator.apache.org) || TinkerPop requests the following mailing list:

|| User Mailing List || users@tinkerpop.incubator.apache.org ||
Line 105: Line 110:
TinkerPop requests the following mailing list:
Line 109: Line 112:
TinkerPop will use subversion for it’s website and requests:  TinkerPop will use subversion for it’s website and requests:
Line 111: Line 114:
 * https://svn.apache.org/repos/asf/incubator/tinkerpop   * https://svn.apache.org/repos/asf/incubator/tinkerpop
Line 115: Line 118:
TinkerPop wishes to have the following created:  TinkerPop wishes to have the following created:
Line 117: Line 120:
 * https://git-wip-us.apache.org/repos/asf/incubator-tinkerpop.git   * https://git-wip-us.apache.org/repos/asf/incubator-tinkerpop.git
Line 120: Line 123:
 
Line 123: Line 126:
TinkerPop is currently making use of Github issues. We plan to continue this way. Please help us setup a JIRA instance for both issue tracking and code review (TINKERPOP).
Line 125: Line 128:
=== AA. Initial Committers and Affiliations === == AA. Initial Committers and Affiliations ==
Line 131: Line 134:
=== CC. Sponsors === == BB. Sponsors ==
Line 135: Line 138:
 * Sponsoring Entity: We request the Incubator to sponsor this project.   * Sponsoring Entity: We request the Incubator to sponsor this project.

Apache Tinkerpop Proposal

http://www.tinkerpop.com/docs/3.0.0-SNAPSHOT/images/tinkerpop-logo.png

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 with TinkerPop-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

  • # get more exposure to the project and

    # legally protect the developers and contributors of TinkerPop # 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 support TinkerPop 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/tinkerpop3.

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:

Y. Git Repository

TinkerPop wishes to have the following created:

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.

TinkerPopProposal (last edited 2015-01-08 14:00:37 by MarkoRodriguez)