I have put together a proposal for best practices for working in a MeeGo team. Quoting my foreword:
This is a DRAFT proposal for TSG eventually to consider, in order to encourage or establish policy of best practices for working should be like for MeeGo groups, teams, WGs, appointed groups of people. In the following, team/group/WGs/appointed groups of people is shorted to 'team'. Instead of pointing out how each team is doing it wrong and each and every problem, it was cooked down to this proposal, so we can have something to point to when things aren't being as open as it should be - which is effectively blocking public R&D as intended. These simple Do's and Don'ts were supposed to be obvious, but we are not seeing this happen in practice, hence this proposal. The scope of these practices is any team organised underneath the MeeGo umbrella which works with the public MeeGo project. The proposal can be found at: http://wiki.meego.com/Proposal_for_Best_Practices_for_working_in_a_MeeGo_team Comments/changes/constructive criticism are welcome. My hope is to get it tabled for next TSG meeting (Wed. 21 april 2010) as a policy decision, with emphasis on that henceforth teams should operate with best practices. We are seeing a lot of secrecy and non-public development which is effectively harming the project and I personally think that TSG should lead the way and point out this is not how things are supposed to be. Instead of ranting over and over on issues and cases, let us tackle this problem early, directly and constructively. We're supposed to do public R&D between many different individuals and companies - not only R&D between Nokia and Intel and those contractually involved with them. Please keep responses related to the proposal, don't let it become a flamewar. Regards, Carsten Munk maemo.org distmaster _______________________________________________ Meego-community mailing list [email protected] http://lists.meego.com/listinfo/meego-community
