Re: (PTADT) PEAR Task Announcement and Delegation Tool (Was: Task Manager Tool)

Some of the ideas are interesting, but there some things that need to be clarified. Can we assume that the task management will work for general PEAR concerns as well as individual packages? --- Richard York <richy@smilingsouls.net> wrote: > The following outlines my current ideas for a task delegation tool. > I thought before I begin work on the project that it might be > helpful to retain feedback on the tool itself and the proposed UI. > > The following tool assumes that a task has been agreed upon through > the proper channels and those involved with the idea would like to > solicit help from the developer community. > > (PTADT) PEAR Task Announcement and Delegation Tool > > Provides an interface for annoucing various tasks to PEAR developers, > where PEAR developers may either commit to accomplishing the task, or > assist in the solution. > > Categories: > - PEAR-WEB > Contains tasks related to feature enhancements to the PEAR > website itself What will this be different from submitting a bug for pearweb? or a patch for the bug? Will this integrate with the current bug system or be a different view of it? Will this enhance the bug reporting system? > - Documentation > - Contains tasks related to documentation, tutorials, etc. Same as above with the added question on who will add new tasks to this part? > - PEAR > Documentation on PEAR itself > > - Developer Tutorials > - Package Documentation Aren't these redundant w/ the item above? perhaps the indentation is not the appropriate one if this are sub-items > - Package Adoption and Maintainership > Contains tasks related to abandoned packages. Agree firmly with that. See the idea of a 'siberia' for abandoned packages (deep cold, so the are nicely preserved :-) > - Package Creation > Contains tasks related to new package ideas How will this differ from PEPr? will it enhance it/replace it/be different view of it? > Features: > - Task creation tool > - Draft > - Create/Open > - Edit > - Close Some of the details at the beginning are not too clear to me, so the scope need for the task creationg tools are not yet transparent to me. > - Task assistance tool > - Commit to task > - Assist on task Hmm, bug reporting system, cvs commits???? > - Task solution tool > - Post solution directly to the task where others may assist > on the task (to work like a wiki) Patches in bug system. > - Solution is/may be stored until someone with CVS access may > commit the solution if the assisting parties do not have CVS > access. see above > - Open task summary weekly email > - Post a summary of tasks still open weekly to PEAR-DEV Periodic bug summary? (For example, in the PHP DOC list we get a periodic list of comments per page in the manual) > - Task comments pear.php.bet/bugs support comments already > - Task notification email (send email to PEAR-DEV, or other proper > channels when a task is announced) PEAR bug system should do that, although it does not always does it in my experience. ===== -- Jesus M. Castagnetto (jcastagnetto@yahoo.com) Research: http://metallo.scripps.edu/ Personal: http://www.castagnetto.org/ PEAR stuff: http://pear.php.net/user/jmcastagnetto __________________________________ Do you Yahoo!? Yahoo! Tax Center - File online by April 15th http://taxes.yahoo.com/filing.html