Differences between revisions 11 and 23 (spanning 12 versions)
Revision 11 as of 2014-12-22 20:05:10
Size: 13459
Comment:
Revision 23 as of 2015-01-08 14:00:37
Size: 11711
Comment:
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 9: Line 10:
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 [[http://www.tinkerpop.com/docs/3.0.0-SNAPSHOT/#tinkerpop-contributors|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 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. 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 [[http://www.tinkerpop.com/docs/3.0.0-SNAPSHOT/#tinkerpop-contributors|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.
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 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
  
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
Line 23: Line 28:
=== F. Current Status === == F. Current Status ==
Line 25: Line 30:
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 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 32:
=== G. Meritocracy === == G. Meritocracy ==
Line 29: Line 34:
Anyone is welcome to join TinkerPop as a contributor. If an individual provides beneficial pull requests, documentation updates, theoretical ideas, etc. then they are asked to join TinkerPop. Once inside TinkerPop, they are able to voice their opinions/thoughts on the direction of the project. Moreover, TinkerPop actively seeks vendors who leverage TinkerPop in their offering. Each vendor is allowed to place a representative on TinkerPop contributors who can speak on behalf of their organization as it relates to the requirements of their graph system. Every year or so, we list inactive members and request their permission to purge them from TinkerPop contributors mailing list. In this way, we try and keep the TinkerPop contributors list to the most active, participating members. 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.
Line 31: Line 36:
=== H. Community === We believe the values of the community align well with the ASF, and we are willing to adapt our practices when necessary.
Line 33: Line 38:
There are 25 TinkerPop contributors which, of those, 12 are representatives from various graph system vendors in the market today. The [[https://groups.google.com/forum/#!forum/gremlin-users|TinkerPop mailing list]] has 1500+ subscribers with a flow of approximately 10 emails a day. 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. == H. Community ==
Line 35: Line 40:
=== I. Core developers === 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 37: Line 42:
The primary "day in and day out" developers are [[http://markorodriguez.com|Marko A. Rodriguez]] and [[http://stephen.genoprime.com/|Stephen Mallette]]. Over the years, other individuals have come and gone from TinkerPop. Other significant long term contributors include Peter Neubauer, Joshua Shinavier, James Thornton, Matthias Bröcheler, Daniel Kuppitz, Bryn Cooke, and others. == I. Core developers ==
Line 39: Line 44:
=== J. Alignment === The initial committer list is small, and we hope to grow that into a larger, vibrant community at the Apache Software Foundation.
Line 41: Line 46:
TinkerPop is licensed Apache2. The OLAP reference implementation that distributes with TinkerPop is based on [[http://hadoop.apache.org|Hadoop]] and [[http://giraph.apache.org|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 Foundation to be a great home for TinkerPop. == J. Alignment ==
Line 43: Line 48:
=== K. Known Risks & Abandoned projects === TinkerPop is licensed Apache2. The OLAP reference implementation that distributes with TinkerPop is based on [[http://hadoop.apache.org|Hadoop]] and [[http://giraph.apache.org|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.
Line 45: Line 50:
TinkerPop is currently at TinkerPop 3.0.0.M6. By joining The Apache 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. == K. Known Risks & Abandoned projects ==
Line 47: Line 52:
=== L. Inexperience with Open Source === 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 49: Line 54:
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. == L. Inexperience with Open Source ==
Line 51: Line 56:
=== M. Homogeneous Developers === 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 53: Line 58:
The contributors to TinkerPop have varying levels of software engineering expertise and focus. The codebase is complex as it deals with numerous area of software engineering including: data standardization, programming language bindings, query language design, OLTP databases, OLAP processors, distributed computing, end-point services, extensibility via plugins, applied graph theory, etc. Over the years, we have gathered a pool of talent able to work at the requisite levels and as a whole, we have all grown as engineers. == M. Homogeneous Developers ==
Line 55: Line 60:
=== N. Reliance on Salaried Developers === The initial set of committers all hail from different employers.

== N. Reliance on Salaried Developers ==
Line 59: Line 66:
=== O. Relationships with Other Apache Projects === == O. Relationships with Other Apache Projects ==
Line 63: Line 70:
=== P. An Excessive Fascination with the Apache Brand === == P. An Excessive Fascination with the Apache Brand ==
Line 65: Line 72:
TinkerPop is interested in The Apache Foundation for the legal support and protection it can offer our developers, users, and vendors. 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 Foundation brand and believes that by joining The Apache 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 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 67: Line 74:
=== Q. Documentation === == Q. Documentation ==
Line 75: Line 82:
=== R. Initial Source === == R. Initial Source ==
Line 77: Line 84:
TinkerPop is currently hosted on GitHub: https://github.com/tinkerpop/tinkerpop3. TinkerPop is currently hosted on GitHub: https://github.com/tinkerpop/.
Line 79: Line 86:
=== S. Source & Intellectual Property Submission Plan === The following repositories would like to be migrated to ASF.
Line 81: Line 88:
There are no known claims to violations of intellectual property. TinkerPop is not a legal entity, but instead, a loose group of developers. TinkerPop, as a name, has been in effect for this project since 2009 when Marko A. Rodriguez, Joshua Shinavier, and Peter Neubauer started TinkerPop. They are okay to transfer any rights to the name to The Apache Software Foundation. || 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 ||
Line 83: Line 95:
=== T. External Dependencies === == S. Source & Intellectual Property Submission Plan ==
Line 85: Line 97:
TinkerPop relies on open source software that is "equivalent" or less stringent than the Apache2 license. 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
Line 87: Line 99:
=== U. Cryptography === 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 ==
Line 91: Line 109:
=== 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 97: Line 113:
We request the following mailing lists: TinkerPop requests the following mailing list:
Line 99: Line 115:
 1. dev@tinkerpop.incubator.apache.org
 2. commits@tinkerpop.incubator.apache.org
 3. private@tinkerpop.incubator.apache.org
|| 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 ||
Line 105: Line 122:
TinkerPop will use subversion for it’s website and requests:  TinkerPop will use subversion for it’s website and requests:
Line 107: Line 124:
 * https://svn.apache.org/repos/asf/incubator/tinkerpop   * https://svn.apache.org/repos/asf/incubator/tinkerpop
Line 111: Line 128:
TinkerPop wishes to have the following created:  TinkerPop wishes to have the following created:
Line 113: Line 130:
 * https://git-wip-us.apache.org/repos/asf/incubator-tinkerpop.git   * https://git-wip-us.apache.org/repos/asf/incubator-tinkerpop.git
Line 116: Line 133:
 
Line 119: Line 136:
TinkerPop uses GitHub's issue tracker for tracking issues: https://github.com/tinkerpop/tinkerpop3/issues. We wish to continue to use GitHub issue tracker, but if there is a strong push back, can move to JIRA. Please help us setup a JIRA instance for both issue tracking and code review (TINKERPOP).
Line 121: Line 138:
=== AA. Initial Committers ===

We would like to keep the voting rights to 3 individuals: Marko A. Rodriguez (Aurelius), Stephen Mallette (Nidomics), and James Thornton (Electric Speed, LLC).

=== BB. Affiliations ===
== AA. Initial Committers and Affiliations ==
Line 128: Line 141:
|| Peter Neubauer (2009) || Mapillary ||
|| Joshua Shinavier (2009) || Rensselaer Polytechnic Institute ||
|| Ketrina Yim (2009) || Self-employed ||
Line 132: Line 142:
|| Pierre De Wilde (2011) || Retired ||
|| Derrick Wiebe (2011) || XNLogic ||
|| Luca Garulli (2012) || Orient Technologies ||
|| Matthias Bröcheler (2012) || Aurelius ||
|| Bryn Cooke (2013) || Self-employed ||
|| James Thornton (2013) || Electric Speed, LLC ||
|| Sridhar Ramachandran (2013) || LambdaZen ||
|| Nicholas Quinn (2013) || Objectivity ||
|| Xavier Sanchez (2013) || Sparsity Technologies ||
|| Daniel Kuppitz (2014) || Self-employed ||
|| Michael Pollmeier (2014) || Unknown ||
|| Jean-Baptiste Musso (2014) || Self-employed ||
|| Bob Briody (2014) || Aurelius ||
|| Mike Personick (2014) || Bigdata ||
|| Michael Hackstein (2014) || ArangoDB ||
|| Michael McMahon (2014) || FoundationDB ||
|| Ryan Webb (2014) || Johns Hopkins Applied Physics Laboratory ||
|| Avery Ching (2014) || Facebook ||
|| Kendall Clark (2014) || Clark & Parsia ||
|| Michael Grove (2014) || Clark & Parsia ||
|| James Thornton (2013) || Electric Speed ||
Line 153: Line 144:
=== CC. Sponsors ===

We would like to have the following Apache champion and mentors:
== BB. Sponsors ==
Line 158: Line 147:
 * Mentor: XXX, YYY, ZZZ, ...  * Mentors: Rich Bowen, Matt Franklin, Daniel Gruno, David Nalley, Hadrian Zbarcea
 * 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

  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 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/.

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:

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)