CentOS Administrator Reappears
str8edge sends word that Lance Davis, the CentOS project administrator who had mysteriously gone absent, has now returned and is working with the development team to get things back on track. From their announcement:
"The CentOS Development team had a routine meeting today with Lance Davis in attendance. During the meeting a majority of issues were resolved immediately and a working agreement was reached with deadlines for remaining unresolved issues. There should be no impact to any CentOS users going forward. The CentOS project is now in control of the CentOS.org and CentOS.info domains and owns all trademarks, materials, and artwork in the CentOS distributions. We look forward to working with Lance to quickly complete all the agreed upon issues. More information will follow soon."
Lance realized this very public oops wasn't going to do anything for his future employment prospects. A shame it had to come to that, but sometimes you need to upgrade from a feather to a cattle prod to get results.
Everyone will jump on this as proof that open source projects can not be trusted or relied on. Now, that may or may not be true. This instance really is not a poster child for problems with FOSS projects. We are talking about a project based on repackaging and rebranding a commercial distro. The heavy lifting is done by RH and other projects.
This should be food for thought however about other projects, which there are many many instances of FOSS project management issues leaving users high and dry because of political issues.
We really need some better organizational standards for FOSS project management, not just high quality code. Remember the segment of society we are talking about. They might be great at programing or whatever, but they rarely have the leadership and organization skills to handle a project once it reaches a critical mass of popularity or use.
One of the first things I have to do, after years of using FOSS, is look at the project and see how healthy it is before deciding to implement it in my biz. I have to do things like look at how many projects have derived work from it, who is contributing to it, how alive is the forum community both for developers and users, development cycles, and so on.
What we really need is some sort of organizational certification. Something that an end user of FOSS or other FOSS project can with one glance determine what is the status of the organization and the project. Especially the large important ones. Are there for example policies in place to handle the death of the head of the project? Is there a formal system for order of succession? Is there policy for archiving legacy code and related information?
The worse thing that can happen to a FOSS project is a cult of personality forming around just one person ( that is more than just PR).
Living in Chile