Hi, NEdit's development in the past was always triggered by happenstance, aka feature-driven. While this method seems to suggest itself for an unruly environment such as this, it has some dangers: - Feature-driven development tends to blank out the larger picture. - Necessary but unpopular tasks are ommitted.
Therefore I would like to suggest to implement a Road Map. This Road
Map should outline the next steps of NEdit's development so that
workers can see the larger picture and so that the more loathsome
tasks can be brought in.
For an example see Roadmap on Niki. Any Road Map shouldn't be much
more detailed, any step listed should be handled as a project on its
own if more details are desired.
The Roadmap on Niki also happens to be my current proposal, but before
we rip it apart we should discuss about the general idea: Do we want a
roadmap? Do you see the shortcomings I outlined above? If yes, Do you
see a better way to handle them?
Thorsten
--
It's better to vote for what you want and not get it
than to vote for what you don't want and get it.
- Eugene Debs
pgpU3KoSNa6Dt.pgp
Description: PGP signature
-- NEdit Develop mailing list - [email protected] http://www.nedit.org/mailman/listinfo/develop
