On GameSpot: So-called 'Halo killer' gets 23 to life
BNET Business Network:
BNET
TechRepublic
ZDNet
TalkBack 1 of 12:
Next »
Forking vs "moving on"
If someone's ideas are not being accepted in a project quickly enough or completely enough, is he more likely to fork the software or to lose interest. Mr. Blankenhorn has praised forks as saving projects while Mr. Shuttleworth believes potential contributors go elsewhere.

There are obviously examples of both. But which might be considered the predominant response? The issue is significant because it's a potential roadblock to either faster progress or to the software's functionality.

A proprietary software company able to identify worthwhile (for increasing profits) ideas correctly does not have this problem.
Posted by: Anton Philidor   Posted on: 02/25/08 You are currently: a Guest | Members login | Terms of Use
Reply to Story Reply to Message

Alert moderator to an offensive message

Subscribe to this discussion via Email or RSS

Forking vs "moving on"  Anton Philidor | 02/25/08
Proprietary software has different problems ...  MisterMiester | 02/25/08
Management  Anton Philidor | 02/25/08
Absolute power?  MisterMiester | 02/25/08
Both can happen. If it is a critical project like the X-Windows subsystem,  DonnieBoy | 02/25/08
Gain from open sourcing software  Anton Philidor | 02/25/08
The Long Tail  billm@... | 02/25/08
Ironic...  Anton Philidor | 02/25/08
Not exactly the case.  odubtaig | 02/25/08
Also, think about cooperation among companies. There are thousands  DonnieBoy | 02/25/08
A company seeking commercial advantage...  Anton Philidor | 02/25/08
In any regard, the benefits of sharing development among companies are  DonnieBoy | 02/25/08

What do you think?

SponsoredWhite Papers, Webcasts, and Downloads

advertisement
advertisement