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.



Archive for the 'Casey Fenton' Category

Page 5 of 6

Valeri on Project Management Improvement and Communication

Valeri on Project Management Improvement and Communication.

I’m removing this text, since it’s slightly out of context. You can find it through clicking on the link though. — Kasper, September 13th 2007

CouchSurfing NDA Lessons

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.

The beginning of the end of CS 2.0

“It just feels bad to be asked for help and promised something in return by the captain after he set the boat on a riff and than when the ship is running being told: ‘What do you want here? This is the captains lounge. I’ve hired professional help now. You are just a stupid little member. Now stop whining, go down to where the swimming pools are and have fun.’ ” – Torsten (from the Brainstorm group).

As someone who was present in Montreal during the week of the crash, I can add some detail to the Captain’s behavior in those days.

We have been told that the particular combination of events leading to the crash (“The Triple Storm”) was highly unlikely, but even if accurate this excuse for the disaster obscures the fact that the organization’s extreme dependency on Casey in the technical area was a great vulnerability to the organization, and a disaster waiting to happen.

I believe this dependency was not due to the lack of willing, trustworthy and qualified members to spread the responsibility among (and thus provide redundancy and checks and balances), but to Casey’s intention to maintain control of the website and thus, in part, I strongly suspect, justify his privileged (and salaried) position. i.e., If others were doing all the work Casey was doing voluntarily, then it would be harder to justify being the only salaried member of the organization.

If the major crash was unavoidable (we’ll never know for sure), certainly many of the chronic server problems since then, that at times put members traveling in foreign countries at greater risk, were really a direct result of Casey’s policy.

A few days after the crash, Casey terminated the Couchsurfing Project. He did not discuss this with any of the members at Montreal that I talked with: people who had traveled from great distances at their own expense and on their vacation time to answer the call for community participation. It was as though in Casey’s mind, CS was the website and with the website gone (in his opinion) there was no CS.

But most of us there understood that CS was not a website but a community. The Community still existed and needed to come together for each other more than ever. Especially, there were members out on the road, traveling in foreign countries, using the website to make contacts with hosts as they went, many on a low budget who couldn’t afford to just start staying in hotels. It was the beginning of summer, and many others had made vacation plans based on CS. These people needed our help and support. Casey abandoned them.

I was stunned by Casey’s behavior. Not knowing him, I just assumed that there must be factors I did not know of, and gave him the benefit of doubt.

There was a leadership vacuum immediately following the termination, as Casey was absent for much of the time. Members were dazed and directionless, wondering if they should just go home. I organized some meetings, as did Heather. I proposed that the first order of business was to take care of the members. I suggested that we set up message boards on some free site so that members could at least communicate with each other. All agreed and we got to work right away.

Once we were set up, there was only one problem: how to let members know about the message boards? We knew that the home page of couchsurfing.com was still working. So all we needed was an announcement with a link to the message boards put on it. It took about a day to find Casey and get him to put the link in place. No one else could do it because Casey was the only one with the password to the servers.

The next order of business was to get the website back up. While Casey was still out of the picture, we made a group decision to bring back CS any way possible, however long it took. This was the true beginning of CS 2.0.

We knew that the software was not lost, only the data (i.e., members personal information and friendship links). So, the website could be restarted quickly, but members would have to re-register and re-establish their friendships. If this was the only obstacle, I could not understand why Casey would shut down the organization, unless perhaps, he was burnt out and just wanted to be done with it.

One thing very crucial here is that Casey did not offer the community access to the software. We could have quickly (in a matter of a couple weeks at most, which is how long it took anyway to restart the site with salvaged data) brought the site without the data. There was a tremendous, self-organized offering of support from programmers all over the world. They even formed themselves into teams and began extracting member data from Google’s caches. This was the community I was proud to belonged to and wanted to support.

It was clear that Casey considered the software to be his own property, not the property of the community, and he was not willing to just give it to us. The Captain had abandoned the ship and took the steering wheel with him, being willing to let the ship sink rather than give up control and let others save the ship.

In this crucial meeting, I personally committed to take the responsibility to rebuild the website myself, if necessary, but was sure many would help in the effort. I would have done it free of charge and claim no ownership of it. Also, I would have always been accountable to the community, and followed their guidance and stepped down if they asked me to. But I was a new member, and did not have a reputation within CS. Heather, who was an Admin, argued that “we have to get Casey back on board”. She held sway. I did not know at the time that she was romantically involved with Casey (or so I have been told), as this was kept discreet.

Over the next few days, pleas were made with Casey to come back, led by Heather, although, at least, the group insisted that the new CS must be different from the old, and that there should be much more emphasis on member participation. Casey agreed to this. In Heather’s word’s: “CS should not be about just one person”. Heather even expressed that the crash was a blessing in disguise, and urged that the recovery be delayed if necessary to ensure that fundamental changes were made and that CS did not just return to business as usual.

Casey tentatively agreed to explore the possibility of reviving CS, and when he began to have success recovering the data, resumed control over the project. I was relieved at the time, because Casey’s return meant that I could go on the vacation I had planned. But now I realized that those few days were the one chance for CS to become a truly community-based self-governing organization. The seeds of the demise of CS 2.0 were planted almost as soon as it began.

John

Follow the money

To anyone who is trying to sort out what is going on in CS and who to believe, I suggest you apply what many consider to be the “First Rule of Investigation”.

“Follow the Money”.

Something very significant happened to CS during the year since CS 2.0 was launched as a volunteer-centered community-based enterprise. The corporate income drastically increased from a level where there was barely enough to make ends meet, to a big surplus, with the reasonable expectation of much more to come.

It doesn’t take much imagination, knowing human nature, to construct various scenarios that would explain much of what has happened in CS. It’s a certain fact that Casey, at the very least, from early on, was leveraging his position in CS for his own personal profit.

“Site design by Casey Fenton Consulting”

used to appear at the bottom of all emails to members and (if I remember right) every page on the site, with a link to his personal business. Now, this, in itself, is not necessarily a problem. Whether it is or not has everything to do with with impressions given to and agreements made with people who signed on to do do full-time volunteer work for what they thought was a noble cause, for a community built specifically on the value of freely giving without expecting a financial reward, and who literally saved CS from termination.

Things are going well for a young rapidly growing volunteer enterprise, there is tremendous community spirit, creativity, new initiatives, large numbers of highly talented people wanting to get involved. And then suddenly, the rug is pulled out from under them. Some of the most active and committed volunteers are made to feel unappreciated and all but shown the door. Announcements come down about new paid positions for Casey’s close associates.

We are told paid employees are needed to do the necessary tasks that volunteers won’t do, because they tend to do things on a whim. I, myself, had spent 5 months doing nothing but things that needed to be done, fixing hundreds of bugs, postponing my “whim” project (which would have greatly benefited the community, I believe, but never happened). I did all this in spite of the LT, who for the most part, were unresponsive, non-participating, prone to arbitrary assertions of executive authority without understanding the situation, and even at times seriously undermining worthy, community-based projects.

We are told democracy can’t work in an organization like CS and that voting is impractical. Aside from any philosophical arguments, the plain fact is that democracy and voting are happing right now in bewelcome.org, and very successfully, I might add.

These kind of statements defy logic and reality, so why would they be made? Just look at the result: concentration of power and money in the pockets of Casey and his hand-picked associates. A paid developer will be hired, who will do what he or she is told, to replace the 6 highly qualified computer professionals who used to work for CS but are now working for BW, where their individual creative ideas, personal ideologies and cultural diversity are welcome and valued.

We question all this and are branded “whiners” and “CS-haters”.

I would never have given a good part of a year of valuable service to CS if I had known where it was headed. When I started having concerns about what the Admins were up to in their secret meetings back in December, I wrote a long, detailed, thoroughly documented letter to them. It was entitled “Request for Information from the Admins” (approx.). It was posted in a CS group named “CS Core Volunteer Communication” (approx.) created specifically for the purpose of allowing for communication between volunteers and the Admins, who previously were unavailable for communication as a group, and could only be communicated with through a liason.

I specifically mentioned problems with responsiveness, participation and arbitrary assertions of power. I expressed concerns about accountability. I said I was in CS to work freely for the community, and was not willing to work for Casey and/or the Admins if they were not accountable to the community.

The only response I got from the Admins was, from one of them, “Your letter is too long, so I’m not going to read it.” (approx.) This is when I became very concerned.

I started paying more attention to the NDA issue, which was very troubling to me, and I had only accepted it provisionally with the assurances that “it is being worked on and will be fixed soon.” (approx.). It was already going on 6 months.

I wrote another letter to the Admins after about a month or two, reminding them I was still waiting for a response from my first letter, and amplifying my concerns, which continued to be validated.

There was no response from any of the Admins who were in power before the crash.

Now, in retrospect, knowing what they were working towards, I believe I may have been allowed to continue to work for free under false pretenses, while the LT was planning to use the increasing revenue which I and many other volunteers were helping to generate, to pay some of themselves, without my permission or the permission of the other volunteers.

If this is what really what happened, and the total absence of meaningful response to my two inquiries was not just sheer incompetence or negligence (and how can I know when so much is kept secret), it was an ethical breach and I and the other volunteers have every right to feel mislead and disrespected. We certainly have the right to challenge the LT without having our credibility and integrity questioned.

So, to you new investigators, I suggest, follow the money and judge for yourself.

John

CouchSurfing is Hiring

It was announced yesterday that CouchSurfing is seeking to hire a full time developer. They’ve just hired two core volunteers (Jim Stone and Mattthew Brauer). Where are they getting all this cash from? If they’re each paid $2’000 USD a month, between those three and Casey, that makes $96’000 a year.

So the CouchSurfing Corporation is finally starting to pay off…

CouchSurfing Didn’t Crash

It would appear from this thread on the MySQL forum that CouchSurfing didn’t crash in late June 2006, but the database was deleted. For non techies, DROP is the database command for delete. According to the thread, posted by username Casey Fenton, a DROP TABLE command was issued.

The message was posted on 28 June 2006, exactly the time of the alleged “crash”.

If I understand this post correctly, the servers did not “crash”, but the data was deleted. I wonder if anyone else can shed more light on the subject?

CouchSurfing Disappointments

Today I’m reminded of my time in Nelson, New Zealand. I went there, at my own expense, to volunteer for CouchSurfing. When I arrived, I found a job that was urgent. The servers badly needed upgraded, they were very out of date. I researched the situation, investigated a solution, figured out how to do what was required. Then I needed some information from Casey Fenton. I met with Joe and Casey and Casey agreed to pass the information to Joe the following day.

My work was dependent on this information. The information never came. To the best of my knowledge, this information was never given to Joe. My time was wasted.

Unfortunately, I feel this summarises the CouchSurfing “Visionary Leader”. Casey is a great talker, a very friendly guy. When speaking with him you feel like you’re genuinely connecting. However, beyond that connection, in my view, there is no substance. I think Casey is a politician, he tells you what he thinks you want to hear, then he does whatever he was going to do anyway.

It saddens me that CouchSurfing has so many great users and yet such a poor organisational structure. I hope networks like BeWelcome and CrashAtMine will lead to better things.

The CouchSurfing Corporation

Warning: This post contains sarcasm, read it at your own risk. You have been warned.

CouchSurfing recently announced that they have hired two new staff. As we’ve come to expect, there were no interviews, no positions advertised, no visible application process. Instead, Casey invited two of his close friends to join him in receiving a salary from CouchSurfing.

In other news, Chris Burley said in a recent group post, “I wish you the best with democracy, it is known that it tends to crush minority voices. Besides, the majority rarely knows best.” Wow, that’s an interesting statement. But we all knew CouchSurfing isn’t a democracy, didn’t we? Now we do.

One might suggest Chris is in danger of falling foul of the US Patriot Act if he’s not careful. ;-)

Reflections…

…two months after resigning as a CS volunteer, in the form of responses to two calls for an egalitarian CS community in the CS Brainstorm group.

Hello Abrahim,

I appreciate your efforts to bring this issue to the attention of the community again. You obviously put a lot of thought into your post and recognize the critical importance of this to a community which shares the values that we do. I hope I’m proven wrong, but I feel certain that the kind of movement you are proposing would end up going nowhere in CS.

Just over a year ago, there was an excellent opportunity to redirect the course of the CS community away from being under the control of a small elite group, unaccountable and unanswerable to the community at large. This opportunity coincided with a major crash of the servers followed by Casey‘s termination of the CouchSurfing Project. For most of the last year since the community-led rebuilding effort, some volunteers worked towards an egalitarian community, which they thought was consistent with the stated CS 2.0 goal of decentralized participation, while the former administrators of the website redefined themselves in secret. A few months ago, the elite group re-emerged in the form of the “Leadership Team”. These self-appointed leaders are really rulers (if you consider CS as a community) or managers (if you consider CS as a corporation). Leaders generally lead by consent of the led. Rulers need no consent.

Since the Leadership Team members were each chosen (or at least endorsed) by Casey, the owner of the Corporation, and by extension felt entitled to govern the community that has formed around the web site as they saw fit, some of us who hoped for a different CS realized that our cause was lost and moved on, in some cases to alternative hospitality organizations which do have an egalitarian community.

The Leadership Team has clearly taken a stand against democracy. They have taken upon themselves the role of guardians of the CS mission, as they define it. Their “constitution” is as much about protecting their power as it is about protecting the mission. They don’t seem to be aware of the hazards of this stance. It is an easy mistake to make, since they are generally good people with good intentions and a noble mission. But the structure itself is inherently flawed and prone to abuse and corruption. This has happened countless times throughout human history whenever too much power is concentrated in the hands of too few people, even in organizations started by the best people with the best intentions.

As one example of how easy it is for a self-reinforcing group with no accountability to the people they claim to serve, consider the mission of intercultural understanding that they purport to promote and protect. The very essence of intercultural understanding is respect for diversity. Yet, the structure of the leadership team requires unanimous agreement among themselves to make important changes. The implication is that, knowing that one person could bring the effectiveness of the Leadership Team to a complete halt, extreme care will be used to select only those people that will not disrupt the consensus; in other words, people who will not create “divisiveness” or “conflict”, but conform to the established groupthink. This is perhaps the worst possible environment for promoting diversity of values, opinions and ideas, cultural or otherwise. Yet it seems they consider themselves to have a special insight and virtue which entitles them to be the guardians of the CS mission.

I have already seen cases where extremely valuable volunteers have been blacklisted because of what seems to me are mostly cultural or gender differences, or because they had an ideology not in sufficient conformity with the elite’s ideology.

Besides being inconsistent with the CS mission, the LT policies are inherently non-viable according to the lessons of nature, where diversity is the primary guarantee of adaptability and survivability in the face of changing environmental conditions and random events.

Another inconsistency: in a community which is as much about freely giving as anything, truly built upon the generosity of people willing to give without expecting a financial return, how is it that the owner, who should be exemplifying the spirit of the community, is the only one getting financial benefit for his contributions? If someone is to be granted an exception to the otherwise universal policy (so far) of voluntary work, voluntary donations and voluntary hosting, shouldn’t the community, who provides the money used to operate the infrastructure, have a say in this? I’ve heard all the counterarguments to this, but nevertheless I’m certain that CS could be run entirely by volunteers. The fact that it isn’t has not been a community decision.

Without going into details now, there is now doubt in my mind that the lack of participation and responsiveness of many of the so-called leaders in many areas at many times is a symptom of the structural problem (lack of accountability to the community) and the attitude it fosters. (For example: over a year and counting and still no acceptable NDA, something of such grave importance to several volunteers that they stopped volunteering because of this fiasco). Likewise, the chronic server problems and the slow response to member requests for bug fixes and feature enhancements are also traceable to the same problem.

The only possibility I see for CS to become an egalitarian community is for the community to obtain ownership of the Corporation. In other words, buy out Casey. But I don’t think this is realistic considering that perhaps 99% of the users of the CS website are reasonably happy with the free service that it provides. The number of members actively involved in the community (beyond hosting and surfing) are a small percentage of the total membership and of those, only small percentage of us are really concerned with such philosophical and political matters as we’re discussing. There are some other hospitality communities where self-government is considered as important an objective as intercultural understanding, and inextricably linked to it. For me, it is more efficient to start over with one of those communities. Indeed, I was given no choice. Casey himself stated that if we don’t like the way CS is run, then leave and come back later [after all the structural changes now being implemented are locked in - he has veto power over any proposed structural change in the future]. Don’t get me wrong, I like a strong, assertive leader, and even encouraged Casey that way, but any leader without accountability to those led is a dictator, even if a benevolent dictator.

I recommend you think of CS in terms of the Western culture notion of “corporate entity” and all the concepts of ownership and entitlement that go with that, rather than a diverse community of equals with shared values. That may save you a lot of heartache. For me, it is best to think of the new CS as a social website like Myspace combined with a travel website like Expedia. Then, Casey is just a dot.com entrepreneur carefully protecting his investment and his personal vision and getting his just reward financially. No problem with that if you’re a fan of Western corporate culture! (Just be clear about it to potential volunteers: your free work and ideas are welcome, but Casey is the only one who financially benefits from them, and you have no say in that.) We are all free to use what the CS Corporation offers and to go elsewhere if we object to the way it is managed. Thankfully. Just the mere fact that this post will not be censored is a credit to the LT — they ARE doing some things well!

John

   

Responding to David Lee Frazer’s commentary on the “Wolf Pack Psychology” of the LT in another thread:

Hi David:

The following is meant to be taken partly in jest.

I don’t think “Wolfpack” is the best analogy to descibe the LT, although it’s imaginative. I just don’t see Casey as the alpha male of the pack. Brute force is not his means of holding power.

“Monarchy” is a better analogy: King Casey and the Lords and Ladies of CouchSurfing. But most monarchies do not justify their entitlement to power as virtuous protectors of a noble mission. It is enough for them to claim hereditary entitlement, or royal blood, in many cases, or else “might makes right”.

“Religion” is an even better analogy. Pope Casey the First and the College of Cardinals. The Global Ambassadors would be the Bishops, from whom the Cardinals are chosen. The other ambassadors complete the priesthood, and the rest of us are the bleating flock, who are shepherded by the wise and learned Bishops. Very good description, actually. Can you imagine an election for the Pope by the flock ever happening?

Those of use who resigned as volunteers could be thought of as the Protestants and have gone on to find a more tolerant and open cultural milieu. Among other things, we didn’t like the idea of the CS Corporation claiming custody of our creative ideas like a Church claiming custody of our souls. We even had a heretic among us, who was shunned after enormous contributions (Kasper).

The Roman Church began with a noble mission but which over time, due to the inherent structure it shares with CS, erred in many ways. The leaders acquired an attitude of condescension and hubris, thinking themselves infallible, not needing checks and balances. They became enamored of their wealth and power, drifting far astray from the example of Jesus, who wanted neither. Protecting their power became more important than the original mission. Anyone who is ignorant of this danger of concentrated power, or thinks themselves immune to it, is surely vulnerable.

All men having power ought to be distrusted to a certain degree. — James Madison

If I claim to be a wise man, it surely means that I don’t know. — Kansas

You know that those who are regarded as rulers of the Gentiles lord it over them, and their high officials exercise authority over them. Not so with you. Instead, whoever wants to become great among you must be your servant. — Mark 10:42-43

John

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…).