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 B74DA10060 for ; Sat, 10 Jan 2015 06:09:33 +0000 (UTC) Received: (qmail 15852 invoked by uid 500); 10 Jan 2015 06:09:34 -0000 Delivered-To: apmail-incubator-general-archive@incubator.apache.org Received: (qmail 15679 invoked by uid 500); 10 Jan 2015 06:09:34 -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 15668 invoked by uid 99); 10 Jan 2015 06:09:33 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 10 Jan 2015 06:09:33 +0000 X-ASF-Spam-Status: No, hits=0.3 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_SOFTFAIL X-Spam-Check-By: apache.org Received-SPF: softfail (nike.apache.org: transitioning domain of list@toolazydogs.com does not designate 209.85.160.181 as permitted sender) Received: from [209.85.160.181] (HELO mail-yk0-f181.google.com) (209.85.160.181) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 10 Jan 2015 06:09:08 +0000 Received: by mail-yk0-f181.google.com with SMTP id 142so5685194ykq.12 for ; Fri, 09 Jan 2015 22:07:36 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:content-transfer-encoding:message-id:references:to; bh=ncbj7Nx24d93YR0xMIjcjJzef0RFbvqfJU34sHbPa1M=; b=JhV2GwnJXLQMTR4Nu5iE+YENMv9QoNX0C1lh0VYkcW459ewXgJdJqhntI104422OZM rEGsgSpKcvJAUneI7DCOKarwn/I6+zLCIEZzYvpQJOiNQ4YQOyczHv+P8lreqX8IbdSo wJxOZWGX/wn2hXYPRW3CLaBuVaH1UmveMbdYoaaHks0YamWgc9qctHjgE3HTi7m0oItO zcuDwB74wqUim3JCmYnalBt9BakpNfAjs7L1l4aHvSMBwqf8U2k1VmCmCIZ1lm/r+jmT myNqSOfl7ZjRjXYPRZGo4XmFx5bs6ABnPBzmezpk5MdKWe/lgkZR03cSt/UmBLes04BL iTaw== X-Gm-Message-State: ALoCoQl9enV2nB/N6ZNll/uBFS7RElV0MjrNeIVZps/E+6q+ggKWrG0cZO4I2u/CamMYPQcTemfP X-Received: by 10.236.19.36 with SMTP id m24mr14283983yhm.111.1420870056482; Fri, 09 Jan 2015 22:07:36 -0800 (PST) Received: from acabrera-mn.linkedin.biz (dagmar1.corp.linkedin.com. [69.28.149.129]) by mx.google.com with ESMTPSA id r5sm6115872yhr.23.2015.01.09.22.07.34 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 09 Jan 2015 22:07:35 -0800 (PST) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 8.1 \(1993\)) Subject: Re: [VOTE][Proposal] TinkerPop: A Graph Computing Framework [RE-SUBMISSION] From: "Alan D. Cabrera" In-Reply-To: <54B0089E.2050106@gmail.com> Date: Fri, 9 Jan 2015 22:07:34 -0800 Content-Transfer-Encoding: quoted-printable Message-Id: <535BEAE3-7075-47C7-82D2-84C461453351@toolazydogs.com> References: <93C0971F-888A-425D-A7B8-B1139412BBBC@gmail.com> <54B0089E.2050106@gmail.com> To: general@incubator.apache.org X-Mailer: Apple Mail (2.1993) X-Virus-Checked: Checked by ClamAV on apache.org +1 binding Regards, Alan > On Jan 9, 2015, at 8:58 AM, Hadrian Zbarcea = wrote: >=20 > +1 >=20 > =46rom the conversation with Marko, he intended to submit this as a = formal vote, but didn't use the regular voting template. >=20 > Voting will remain open until at least January 15, 2015 18:00 ET. >=20 > Cheers, > Hadrian >=20 >=20 > On 01/09/2015 11:35 AM, Marko Rodriguez wrote: >> Hello everyone, >>=20 >> 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) >>=20 >> We feel it is now in prime shape from submission to vote. Enjoy!. >> (URL to wiki version: = https://wiki.apache.org/incubator/TinkerPopProposal) >>=20 >>=20 >>=20 >> A. Abstract >>=20 >> 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. >>=20 >>=20 >> B. Proposal >>=20 >> TinkerPop was formed in = 2009 and is currently in the milestone series of 3.0.0. =46rom 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. >>=20 >>=20 >> C. Background >>=20 >> 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. >>=20 >>=20 >> D. Rationale >>=20 >> 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. >>=20 >>=20 >> E. Initial Goals >>=20 >> The goal of this proposal is to migrate TinkerPop = to The Apache Software = Foundation to >>=20 >> 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 >>=20 >>=20 >> F. Current Status >>=20 >> 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. >>=20 >>=20 >> G. Meritocracy >>=20 >> 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. >>=20 >> We believe the values of the community align well with the ASF, and = we are willing to adapt our practices when necessary. >>=20 >>=20 >> H. Community >>=20 >> 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. >>=20 >>=20 >> I. Core developers >>=20 >> The initial committer list is small, and we hope to grow that into a = larger, vibrant community at the Apache Software Foundation. >>=20 >>=20 >> J. Alignment >>=20 >> 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 . >>=20 >>=20 >> K. Known Risks & Abandoned projects >>=20 >> 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. >>=20 >>=20 >> L. Inexperience with Open Source >>=20 >> 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. >>=20 >>=20 >> M. Homogeneous Developers >>=20 >> The initial set of committers all hail from different employers. >>=20 >>=20 >> N. Reliance on Salaried Developers >>=20 >> 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. >>=20 >>=20 >> O. Relationships with Other Apache Projects >>=20 >> TinkerPop currently = leverages Hadoop, Giraph, and in the near future, will integrate with = Spark . Internally, the project leverages = Maven3, Apache Configuration, and Apache Commons. >>=20 >>=20 >> P. An Excessive Fascination with the Apache Brand >>=20 >> 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. >>=20 >>=20 >> Q. Documentation >>=20 >> TinkerPop takes pride = in its documentation: >>=20 >> AsciiDoc >> =09 >> http://www.tinkerpop.com/docs/3.0.0-SNAPSHOT/ >> JavaDoc (core) >> =09 >> http://www.tinkerpop.com/javadocs/3.0.0-SNAPSHOT/core/ >> JavaDoc (full) >> =09 >> http://www.tinkerpop.com/javadocs/3.0.0-SNAPSHOT/full/ >>=20 >>=20 >> R. Initial Source >>=20 >> TinkerPop is currently = hosted on GitHub : = https://github.com/tinkerpop/. >>=20 >> The following repositories would like to be migrated to ASF. >>=20 >> TinkerPop3 >> =09 >> https://github.com/tinkerpop/tinkerpop3 >> Blueprints (TinkerPop2 = ) >> =09 >> https://github.com/tinkerpop/blueprints >> Pipes (TinkerPop2 ) >> =09 >> https://github.com/tinkerpop/pipes >> Frames (TinkerPop2 >> =09 >> https://github.com/tinkerpop/frames >> Gremlin (TinkerPop2 ) >> =09 >> https://github.com/tinkerpop/gremlin >> Rexster (TinkerPop2 ) >> =09 >> https://github.com/tinkerpop/rexster >>=20 >>=20 >> S. Source & Intellectual Property Submission Plan >>=20 >> 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 >>=20 >> 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. >>=20 >>=20 >> T. External Dependencies >>=20 >> 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. >>=20 >>=20 >> U. Cryptography >>=20 >> None. >>=20 >>=20 >> V. Required Resources >>=20 >>=20 >> W. Mailing Lists >>=20 >> TinkerPop requests the = following mailing list: >>=20 >> User Mailing List >> =09 >> users@tinkerpop.incubator.apache.org = >> Developer Mailing List >> =09 >> dev@tinkerpop.incubator.apache.org = >> Private Mailing List >> =09 >> private@tinkerpop.incubator.apache.org = >> Commits Mailing List >> =09 >> commits@tinkerpop.incubator.apache.org = >>=20 >>=20 >> X. Subversion Directory >>=20 >> TinkerPop will use = subversion for it=E2=80=99s website and requests: >>=20 >> * >> https://svn.apache.org/repos/asf/incubator/tinkerpop >>=20 >>=20 >> Y. Git Repository >>=20 >> TinkerPop wishes to = have the following created: >>=20 >> * >> https://git-wip-us.apache.org/repos/asf/incubator-tinkerpop.git >>=20 >> And to have all of these mirrored to Github with integration taken = care of. >>=20 >>=20 >> Z. Issue Tracking >>=20 >> Please help us setup a JIRA instance for both issue tracking and code = review (TINKERPOP). >>=20 >>=20 >> AA. Initial Committers and Affiliations >>=20 >> Marko A. Rodriguez (2009) >> =09 >> Aurelius >> Stephen Mallette (2011) >> =09 >> Nidomics >> James Thornton (2013) >> =09 >> Electric Speed >>=20 >>=20 >> BB. Sponsors >>=20 >> * Champion: David Nalley >> * Mentors: Rich Bowen, Matt Franklin, Daniel Gruno, David Nalley, >> Hadrian Zbarcea >> * Sponsoring Entity: We request the Incubator to sponsor this = project. >>=20 >>=20 >=20 >=20 > --------------------------------------------------------------------- > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org > For additional commands, e-mail: general-help@incubator.apache.org >=20 --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org For additional commands, e-mail: general-help@incubator.apache.org