So, we're past Handset day one. MeeGo has published the Core, the Netbook UX and the Handset UX development is opened. It's summer, many people have gone on vacation. Nothing will probably happen during this month.
But I'd like to plea for you think about something while you're relaxing. Just something for you to keep in mind for when you're back at your desk. That is, to remember that we are supposed to be doing, random citations from around the website: "MeeGo software is developed and designed in a collaborative effort by an open community of professionals and volunteers" "The governance model is based on meritocracy and the best practices and values of the Open Source culture." "Yet MeeGo operations are expected and designed to be completely transparent - R&D in the public internet! " and many other quotes regarding this topic. I know I'm continually beating this horse called openness, but so is this project doing in countless presentations and I think, honestly, we should walk the talk. We don't have any excuses any more and we just look silly if we don't practice as we preach. If -you- are a release manager, a product manager, a team lead, a maintainer or just a regular team member, please consider these simple questions when you go about your MeeGo related business, be it meetings, development, telcos, whatever. * Would a random skilled contributor from the Internet be able to participate and contribute to this activity? * Would a random skilled contributor from the Internet be able to show his merits and eventually join my team? * Would a random skilled contributor from the Internet be able to follow and read details about most of the work being done in this team? If your answers are no - you're not doing your MeeGo work right. Write down the problematic activities and feel free to ask here how to make your team work in the open or ask advice on specific problems. It's homework for August - for you and your team to execute to bring it into the open. Openness aids collaboration and behind the doors work hinders collaboration, also between Nokia and Intel, or between the companies involved or committed to MeeGo, or between company and private person - and we need all the skilled hands we can get to get this project to be strong and to get things implemented. There is only one way to work this MeeGo project. Working in the open. Public R&D. Will you pioneer it in your team? Best regards, Carsten Munk maemo.org distmaster and N900 hardware adaptation team member _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
