This site was archived on 24 April 2012. No new content can be posted. The mailing list remains online and the site will stay in this archived state for the forseeable future. If you find any technical errors on the site, please contact Callum.



Monthly Archive for May, 2007

BeWelcome

During the first week of the CS Collective in New Zealand I heard about the rumors of Hospitality Club volunteers who decided to finally break away from Veit to start a new network. I was very excited about that! I discussed it with Casey. He saw this as an opportunity to attract more volunteers to CS. I uttered my doubts about that. Better let the HCvols continue whatever they were doing, and stick to cooperating and finding ways to communicate. So even though I perceived some sense of bureaucracy, I tried to become a volunteer for BeWelcome.

Unfortunately it took 6 months before I actually was given access to the BeVolunteer wiki and the non-public part of the forum. But considering the hundreds of people who never ever heard back from CouchSurfing after indicating their offer for help right after the CS Crash 1.0, half a year is not that bad for a brand new organization!

On the wiki I saw that 13 out of 14 people had voted to release the software under the GNU General Public License (one undecided). In the forum I saw that people were having meaningful discussions and that everyone is open to ideas. I saw that about half the Board of Directors of the official organization had been replaced by new people. I noticed that releasing more information is mostly hindered by trivial issues – finding and removing personal information on a wiki takes time. The source code is not (yet) as feature rich as CS, but it’s built on a decent framework, and it looks amazingly clean – in comparison.

BeWelcome does not yet have a super nice running system, but everything is in its right place, or Coming Relatively Soon: free software, a fairly representative official power structure, open data, and transparency.

P.S. the founders of OpenCouchSurfing were aware of BW, but remained sceptical. The main goal of OCS is still a more free and open CouchSurfing, but at present volunteering for the newly born BW seems a much more efficient way to achieve a free and open hospitality exchange network.

In retrospective

During all recent events I often thought about what must be going on in Casey’s head. He’s the one pulling the strings. Then I remembered an email I received from Casey Fenton, a long time ago, November 29, 2005 10:01 PM to be exactly.

Subject: Censorship in Hospitality Club / CS

Hi Kasper,

I was just sent a link to your page about HC censorship.
(http://www.industree.org/guaka/index.php/Censorship_in_Hospitality_Club)
You said: “The thing that I find most revolting is that it, at least to
me at this point, seems such a closed process. Rules are somehow being
set up, and the 90000 members of HC are just to follow them.
CouchSurfing has actually the same problem, and I think it will be good
to address this.” I was wondering what the problem is that CS has that
you’re referring to? We always want to make sure that we’re doing
things right… and it there’s something we’re not doing right, please
let us know! If you need any questions answered, I’d be happy to answer
them.

btw, love your photos… especially the one of those kids in Bamako and
the one of you on the beach with the guitar.

Cheers,
Casey

Which implies that Casey read about the ideas I have for hospitality exchange a long time before we actually met in Montreal. As Joe wrote: “Many aspects of CouchSurfing have been marred by these issues: (a) a tendency to do
things in the dark, (b) a tendency to tell people what they want to hear, and (c) a tendency to work *near* people, but not *with* them.”

Sometimes I feel sad, sometimes I feel bitter. But…

Life is still good, though I hope that some things will change. In my opionion there are several principles a free hospitality exchange network must follow:

  1. Open policies
    It should be clear what is going on. Policies and guidelines should be accessible by anyone.
  2. Democratic processes
    All people making part of the network should be able to take part in discussions.
  3. Open data
    People should be able to “take” their own data in a portable, open format onto their computer, into their phone. It should be possible to give permission to others (based on a trust level) to copy part of one’s information. Similar to ideas implemented in Indyvoter (http://beta.indyvoter.org).
  4. Free software
    Like Wikipedia, hospitality exchange networks should be based on free software. This will attract more programmers, open up new possibilities (like integrating electronic authentification and encryption (http://en.wikipedia.org/wiki/GnuPG) or efficient access on portable devices (http://hardware.slashdot.org/article.pl?sid=05/05/25/139202&from=rss), extending it into a getting-car-rides system where drivers and hitchhikers can get in touch using GPS…).

I’ve Been Fired!

This morning I woke up to find an email in my inbox telling me that my volunteer services are no longer required by CouchSurfing.

Apparently I have “fundamental differences in ideology and communication styles”. I’ve asked for clarification on that, fundamentally different from whom. I’m not holding my breath for an answer!

One thing was stated clearly in the email, CouchSurfing is not going open source. Not now, not any time soon. So at last the OpenCouchSurfing campaign has received one answer. That’s real progress I think.

Interesting times… :)

A final goodbye

I have received a “thank you” letter from Chris Burley that effectively closes the NDA discussion and other related matters for me. To be honest I’m quite grateful for it.

It is much better to know that the Couchsurfing admins really don’t want to discuss our issues than to be left with a false glimmer of hope. CouchSurfing has – for good or for bad – decided to show itself as a top-down run community and while I don’t agree with that decision, it is at least clear and final.

There are a few small corrections I would like to make (read the letter first):

  1. OpenCouchSurfing was primarily about a Free and Open CouchSurfing organisation. While OSS (Open Source Software) would certainly have helped in getting there, it was hardly the only proposal that has been made. For me personally, an Open Organisation was a much more important issue for instance.
  2. “We value group consensus above individual ideology” seems a bit weird to me. We had over 90 people signing the petition, including two admins, so its hardly an individual ideology. There were many people that really would have like to see some of our proposals come true, but unfortunately we don’t have the keys to the castle.
  3. As has happened before, Chris makes it sound like it was more about style than about content (“constructive criticism”). I think most people will agree that there has been ample opportunity to engage in friendly debate for the admins, which was never taken up. Most critical (but friendly/constructive) questions have simply been ignored over several months. It should be of no suprise that this angers people in many ways and it is therefor quite unreasonable to expect friendly banter all the time. “We’re working on it” or “we’ll publish something… soon” can hardly be considered constructive debate either.

In conclusion I would like to personally thank everyone who has tried to help us make a positive change within CouchSurfing towards a more Open and Free organisation. I do not feel that this was a wasted effort as getting the admins to make up their minds is an added value by itself. Amongst the relatively few cases of outright hostility, there were plenty of comments that helped us to continue this extremely difficult effort. Thank you for that support.

“A new discussion about improving the NDA”

Chris Burley announces new possibilities:

We agreed about the following action items
1. Triple T, Casey and I will start a moderated public working group
inside CS groups to invite current and future volunteers to ask for
feedback on the NDA. We will allow feedback and suggestions for
improvement and do our best to include this feedback into a revised
version.
2. I personally will contact two unbiased corporate lawyers who have
experience in international law and have offered assistance to ask for
their help in drafting certain portions of the NDA which are in
question.

I hope this means that the current draft will be scrapped, but anyway,
this message is all very very positive compared to the whole draft itself.

Kasper

The horror! The horror!

The fun never stops:

  • The proposed Volunteer Agreement in all its paranoid glory. Read it and weep.
  • Appearantly the tax ninja that wrote it* is on the Board of directors! Who knew? (Hint: noone.)
  • We’re also keeping track of everyone that quit or will never start developing for CS because of this fiasco.

That’s all for today.

*: Or copied it from here. CS really seems to have problems writing original text. Maybe they need a copywriter to volunteer for that?

A Sad Day for CouchSurfing

At least three volunteer developers have resigned from the CouchSurfing Tech Team on account of the new NDA that all volunteers will be required to sign.

The new NDA includes a non-compete clause preventing volunteers from working with any other travel or social networks. It also requires that volunteers transfer their Intellectual Property rights to CouchSurfing International Inc.

I heard that somebody describe it perfectly, they said “it’s not volunteering, it’s slavery”.

Round up

It is difficult to describe just how shocking the last 24 hours have been. The final result is pretty clear though: instead of taking any practical step towards Openness and Freedom, Couchsurfing has decided to take the path of a closed, protected, corporate-like structure.

A brief history:

  1. Sunday 6/May/2007: OpenCouchSurfing.org is launched after about 2 weeks of preparation. It was the result of months of uncertainty and dissatisfaction in the development group. First real reaction comes from Leo (who later turns out to not be a part of the “inner circle”. No “official” reaction.
  2. Wednesday 9/May/2007: The CS site goes down for 18 hours to upgrade the database. No warning to the tech team. Casey finally proposes to talk over the phone with me; on Sunday.
  3. Thursday 10/May/2007: Casey announces the Leadership Circle. Couchsurfing will be run by a self-appointed and closed group of (mostly) his personal friends.
  4. Friday 11/May/2007: Casey suddenly and unannounced decides to move the SVN server with all of the CS code, quoting “upgrades”. It stays offline until today and now everyone has to reapply for commit rights.
  5. Sunday 13/May/2007: I finally get to talk to Casey over the phone. He tells me he doesn’t want “politics” in Couchsurfing and clearly has no real-world knowledge or experience with code licensing. We agree to try and investigate two things together: a community code license of sorts and some form of elective experiment to determine a tech team “coordinator”. We agree to call again the next day. It gives me hope. (False hope as it turns out.)
  6. Monday 14/May/2007: Casey postpones the phone call by a day. He’s too busy communicating with others.
  7. Tuesday 15/May/2007: Everything seems to happen at once.
    • All day long, there is a flame-war (warning: long and ugly) between Naz (a completely new and unknown developer since 2 weeks) and Kasper on the developers mailing list. Naz is simply nasty and basically tells Kasper to take a hike. Chris Burley, our “tech team leader” does not step in at all.
    • I talk to Casey on the phone again. He basically states that he wants to split CS into a “staff” of sorts and “volunteers”. Ambassadors would be mere volunteers and developers would probably have to be split into people within and people outside of “the circle”. (I’ve now come to understand that they simply don’t want developers outside of the circle.)
    • Morgan Tocker resigns (see his Blog article).
    • Appearantly the long awaited NDA is now called “Volunteer Agreement” and is sent in secret to “core devs”, including John, Walter, Naz (who has been a developer for 2 weeks!) and Anu. Kasper, who has at least 1/3rd of the code commits to his name, is not included as a “core dev”. We learn all of this by accident. Chris Burley chats with both Kasper and me and tries to talk “off the record” with me, which I decline. We know it contains the following:
      - Automatic transfer of all intellectual property (=ideas) to CS.
      - A non-compete agreement, which basically states you can’t work on any travel or social network site simultaneously or 1 year after volunteering (working) for CS, profesionally or otherwise.
      - A complete gag order. You are not allowed to discuss anything “internal” with non-NDA people.
    • Kasper resigns.
    • Chris Burley offers me the Volunteer Agreement document, under the condition that I don’t talk about it. I decline. He tells me certain people might get “exceptions” to the NDA rules.
    • I quit.
    • After at least three people tell Chris that he should have stepped in with the Naztyness on the mailinglist, he finally does. The discussion is by that time already long over and done.

After that, there was a mixture of saying goodbye, total apathy and more nastiness (style: “Glad you guys are gone”). The Leadership Circle still doesn’t have the guts to publish the Volunteer Agreement.
So, what are we left with after 1,5 weeks of campaigning?

  1. A completely closed CS organisation that is heading for a semi-commercial structure. Volunteering is considered second rate.
  2. An NDA/Volunteer Agreement that is probably 3 times worse than the previous one. In all practicality, no IT professional could ever sign it, unless you never want to work on travel or social network related websites again besides CS.
  3. Open sourcing, transparancy and representation seem farther away than ever. They have succeeded in getting Kasper to quit, which clearly was something they wanted. “Not a core dev” is probably the closest one can come to being tarred and feathered.

To put it simply: OpenCouchSurfing has failed miserably in its goals. Even though around 70 people ended up signing our petition, including Heather O’Brian and Jim Stone (both part of the Leadership Circle), none of it made any difference.

Have we made matters worse? I don’t think so, because clearly these things were already being planned for a long time. We have however clearly accelerated the process and discovered things that were meant to be kept secret. The back-room dealings, the secrecy, the buddy-systems, the social manipulation, all of these things are not new to me and can happen in any organisation. The scale and rate at which they happen in Couchsurfing, an organisation that boasts a mission to “Participate in Creating a Better World, One Couch at a Time” is however frightening.

There are only three options left:

  1. Waste energy and time whining and being ignored.
  2. Start taking destructive action.
  3. Bow out.

Out of self-respect, I will obviously choose the latter.
The End.

And here I go

I said I would continue to contribute if it does “more good than harm,” but I’ve decided to change my stance on an issue, and I’m resigning from the CS dev team & mailing lists.

Prior to working on couchsurfing, I decided that I only wanted to work on Open Source software. When I heard that Kasper was pushing for couch surfing to be open it sparked my interest.

Open source is important to me, because it represents a freedom of information and ideas. But for the record, it wasn’t the non-opensource thing that made me leave per-se; it’s the resistance & lack of communication to comment on, or work towards a New NDA.

Maybe I should hang on and wait, because something is right around the corner?
These issues are old, months old. Now I’m cynical enough to think a delay or a ‘not now’ is a politically correct way of saying ‘no’. So, I’m now changing my tactic; If they get addressed then I’ll rejoin.

There’s no reason we need a non-compete clause. I had contemplated signing a non-compete that still permits me to just work for MySQL; but now I’ve decided I’ll choose who I work for.

I had some good times at the Collective. My two most treasured memories include learning how to drink scotch and beer with Gardner (a first for me, and a lesson that will no doubt further me in life), and performance hacking with Joe & Kasper in a 3-way screen, sitting next to each other.

Walter: I’d like to still come and visit the Collective, but I’m withdrawing my request to participate. I enjoyed seeing your comments on MySQL optimization, and that you could also spot so many of the changes that needed doing. It’s unfortunate we didn’t really get the
change to work together.

I’ll still keep couchsurfing like everyone else, so keep making the site better!

Deconstructing the Leadership Circle

Wow. Within a week of launching OpenCouchSurfing, we’ve seen an immediate upgrade to the CS DB (resulting in the site being down for 18 hours). They (*) have announced upgrading the webservers as well (to reduce the current security risks). The “Leadership Team” has finally been made official. Now, some of these things have been announced before (the DB upgrade and Leadership circle), but it seems like to much of a coïncidence that all this happens in one week. So, this effort seems to have good and positive effects which strengthens us to continue to improve things.

What I wanted to talk about is the Leadership Team. At first view, it seems like it is indeed a step in the right directon. At second view it actually makes matters worse and formalizes the closed culture of CS. Let’s have a look, shall we? The most important sections to pay attention to:

  1. To become a new member of the leadership team (after May 2007), a volunteer must have been an ambassador in good standing for at least one year.
  2. To become a new member of the leadership team (after May 2007), a volunteer must be approved by consensus (unanimously) by existing leaders.
  3. [For a leader to remain active, he/she must] produce a biannual departmental progress report and goals for the coming semester.
  4. Ambassadors may officially censure any one or more leaders. Censure requires:
    - a petition of specific grievances endorsed by a simple majority of ambassadors
    - the leaders to immediately make a public statement regarding the planned course of action to correct the grievances.

What does this mean in practice? A boys club. You are not allowed in unless you are in good standing with the Leadership group, because they hold each and every means to allow or disallow you. Dissenting ambassadors are explicitely discouraged from even trying to apply (“in good standing”), not that they could get in anyway. Oh, wait. There is no application process defined. Never mind. But there’s no official end to a Leadership position anyway, so we don’t actually need candidates. But hey! Ambassadors can censure a leader, right? Uhm. No. Leaders are only required to make a public statement regarding the “planned action” to address this. Case closed. There is no way in and no way to get anyone out. A proper way to do it would have been to let the ambassadors actually vote for their “leaders” every year or so, but I guess that is too threatening for the existing power structure. The current state of affairs is just outrageous.

Transparancy by biannual reports? This is not transparancy, this is PR. We need insight into the decision making process and there need to be tools in place to ensure accountability, not just promises of “focussing on the mission”. We don’t need binannual PR reports.

Funny intermezzo: Look at the Leadership Qualities page. Now have a look at the self-evaluation form for level B registered nurses. E.g. “Teamwork: Interacts effectively and builds respectful relationships among individuals and in teams” (leader) versus “Teamwork: Interacts effectively and builds respectful relationships within and between units and among individuals.” (nurse). Some requirements are copied almost verbatim. So, are we getting leaders or nurses? On a more serious note, this is indicative of the increasing use of marketing speak coming from the Leadership Circle. They’re not talking, they’re making announcements/press releases. This is no way to treat a community run by volunteers. And it doesn’t speak well for the effort put into this document that parts are just copied of the net, it definitely makes it seem like a rushed PR job.

What is all of this lacking?

  1. Real transparancy. Where is the agenda/meeting notes section for the Leadership Circle? Where is any serious timeframe for anything? Biannual? When? In 6 months? Tomorrow? These people have consistently shown an unwillingness to commit to any kind of deadline, which is plain bad leadership. Slipping deadlines? Fine, worst case for that is a bunch of angry people and a bit of stress. No deadline? Not acceptable.
  2. Real representation. Not another boys club system please.
  3. Where the hell is the new NDA? It was announced half a year before the Leadership Circle was even mentioned. It shows you where the priorities are. (Hint: Power, not your average volunteering developer)

Say no to the circle of level B nurses**. Write to them and demand direct representation, transparancy and accountability. Help us make CS more Open and Free.
*: There has been a lot of complaining about using “us vs. them” language, which is just annoying. Raise your hand if you don’t know who “they” are. You’ll know when you’re not part of “them”.
**: It’s called humor people.