Mark Shuttleworth - Open source collaboration wondering what he could contribute to such a talk, he is not a kernel hacker, however he has been watching the open source movement a lot and the collaboration happening between people, people interested n working together to make really cool shit happen has been extraordinary look at some of the really big free software projects out there, show how they work together, and see where they may be able to improve he suggests on redmond campus there are very efficient processes by which people form different mind sets can collaborate, we have to do as well what do the successful projects have * strong process for decision making capability - benevolent dictator - strong internal governance for decisions and roadmap -- debian does so well because it has clearly defined internal government structures codified and well known * tools for collaboration - code, bugs, project management, does not matter which bug tracker you deploy, they can all do the job and provide internal communication - translation, docs * strong communities - strong values - fair treatment, low bozo factor Every time a patch falls on the floor a kitten dies (very similar to AKPM's do not lets anything through that may help you improve) Translations are really important, our ability to innovate depends on the size of our community. best examples Gnome, OpenOffice, Ubuntu, Linspire, GNU * Barriers to translation - tools are crufty and obscure - translation requires PO and commit capability - Multiple different formats, PO, Mozilla, OpenOffice, XLFF * Web based approach is good.... Pootle, Rosetta, IRMA of all the languages in the world only about 15% of them are reasonably well translated currently. Moving bugs between projects causes you to lose the conversations on a given bug. Mark wants to see bug tracking systems start to follow conversations on other bug tracking systems and be able to show the information going on. He would like to see some intra bug tracking systems protocol that means they can all share information Bug collaborations, Debian BTS does it well, you send an email and the bug is filed, no account creation, no nasty intimidating system Once more see the slides to get more information recommend the look at git, hg and bzr for distributed VCS, mark suggests it is the future of VCS to handle things in a distributed manner, no second class citizen, ability to collaborate with all the other people (up stream, other distributions, etc) easily and track your own and other modifications