On Sat, 2010-01-02 at 15:42 +0530, jtd wrote:
On Saturday 02 January 2010 13:36:14 Kenneth Gonsalves wrote:
- However hard you work, however great your code, however much
- most important of all - development must be done openly. Any
software where people labour for months in secret and then suddenly 'release' their software is bound to fail. You need testers at every stage - not after the software is 'complete'.
Complete? I think no FOSS based project is complete. Orca screen reader to which I contribute is more featured and of better quality than its proprietory counterpart. While the proprietory project claims that their work is complete, orca team never claimed that. Right from the day we felt we have some thing to share and actually start the project in the real sence, we started or re-started the project and from the vary nasent stage it was open.
IMO the inputs BEFORE you write a single line of code is far more important than any number of bug fixers you are likely to get later. You miss this and you will have a full rewrite on the menu card.
True.
Closed systems have to suffer the secrecy that is the cornerstone of their business plan (atleast they believe it is a cornerstone). An open project has already shot itself in the head by this approach.
Which one?
Happy hacking. Krishnakant.