Re: Project scope was Re: Thoughts on Voiding Invoices

[David Tangye <..hidden..>]

That's the right track for sure.

One point...

On Mon, 2006-09-25 at 10:01 -0400, Christopher Murtagh wrote:
> Project Scope where we all submit our
> ideas/plans on direction for LedgerSMB and after a brief discussion we
> come to a consensus? 

I would not worry about needing a brief discussion, or consensus.

1. At  any time soon, set the Scope and a Project Roadmap that gives
possibilities for extending the scope over time

2. By all means get on and develop/code to that scope.

3. Let that discussion continue to range over time, and in fact welcome
it. That is the main difference between a closed project with open
source and a truly open project.

4. Make changes to the Roadmap over time as consensus on new priorities
for functionality/changes to Scope emerge. The Roadmap is simply a
statement of approximate Scopes (limits of functionality) optionally
over approximate timeframes else implied 'somewhere in the future,
possibly in this order' timeframes.

At this stage I might keep the future stuff generalised enough that you
dont get too distracted from development to have to answer nit-picking
arguments about what exactly is further down the road in the map. The
idea is to obtain the happy medium between 'hacking code to no plan' and
'analysis paralysis'.