I know there was a very long discussion around this posted a while back but
maybe it would be good to break that down here for those of us that haven't
had the time to go through the entire thing (e.g. why you reached that
conclusion).

This would certainly make the dialogue easier.

Best,
Dylan.

On Fri, Oct 2, 2015 at 3:15 PM, Rich Bowen <[email protected]> wrote:

> On Oct 2, 2015 3:08 PM, "David Nalley" <[email protected]> wrote:
> >
> > Hi folks,
> >
> > A number of the mentors (Daniel, Rich, and I), along with several
> > other IPMC members were in Budapest for ApacheCon; while there we
> > discussed the state of
> > Tinkerpop, it's incubation, and a number of other topics. I wanted to
> > bring one of those topics here to foster a larger discussion, and
> > perhaps for the community to decide on a way forward.
> >
> > After a lot of deliberation and thinking both together and
> > individually, I think we reached an inflection point for ourselves.
> > While I don't want to speak for the others,
> > I will state my opinion. I think it's become apparent that Tinkerpop
> > as a project and a community is not a fit for the Apache Software
> > Foundation, and I see little potential for that to change.
> > This is not a statement that Tinkerpop is bad or evil. The ASF isn't
> > the only place projects live to be successful, nor is the Apache Way
> > the only method that successful projects adopt.
> >
> > That said, the ASF cares deeply about it's existing culture and that
> > the communities that are here adopt "the Apache Way"; that's actually
> > a core tenant to accomplish during incubation. That leads
> > me (speaking only for myself) to believe that you would thrive better
> > elsewhere, rather than chafing and being unhappy, and eventually
> > failing to graduate.
> >
> > --David
>
> David expresses this as just his own opinion, but we did discuss and draft
> this together. I want to reiterate that we think you have an amazing
> project and a great community, but that the fit doesn't seem to be there.
>

Reply via email to