As a followup to my post on December 8th, I wanted to share that we had a kickoff meeting this morning with the Linux Foundation to review the charter for our community graph project.
We are forking the Titan code base. The name "Titan" cannot be used, so a new name has been chosen. We will continue and coordinate the efforts already underway for the past year by organizations around the world. We will post a plan with more specific details of features and future development plans, including participation guidelines, in January. Happy Holidays! -- Jason On Friday, December 16, 2016 at 12:39:35 PM UTC-5, Austin Sharp wrote: > > This is my question as well. Is this new project starting over from > scratch, or will it be something evolutionary based on the Titan codebase? > > On Tuesday, December 13, 2016 at 6:14:10 AM UTC-8, Tom Ellis wrote: >> >> Does this therefore spell the death of Titan? There will be no fork? >> >> On Thursday, 8 December 2016 19:24:33 UTC, Jason Plurad wrote: >>> >>> Many folks in the Titan community have continued to reach out wondering >>> how to continue development on an Apache-licensed, open source, and >>> scalable graph database with pluggable backends. I want to let you know >>> that the Linux Foundation is establishing an open community graph project, >>> including developers from various backend providers, to fulfill that need. >>> The logistics for this new home are being finalized, and it will carry on >>> the open source heritage of Titan with open governance. The Apache license >>> will be maintained, and the community will operate along the same >>> principles of an Apache project. Once naming the new project is complete, >>> all are welcome to join, contribute, and drive forward this scalable graph >>> solution. >>> >>> -- Jason >>> >>
