I just found this factoid on Ohloh and I am amazed to read this:
LXDE: Very large, active development team
Over the past twelve months, 26 developers contributed new code to LXDE. This is one of the largest open-source teams in the world, and is in the top 2% of all project teams on Ohloh. For this measurement, Ohloh considered only recent changes to the code. Over the entire history of the project, 46 developers have contributed. (http://www.ohloh.net/p/lxde/factoids/)
I believe everyone in the LXDE team still considers the project as a rather small project with a small team. There have been many changes and advances, but I would have never guessed that LXDE is one of the big projects. If we see it in regards to Gnome and KDE, the relations become different though. Gnome has 432 developers according to Ohloh and KDE even 482 code contributors. XFCE shows up with 12 coders during the last twelve months.
I wonder how many people actually work in different desktop projects at the same time. We have friendly relationships with many contributors working on different projects already. Chris Wickert for example is a core member of LXDE and at the same time taking care of XFCE packages in Fedora. In the end we all share the same ideas and goals about free and open source and we actually share a lot of the code with many projects, especially with our friends from XFCE.
Everyone, keep up the good work! I hope to see more exchange and friendships among our projects. We welcome everyone to work and cooperate with us even if we have some different views sometimes on specific questions. In the end it is cooperation what makes us – as a software project and a community – advance faster and become better.
The current release of MySQL shows the problems free and open source software projects face that put business first and community second. Michael “Monty” Widenius critizes in his Blog the current developement model of MySQL and recommends not to use the current release 5.1 of the database system.
The reason I am asking you to be very cautious about MySQL 5.1 is that there are still many known and unknown fatal bugs in the new features that are still not addressed.
Monty gives a some reasons why the MySQL development department again got a quality problem with the release. Some of them are:
- MySQL 5.1 was declared beta and RC way too early. The reason MySQL 5.1 was declared RC was not because we thought it was close to being GA, but because the MySQL manager in charge *wanted to get more people testing MySQL 5.1*. This didn’t however help much, …
- We have changed the release model so that instead of focusing on quality and features our release is now defined by timeliness and features…
- The MySQL core developers have been split into too many teams and only a small part of the core developers have been working on MySQL 5.1 to get the bugs fixed. Some of the core developers have also recently left the MySQL organization which is a serious issue as there is not many of of them.
- Too many new developers without a thorough knowledge of the server have been put on the product trying to fix bugs…
- Bug fixing and development processes are not systematic and not persistent.
- We have not been giving the MySQL community enough opportunities to test MySQL 5.1 (too few releases). … the MySQL current development model doesn’t in practice allow the MySQL community to participate in the development of the MySQL server …
- Internal QA on the MySQL server was started very late in the process. Now when the process have started to show results, the found bugs have largely being ignored as fixing these they would delayed the MySQL 5.1 GA date.
- The MySQL server team have a bug fixing policy where a bug that has existed a long time has a lower priority ‘because people know about them’. This is supposedly one of the reasons why the Bug#989 mentioned above has not been fixed.
As I said in my talk at the MySQL users conference, I think it’s time to seriously review how the MySQL server is being developed and change the development model to be more like Drizzle and PostgreSQL where the community has a driving role in what gets done! (http://monty-says.blogspot.com/2008/11/oops-we-did-it-again-mysql-51-released.html)
What can we learn for the LXDE project here? The consequences are clear. During recent months we have already worked hard to improve the tools and infrastructure for the growing LXDE community and we will continue to do it. The community must take a leading role in development of software systems in order to keep the system on the bleeding edge.
Companies are always welcome to join development and focus on their business models. Projects like LXDE have a roadmap that is following long term goals instead of short term profitability. We are inviting more people to join the LXDE development, test LXDE and support and contribute – for faster and more energy efficient software. Please check out our contribution page at http://join.lxde.org.
Fred Chien, core developer of LXDE, and me had a presentation of LXDE at ICOS 2008 in Ilan Taiwan.
今年的會議議程，將從『政府』、『教育』、『商業』、『社群』及『非營利組織』等五 大族群，邀請政府官員、民意代表、企業代表、學術研究人士，社群計畫發展人員、 非營利組織應用發展代表等，共同參與各項發表會、座談會。希望藉由這個研討會 的舉辦，提供一個網路之外的交流機會，透過各方英雄好漢的分享經驗及心得交 換，也期望能為未來相關領域的發展及合作提供一些助力。 本研討會之議程委員皆在自由軟體相關單位、產業界、學術界或相關社群享有 盛名，具有高度成就。本大會將著重於:
本次會議預計將會吸引來自各地的學者、專家、研究生及相關社群人士與會。 希望能提昇國內產官學研等單位人士對自由軟體、自由軟體社群、自由軟體共同開 發平台之瞭解。並建立自由軟體有助於增進數位學習、縮減數位落差之形象。建立 產官學社群交流之機制並提昇各界對國家自由軟體政策推動之認識。(Aug, 30, 2008, http://www.slat.org/icos2008/)