The "Doctor Who" Model of Open Source
Glyn Moody writes "Open source projects are generally fine when there's a long-term leader like Linus; but what happens when nobody is able or willing to run things for extended periods? Peter Murray-Rust explains how the open chemistry group known as the Blue Obelisk has evolved what he calls the 'Doctor Who Model of Open Source': 'You'll recall that every few years something fatal happens to the Doctor and you think he is going to die and there will never be another series. Then he regenerates. The new Doctor has a different personality, a different philosophy (though always on the side of good). It is never clear how long any Doctor will remain unregenerated or who will come after him. And this is a common theme in the Blue Obelisk.' Could other open source projects learn from this experience as long-term leaders start to move on?"
Doctor Who? We're talking about a contrivance that was used to explain away actors leaving a show. Meanwhile, in reality, open source projects leave a lot of code that may or may not be well-documented. Changing project managers every few years strikes me as rather difficult, although I guess if you can maintain interest in the project throughout, it could still be a success. Still, it seems like a warning sign to me, kind of like when a movie has 5 screenwriters or 5 editors.
(-1, Raw and Uncut is the only way to read)
After 12 deaths, you need hyper-advanced aliens from another planet to grant a new regeneration cycle? Does Davros take over? I'll explain later.
Feudalism with a herditary monarchy. Trouble is anybody who works on open source projects doesn't breed, so you'd have succession wars all the time.
No change there, then.
Only three things are certain; death, taxes, and apocryphal quotations - Ben Franklin.
with characters such as RBS, Linus, Guido Python, Larry Perl, etc.
Um..... RMS, Linus Torvalds, Guido van Rossum, Larry Wall