March 14 2007
The CouchSurfing Wiki, an informal workspace which anyone can edit.
Agenda
- Status checks
- who should become a developer: discussion hoping to form a sustainable consensus view, concerns being: developers have more ability change the site than the rest of the community, so there should be either prior approval based on already existing site involvement or way to effectively make sure controversial changes that are likely to stir things up remain minimal
- Defining "controversial change" (XHTML-compatibility is clearly not, personal security features are - making our way through the gray areas)
- New developer intros
- Your tech goals by the end of this collective?
- Status of alpha/beta servers and what we need to get them running?
- Idea: code efficiency workshop conducted by Casey (&possibly Joe) to be filmed (needs to be done before Saturday if decided is a good idea)
- New developer "how to get involved" pipeline
- identify & prioritize the existing projects that new developers could get into
- how to make sure we maintain our direction and quality of work with more people involved?
- coding guidelines
- Clearly defining our roles as developers (backend, civic, artist) to make sure each of us understands the limitations of each and
their impact to the larger community.
- In case any "newbies" participate via phone, troubleshooting / Q&A session at the end
- What is the relationship of the tech team with the upcoming "leadership group"?
- It will be good to discuss this before the leadership structure is "finalized".
- Decision making process? Transparency?
- Evaluation (first impressions) of page ownership.
- Anything else?
Contents |
Meeting
Present: Casey, Joe, Anu, Jim, Kristen, Gardner, Walter via Skype & featuring Digs as meetings facilitator
Due to short time, most of the topics needing more coverage didn't get discussed in enough depth and time to hear the viewpoints of each other in a non-rushed manner.
Status checks
Joe
- translations not being saved bug - in progress
- page ownership - fix
- server stats - casey - add
- source - merging 2 branches - web interface and such -
- backup - image - logging servers - sudo
Casey
- svn deployment log
- page ownership
- server load checkups -
- verifications upgrade
Jim
- verification - language corrections
- admin tool efficiency - splitting up so others can access & help out
- dashboard + volunteers
Keith
- want commit powers!
Kristen
- css
- review
- moving pages to views
- meetings familiarization
- picture montage
Walter
- sort it out later when back from trip
- Keith will be helping out with getting started
Goals
Joe
- Kernel for trust networks
- search
- site stability & maintenance
Casey
- source control
- backups
- control panels
- uniform server
- NDA
Jim
- getting more into code
- more tweaking with admin features
- greetings management (? or meetings?)
Keith
- views to xhtml
- cleaning up the libs code
Kristen
- cleaning up the libs code
Gardner
- fix groups bugs
- unit test structure
- regression test system
Walter
- getting familiar with code
- notes about dev server setup process to help future developers getting started! (sweet ass ---Anu :)
Anu
- Ambassador structure
- user inclusion in feature development
- external tech comms
- new developer inclusion
Intros
- Walter from the Netherlands "drafted" from CS-development related discussions would like to help out with XHTML-compatibility for starters.
Leadership group?
- to be discussed individually
General discussion
- New developer inclusion: overall view of the people present is that developers should have at least some surfing / hosting experience to understand the community needs. Moving forward with drafting more "community minded" developers to get them started before the Nelson collective ends.
