I too am kind of down on the speculation of regime change on Sun, though I'm not sure I can
articulate why. However, I think the point made is entirely valid. Code availability
matters, but code community matters also.
There are different levels of concern, of course. For projects like Postgresql where
development began outside a commercial environment, and have continued into a variety of
sponsored environments, the lack of a large community of participation is not nearly as
important as the demonstrated ability of the project to adapt to sponsorship change. Projects
like Solaris which have only ever lived inside the auspices of a single organization are of
more concern over view changes in the owning organization.
It's a meaningful point to consider when looking at risk-management of software use in the
open source world.
Posted Jul 24, 2008 6:06 UTC (Thu) by dlang (✭ supporter ✭, #313)
[Link]
postgresql almost died when Greatbridge went under (A .com that hired most of the developers).
the core developers point out that it's not a coincidence that they all work for different
companies now.
they are enforcing the diversification themselves where a large project (say the kernel) gains
the diversification from the sheer number of people who work on it, but even there, for many
years Linus avoided working for any of the Linux companies, specifically to avoid the
appearance that any one company would have undo influence on his work
I've seen several other projects flounder when they core developer(s) have real-life things
cause them grief. the point that we need to watch out for this sort of thing is very true.