Streamlining developer involvement

Streamlining developer involvement in CouchSurfing: making it easier for people interested to actually participate in coding.

Solidifying programmer coordination

Find the right way of communicating, through the Wiki, CS Groups, the Bug Tracker, the mailinglist

Starting long-term technical projects

• Could be as simple as assigning responsibilities for specific parts of the site or sub-projects for people joining the collective based on their interest and ability, continuing participation beyond the collective.
• One example: Ride-share subsystem (or any other of the requested features found in the Brainstorm and other CS groups and Site improvements page) could be drafted out at the Collective with the help of local non-tech participants and relevant branches of the off-site organizational structure, while finishing the code and maintaining it could and should continue after the collective.
• Telephone Surfing?

Defining a feature development process that works for CS

• Taking into account huge diversity and global nature of the organization, using any existing "business process" might not work for us
• Should be: participatory and transparent
• Do-ocracy-based?
  • Wiki and Bug Tracker

Developing coordination with non-technical feature development parts of the CS organization

• What are non-technical feature development parts of the CS organization?
  • Any sub-branch within the org structure that might need developer resources at one point. Example: implementing new security features for members or admins (security branch would need "trusted" developers).

Convenient and safe way of giving CouchSurfing programmers

1. Clean(er), (more) object oriented code
2. Security audits
3. Separation of sensitive code (e.g. credit card stuff) from non-sensitive code

Bug reports

• Set up a Report bug link, so that feedback will include very useful information.