Understood. For the record, as I had said previously, my intention is to make sure people know exactly what happened on TinkerPop both in terms of what the Apache Board did and what the Apache TinkerPop PMC didn’t do.
There are young, talented developers that are coming into themselves with bright ideas. If their work could be stripped from them for something as inane as posting a Photoshop picture of their pet chicken in WW2 regalia to a social media site (and under no Apache capacity), they need to know this. More generally, regardless of how “right” or “wrong” you believe some behavior is, realize it is possible that one day, how you conduct yourself may be considered “wrong” by the powers that be and Apache is structured in such a way that you can be separated from your work as they have inserted a “must follow social norms” clause into Apache’s statute (this came after me signing my codebase over to Apache). As a side, around 10 Apache members from various projects, including an Apache Board member, resigned from Apache for the weakness of their argument for why I should be removed from Apache TinkerPop (to which I still have not received a response to my questions regarding their decision). Moreover, such “moral elitism” is being used where it suits individuals and institutions best. Prior to starting TinkerPop3, Stephen and I were courted by IBM’s Kelvin Lawrence (now on the TinkerPop PMC). IBM wanted TinkerPop in an OSS foundation such as Apache or Eclipse. Stephen and I thought this was a good idea and went through the process. IBM’s intentions were not pure. When at the point of getting into Incubation, Sam Ruby (IBM and Apache Board member) realized my character to be one that wasn’t going to be pushed around, they wanted me off the project — in essence, IBM wanted my codebase and foer me to disappear. So much so that Sam Ruby threatened me with physical violence and the Apache Board did nothing but stood there and watch. If you know me, you know there is no amount of space nor time that can distance you from a grievance of mine. And so, I stood my ground as I continue to do so to this day. Imagine if I didn’t have the strength of character to do so. TinkerPop would be a nothing project. The beauty that is TinkerPop3 comes from the muse that drives me and the precision and steadfastness that Stephen wields. That core is the foundation from which everything else attached and has come to be. To conclude, it would be a disservice to young bright developers to withhold information about the organization and people they may be handing their life’s work over to. Apache is not what it says it is. This organization is corrupt. Over this last year, I’ve spent my time as a consultant explaining to people what OSS has become. In doing so, as I tell my story other Apache members past and present have reached out to me to tell similar stories (and some even more outrageous than mine) of what the Apache Board has done in the past and is currently doing now. This information is all being collated so the next generation can make an informed decision regarding the direction they take their software (their creative energy). Marko. > On Apr 6, 2022, at 4:52 PM, Stephen Mallette <[email protected]> wrote: > > I imagine Florian omitted my leaving the PMC in this draft as he was > waiting for it to become public knowledge. I expected to send an email > about it after the release at which point the report could have been > amended. > > > > On Wed, Apr 6, 2022 at 12:05 PM Marko Rodriguez <[email protected] > <mailto:[email protected]>> > wrote: > >> Hello dev@, >> >> Stephen Mallette has stepped down from both the PMC Chair and now the PMC. >> I believe this should be included in the report given the significance of >> the event. Furthermore, it would be good to address why the two primary >> developers of Apache TinkerPop (10+ years) are still active members in the >> project, but are no longer on the PMC. Noting this is important for the >> historical record of the project and more generally, so others who may look >> to submit their work to Apache can have full knowledge of what ~2 years ago >> would be considered unthinkable, but now has become manifest: an >> institution becoming so degenerate that it would separate a man from his >> work against the will of his colleagues. >> >> Thank you, >> Marko. >> >> http://markorodriguez.com <http://markorodriguez.com/> >> <http://markorodriguez.com/ <http://markorodriguez.com/>> >> >> >>> On Apr 6, 2022, at 3:53 AM, Florian Hockmann <[email protected]> >> wrote: >>> >>> Here is the attached draft of our board report for this quarter - please >> let >>> me know if there is anything to add or edit. >>> >>> >>> >>> >> -------------------------------------------------------------------------- >>> >>> >>> >>> ## Description: >>> >>> Apache TinkerPop is a graph computing framework for both graph databases >>> >>> (OLTP) and graph analytic systems (OLAP). >>> >>> >>> >>> ## Activity: >>> >>> TinkerPop is currently in the process of releasing 3.5.3 and 3.6.0. >> Version >>> 3.5.3 is mostly a maintenance release. 3.6.0 represents a major release >> with >>> breaking changes and a variety of new features, including support for >>> regular expressions directly in Gremlin and better support for commonly >> used >>> upsert-like functionality. >>> >>> The default logging implementation in the distributions of Gremlin Server >>> and Gremlin Console will also be changed in 3.6.0 from log4j 1.2.x to >>> logback due to the vulnerability CVE-2019-17571 [1]. >>> >>> >>> >>> These releases will be accompanied by the first pre-release versions of >>> gremlin-go, making Gremlin natively available in Go which has been the >>> mostly requested programming language for which we did not offer a >> Gremlin >>> Language Variant (GLV)[2] yet by users over the last years. >>> >>> Notable about this new GLV is also that it has not been developed by a >>> single contributor but by a group of contributors who collaborated on >> this, >>> an effort that was mostly led by committer Lyndon Bauto. >>> >>> >>> >>> We have welcomed Mike Personick as a new committer who has already >>> contributed great improvements around core aspects of Gremlin. >>> >>> >>> >>> ## Issues: >>> >>> There are no issues requiring board attention at this time. >>> >>> >>> >>> ## Releases: >>> >>> - 3.4.13 (January 10, 2022) >>> >>> - 3.5.2 (January 10, 2022) >>> >>> >>> >>> ## PMC/Committer: >>> >>> - Last PMC addition was Kelvin Lawrence/Josh Shinavier - June 2021 >>> >>> - Last committer addition was Mike Personick - March 2022 >>> >>> >>> >>> ## Links >>> >>> [1] https://nvd.nist.gov/vuln/detail/CVE-2019-17571 >>> >>> [2] >>> >> https://tinkerpop.apache.org/docs/3.5.2/reference/#gremlin-drivers-variants
