Transparency guidelines
The CouchSurfing Wiki, an informal workspace which anyone can edit.
Make CouchSurfing an Open Organization
Transparency guidelines • Transparency discussion • Adhocracy • Self Organizing Volunteers • why we work on CS
Goal
In the interest of creating a better functioning organization, CouchSurfing will provide that its leadership and internal practices are open to scrutiny and input from all members in such a way that does not compromise the efficiency or security of the organization or violate member privacy.
Guidelines
CS website describes the leadership team, including:
- who is on the leadership team and their specific roles (still being decided)
- how new leadership team members are selected from the general membership (still being formalized)
- the leadership team’s role in the organization and community (basically an inspirational & strategic role vs. tactical)
- how the leadership team receives input from the community (basically through core volunteers who are project leaders)
CS website documents leadership team actions, including:
- biannual leadership team reports announcing team's specific strategic goals for the next six months (coming soon)
- any final documents, guidelines, procedures, etc. created by leadership team (coming soon)
Note that the guideline does not require the leadership team to document their internal discussions, or to
document individual team member’s position on an issue. This allows the leadership to brainstorm and
strategize internally, then release well thought out decisions and documents reached through team consensus.
CS website describes organizational departments, including:
- who are members of each department, and who is head is each department (still being formalized)
- how members are selected as department heads (still being formalized)
- each department’s role in the organization and community (the departments are still being defined. But basically departments handle tactical decisions)
CS website documents organizational department actions, including:
- biannual reports from each department on it's specific accomplishments and its future goals (coming soon)
- documentation of all departmental discussion, except when that would violate member privacy or risk website security (exists now!)
Note that “departments” includes ambassadors. Note that the guidelines do require documented discussion
in the case of departments. This public discussion allows the general membership to keep track of most
decisions affecting the website, give input, and become department members.
CS website describes administrative process, including:
- descriptions of each type of administrative power (from approving a meeting message to reading private messages)
- a list of members with administrative powers, including which powers (e.g. safety team member can read private messages to mediate member disputes)
- how members are selected for administrative powers (still being formalized)
- how the membership can communicate with these administrative members (still being formalized)
- members who are affected by administrative actions will be notified, except when that would risk website security (exists now!)
Note that the guidelines do not require a log of specific administrative actions that have been
taken because these actions are almost never relevant to the general public.
CS website documents organizational finances, including:
- an explanation of how the budget is created and by whom (still being formalized)
- categorized income and expense reports for previous years (including dollar amounts) with a reasonable level of detail (coming soon)
- a budget for coming year (coming soon)
CS website describes and documents Collectives, including:
- definition of a Collective, including how one can be started and awarded funding (still being formalized)
- description of each Collective including its specific goals, its time-frame, and how members can participate (exists now!)
- financial reporting for each Collective (coming soon)
- monthly documentation of each Collective’s accomplishments (exists now!)
See also transparency discussion
