This blog includes two statements. One from Dries Buytaert, as Drupal Project Lead, and another from Megan Sanicki, as the Executive Director of the Drupal Association and the Drupal Association Board.

We recognize that events and conversations earlier this year surfaced many concerns and needs within the community. One in particular is related to Larry Garfield’s role within Drupal. After several conversations with Larry, and careful consideration, we can now provide an update to this situation, our decisions, and Larry’s role moving forward.

We thank you for your patience while we spent many hours meeting with Larry and outside experts to resolve this matter. We recognize that actions were taken quickly before, which resulted in poor communication, and we wanted to avoid this happening again. We made sure to provide the proper time and attention these conversations needed before releasing this follow-up post.

We know our poor communication in the past led to frustration with us and pain for others. For that, we are sorry. We want to learn from this and improve. We listened to the community’s request to provide more streamlined, clear, and easy-to-follow communication. So, this post includes a statement from Dries Buytaert, as Project Lead, followed by a statement from Megan Sanicki, Executive Director of the Drupal Association.

Statement from Dries Buytaert, as Drupal Project Lead

I know there are many people out there still uneasy about where things were left off with regards to Larry's status and uncertainty around why he was asked to leave. I would like to personally clear up these things.

The actions that led me to ask Larry to resign involve a woman who attended Drupal community events with Larry, and was "allowed" to contribute by him. I originally characterized these actions as 'beliefs,' which was inaccurate on my part. To be clear, potential legal and ethical questions were raised by various people, including the Drupal Association lawyers, that this person could be vulnerable and may have been subject to exploitation, which raised the risk of substantial damage to the project.

Based on the legal and ethical risks to the Drupal project caused by Larry’s actions, both the Drupal Association and I needed to take action.

In balancing these questions and this risk, with Larry’s stated desire for privacy, the most obvious solution at the time was to ask him to resign. This was difficult. Larry has been a longtime contributor and colleague, and given the gravity of this situation, I did not communicate as clearly as I should have. When Larry chose not to resign, I took no immediate action with Larry’s role in the community in order to allow more time to better understand the situation and for mediation to occur.

Instead of continuing a dialogue and working towards a solution, Larry chose to end our discussion and share parts of the information surrounding this situation publicly. I understand why Larry blogged, and I support Larry’s — and every community member’s — right to speak out constructively when they disagree with those of us in leadership roles. However Larry’s blogs led people to think that I, and the Drupal Association, doxxed, bullied, and discriminated against him, which we did not. His blog posts led many to think that people who are into kink are not welcome in our community, which is not true. Larry's posts created material disruption to the project and the Association based on incomplete and inaccurate information. Even though Larry saw the negative impact he further inflamed the situation with additional blog posts.

Our current governance model lays out numerous positions that can be held within the project and who has the ability to appoint or remove people from them. Larry’s various roles and who governs them are listed in the table below. Most of Larry’s leadership roles are associated with the Drupal Association, but as project lead, I am responsible for assigning technical leadership positions within the project. Part of my job is to appoint and replace maintainers, to make sure the team functions well; and to make sure the leadership team is effective setting the technical direction of the project as well as collaborating with other members of the Drupal community to achieve our technical vision.

After talking to Larry and consulting other key contributors, I remain steadfast in my decision that it is best for Drupal that Larry should not continue to hold a technical leadership role. I've therefore decided to remove Larry as a core subsystem maintainer and as the PHP-FIG representative for Drupal. Larry will maintain his individual contributor roles which means he can participate in the development of Drupal as a regular member of the community.

Statement from Megan Sanicki, Executive Director of the Drupal Association and the Drupal Association Board

As the Executive Director of the Drupal Association a key part of my job is to protect the Drupal Association and the project from risk and harm. The Drupal Association is the steward of two critical drivers for Drupal’s longevity: Drupal.org and DrupalCon. And we are charged with caring for those spaces. Should the sustainability of the Drupal Association be impacted, we would no longer be able to maintain Drupal.org, which would have devastating implications for the project.

As Larry stated in his blog post, he was in a relationship with a woman he describes as “acutely autistic” and “mentally handicapped”. They attended Drupal events together where, in Larry’s own words, he “allowed” her to contribute to Drupal. The Drupal Association Board and I learned about this information from other sources as well as from Larry himself before Larry’s blog post was issued.

I was concerned not only about this person’s well-being, but I also had legal concerns about her ability to give informed consent or whether she was being exploited. The Drupal Association recognizes that Larry did not use the accurate medical terms to describe this person and we also recognize that most vulnerable people have the ability to consent. However, in this case, given the information we received about this person, we were concerned that it was possible that she could not consent. I sought input from board members and from professional experts, including legal counsel, who expressed concern that Larry’s action in his leadership roles created possible legal risk to the organization.

I learned about these issues just as the DrupalCon Baltimore sessions were about to be announced, and in order to give myself time to evaluate the risks, I ended Larry’s role as track chair and removed his session for only DrupalCon Baltimore. Making a decision for just one event provided me the time to better understand the situation and how to address the risks and concerns with appropriate counsel and authorities. The Drupal Association can not and should not investigate or adjudicate legal matters. We referred the situation to our legal counsel and followed their advice by removing Larry from leadership roles and we referred the matter to authorities.

Larry's subsequent blog posts harmed the community and had a material impact on the Drupal Association, including membership cancellations from those who believed we doxed, bullied, and discriminated against Larry as well as significant staff disruption. Due to the harm caused, the Drupal Association is removing Larry Garfield from leadership roles that we are responsible for, effective today.

These roles include being a DrupalCon track chair, DrupalCon speaker, member of the Drupal Association Advisory Board, and a member of the Licensing Working Group. Larry will maintain his individual contributor roles that the Drupal Association governs, which includes attending DrupalCon and contributing on Drupal.org using his Drupal.org user profile. It is important to note that Dries recused himself from the Drupal Association board decisions on this matter to avoid as many conflicts of interests as possible.

As long as Larry does not harm or disrupt the project, he will continue to be a member of the community as an individual contributor. However, we reserve the right to remove Larry's individual contributor roles if that is not the case. Also, we recognize that situations can change over time, so the Drupal Association will revisit these decisions in two years.

I recognize that my communication to Larry and with the community did not provide transparency into this situation and I apologize for the pain and confusion that caused. Our advisors told us not to share these details in order to protect all parties pending evaluation from authorities. Also, when Larry shared these details during the appeal process, he asked us to keep them confidential. It is my hope that this statement provides the clarity that many have been requesting. 

What We Have Learned

Dries, Megan, and the Drupal Association Board of Directors hope that the community can stay focused on healing and the needed discussions about ways we can improve our community.

It is clear that we were unprepared for a challenge of this complexity. We struggled to move forward in a careful, timely, and clear fashion. We need to provide the community with clarity and understanding whenever possible. Many ideas are surfacing from the recent community discussions and we are looking at them to identify other ways to be better prepared for future challenges.

Another key take-away from this incident is that everyone in our community needs to be able to understand the answers to these questions:

  • What is expected of me by the community?
  • What can I expect from the community?
  • How is Drupal governed?
  • How can I participate in governance?

The best way for the community to get these answers is by working together to refine our community governance model. We support this work and we are eager to help the community achieve its vision.

We believe this community is a role model for the world on how to be a great open source community. Even at its messiest, we believe this community is strong and has much to share with other projects and communities. We consistently come together to solve hard problems. Even now, we are coming together to redefine our community governance and we are confident Drupal will become stronger because of it.

If you want to be part of creating a stronger and healthier community for the future, we encourage you to get involved in the discussions taking place on Drupal.org. Plus, you can go here to learn about the findings from the recent Community Discussions that were mediated by Whitney Hess along with the next steps that the community wants to take in evolving governance. We hope you will join this effort.

Governance of Roles

As mentioned in Dries' statement, these are Larry's roles and who governs each one.

Larry Garfield’s Role Role Type Who governs this role Status
Technical Leader (Core Maintainer & PHP FIG) Leadership Role Project Lead Removed as of 2017-07-13
DrupalCon Presenter Leadership Role Drupal Association Removed as of 2017-07-13
DrupalCon Program Team / Track Chair Leadership Role Drupal Association Removed as of 2017-07-13
Licensing Working Group Leadership Role Drupal Association Removed as of 2017-07-13
Drupal Association Advisory Board Leadership Role Drupal Association Removed as of 2017-07-13
DrupalCon Attendee Individual Contributor - subject to DrupalCon Code of Conduct Drupal Association Intact as of 2017-07-13
Drupal.org user profile Individual Contributor - subject to Terms of Service Drupal Association Intact as of 2017-07-13

Comments

hurricane66’s picture

Drupal Association, the "plaintiff", the jury, the judge and the executioner all rolled into one. Of course this has to change.

Anonymous’s picture

This reminds me of the Little Britain character who thinks he's hypnotising people but he fails miserably at every attempt:

https://www.youtube.com/watch?v=_aZ2bdnG97A

This latest statement is a carefully worded pretext in order to bring in a set of rules of governance of the community according to the Drupal Association - a nonprofit organisation funded mostly by corporations and events where those corporations put on a public display of their products and services. Individual memberships are a very small %age of the funds. Compare this to something like the Free Software Foundation who pride themselves on their high percentage of individual memberships and compare the kind of work they do for Free/Libre Open Source Software, of which Drupal comes under the umbrella of, although many in the Drupal community only refer to it as "Open Source". For those who don't know the difference between Open Source and Free Software please have a read of this:

https://www.gnu.org/philosophy/open-source-misses-the-point.en.html

So as you can see in the post, the roles are set out so we know what positions are classed as leadership (i.e. you have a pronounced influence in the direction of the project within Drupal Association-run events or those covered by it's Code of Conduct) and the couple thrown in at the bottom which come under "contribution", which include going to events (which brings revenue to the Drupal Association) and code contribution (which brings wealth to the project as it relies on code being contributed). This also highlights the fact it has nothing to do with the Diversity and Inclusion issues of people saying they wouldn't go to events if Larry was there, along with the shift of focus from "Larry did something bad" to "Larry did something bad to the DA" which of course only happened after he'd already suffered from whatever went on. There's also been no financial proof of any harm to the DA, in fact all I've seen over the past few weeks is daily tweets from them thanking commercial supporter X or partner company Y, so seems if anything financial support is increasing, which of course is a Good Thing because what little tools we have to collaborate have a chance of staying up a little longer. Of course those tools won't be improving massively very fast because it's not in the commercial interests of most of the supporters of the DA for Drupal to be easy because most companies make money out of Drupal not being easy. I digress.

Meanwhile whilst everyone is discussing the ins-and-outs of whether Larry did this or Dries did that and whether it's morally OK to have sexual persuasion Y, good old George & team are busy drawing up the new set of extended rules which will be implemented in order for something like this situation to "never happen again" which of course it will, because total control (which is what the ones in power always require in order to stay in power) never works, it goes too far and implodes as we are seeing right now before our eyes. How it ends up is different every time - we are already seeing breakaway groups, cooperatively run distributions, and talk of more teaming up in order to bring some sense of normality back into the Drupal world which is after all far far bigger than this small group of power-hungry people sat around a table discussing how they think the world according to them should be.

Now whether the people in these roles actually see this and are deliberately doing it I do not know, I find it hard to believe they don't but having met and spent time with them I know they are all good people who work very hard, far more so than I have seen in any pure corporate environment - what has been built in the Drupal community is truly amazing and everyone involved should be very very proud of themselves and the dedication they have shown, I am in awe of many.

Perhaps it is down to society and the American way with the pure financial view on things. It is true there are many very big projects and clients and partners out there who simply don't want to have the risk of problems arising if they are going to invest millions in a piece of software to run their systems which make them money. They can't afford to have the chx's around complaining about this and that, or the crell's with his crazy ideas of permissive licensing or the purkiss' with his idealistic views of cooperation, they want to know that if they input X they get Y out.

This is why we see rounds of questions being asked to the current community members as to how they want things to progress. You ask your current audience what will please them and you shape your agenda to that. This way you keep as many of those who are willing to submit to your new set of rules and regulations, and you have enough of them that anyone who dares to say different is frowned upon due to the group think, the thought that they may be wrong, the almost incomprehensible though that after all these years and effort they've put in (obvious variations there per individual) that this is in fact all one big game to be able to create wealth by leveraging the value differential between what the creators create and what the capitalists sell.

For many years I've been saying and showing that a cooperative way of scaling the community will result in a better outcome than the top-down command-and-control tactics currently implemented (which come from the military), and I still believe this will be the eventual outcome of this whole episode as we see cooperatives form and grow by those who are disenfranchised with the current setup and just go 'do' as we've become accustomed to in this community of do-ers, I'm just sad that those who are in current places of power don't just be honest and open about the situation and show some support for alternatives. They can't of course because they're already too deep and fear losing control, and a product without a community to support it means they will have trouble selling it to the increasingly bigger companies they need to in order to return the investment they've promised to their investors.

Drupal has shown that amazing things can be built by cooperating, and is a leader in the new way that we work - commons-based peer production as one researcher who used Drupal as his PhD subject enlightened me to. Where it has so far failed is to take this modular web app platform and create the modular business model on top. As commercial elements struggle to find their niches because where they have money they don't have innovation to as much a degree as the whole community put together we will see more fragmentation, more pull to sayings such as "we should focus on one thing well" and meanwhile Drupal will continue to fail to be what it truly could be if only we collaborated at anything like the level we do on the code at the business level too.

The only solution is to build new infrastructure, new supporting organisations which support the vast wide community that is now Drupal but only currently a small percentage actually join in. It is our duty to do this now we have lumbered many governments with it and organisations of all sizes. We still, 13 years after I joined, fail to communicate what Drupal is and why it exists - every day I see posts from new people who've been told to use Drupal but have absolutely no idea of why or what or how and many will go on to develop bad sites because they only see the 0.00001% of what a core download gives them and missed out on things like DrupalVM, simplytest.me, native Drupal CRM, and so on because the 'front page' of the website is dictated by those with the money to do so and community efforts shoved to the geeky backend.

I don't know what the future holds here, it's not looking too great at the moment and if the people doing this do know what they're doing then shame on you, you're destroying the passion, work and lives of many who have done nothing but give you their love. For me, I'm continuing on as usual with my purpose of helping communities to be sustainable and using Drupal to do it. I still stand behind the model the book I've been carrying around the world with me to Drupal events with as a blueprint for how it could be, here's a link and a couple more if anyone's interested in seeing how things could be done differently. Sure, we need governance, but the DA is too intertwined with business to be able to support the community as a whole which I believe is the mission of it:

https://www.amazon.co.uk/Networked-Enterprise-Competing-Through-Networks...

https://platform.coop

http://www.fairshares.coop/the-case-for-fairshares/

memtkmcc’s picture

It drills into the deepest core of the situation, so it's both very painful and very true. Hats off to you Steve!

gnuget’s picture

Hi, it was very interesting to know that the biggest part of the money comes from companies and not from the community, i would like to read more about that. 

Can you share your source? Thanks! 

Anonymous’s picture

Sure, the accounts are here - you'll even see my name in some old ones ;)

https://www.drupal.org/association/accountability/990

Page 9 has the revenue overview, $5m total, $500k from membership dues, that's organisational and individual.

Paulmicha’s picture

After dust was starting to settle on varying degrees of complex and intelligent debates, such unilateral manichean stance feels like the dark weirdness where all this stemmed from :
a strong wish it could have been kept to yourselves.

One might find irony in the publication date, the eve of the french revolution celebration... "Unité indivisible de la République - Liberté, Égalité, Fraternité ou la MORT". On that note, let's read again "Der 18te Brumaire des Louis Napoleon" by K. Marx to move on.

"L'imagination est une ivresse, la réalité est sa gueule de bois" - Boulet

sunnydeveloper’s picture

(this was response to Steve's comment, not post content)"the current governance model is not working".   - I believe is the summary?  But I think It's really important to ask yourself what the straw was - was it that the the public communication? Was it the decision?  was it the amount of disclosure?  Was it because this is a core contributor with influence ?   Would it have been the same for someone of lower reputation? Why or why not?

at the end of the day drupal requires a governance structure which is trusted, which means if a core contributor is expelled/limited/ people trust the process, and the people running the process enough to (whether they have personal relationships with the person or not) to know full effort was expended to do what was right by code of conduct.  Because... personal information is involved, and publicaly you cannot share that which might make everyone feel 'convinced' .

What I see is that people don't like the verdict, this person is a core contributor - seems like a nice guy, therefore, there must be  personal bias or simplistic resolution process in the system( that otherwise worked for everyone)until the decision was made). 

By the way there is plenty of research to say toxic people, harmful people are sometimes the most productive people. 

kattekrab’s picture

Thanks for your comment Sunnydeveloper - its a good question, and one I'd like all those expressing so much raw anger and frustration to consider.  This has been hugely painful for many people, for many reasons.

I'm keen to see where we go next. 

The survey about how we, as a community, want to evolve our governance is an incredibly important stepping stone.

https://www.drupal.org/association/blog/take-the-survey-on-the-community...

jamsilver’s picture

My own views notwithstanding, the bulk of responses here very much represent one "side" of the response.

Common sense would dictate that many many people within the community (perhaps the majority) will be taking a different view and if any feel able to it, and/or have the time, it would certainly be beneficial to see it in this comments section.

Otherwise a misleading impression of community unanimity is easily construed, which helps no-one.

I'm sure a single-use "anonymous" account would not be looked down upon if felt necessary.

rj’s picture

Just when I thought the community was moving on. This response from Dries and the DA sounds like a 5 year old screaming they're right and everyone else is wrong. 

The only damage Larry caused to Drupal is that Acquia wasn't able to go public as quickly as Dries' wanted it to. 

--rj

xtfer’s picture

The usual strategy, when stuck at the bottom of the hole, is not to keep digging...

kattekrab’s picture

Thanks for taking a moment to comment here.

As you are someone I know personally, and respect hugely - I'd welcome a chance to chat.  

Could we find a time? I'll reach out through other channels.

In the meantime, I'd very much appreciate your response to the governance survey.  It's our next step, and I hope it's in the right direction.

https://www.drupal.org/association/blog/take-the-survey-on-the-community...

pivica’s picture

I want to thank Dries and DA for continuing handling this issue so... badly. Thank you for showing us clearly that you still do not see the errors that you made and that actually you do not care about Drupal community and other people opinions and perspectives.

And this is cool, this is your right. And in light of this latest post from Dries and DA, I will also stop wasting my personal time on this whole issue, DA and Dries. This will be my last post on this or any other DA or Drupal community discussion. From now on Drupal will be only taking my professional time and nothing else.

Thank you all.

UPDATE: And just to make clear to everybody this does not mean i will stop maintaining all the current and future Drupal modules and themes i maintain. I still believe that Drupal is the best open source web platform in the world and we should continue making it even better in the future. Drupal is much more than Dries and DA and i will continue concentrating my energy on open source Drupal version and ignore all the politics around it :)

Anonymous’s picture

In addition to this statement, several leaders in the community are spending time on social media strongly implying criminal behavior on the part of Larry and that people suffering from autism are incapable of making their own decisions. Others have suggested the offense taken over their actions can be sorted with hugs or other emotionally manipulative tactics. 

Instead of leaving the community, I encourage everyone to condemn this behavior in the strongest terms possible. Demand immediate changes to leadership.  

Despite the imposed hierarchical structure, this is our community, we made it. The people involved in this action represent a very small portion of the hundreds of thousands of developers worldwide who have contributed to the platform. I'm not sure I agree with the logic that it's their right to make decisions on behalf of the entire community without our consent - which is what this entire action against Larry was about.

No is a very simple word. Use it when you see something that's wrong.

Shyamala’s picture

It makes me feel proud to be part of a community where people are able to express their opinions. The intentions of many a members on these comments is to make Drupal better. 

I also appreciate Dries and Megan's statement. Knowing them personally this issue has not easy for either of them. I also know that they have taken extra care and are operating to make Drupal community a better place. 

There are definitely things we can do better in Governance, Communication and may specific areas that were identified during the Community Discussions. Whitney’s Community Discussions was a good place to hear the community voices. It gave  a chance for the Community to have their voices heard, even the not so loud voices. There were many constructive steps and ideas.

Moving from here we should make sure we build for the better. Request you all to watch out for the communications from Whitney and participate in the Drupal Governance next steps.
 

kattekrab’s picture

Thanks for this statement here Shyamala.  This has been really tough on every one. 

I've been sad to see some people hell bent on making it harder, rather than working together to address the concerns that have been raised.

The survey to determine how best to move our community governance processes forward is an important one. 

I encourage all who care about doing something about the future of our project, and the people who work together as a collective, to complete the survey.

We can not change the past, but we can create the future we want to live in. The only time to do that, is now.

https://www.drupal.org/association/blog/take-the-survey-on-the-community...

hgurol’s picture

I have already said that I have no faith, confidence and trust to Dries & DA long ago. They keep proving me right over and over again.

I am looking forward for the day that Dries leaves his role as the Project Lead.

kattekrab’s picture

Do you have a suggestion around who else could be project lead? And by what mechanism they would be appointed?

calbasi’s picture

@kattekrab I think Debian choose project leader from time to time. And developers are who vote him/her. That's a simple democratic idea. I can't understand why Drupal Community is not doing the same.

hgurol’s picture

Of course I do but I find the question and the timing a little strange. Do you think the reason that we are lead so poorly by Dries and the reason that he insist on leading the project is because of the lack of not having good replacement candidates?

Here is the deal, you make him understand that he is doing a poor job and needs to leave, then I will work on the candidates and the mechanism.

How about that?

Soul88’s picture

Sorry, guys, but it's unacceptable to treat this issue in such manner.

If you have real proofs of Larry doing something illegal - report the police. If you don't have such proofs - then I don't see what is Larry punished for.

This statement is a pure disappointment for me.

oxyc’s picture

Do read Larry's response to this post as well: https://www.garfieldtech.com/blog/tmi-part-5

pivica’s picture

I said in the previous comment i will stop tracking any happening around this or any other community topic, at least until this situation is resolved. I guess i lied ;)

Do read Larry's response to this post as well

And when you think stuff can't go any worst... Shame on you Dries and DA leaders, you completely fail us all.

Anonymous’s picture

As I said on reddit earlier, Larry stated they're under confidentiality agreements, so I'd be very aware as to believing anything either "side" says at this point:

"Because of the confidentiality agreement Dries and Megan required, I am not permitted to discuss what we talked about in any of those calls."

JvE’s picture

To whoever hacked megan's account to post this: not cool

If this post turns out to be genuine:
I think the healing begins by Dries and Megan admitting they listened to bad advice and made poor decisions. Then apologizing to Larry and welcoming him back.

The only harm done to the community seems to have come from posts by Dries and Megan. Those created uncertainty fear and doubt. Larry's posts were factual and informative.

Time to move the last of my clients from Acquia to Platform.sh (the ones that went before are glad they did)

hgurol’s picture

Time to move the last of my clients from Acquia to Platform.sh (the ones that went before are glad they did)

Now you are talking. All this masquerade is just because Dries worried way too much about his business. Let's see how acting poorly will help his business.

pubtastrophe’s picture

It may interest people to know that in the United States, the phrase "material disruption" - used by both Buytaert and Sanicki above - is a concept in constitutional law regarding the free-speech rights of children. In the United States, schoolchildren do not share the same constitutional protections of speech that adults do; if a child's speech "materially disrupts" the orderly conduct of school activities, the child can be silenced or punished.

It's odd to see this phrase imported into this controversy regarding the behavior and speech of adults. One can draw the inference that the Drupal Association or its lawyers regard the thousands of paid and/or volunteer workers who contribute their labor to the Drupal project as having a role equivalent to schoolchildren, with the limited rights of schoolchildren. In short, it appears to reproduce exactly what the DA accuses Garfield of doing: holding patronizing attitudes and opinions, and exploiting the alleged limited agency of other people.

Anonymous’s picture

Thank you for the comment. I was waiting for someone to point this out. It means the relationship between developers and the project is that of a subordinate and you don't enjoy certain rights - which should be spelled out.

kevingeorgeson’s picture

I truely hope that this saga is the end of Drupal. 

I've been disgusted time and time again with the disgusting attitudes and arrogance often publicly displayed by drupal contributors in the public domain, But now I realise that they are just trying to emulate the people at the top. 

The Drupal association should be ashamed of them-selves. A large project I am running just chose drupal to run all all 130 of our digital assets. 

Looking forward to going in on monday and telling the team to pick something else as there is no way I'm letting my company have anything at all with something being run like the drupal association runs this shop.

Good Riddance. 

pbattino’s picture

Dries, Megan,

this post reinforces what I thought: months ago you made a mistake (can happen to anyone) but you are not willing to admit it so you twist the facts to cover it (NOT ACCEPTABLE).

The way you are describing the problem with the vulnerable girl is simply incoherent with what you have said until now. Even more unacceptable, you did not raise this issue directly with Larry months ago, leaving us and him in the dark about what was the real imputation (facts? beliefs? Dries said "beliefs" but now admit they were "facts"...? WTF!).

You could have clarified this, but no, instead you kicked him out, he wants to discuss this further but he did not hear from you for a while apart from your request to keep it quiet... and you say that "Larry chose to end our discussion "... EXCUSE ME???? YOU avoided a proper discussion in first place, DON'T MAKE IT UP.

As for why you did all this mess and cover up, we all have our own opinion, I'm not interested in discussing it again. I can only say that you simply got the opposite result: in order not to (potentially) "damage the project" in one way, you actually damaged it badly in another way, with your own hands. Really, an achievement!

Maybe next time talk less to lawyers and more to the people your accusing, would you?

mrgoodfellow’s picture

Two years is right around the corner... excited to see the next update on this one!

Pages