I've started a wiki page at http://open-ils.org/dokuwiki/doku.php?id=acq:timeline
This is just a skeleton of notes taken from the Acqfest earlier this summer. We have a very large, amorphous set of requirements submitted from different organizations. Ideally, the process of defining, de-duplicating, organizing, and prioritizing these requirements would be a community process. Whoever is involved with the initial rounds of this process, however, needs to have a decent understanding of ACQ/SER terminoligy and workflow to make sense of the free-form documentation. I'm thinking the data needs several passes: 1. de duplicate 2. organize into functional areas and dependencies 3. vote on necessity of requirements 4. draw lines in the sand defining which release each block of requirements is part of I would like to open the floor for suggestions on the best way to get people involved and the best way to manage this process. -bill -- Bill Erickson Equinox Software, Inc. [EMAIL PROTECTED] http://esilibrary.com/
