2010/7/6 Carsten Munk <[email protected]>: > 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:
Backing up a bit, because there seems to be a lot of emotion and borderline flamewars in this thread, which was not the intention. To everyone contributing or wanting to contribute to MeeGo: Remember we have a challenge. We (and by this, I mean everyone involved in MeeGo or wanting to contribute) have to work together across location and affiliation. Also, we have to get a product out, the MeeGo platform. To this extent, a project structure has been set up, check out http://meego.com/about/governance . Key positions have been filled with people with skill and merit. They have proven themselves capable of getting products out - it might be difficult to see that as they have done it inside their companies. While it may be tempting to claim that this now means it is company controlled, do keep in mind that we're now having industry experts involved in getting this product done properly, with quality and with the goal of meeting deadlines. These same people would have been open source heroes if their merit had been gained in open projects instead of company projects. I think it's time to end the feeling of 'us and them'. We're all in this MeeGo project together. And we have our challenge to accomplish. Proving that open source and open development can work for a project like this - and that it will be a quality product and most importantly, that things will get done. Working in the open is the infrastructure that binds us together and makes us able to work together across location and affiliation. To potential contributors to MeeGo, try to approach MeeGo work like how you would act in a company as an employee. You might disagree with the viewpoints of your superior - it is fine to argue your view, but in the end, they have to make a choice to accomplish the team and project goals according to roadmap. And mutual respect exists for each others role and reasons. If there's a definite problem with a superior, there's dispute possibilities in the project structure. If you don't have access to information or infrastructure needed to contribute, you ask, you ask again and again. The solutions to those challenges you struggle with is what effectively creates open development. To current contributors of MeeGo, approach potential contributors like new employees who have to get up to speed with the work. Just like in companies, handbooks are made, documentation, information is made available and infrastructure access granted. They have talent and skill and just needs those small things to accomplish their work. The challenge is that this new employee might sit thousands of kilometers away from you and even be in another company! - you have to make it possible for him to do his work as it makes us able to faster approach the team goals. And that's why you need to work in the open. This project can't work any other way. And this isn't just for people affiliated with companies - it is also for the individual contributors or groups of people - open development isn't only about giving, but also about participating and contributing back. Open development isn't going to happen overnight. Open development is what all of us work to create and show it is sustainable and workable amongst multiple companies and private contributors. Best regards, Carsten Munk _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
