A botched technology squeeze play: The story of Juicero

Not that long ago, Bloomberg reported on Juicero and the surprising revelation that the $400 juicing machine was, strictly speaking, unnecessary and produced results not much better than hand-squeezing the juice packs. From the article:

Juicero declined to comment. A person close to the company said Juicero is aware the packs can be squeezed by hand but that most people would prefer to use the machine because the process is more consistent and less messy. The device also reads a QR code printed on the back of each produce pack and checks the source against an online database to ensure the contents haven’t expired or been recalled, the person said. The expiration date is also printed on the pack.

So basically, the machine exists for sometimes giving you juice, and sometimes saying “Sorry, Dave, I’m afraid I can’t do that”. Given the device costs $400, and the packs for it are priced with a similar needless markup (not to be confused with that needless markup), I really don’t see the advantage.

For some strange reason, I am reminded of the creativity that slot machine manufacturers used to get around laws, by disguising the slot machine as a vending machine for mints. Surprisingly, back in the era during which this was needed, it worked, though from what I remember reading the judges did wonder why so much machinery was needed for the simple task of vending mints. Indeed, I don’t see the issue with scanning QR codes by hand (with my phone, or perhaps with my laptop’s webcam), and looking up the result for a recall (the expiration dates are printed in human-readable form). Or, for that matter, I could pick my own produce and make juice using an old-fashioned juicer.

But then Juicero wouldn’t make any money, and we can’t have that, now can we?

I like technology. But there is a difference between using technology to solve problems, and making a technological solution in search of a problem. The Juicero machine takes its place right next to the failed DIVX discs and players as an example of the latter.

Cookie-cutter failure: thoughts on WordCamp The Netherlands

The Netherlands WordPress team recently announced that WordCamp Central would not approve a WordCamp The Netherlands event for 2017. The blog post is in Dutch of course, but the emails exchanged with WordCamp Central are in English and tell the story quite well.

Let’s keep a few things in mind: The Netherlands is a rather small country. Small enough that the US states of Vermont and Connecticut put together would have a comparable land area, or looking at it another way, The Netherlands has around one-sixteenth the land area of Texas.

The culture over there is a lot different as well. Quoting one email from The Netherlands WordPress team:

The Netherlands has its own culture, which is unaffected by decisions made in other communities.
[…]
The second, and more important reason to keep WordCamp The Netherlands is because it is for everyone in The Netherlands. We as a people are proud to be Dutch. Being Dutch is something that unites. Being Dutch overrules all the issues there are between people from different cities and regions.

For example, if we drop WCNL in favor of city-based WordCamps, the people from Amsterdam wouldn’t visit a WordCamp in Rotterdam, or any WordCamp east of Utrecht. The people of Rotterdam wouldn’t visit a WordCamp in Amsterdam, or any WordCamp east of Utrecht. The people from Groningen wouldn’t visit a WordCamp in Eindhoven, and vice versa. Of course, you could argue that WCNL could become WordCamp Utrecht. But that has a few issues too.

I’m keeping the quote as short as I can to get the point across, though it does mention fragmentation and the fact that none of the current WordCamp Netherlands organizers are from the larger cities in The Netherlands, and would thus be disqualified from organizing. (As it stands right now, the first city-based WordCamp in The Netherlands would be in Utrecht, and the status is listed as “Application vetted, Needs Orientation/Interview” as of about a week ago. Unfortunately I did not follow the WordCamp status page closely enough to see when the original application for WordCamp Utrecht was submitted, but I can’t imagine it being all that long ago.)

The response from WordPress Community Support contains quite a few points of note. In order:

We have worked hard in the past eight years to move the WordCamp program away from country-named events and toward city-named events for a number of reasons that focus on the health and longevity of the community as a whole.

While I can see how the city-named model would work in many countries, it is obvious to me that The Netherlands is something different. It’s just a guess, but I suspect that none of the “hard work” mentioned was put into looking at the culture of The Netherlands and why it still had a country-named WordCamp after all this time. Of course, if it was, that’s even more damning, as this change is being forced on the WordPress community of The Netherlands despite knowlege of that cultural difference.

In the case of WordCamp The Netherlands, the discussion around moving to a city-named event has been ongoing for five years. We requested the change (via phone calls or in person, with volunteers or with paid staff) and received verbal agreements multiple times.

There’s a somewhat humorous saying (original author unknown): verbal agreements aren’t worth the paper they are written on. Apparently whoever entered into this verbal agreement either lacked the authority to do so or did so without advising the rest of the community team in The Netherlands. Or, perhaps “verbal agreement” is a misrepresentation of what actually took place during the conversation. If the call starts off “we aren’t approving WordCamp The Netherlands in 2017, you guys need to start organizing city-based events” and the gist of the response is “we still want our WordCamp”, that’s not an agreement, that’s coercion. I’m not saying that’s what happened, but it’s one possible situation.

The Netherlands is not the only community we’ve asked to make this change (other examples include the UK, Switzerland, Denmark, and Israel to name a few). We realize it is certainly a hard thing to ask. But we also have seen benefits for the WordPress community as a whole in areas that have taken this chance.

Do any of these other countries have the same culture as The Netherlands, where they all unite as Dutch at events like previous the WordCamps (held as WordCamp The Netherlands versus WordCamp The Hague, WordCamp Utrecht, etc)? I would be willing to bet the answer is no. How willing were smaller countries like Denmark willing to make the change? I would guess they made it only reluctantly so they could continue to have events.

What does this mean for WordCamp The Netherlands? We previously recommended they rename the event WordCamp Utrecht and continue to do the outstanding work they already do. WordCamps in other countries have moved on to new names and have been successful, and we’re hopeful that the same will happen here.

I read two things in this: “we’re hoping the same ‘cookie cutter’ solution works for The Netherlands despite there being clear cultural differences” and “what we really got our undies in a wad over was the country name as the WordCamp name”. The former is at best rather short-sighted. I’m not even sure how to best characterize what it could mean at worst. The latter is just plain silly. Clearly the Dutch are happier continuing to call it WordCamp The Netherlands. I fail to see the harm in that.

Jumping back to the beginning:

We’d like to start by saying we are truly thankful for the hard work WordCamp organizers in the Netherlands have put into their events over the years. They have invested countless hours working on their events and the community, and we value their dedication and contributions.

Actions speak louder than words. To me, the non-approval of WordCamp The Netherlands 2017 sends quite a different message than the words written in this post. I believe if those in charge of approving WordCamps are truly thankful for the hard work and dedication of the community leadership in The Netherlands, the right move is to maintain the status quo and approve WordCamp The Netherlands 2017, or allow the current WordCamp Utrecht to change its name to WordCamp The Netherlands at the organizer’s option.

[Update 2021-07-25: correct punctuation error]

The witch-hunt against Larry Garfield, part 2: “I do not know which one is more damning.”

This entry is part 2 of 3 in the series The witch-hunt against Larry Garfield

Sorry for the delay in getting this up. I’m posting this sometime on either a Saturday or a Sunday, something that I almost never do for several reasons. But this can’t wait for the next nominal business day, which is Monday 2017 April 17 (ignoring that many businesses will be closed because it’s the Monday after Easter Sunday).

I had posted this immediately after Larry’s third post on the topic. I had hoped more would develop in the extra days I wound up giving this post, but little has. That said, it’s a relief that people are still talking about this. I got a link from Misha Verbitsky’s blog on a LiveJournal-based platform earlier this week, which I appreciate (the entry is in Russian, and I might add, doesn’t appear to be handled well by Google Translate without reformatting). Misha is one of many that have denounced the actions of Mr. Buytaert and Ms. Sanicki regarding this situation.

Anyway, the basic theme of Larry’s third post on the topic, with the title “Regarding the continued mystery” and with the all-too-appropriate slug “tmi-part-3”, is to list two alternative possibilities in response to several things that have been said or done, with the statement “I do not know which one is more damning.” after each set.

I’m going to quote at least some of those here with my own thoughts.

The [joint post from Mr. Buytaert and Ms. Sanicki on the Drupal Association blog] implies that the “information” considered included “some of Larry’s online interactions, both on and off Drupal.org”. In the information provided by the Community Working Group (CWG) to both me and the Board, however, there is no Drupal.org interaction listed at all. The only off-Drupal.org “interaction” mentioned that was not part of the CWG’s “mediation” process was from the original individual who reported my private life to the CWG, who now, in hindsight, was upset that I had brought my autistic housemate to Midcamp.

It’s also worth noting that on 3 February 2017 I asked the CWG for copies of what excerpts of my private posts they had as of then. I asked them again on 25 February, after my call with Dries. I was not provided with any such information until 27 February, a mere two hours before I received Megan’s email dismissing me from the track chair position and DrupalCon engagements. Even that information was incomplete, as it included only a screenshot and two non-Drupal links. The packet I received for the Board meeting (after action had already been taken against me) included the out-of-context excerpts Klaus had shared with me, an additional excerpt that Klaus had dug up after speaking with me (which I’d not seen before), and anonymized copies of emails to the CWG from three individuals (one of them being Klaus) which included the very first mention of my autistic housemate. At this point there still were no excerpts from anything from Drupal.org.

That leaves two possibilities:

  1. The CWG and/or the Board and/or Dries had/has damning evidence of actions I’ve taken in violation of the CoC, actively withheld that information from me over the course of several months, and issued a statement stating clearly that I had not violated the Code of Conduct, but is still committed to withholding the information as they won’t even tell me what supposed evidence they have or are accusing me of.
  2. Megan and Dries are making misleading and inaccurate statements now (which I list and go into below) to cover up the lack of justification for their actions.

I do not know which one is more damning.

Of the two, I would consider withholding evidence from Larry to be slightly more damning. But either possibility means that Drupal’s governance is pretty broken: either the leaders (Ms. Sanicki and Mr. Buytaert) are corrupt and dishonest (in the second case), or the CWG and Board had it in for Larry since the beginning (in the first case).

Next up:

Second, the post indicated that Dries decided to remove me because “Larry had indicated on several occasions that he was drawing down his involvement in the Drupal project, and that context helped inform Dries’ decision.”

It is true that I mentioned to the CWG, and to Dries, that it was ironic all of this was blowing up now as I was likely going to scale back my Drupal core involvement before too long anyway (something many people have done many times). However, I did not say I was going to leave Drupal entirely any time soon; I indicated that it might happen long-term, or not. I never said or implied that there was any imminent departure planned on my part. If that were my intent, why would I have submitted sessions for DrupalCon at the beginning of February, 3 months before the conference? That wouldn’t make any sense at all. Drupal is still a key part of my professional career, as is presenting at conferences, Drupal or otherwise.

That someone gives informal fair warning that they intend to “step down considerately” (as the Code of Conduct specifies one should do) from some positions in no way implies that it is appropriate to force them out of those or others, nor does it rise to the level of a complete and total removal from the project in all aspects.

Additionally, when Dries called me on 24 February he had already made up his mind to ask me to resign. That means he could not have known I was planning to scale back (but not leave) before that unless the CWG specifically told him. That means either:

  1. The CWG told Dries of my likely scaling back when they talked to him, despite CWG discussions supposedly being confidential, and Dries then not mentioning that to me until I told him that I had been planning to scale back late in the conversation on 24 February.
  2. Mentioning that in the post is purely a post-hoc justification for an action taken that did not have anything to do with it.

I do not know which one is more damning.

To me, clearly the first of the two is much more damning, as it means the CWG can’t be trusted to keep confidential conversations confidential. Obivously if Larry wanted to tell Mr. Buytaert that he was scaling back his involvement, he would have done so himself. To mention that there was a possibility in a confidential conversation, that gets twisted around when repeated to “oh, Larry’s going to be leaving the project soon anyway”, is a huge breach of trust.

Given what I’ve seen, I’d expect Drupal’s leadership to “cover its asses” with such justifications. That’s still very damning, don’t get me wrong, but doesn’t rise to the level of violating confidentiality.

Neither of the two possiblities Larry mentions in this stanza of the post should happen in a healthy free software project’s governance.

And then, the process by which Larry’s removal from his track chair and speaking position was decided:

Third, the post states that there was “a careful, and deliberate process that has been going on since October 2016.” Let’s consider the timeline implications of that.

  • October 2016: First report to the CWG, in which they find no Code of Conduct violation by me. They do not inform me of this fact.
  • 16 November 2016: First time the CWG contacts me about there being any reports, and tell me there is no CoC violation.
  • 16 January 2017: Klaus and I have a Google Hangout in which he threatens to blackmail me. I report said blackmail to the CWG the same day.
  • 3 February 2017: I have a “mediation” interview with a member of the CWG. Aside from that member sending me notes to validate, I receive no further communication from the CWG.
  • 24 February 2017: Dries calls me and tells me to resign. I have one brief call with a member of the CWG later the same day.
  • 27 February 2017: Megan emails me to tell me I’m out from DrupalCon.

At no point in this process was there any indication that I was “under investigation”. Aside from the single interview with the CWG there was no request for information from me at all. If the Board was even aware of the matter prior to my referring it to them, I did not know of it. However, when Dries spoke to me on the 24th he said quite clearly that he had not been part of any CWG conversations. That leaves two possible conclusions:

  1. The CWG, Dries, Megan, and the Board were having continual meetings to plan to kick me out of Drupal and actively kept it secret from both me and the DrupalCon track team (who, presumably, would have objected to me having a session picked in the first place if I were already in the process of being removed).
  2. The process was not “careful and deliberate”, but they must now claim that it was in order to protect the current structure and their ultimate decision on my fate.

I do not know which one is more damning.

This is a tough one, but a secret conspiracy to kick Larry out of a project that he has been a loyal contributor to strikes me as at least a bit more damning than simple lying for the sake of ass-covering. Of course, both are very damning for Drupal’s project governance and do not reflect well on those in charge at all.

Three months between the first CWG complaint and Larry being effectively fired from at least his positions at DrupalCon, if not within the entire Drupal project, with no notification to Larry that he’s under investigation, does not strike me as “careful and deliberate”. The half-assed “mediation” between Larry and Mr. Purer also comes across as just another form of CWG ass-covering, now that I think about it. While the amount of care and deliberation can be a very subjective matter, I feel I’m being fair when I call bullshit on the “careful and deliberate” bit.

Moving on, Larry then addresses the question on everyone’s mind: why was he removed from his roles, anyway? (A question, I might add, that has not been satisfactorily addressed by anyone in charge of the Drupal project, including the DA and CWG.)

This seems to be the million dollar question for many (myself included). The post from Megan and Dries implies it’s because of actions I took, or reports they have about me… but they can’t talk about what the actions were, or what kind of allegation they are, or when it happened, or why it was evidently never given to the CWG to resolve, or (if it is as bad as they make it out to be) why it was never given to law enforcement to have me charged with a crime. But don’t worry, just trust that they have this evidence, which they can never speak of. That this evidence totally justifies the decision they’ve already made. A decision which they felt they needed to justify with my supposed withdrawal from the project, despite claiming that regardless of anything else, this secret evidence would, alone, justify my removal.

While a viable plot for a late night comedy show, this is the argument they are using to attack my reputation and my career, so you’ll forgive me if I don’t simply take them at their word that such evidence exists. Especially as we have the original reason direct from the source (Dries’ original, unedited blog post).

Dries’ original blog post, before he edited it, stated quite clearly why he asked me to resign:

However, when a highly-visible community member’s private views become public, controversial, and disruptive for the project, I must consider the impact that his words and actions have on others and the project itself. In this case, Larry has entwined his private and professional online identities in such a way that it blurs the lines with the Drupal project. Ultimately, I can’t get past the fundamental misalignment of values.

First, collectively, we work hard to ensure that Drupal has a culture of diversity and inclusion. Our goal is not just to have a variety of different people within our community, but to foster an environment of connection, participation and respect. We have a lot of work to do on this and we can’t afford to ignore discrepancies between the espoused views of those in leadership roles and the values of our culture. It’s my opinion that any association with Larry’s belief system is inconsistent with our project’s goals.

Before I continue with the quote from Larry’s post, I want to address Mr. Buytaert’s post, as originally written, quoted here. The reason Larry self-outed and thus “entwined his private and professional online identities” is because someone was threatening to blackmail him, namely by making content from a private website public (again, lest we forget, in violation of a privacy-protecting AUP/TOS). And again, what Larry does behind closed doors should not affect his role as contributor to a community-based free software project, especially when that is his livelihood, whether that activity behind closed doors is Gorean role-play, BDSM, or whatever sexual practices or roleplay, no matter how bizarre or “Offensive™” others might find it. That Larry had to self-out to protect himself from blackmail is bad enough.

Again, as I read it, the whole Gorean thing is not even Larry’s “belief system” but simply roleplay. Today, it’s someone into Gorean roleplay and BDSM. Tomorrow, it could be… LGBTQ people? Muslims? Jews? Atheists? Microsoft stockholders? Duck Dynasty fans? The best way to avoid this potentially slippery slope is not to take the first step.

Continuing on:

Note the first line in particular: I’ve been active in Drupal for over a decade, and only now have my “private views” become “public, controversial, and disruptive to the project” despite no changes in the level of “entwining” I was supposedly doing. And they did so through no action of my own, but because of a whisper campaign behind my back which lead to the actions of others who chose to blackmail me. But now Dries needed to excommunicate me because my private life might be “disruptive”. He didn’t, however, go into any detail about what was so problematic about my beliefs other than talking about “equality” in the abstract, despite a decade of evidence that I actively support the same.

In his call with me, Dries said very explicitly there had been no Code of Conduct violation, as far as he knew I had done nothing illegal, and as far as he was concerned my private life was not his business even though he personally found it distasteful. Yet he was still asking me to resign because of the possible disruption to the project from someone else going public. In particular, he indicated that “someone” was threatening to go public in a matter of “days, not weeks”, unless I was removed from DrupalCon.

So I see two possible conclusions:

  1. Dries is so personally disgusted by my (not illegal, not CoC-violating, not his business) personal life he wants to remove me from Drupal because of it, but won’t just own up and say that.
  2. Dries was mostly afraid of my blackmailer making good on his threats to go public and what the bad PR would be, caved, and now refuses to admit that he was in the wrong.

I do not know which one is more damning.

It’s really tough for me to say which one is more damning, but I’m going to go with the first choice. If that really is the case, that Mr. Buytaert can’t just own up to the fact he finds Gorean roleplay and BDSM distasteful, even though they obviously do not affect Larry’s skills when it comes to contributing to the Drupal project, then it’s time for him to resign and let someone else take the reins.

Caving into a blackmail threat and not being able to own up to that being a mistake is also a grave error. But letting one’s personal views cloud the actions one takes against another, especially when the target of those actions suffers career-related damage as a result, is far worse.

This does not have two conclusions of which we are left to decide which is more damning:

With regards to the individual or individuals who “participated in gathering information about [my] private life”, the post claims “The Community Working Group is currently handling this situation through their standard process.” This seems odd given that, regardless of the CWG decision, Dries evidently has the authority to unilaterally remove the offender(s), but has not done so despite agreeing that what they did was a violation of the CoC and likely a crime.

Given that I reported the blackmail attempt to the CWG in mid-January and it is now April and I have heard nothing but a single “mediation” interview, in addition to the innumerable process fails listed above (which even the post from Dries and Megan admit), I must confess that I have little faith in the “standard process”, whatever that is.

This, in and of itself, is outrageous. Get “Offended™” and violate the privacy-protecting AUP/TOS of a private website to out someone whose activities are thusly “Offensive™”, and nothing happens. Even though such conduct is at least a civil tort if not a criminal act, and a clear violation of the CoC.

On the other hand, it’s Larry who’s having to fight to save his career and reputation after being thusly wronged. It’s no surprise that Larry has no faith in the “standard process” after that; I wouldn’t either, and I’d assume most sane people wouldn’t as well.

The post from Dries and Megan also implies that there were to be many more “discussions” between Dries and I, and that I somehow cut it short by going public about the fact that I was being blackmailed. That is a grossly disingenuous statement.

In the very first communication I had from Dries on 24 February, he made it very clear that he wanted me to resign and wouldn’t take no for an answer, yet “no” was the only answer I would give. There was no indication of plans for further discussion, other than him ending with “let’s talk again soon”.

In the only communication I received from Megan, on 27 February, she informed me of my removal from presenting at DrupalCon “given [my] recent discussions with Dries”, with no further explanation or even implication of more communications were to come.

That did not in any way indicate a potential for “a number of conversations to resolve any remaining concerns”. It was an ultimatum, and the end of a conversation. There was no further discussion to be had. Yet the post accuses me of “effectively ending the process in the middle of what we expected to be a series of constructive discussions” when I posted my initial self-outing post. However:

  • I had discussed self-outing with members of the CWG on multiple occasions since January
  • I had told Dries on 24 February that I was considering self-outing precisely as a way to undermine blackmail
  • In my written statement to the Board on 16 March (which Dries would have read) I made it explicitly clear that I intended to self-out as a way to minimize the public damage to my reputation, regardless of the board’s decision
  • Dries emailed me after the Board meeting (on 19 March) to encourage me to not self-out, but held firm on my prompt departure from Drupal
  • On 19 March, I invited the CWG to review my self-outing post before publishing in order to verify that it would not, itself, violate the Code of Conduct

That I was going to self-out was not a surprise to anyone, and at no point was it expressed that there were conversations to be had that didn’t begin and end with me leaving and giving in to blackmail.

I see two possible interpretations:

  1. Dries and Megan intended to have a series of conversations with me to try and convince me to leave quietly and give in to blackmail, but failed to actually tell me this, even after they were aware of the self-outing post I was going to publish, and instead opened with an ultimatum.
  2. They had no such intention and are ret-coning events.

I do not know which one is more damning.

On this one, surprisingly, I really don’t know which is more damning either. I’d lean towards saying revisionism (or as Larry says it, “ret-coning”) is the worse of the two, but the reality is it really doesn’t matter whether Mr. Buytaert and Ms. Sanicki have been caught in a big, huge lie, or are just such terrible communicators that they couldn’t have told Larry their intention was, over the long term, to try to talk this out. Again, both scenarios are dreadful.

The sum total of the actions of Dries Buytaert, Megan Sanicki, Klaus Purer, the CWG, and others invole clearly indicate a gross failure in leadership and culture within the Drupal community. That a gross violation of the standards by which decent people live has been deemed acceptable by no other than Mr. Buytaert himself is enough for me to declare the Drupal project as it stands today in danger of collapsing unless drastic changes are made.

Finally, the conclusion of Larry’s post:

So what does Larry want?

A few people have asked me what it is I want, and what I hoped to accomplish by going public. A fair question. My goal has been, and remains, to defend my name, reputation, and honor against blackmail and libel, from anyone.

There has been wild talk of a Drupal fork, of reorganizing the Drupal Association, of people resigning, and so forth. I have no interest in such discussion, nor interest in a Drupal fork. My goal is not to split or harm Drupal, nor anyone in it. My goal is entirely defending my reputation and putting a stop to blackmail and libel.

I admire Larry’s desire to keep the community unified. However, I just don’t see that happening with the current leadership.

Reorganizing the community leadership, including the DA, is necessary to keep problems like this from happening again. As I see it, as more or less an outsider who has not ever followed the Drupal community that closely (but who nevertheless wants the option to run a Drupal site without regrets in the future), is that there are systemic issues here that need to be fixed to restore confidence in the community’s leadership.

Before I conclude this post, I’d like to briefly address Larry’s hot-off-the-presses blog post “Don’t go low”. Apparently some people are outraged enough to engage in harassment and stalking-like activities, including “doxing”, of those involved such as Mr. Buytaert and even people like Angela Byron, who did not even get involved until after the decision had been made to remove Larry from his positions.

Larry condemns the activity and cites it as no better than what has been done to him:

Dries mentioned that he had received a great deal of private hate mail over this matter, and that it was impacting his approach to the situation. I’ve previously seen a (very small) number of people on Twitter suggesting gathering private information on Dries and others, including their families(!), to use as leverage. In a previous comment, Angie Byron (who was not even involved in matters surrounding me until after I went public) said that she’d received threats against both her and her daughter.

I want to speak directly to those presumably few who have sent such messages, and in the calmest and most restrained manner I can:

What the fuck were you even thinking???

No, seriously, how did you even think that was a good idea? Responding to cyberstalking, prejudice, and blackmail with… cyberstalking, threats, and blackmail? No. NO! Even if you’re trying to support me, NO! I do not want any such support. You are actively making it harder to resolve this situation.

Incidentally, Angela has made a blog post about what the CWG does since she was a former member, and can now speak a bit more freely. I may address this in more detail in a later post here, but did not want my readers to wait until I posted the next part to have a chance to look at it. I am not sure what others are seeing in this post of hers that is hostile to Larry; it appears to be a neutral attempt to get information out there and counteract FUD (fear, uncertainty, and doubt) being spread about Drupal’s CWG.

Finally, since I began this post, Mr. Buytaert has issued what he titles as an apology on his personal blog. In part three, I analyze this post as well as other happenings that have taken place related to the situation, as this post has gotten way too long to try to cover it here.

The witch-hunt against Larry Garfield, part 1

This entry is part 1 of 3 in the series The witch-hunt against Larry Garfield

This story has been out there for a while, but I haven’t posted until now because I was letting the story develop a bit more. (I have, in the past, posted too soon before parts of the story have developed and wound up looking, or at least feeling, like an idiot. More on this later.) Now that both sides have posted at least one statement, I feel the story has developed enough that I can go ahead and comment.

At present, I am not a Drupal user, but the issues that this situation presents could just as easily happen to anyone in any community-based free software project (WordPress, Joomla, Concrete 5, etc) and it’s entirely possible that I could wind up a Drupal user at some point in the future (I have set up a Drupal site before that I wound up never actually making a live website). In fact, I see parallels between this story and things that have happened to me in a couple of the various communities I have been involved in over the years. So I don’t see this as a Drupal issue, I see it as a community leadership and project governance issue, and a mighty big one at that.

A recent article on TechCrunch reports on the issues surrounding Larry Garfield and his continued participation in the Drupal project after over a decade of contributions. How the issues came to be is a chilling tale, which I will attempt to summarize in a timeline fashion, but I would like to invite readers to also read Larry’s blog post about the situation (titled appropriately enough “TMI About me”).

The timeline:

  • 2005 (April or later): Larry Garfield begins his involvement with the Drupal project.
  • 2016 October (approximate): Someone finds Larry’s profile on a private website for alternative lifestyles (in this case, it would appear, a BDSM community). This person was “Offended(tm)” (as Larry says it), screenshots a post, and passes it around, which is a direct violation of the site’s terms of service (TOS).
  • Some time later: This post makes it to Drupal’s Community Working Group (CWG), which finds no code of conduct violation that they can take action on. Despite this, a “gossip campaign” continues against Larry.
  • Some time after the above: The CWG informs Larry of the situation, who responds with an open offer for others to speak privately with him about his personal life if they so desire.
  • Late 2016 November (US Thanksgiving weekend) at Drupal Iron Camp in Prague, Czech Republic: Klaus Purer takes up Larry on his offer, though he doesn’t listen to much of what Larry had to say, ending the conversation with a statement that he was going to “distance himself from” Larry. Larry offers a handshake, which I would assume was declined by Mr. Purer.
  • Some time later: Mr. Purer signs up on the same private website, to go “spelunking” through Larry’s post history, sharing the “worst” posts with the CWG (again, in a flagrant violation of the TOS of that site).
  • 2017 January: Larry has a Google Hangouts conversation with Mr. Purer, during which the latter implies he is speaking not only for himself but for another group of anonymous individuals and attempts to blackmail Larry into resigning from his positions in the Drupal community, including his Drupal advocacy within the PHP community. Larry, in his post, states he “do[es] not suffer bullying and threats lightly” and as a result referred the matter back to the CWG, who mediates by having separate conversations between both Larry and Mr. Purer. They conclude again that no code of conduct violation has occurred.
  • Some time after the above: Mr. Purer continues his “spelunking” of the private website and sharing of content from that site with the CWG (still in violation of that website’s TOS).
  • 2017 February 24 (a Friday): Larry gets a phone call from Drupal project lead Dries Buytaert (roughly equivalent to a prominent WordPress user/contributor getting a call from Matt Mullenweg himself). Mr. Buytaert would reveal that he and the Drupal Association’s executive director Megan Sanicki had known about this situation for some time, but not once reached out to Larry until this phone call. Mr. Buytaert asks Larry “to step down from Drupal… in the best interest of the project”. Larry says this is impossible as it would directly impact his career (and due to Larry’s advocacy of Drupal in the PHP community, not necessarily in the best interests of the Drupal project either).
  • 2017 February 27 (the following Monday): Ms. Sanicki sends Larry an email dismissing him from his position as track chair and speaker at DrupalCon “per [his] conversation with Dries [Buytaert]”. From Larry’s blog post: “I do not know if ‘per my conversation with Dries’ means I’m unwelcome in Drupal because of my sex life, I’m unwelcome in Drupal because Dries was afraid Klaus would go public and embarrass the project otherwise, or something else. I have been given no further information than that and still have not been.”
  • After the preceding email: The Board of Directors (of the Drupal project) votes to affirm Ms. Sanicki’s “decision to revoke the session for DrupalCon Baltimore and end the track chair term”. They did this after Larry presented his case in writing when he was unable to present his case in person due to being scheduled to present at a conference.
  • 2017 March 22: Larry makes his blog post (linked below).
  • 2017 March 23: Ms. Sanicki makes a blog post on behalf of the Drupal Association addressing the situation (linked below).
  • 2017 March 26: Techcrunch publishes their article and it is shared to the Cypherpunks email list (and many other places, I’m sure) shortly thereafter.
  • 2017 March 27: Larry makes his second blog post (linked below).
  • 2017 March 29: Ms. Sanicki updates the DA blog post.
  • 2017 March 31: Another DA blog post from Ms. Sanicki (or at least posted from her author account) goes up (linked below).
  • 2017 April 5: Larry makes a third blog post, which I will comment on in more detail in the second part of this post (as this one has already grown to be rather long).

Larry goes on to quote from both the Drupal and DrupalCon Codes of Conduct. The first quote from the Drupal Code of Conduct:

We expect members of the Drupal community to be respectful when dealing with other contributors as well as with people outside the Drupal project and with users of Drupal.

It is obvious to me that at least Mr. Purer and the original as-yet-unnamed individual who found Larry’s profile have violated this rule by sharing information about Larry from a private site where such sharing is prohibited by the TOS. I would think that everyone, including Mr. Buytaert and Ms. Sanicki, who has acted on such information shared in violation of the TOS, should be considered as “having eaten from the fruit of the poisoned tree” as it would be said in US criminal law.

Larry hasn’t broken this rule just by having a different lifestyle and adopting quirks from a subculture. He mentions saying “be well” or “I wish you well” to end a conversation. The US pharmacy Walgreens had their cashiers say “be well” for quite a while, so it’s not like it’s all that weird. I certainly hope they didn’t quit because someone made a stink about it.

And Larry’s quote from the DrupalCon Code of Conduct:

Sponsors, volunteers, speakers, attendees, and other participants should strive to treat all people with dignity and respect, regardless of their culture, religion, physical appearance, disability, race, ethnicity, gender, or sexual orientation.

Larry goes on to refer to Gor as a culture and BDSM as a sexual orientation, both of which I would consider reasonable categorizations. And so the story sat for a few days, while both the Drupal Association made its statement about the issue and Larry made a second blog post about the topic.

I’m not going to go into detail on the second blog post (other than that I made a few edits to the part I wrote before it went up, based on that information). However, I am definitely going to call out Ms. Sanicki’s blatant lies and contradictions in her statement made on behalf of the Drupal Association. My commentary to each quoted section of their statement is directed at the Drupal Association and specifically at Ms. Sanicki:

We want to be clear that the decision to remove Larry’s DrupalCon session and track chair role was not because of his private life or personal beliefs. The Drupal Association stands by our values of inclusivity. Our decision was based on confidential information conveyed in private by many sources. Due to the confidential nature of the situation we cannot and will not disclose any information that may harm any members of our community, including Larry.

Okay, so this wasn’t about his private life. Yet you’re not saying exactly what it was. It’s funny how the reason is so confidential yet Larry has no problem putting out there exactly what parts of his private life people are apparently taking issue with. Even if the community doesn’t have a right to know why you, the Drupal Association, have a problem with Larry remaining a part of the project, Larry himself deserves to know. Larry refused to resign after Mr. Buytaert’s phone call to him, so the fact Larry was summarily removed from his track role and DrupalCon session after that call is a bit more puzzling.

What exact rule(s), in either the Drupal or DrupalCon Codes of Conduct, did Larry break? If there are none, why is he being treated like he did break a rule?

This decision followed our established process. As the Executive Director, charged with safekeeping the goodwill of the organization, I made this decision after considering input from various sources including the Community Working Group (CWG) and Drupal Project Lead, Dries Buytaert. Upon Larry’s request for an appeal, the full board reviewed the situation, all the evidence, and statements provided by Larry. After reviewing the entirety of the information available (including information not in the public view) the decision was upheld.

What you (Ms. Sanicki) did not tell us, is that the CWG is three people, all selected by Mr. Buytaert. Thankfully, the comment saying so was allowed, so the rest of us following this debacle know this. I am also reading between the lines here that the CWG could be seen as an extension of Mr. Buytaert’s ego and that he would be unlikely to pick people that would vote on matters like this against his wishes. The CWG should be picked by leaders in the community and not just the project lead. How can we possibly trust the CWG to make unbiased decisions otherwise?

In order to protect everyone involved we cannot comment more, and trust that the community will be understanding.

I read this as “we are above admitting we really screwed this up and so this dollop of bovine excrement is all we’re going to drop on the concerned members of the community.” Sorry, no sale.

We do see that there are many feelings and questions around this DrupalCon decision and we empathize with those community members. We will continue to monitor comments. We are listening.

Good, then I hope this blog post finds its way to you. I want to know at what point the two of you (Ms. Sanicki and Mr. Buytaert) are going to admit that you screwed this whole thing up and reverse it. Also, Klaus Purer and whoever originally sent the complaint about Larry to the CWG both need to face some serious consequences (though I suspect it was, in fact, Mr. Purer who sent in the original tip). Everything that has wound up being leaked from the private website (mentioned by Larry) and put in the hands of any non-member of that site was done so in violation of that site’s Terms of Service or Acceptable Use Policy (TOS/AUP). It’s all “fruit of the poisoned tree” and if everything stems from what was posted on a private website which was accessed on behalf of the CWG and DA in violation of the TOS/AUP, regardless of who did it, then the foundation of any action against Larry is flawed.

It looks like, per the March 31 blog post to the DA blog, that there may yet be action taken against Mr. Purer. However, Larry still needs to be made whole. If there’s a reason for removing him as speaker and track chair at DrupalCon, then we should know why. And not just vague terms like “holds views that are in opposition with the values of the Drupal project” (which in and of itself shouldn’t be an issue), “[people] suffered from varying degrees of shock and concern” (there’s a reason those kinds of websites are private), or “protect the shared values of the Drupal project” (when the action to remove Larry from community involvement is seen by many as a direct contradiction of those values and the first step down a very slippery slope). No, we the community have the right to know what rules Larry broke, chapter and verse.

I’ve seen these kinds of things unfold before–not to mention experiencing a similar situation myself. I would hope those in charge will do the right thing, and try to fix the damage they have caused to Larry’s career. The more likely outcome, unfortunately, is that they don’t give a tinker’s damn and let the (wrong) decision stand. If Drupal wasn’t Larry’s entire career at this point in his life, this would be much less of an outrage. But it is, and this is the most outrageous thing I’ve ever seen a software project’s leadership do to a contributor–many times more outrageous than what happened to Theo de Raadt as a NetBSD contributor back in 1994 (finding the details of which, I leave as an exercise to the reader).

Mr. Buytaert: If you really wish to “protect the shared values of the Drupal project” then you need to reinstate Larry Garfield as a contributor and issue a sincere and meaningful apology to both Larry and the Drupal community, without any further undue delay. You also need to understand the difference between fantasy roleplay and real-life conduct as a member of the community. It really isn’t any of your business if Larry’s into BDSM or Gorean fantasy role-play, and the fact that information was leaked to you from a private website in violation of its privacy-protecting AUP/TOS doesn’t change that. That Larry has had to make this public just to try and protect himself is outrageous and egregiously offensive not just to me, but to a lot of other people out there (judging by the comments I’ve seen on both your blog and the DA’s blog). You should also strongly consider resigning as project lead because instead of “protect[ing] the shared values of the Drupal project”, you have diminished and tarnished them.

Ms. Sanicki: Your role in wrecking Larry’s career by dismissing him as speaker and track chair at DrupalCon is also egregiously offensive. That you pretend it has nothing to do with leaked details of his private life, leaked to you in violation of a private website’s privacy-protecting AUP/TOS, is perhaps the most egregious lie I have ever seen told in my entire adult life. You have made the Drupal Association look just awful, and as I see it, the most certain way you can fix it is by resigning your position without any further undue delay.

Mr. Purer and the as-yet-unnamed person who, in the words of Larry, was “Offended(tm)” by what you found out about him: Your disrespect for privacy in the quest to ruin a man’s career is shameful. I don’t know how you can look yourselves in the mirror in the morning after doing what you have done. If you lack the integrity to remove yourselves from the Drupal community, I hope the leadership does. To violate the AUP/TOS of a private website, put in place to protect the privacy of its members (not just Larry, but all the other members as well), for the purpose of leaking information to destroy a man’s career because you don’t like what you saw, is saying a huge “fuck you” to how we operate in decent society. It may not be a crime in and of itself to do what you did, but it’s definitely unethical and immoral and probably a civil tort as well. Shame on you.

In part two, Larry’s third blog post (which I had skimmed, but not read in detail, before putting the finishing touches on this one).

Fixing broken tractors, Ukranian style

Recently, the Motherboard blog on Vice.com reported on the extreme measures some US farmers are having to take to fix their John Deere tractors, namely downloading cracked software hosted in countries like the Ukraine and Poland.

From the article:

Tractor hacking is growing increasingly popular because John Deere and other manufacturers have made it impossible to perform “unauthorized” repair on farm equipment, which farmers see as an attack on their sovereignty and quite possibly an existential threat to their livelihood if their tractor breaks at an inopportune time.

“When crunch time comes and we break down, chances are we don’t have time to wait for a dealership employee to show up and fix it,” Danny Kluthe, a hog farmer in Nebraska, told his state legislature earlier this month. “Most all the new equipment [requires] a download [to fix].”

The nightmare scenario, and a fear I heard expressed over and over again in talking with farmers, is that John Deere could remotely shut down a tractor and there wouldn’t be anything a farmer could do about it.

The article goes on to describe a license agreement John Deere forced farmers to sign in 2016 October, which not only forbids the farmers from doing their own repairs but includes a covenant not to sue John Deere for “crop loss, lost profits, loss of goodwill, loss of use of equipment …arising from the performance or non-performance of any aspect of the software” running on the embedded systems in the tractors or other equipment. Basically, John Deere is saying “if our tractor breaks, it’s your problem, not ours, for the length of time it’s out of action.”

If this sounds like pure lunacy to you, you’re not alone. I would go as far as to call this one-sided agreement unconscionable. No judge worth his or her salt would possibly uphold such a blatantly lopsided agreement, especially given some of the rather exorbitant rates charged by John Deere: the article mentions $230 plus $130 an hour for a technician to drive out to a site and plug a connector into a USB port to “authorize” a repair done by an independent repair shop (which, of course, they could decline in theory). Given farms are by definition not going to be close to major cities or even larger towns where John Deere technicians are likely to live, a bill for such a service call could potentially cross the thousand-dollar mark.

So the farmers and independent repair shops say to hell with the license agreement and do the repairs in violation of it using cracked software from the Ukraine, Poland, and elsewhere. I can’t really blame them. And it’s possible that despite the license agreement, the repairs themselves may not be quite as unlawful as it first appears, though the acquisition of software intended for use only by “blessed” (i.e. authorized) John Deere technicians could still be against the letter of the law. In 2015 the Librarian of Congress approved an exemption to the Digital Millenium Copyright Act (DMCA) for land vehicles, which would include tractors and farm equipment. Curiously, around the time the exemption went into effect was when John Deere started requiring farmers to sign the license agreements.

One farmer modified his tractor to run on methane produced from pig manure, which I certainly applaud from an environmentalist standpoint. Who is John Deere to say that gasoline is a better fuel than the methane from pig shit (that would ordinarily be considered a waste product outright)? I would think most people (by which I mean non-stockholders in companies involved in the petroleum products trade) would agree that pig poop methane is a far better choice.

But the environmentalist side of me isn’t done. Toward the end of the story, there’s this quote:

“What happens in 20 years when there’s a new tractor out and John Deere doesn’t want to fix these anymore?” the farmer using Ukrainian software told me. “Are we supposed to throw the tractor in the garbage, or what?”

There’s one way to stop this, and it’s a “right to repair” law such as those already under consideration in five states: Nebraska, Minnesota, Kansas, Massachusetts, and New York, with a similar bill targeted more precisely at farm equipment in the works in Wyoming. The bills are modeled after a similar law already passed in Massachusetts targeting motor vehicles (but unfortunately, not including farm equipment it would appear).

Not surprisingly, John Deere is one of the opponents of this legislation, along with companies like Apple, which I have already written about at length on this blog. Gee, I wonder why? Maybe they fear the loss of an income stream built on robbing farmers (or hapless iPhone owners)?

This situation the farmers find themselves in is a large part of the reason why I fight for computing freedom and limit the amount of non-free software I use (and specifically why I do not run Windows on my PC and will never buy any Apple hardware, including Beats headphones).