Forum OpenACS Improvement Proposals (TIPs): Re: TIP #28: Create package-specific enhancement lists under

Collapse
6: Re: TIP #28: Create package-specific enhancement lists under (response to 1)
Posted by Joel Aufrecht on 11/13/03 09:49 AM
Why use an ETP, when all of the content is list entries?  Lists of problems, lists of to-dos.  Each item has text descriptions, current status, planned target for fix, owner ...  Why not just use the bug system?  Then the home page for each module is basically an auto-generated page, and if we want a running commentary we could make it a two-column page, with a blog on one side and the bug tracker list on the other.
Collapse
7: Re: TIP #28: Create package-specific enhancement lists under (response to 6)
Posted by Dirk Gomez on 11/13/03 10:41 AM
Great proposal, Joel. That avoids duplicated and thus information that will get stale over time.

I volunteer for programming the include snippet for bugtracker.

Collapse
8: Re: TIP #28: Create package-specific enhancement lists under (response to 6)
Posted by Malte Sussdorff on 11/13/03 01:01 PM
Just have a look at the survey situation. Getting this specification in ONE file is just to much to read in a bug-tracker. If you talk about creating bugs for each of the items, then this might make sense, but again, how would we generate an overview page? Display all tickets associated with the package?

So not sure how this helps collaboration on the status and specifications of packages.