March 7 2007
From the CouchSurfing Wiki, an informal workspace which anyone can edit.
THIS PAGE IS OUTDATED
Contents |
Agenda
Wednesday March 7th 10am NZ time, remote developers are encouraged to participate via Skype/phone. World clock time planner for NZ, US east coast, Europe
- tech team internal & external communications
- making sure people who need to be in the loop are in the loop (making sure major bugs are reacted to when they are first reported by the users, that our "helpers" have all the info they need, that people with higher access levels are approachable enough to get stuff done...)
- preparation for online-only working mode - this is reality in a month from now so we'd better be ready
- preparing for the next collective
- what the tech team needs to implement here so CS is ready for the next collective
- what's the role of tech people at the next collective(s) & in case the collective is "less-tech", how to make sure collective workshop proposals actually get somewhere, if they require site improvements and there are not enough developers with CS coding experience around locally to get them done.
- position statement for embedding open-source code into CS codebase
- e.g. Google calendars, javascript widgets
- meetings upgrades? Any takers / forming a team of interested people
- assigning code ownership/roles (as per bugtracker categories that have no "owner" right now):
- chat?
- groups?
- authentication?
- translations?
- email?
- images?
- layouts?
- user profile?
Announcements:
- some greetings improvements suggestions (Anu)
- new developer intro (set-up, first tasks, how to involve into our current projects)
- status checks of projects outlined at the last meeting
What we actually ended up talking about :)
Participants: Casey, Joe, Jim, Anu, Kristen (in NZ), Thomas (happened to be online so we hooked him up on Skype - thanks dude, was good to have your input), John (virtually present, as we all read his email before starting the talks)
Internal communications
To address most urgent issues that will be problematic when the NZ Collective is over unless we plan ahead.
- Site down situations
- Training more people to be able to watch over servers
- Implementing helpful software
- Timezone-sensitive alerting system
- Joe and Casey will research their workflow on these issues and provide training material to others
- DB update requests handled more orderly
- email about the updates
- committing each change into our codebase to be traceable & enabling new / old developers to get up to speed faster
- All requests through Joe (currently), ultimately responsible for keeping the update backlog in good shape
- General reachability
- Defining code ownership areas and ensuring we have "strong ownership" in each area
- Email habits: address to people who should take action and/or respond + make this clear in the subject line, cc the rest of the team (to ensure all of us know what's going on)
- Trying out bi-weekly conference calls after the collective is over (since some of us will not be online 24/7, to touch base & define direction)
- Code ownership
- "it's worse to have weak ownership than no ownership" (Firefox development team talk on Google Campus
- signify current/previous owner on the pages (Joe) - previous owner in the case a new owner will be necessary
- reachability after this collective: TBA, but seems most of us are on the go from early/mid April until ???
External communications
- Anu has some ideas, as does John - will most probably be working on them together.
Unassigned Bugtracker areas
- chat? -> tristan (more logging over chat-activities to be implemented)
- groups? -> ?
- authentication? -> Joe
- translations? -> Joe (dealing with a major bug) Anu later
- email? -> ? ??? (resolving our NDA status would help!)
- images? -> (minor area, image server stuff to be handled by people with access)
- layouts? -> Kristen, Keith, Kasper
- user profile? -> Thomas
Preparing for the next collective
- project management tools for the next collective
- Developers' gathering in North America next summer as bunch of us will be around?
- Anu will sit down with Bruno to check up on what's being planned for the next summer collective & what tech needs they may have
Updates
- Subversion
- formalizing code review & having developers commit to different branches
- need an integration manager
- while enabling quick patches to go through immidiately
- developer tools
- Anu: general info, possibly some bugtracker embedding
- Joe & Casey: server babysitting etc.
- NDA status
- same as last week
- blog status
- Anu will check up how well has the integration been done, what's the status and see what needs to be done on the server side to get it running
- community tools status
- modifications discussed last time done, the system is live
- verification upgrade status
- done, except for a small bug
- newsletters preferences
- Casey: DO IT!
- SUDO shell
- Joe
- member project gallery
- Joe WILL do it
- collective info/self-serve page for the next collective -> Project management tools for the next collective(s) (Casey, Anu)
- Casey / Anu (need to ask "next collective" folks some info)
- age by birthdate
- Thomas wants to take over :)
- only the exact date to friends? Or just show the number
- date formatting preferences
- Anu (while doing calendar stuff anyways & being European and not really happy with our date format / handling ;)
External code?
- e.g. Google calendars, javascript widgets
- it's okay :) (so Anu will be experimenting with some calendar software...)
Meetings
Forming a team with developers and some other enthusiastic proactive helpers we've had.
Announcements
- greetings - giving more tools to greeters to notify admins and such about questionable / technically non-functional profiles (Anu)
- new dev - Anu will give our new dev person a hand in setting things up (information & setting up accounts & make sure they have all they need)
Next meeting
Wed March 14th 11 am - any current devs welcome to participate via Skype / Google talk (let us know your usernames on those on the dev list). World Clock meeting planner
TODO for each participant:
- add agenda items on this page if you have any issues you'd like to discuss
- define what you wantto have accomplished by the time you leave the collective
