Hello,
The reason for silence from me (in particular) was to demonstrate a flaw in
Dave's argument. He was trying to reprimand an individual (or two) but he
inadvertently jumped the hierarchy and talked in terms of TinkerPop as a whole.
Thus, there was a lack of precision to his presentation which was further
enforced by the fact the individual(s) he was trying to get at did not reply.
Why did they not reply? Because they didn't need to as it wasn't addressed to
them, but the community. As such, the best defense is to have the community
reply as their responses were as one would expect:
* "What are you talking bout?"
* "Can you please explain yourself in more detail?"
* … and the like.
This seemed to have left Dave in a pickle. Where does he go from there? What
saved the situation, I believe, was Mr. Gruno with his remarks to particulars
and what I think has ultimately remedied the situation -- Apache HipChat! Once
we had a room set up where everyone could talk, ask questions, etc., then it
all didn't seem as dire as originally proposed. Communication is key and fast
back-and-forths with Gruno helped illuminate the best steps forward.
* "Oh, you mean just bring up juicy JIRA ideas on the mailing list with
[DISCUSS]? Sure."
* "Oh, set up a merge to master process. Okay."
* "Yes, makes sense... thank you for your help."
Next, to your recommendation about pulling people into the PMC that have simply
replied to Dave's email (though not belittling with "simply" as their arguments
were brilliant and well written). My view on the matter is as follows. Here is
what I (me personally) think makes a project lead (in rank order):
1. Consistent dedication to the project -- both in daily time and
effort over the years (where the latter will have to rely on prediction).
2. A deep understanding of the graph community -- the providers, the
languages, the players.
3. A deep understanding of the graph technology -- the theory, the
algorithms, the future.
4. Consistently promoting TinkerPop through collaborations, academic
writing, blog posts, provider engagement, conference presentations, books, etc.
5. An ability to attract talent and grow TinkerPop, not with "people,"
but with "artisans" (individuals who love the craft and dedicate themselves to
it wholeheartedly).
6. The ability to communicate effectively and work situations in
TinkerPop's favor.
Does an individual have to have all 6? No, but writing "an email" is only one
of those --- #6. The PMC is definitely conscious of the requirement to
diversify the PMC for graduation. Though, one must not act hasty in such
matters. If graduation is the goal, then TinkerPop has failed. The goal (for me
personally) is a successful open source project that leads the graph space into
the future with or without Apache. If we rush to graduate by being artificial
in our behaviors and insincere in our approach that will yield the destruction
of our prolificness and the ultimate joy we get from the love given to us by
The TinkerPop.
Thanks,
Marko.
http://markorodriguez.com
On Oct 10, 2015, at 5:30 AM, Rich Bowen <[email protected]> wrote:
> There's been some good discussion here. I'd like to make an observation -
> most of the best "let's fix this" discussion has come from people who are not
> on the PMC, while the PMC members have been largely silent.
>
> This seems important to me. I would suggest that it indicates that there are
> a number of people who should be on the PMC who are not yet.
>
> On 10/02/2015 09:08 AM, David Nalley 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
>>
>
>
> --
> Rich Bowen - [email protected] - @rbowen
> http://apachecon.com/ - @apachecon
