Archive for the 'NDA' Category

I think almost all of John’s comments deserve to be blog posts on their own. So I’m copying this one over here:

“I think it was Matrixpoint who said that Casey really insists that he is not the true leader of CS…”

Actually, I don’t know that he ever said this. On the contrary, since I first appeared at the Montreal Collective, and during the following year as a volunteer, I found it very difficult to determine the organizational structure of CS and Casey’s role in it.

Everyone knew that the organizational structure was being revamped as part of CS 2.0, but the only public information I could find was an organizational diagram on the website that showed a central box labeled “Admins and Founders” or the like, months after I left Montreal. I was disturbed to see this for two reasons: 1. the complete lack of detail of the internal structure of this box, and 2. it’s central position, which was in conflict with the agreed upon decentralized organizational structure suggested by the tree model (see the logo of this website) that was created during the Montreal Collective.

There was no particular mention anywhere that Casey was the supreme, unaccountable head of CS. He was only included among the list of 4 founders prominently featured on the website. There were no by-laws to be found. The only information available about the Admins was a brief statement that they were volunteers who helped with important administrative duties involved in running the website. No information about how they got their positions or whether there was a term of office, etc. No information about performance reviews, etc.

As someone who had begun volunteering full-time with the intention of working freely on behalf of the hospitality community for years to come, I sought clarification as to who I was actually working for. I made it clear that my intent was to work for the Community, not for Casey and the Admins unless they were in some way accountable to the Community. Why in the world would I (or anyone) work full time so that Casey and his hand-picked buddies could live it up in exotic locations, unless the Community who provided the support for that had some say in it?

I got no meaningful response to two lengthy requests for information from the Admins beginning in December, 2006. That’s when I started reconsidering my commitment to CS and paying attention to such matters as the NDA (another whole story in itself).

It wasn’t until the following year (in the spring I think) that Casey finally revealed to the developers that he was the sole member of the Board of Directors. (According to Pickwick, Casey’s told a different story to NH government officials).

So, you see, Casey’s style was very indirect. CS 2.0 was supposed to be about members participating in the operation and evolution of CS, and the emphasis was **decentralized** participation. It was “The CouchSurfing Project”, not “Couchsurfing International, Inc., Casey Fenton CEO and sole member of the Board of Directors”. “Do-ocracy” was promoted by at least one of the Admins, and another Admin was generating most of the communication which included a call for member involvement.” No where was it mentioned that these Admins derived all their power from Casey and that he quietly controlled everything with absolute authority. He rarely took a public stand one way or the other, but rather allowed people to form impressions, whether they agreed with his personal agenda or not, that he did nothing to correct.

An example of his indirect style was when he made Chris Burley the new Tech Team leader near the end of the New Zealand Collective. Chris obviously was functioning as Casey’s tool, being used by Casey to shake up the development team (probably due to issues with Joe and Kasper). Chris had very little familiarity with the code or with ongoing initiatives. He only had Casey’s authority backing him up and used it to rule with an iron fist, announcing that no “personal ideologies” would be tolerated and all developer-initiated projects would be put on indefinite hold. (Developers were clearly now to be thought of as order-following employees, but without the pay, not co-participants in a project to make the world a better place.) Casey remained quietly in the background while Chris took most of the heat for Casey’s “house-cleaning”. Chris quietly dropped off the radar by the end of last summer, as if his usefulness as a tool had expired.

What was most disturbing to me about this incident was that not long before this Casey had finally talked with me on the phone (after a 3 month wait) for a few hours and we seemed to have reached a meeting of minds. I explained to him that I would begin no new projects until the NDA was fixed (as he had promised some nine months before). I told him that it was outrageous as it stood. He said nothing in response. But he actually invited me to participate in the formulation of the organizational structure that was in its final stages. I said, yes, I would very much like to be involved. The result of this call was that I felt Casey had heard my concerns and that I now was getting some respect as a full-time volunteer (of more than half a year).

So I was very shocked that Casey appointed Chris, without even consulting me or any of the Tech Team about it, especially since he had the opportunity to discuss it with me on the phone and had given me the impression that he wanted me to be in the loop when it came to organizational issues.

I was even more shocked when I sent him an email saying that although Chris might be a good choice based on his past general contributions (this was before his new personality as a “leader” emerged) but that he didn’t have enough technical knowledge to lead the team, and a least another co-leader who did was needed. Casey never responded to my email.

I was even more shocked when the new organizational structure was announced (completely done in secret), and that what little apparent accountability it seemed to include amounted to nothing.

I was ultimately shocked when the proposed NDA came out (after a year) that was supposed to be the “fixed” version, but it was 10 times worse than the original. It had the feel of the Patriot Act to me. I was utterly uppalled by the mindset that produced it, and by the way this whole drawn-out fiasco was conducted by Casey and his appointed elite.

I certainly felt the trust I had put in Casey as a result of the phone call completely betrayed, and I took the NDA as an indirect message to me that I was no longer wanted as a developer, since I had publicly announced I would no longer begin any new projects if the NDA wasn’t sufficiently fixed.

I would have much preferred that Casey had told me this directly, as I would have preferred that he shake-up the Tech Team himself instead of having a henchman do his dirty work for him.

This is Casey’s style: indirect, manipulative, pulling strings from behind the scenes, while giving a casual, no-worries, laid-back, often non-committal impression in public: a fun guy to party with.

In case any one is wondering whether Casey might have been justified in “cleaning house”, I can say that the 4 core developers made a huge contribution to CS, much more so than Casey, at least in the technical area, for most of the year following the Montreal Collective. (I suspect it was our very success that scared Casey, and threatened his absolute control.) Speaking for myself, the greatest problems I encountered as a volunteer developer were all caused either directly or indirectly by Casey or the Admins due to their arbitrary assertions of power without understanding the situation, extremely poor communication, and poor judgment. Working with the Community, on the other hand, was delightful and I still have those good memories.

John