We have seen this with other Open Source projects. Nothing hurts a project more than a lack of developers to participate. One approach might be to fish in the corporate pools to see if any of them would like to participate at all. They might decline, but it never hurts to ask.
Open source productivity suite OpenOffice.org may be touted as a viable alternative to Microsoft Office, but there are claims its pace of development and adoption of new features is being stifled by a “monolithic” code base and a developer community still largely controlled by Sun Microsystems.
Project contributors speaking at the annual OpenOffice.org miniconference in Canberra this week raised numerous issues, including a lack of independent contributors.
OpenOffice.org developer Ken Foskey said the biggest problem with the project is a lack of developers and a code base that is “just too big”.
“It’s 10 million lines of code and takes serious commitment just to compile the thing,” Foskey said. “I’m interested in [having] more community developers [involved],” he said, adding they shouldn’t “just say ‘I want to work on OpenOffice’ but focus on a particular part of the project.”
Sun is still the largest contributor to the project with some 50 developers in Germany, followed by Novell with about 10 contributors, and only four active community developers. [Read the rest]