It’s A Scam!
The campaign for a truly open CouchSurfing organisation
Good news for all CouchSurfing volunteers who signed the non-disclosure agreement: the California Supreme Court rejects noncompete clauses.Â Since it seems as if the organization has moved on to San Francisco it would be even harder to enforce anyone breaking the non-compete clause, although Matt Whatley seems to have been aware of issues with the non-compete clause in California.
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.
Damn Kasper, how do you do those quotes?
For your information: this is an extract of the original post by Kasper (http://www.opencouchsurfing.org/2008/01/14/ill-communication/)
It would be nice if Diederik could speak up about his experience and his own evaluation of the CS organisation.
A (small) word of warning: Speaking out against CS will almost automatically get you lumped in with the â€śOCSersâ€ť, even if you specifically state that you arenâ€™t.
Well, to be honest, I probably already am. Some months ago, I had some posts, also on my own website. Seems that the communication went dead afterwards.
Letâ€™s start at the beginning. I think this gives a better insight in my current feelings towards the Techteam, and in general: the leader of it, and Casey (ok, here comes my banâ€¦)
My CS experience started at my former employer. Walter was a programmer then. I and Walter could (and still can) get along quite well, and I was invited in his house.
There were several great people, which had the same â€śfrequencyâ€ť (another word of saying we could get along, but that sentence would became corny ). I met Duke, Aldo, Tiina, Paul and some others I forgot due to the use of ethanol My current position then was system engineer, and I was asked for that position at couchsurfing.
That would become handy, because of the start of the Rotterdam Tech Collective. Some several others were there too. Anu* (love!), Weston, Naz (great friend), Chris where several of them.
I got introduced with Nicco and we had great chats about the code (Iâ€™m not a programmer, so having some insight is perfect for me), system engineering, the couchsurfing system etc, etc. At that time, there were several things an issue. Nicco and I (as the only admins, besides some Indian people) started to work.
We had an agenda, and could start.
Several issues were addressed quite quick. Most of them are not-to-be-disclosed, but several were visible from the outside:
That time, the collective was already 3 months (or something like that) in the past. Several people came to become â€śsysadminâ€ť, Nicco was degraded as leader, while Weston became TT-Leader (managing dev and sysadmin). Communication became less and less. From some times, we couldnâ€™t reach Casey, which was our first contact for the code. At that time, my irritation began (my irritation towards the OCS was already there ). Could some parts from OCS be *INDEED* true?
(Anu isnâ€™t really stupid, you know, and Daz is just Daz and should drop dead, etc etc ) At that time, it seemed to *ME* that some people were only busy programming, and not with management.
We had a great CSInterklaas weekend, and the Thai-collective started. We had several â€śincidentsâ€ť before and after that (not-to-be-disclosed), and my irritation was at top. When I decided to resign (1 week ago) at the same time the poweroutage at the datacenter happened. Bad timingâ€¦ Or probably not, because there were some more â€śincidentsâ€ť.
This morning, I pulled the plugs from cs-sysadmins, cs-erc, cs-devel(|public). At my desktop is a Freemind scheme (http://freemind.sourceforge.net, go get it) with my thoughts, ideaâ€™s and remedies. I had the idea to post it in the CS-Sysadmin group for learning. If only someone would not only *READ* it, but also *REPLY* to it. Therefor, I decided not to do so. I have the feeling that Iâ€™m being ignored, so why should I put more energy in it?
From my opinion (an censored version of the mindmap):
Letâ€™s end with some positive notes:
I guess that the post shuld be called â€śCasey Loveâ€ť, the feeling that you were loved, but the other end just decides to move on to the next one.
Love from Rotterdam!
Diederik (And Frank Sinatraâ€¦ â€śThe best is yet to comeâ€ť)
p.s. When resigning from cs-sysadmins this morning, I saw the description of the group. Guess that this one is not NDA bound:
â€śDescription: This group is free from political agendas and personal ideologies. It is a place to serve the one of the core needs(server administration) of the CS Organization in order to make sure that the members have access to the site at all times so that they can experience inter cultural understanding.â€ť
For your convenience I put it a copy of the new CouchSurfing NDA on the OpenCS wiki.
It’s so beyond anything that it’s very funny, and merely deserves to be laughed at.
The burning question is just: Who will be asked to sign this monstrous document?
Reading recent posts on this blog I realise that a number of people signed the CouchSurfing NDA under the impression “it was going to be fixed”.
I think there’s an important lesson for volunteers to learn here. Don’t sign unless you’re happy with what you’re signing.
It’s impossible to say how things could have happened if people had made different choices, that’s not my purpose here. I’m looking forward, both to new CouchSurfing volunteers and to other NDAs. If you’re not happy with the terms, don’t sign them. A verbal agreement to change the terms later simply doesn’t cut it.
I held off signing the NDA on the basis that it would interfere with future businesses I might be involved in. Now, I’m glad I made that choice, because it seems clear that CouchSurfing (Casey) have no intention of producing an NDA I would be willing to sign.
CouchSurfing.com is back online after almost 20 hours of down time.
This downtime was especially frustrating for a number of reasons.
1) It was unannounced. Even on the public developers list, there was no forewarning of the upgrade. No doubt travellers were left stranded while the site was down for almost a full day.
2) It clearly wasn’t planned well enough. There are so many willing and skilled volunteers who could have helped with this upgrade, if it weren’t for CouchSurfing’s ludicrous NDA.
This site has been getting quite a bit of attention so far. Couchsurfers are responding to these issues from all sides, both positively and negatively. Overall, it can be said that the majority of reactions respond positively to the concept of more openness. The main objections are to the style of communication and to individual campaigns.
Why in this (direct and not so subtle) way? Why not through the organisation itself? Why now? Why not wait for … (insert something here)?
The Wiki main page adresses this more thouroughly, but simply put:
Things that have been long overdue:
On a side note, we’re trying (as per some people’s suggestion) to present the “other side” of the argument as well. Please help us complete the Wiki with pro’s and con’s.
Mattthew Brauer is one of the people who is involved in the creation of a new Non-Disclosure Agreement (NDA) for CouchSurfing. The current NDA is simply ridiculous, it transfers all trade secrets from the volunteer to CouchSurfing. A trade secret is a very ill-defined term that literally can include anything you can think of, such as “programming techniques” and “software patents”. The NDA should be limited to giving CouchSurfing a license to use the work of the volunteer, it should not try to transfer copyrights or just ideas.
My main concern for the new NDA used to be this part. A secondary concern is the non-compete clause, which forbids the signee from working for related organizations or companies, which is, again a bit vague. It could mean that if you sign the NDA, you can’t work for any other website. Or you can’t work for a travel agency.
When I signed the NDA in August 2006, Casey told me the NDA would be changed. This year I found out Casey Fenton had already been promising a new NDA in June 2006. It’s nearly one year later and no draft has been shown to people outside the Leadership Circle. Mattthew, one of the people who was working on this wrote yesterday:
I support a reasonable non-compete clause. The non-compete clause will apply only to other travel related social networks and will last for one year. It’s good for CS to require a commitment from volunteers. They have to make the choice to work for CS over competitors, and if they make that commitment, they are likely to be dedicated and motivated. It’s also safest for CS to ask that volunteers don’t immediately go work for competitors with the knowledge they’ve gained from CS.
…and I am deeply shocked. I know that many CS volunteers are also volunteers for Hospitality Club. I know that most people don’t give a damn about whether it’s called CouchSurfing, Servas, HomeStay, WWOOFing, WarmShowersList, BeWelcome, or WhatEver, as long as they meet interesting people. Most volunteers care about the mission of all these organization a lot more than that they care about the individual organizations.
And what about Hitchwiki, Wikitravel and other websites created by travelers. Add “friend links” and voila, suddenly it’s a travel related network, and anyone who has signed the NDA for CouchSurfing can’t work on these projects anymore.
from feeling part of something bigger, from responsibility. Someone who takes the step to find out how to volunteer is already motivated, and in CS, if they actually get to do something they must have been truly very dedicated, going through mires of information, contacting many people without getting replies. Commitment doesn’t come through the force of law.
If there will be any non-compete clause in the new NDA, I will stop doing any work for CouchSurfing and demand that the NDA I signed in August is declared void. I am sure that other technically inclined people will do the same. Since the NDA is also supposed to be signed by many more people CouchSurfing will loose a lot of its core volunteers, the people who have been struggling for more transparency, who have been working off their asses for free, and who have been able to keep the site running. If they leave, CS will be left amputated and there will just be a core of people who highly value secrecy and prefer to work with people who think the same as they do and with whom they have been close friends with for a long time.
P.S. If there will be a non-compete clause the OpenCS project could be terminated very soon: Yesterday I heard it’s likely that BeWelcome will soon release their code under the GNU General Public License.