Tech Brainstorming

The CouchSurfing Wiki, an informal workspace which anyone can edit.

This page is for any and all ideas anyone of us has (that might be too techical to be exposed to non-developers e.g. in CS Brainstorm or Ambassador's groups).

Contents 1 Somewhat regular online team meetings 1.1 Chat 2 User Profile Security 3 Developer communications 4 Dev server 5 Beta test server 6 Database schema 7 Encryption 8 Public TODO list access 8.1 Public access? 8.2 Bug info updates / user support 8.3 Essential functions

Somewhat regular online team meetings

To catch up on issues in real time, to discuss more demanding issues where getting instant feedback from others might actually help. (And not to overflow Casey's Inbox even more.)

Chat

CS developers IRC channel, chat room, instant messaging meetings. Freenode is used a lot for this, especially by free software projects. Maybe it's possible to have a moderated room in there.

User Profile Security

1. Encrypt email addresses so that web spiders can't easily pick them up.
2. Encrypt skype, AIM etc in order to prevent easy harvesting of these items. -Chris

Developer communications

1. Having a developer's group within the site for dynamic discussion about this. Here!
2. Mailing list (on Google groups, ask Kasper / Anu to be invited)

Dev server

With SSH access, for easy & secure access to code when your dev-bundle computer is not around. (would come handy sometimes when you're supposed to do the dayjob thing ;-)

Beta test server

Beta test server for developers to collaborate and experiment with. (Yeah there is something already but...)

Some users (10 or 20 or so) can and should be using the beta server all the time. They can be given access to the bug report system. After a while developers should have the possibility to put stuff on the beta server themselves. Casey can be the release manager, and move stuff from beta to the real thing.

In the future it will be good to work with specific releases.

Database schema

WOuld be cool to have database schema available in some visual form. Preferably produced by automated tools, any suggestions anyone?

Encryption

• Encrypted e-mails for developer issues - if there's some more sensitive information such as server passwords etc there should be a secure way to spread this info (Anu)
  • But senseless if you then use those passwords to log into plaintext systems (like FTP) Guaka 16:31, 17 August 2006 (EST)

Public TODO list access

There's a strong pressure from CS community to be more open about bug fix / feature implementation status. More transparency is required!

Public access?

It would be even cooler to give people access to the bug lists itself. Only problem is security issues. Maybe it's possible to give public access to all but the Urgent bugs. Write access should be limited to adding comments. On the other hand, urgent bugs are the ones users are usually most concerned about...

In free software projects bug trackers are usually completely open to the public. See bug-tracking at Producing OSS and also Users to volunteers.

Bug info updates / user support

Related to the latter. More effective reporting on current, most debilitating bugs in the system is needed. Contact us page now has a list, but

1) contact us might not be first thing new users look at

2) that information alone does not help users to solve a problem, something suggested in this post would be better

SUGGESTION: How about adding a Help/Member support page under the Info tab? And link that from Contact Us page. With current bug info AND how to live with an existing bug?

Starting a draft page to collect some threads from the Cockroach group. Troubleshooting

• Public bugtracker: DONE
• Bug info updates: from Bugtracker to Cockroach group, partially covered by wonderful volunteers who stepped up themselves (MIDSCH, BSIRIUS & GEVA deserve a special mention)
• From Bugtracker to single page on CS Tech News, with info about
  • Bug workarounds
  • Fixed bugs
  • New & upcoming features

Essential functions

As in, what should be up at all times to ensure core function of the site: finding couches. If bugs need to be prioritized, any problems with any of these should always be taken care of first. (Point made by Rico to Anu: focus on these first, the bells and whistles can wait until these are quaranteed to function.)

• Login - point of entry for everything else
• CouchSearch
• Profile - core information necessary to find a couch at least should be available
• Messages - and their delivery to the email address of the user

+ Locations (missing cities, wrong states etc. -> Wrong locations page)