Leopold Toetsch wrote:
William Coleda <[EMAIL PROTECTED]> wrote:
I had great plans to flesh it out more than I have, but work has intruded. I've checked in what I have so far in docs/ROADMAP.
I really appreciate the effort putting all that together. But it's not that simple. E.g. the TODO WRT pdd05: this pdd is totally outdated. It describes the function-based run-core before the times, where ops2c.pl did exist. Or: most of what is listed under DESIGN, are documentation TODOs.
Design is a special kind of documentation that, in my mind, needs to be broken out. If these PDDs are outdated, then the design needs to be "redone", that is, re-documented.
Before creating a detailed list of items, these should be verified against the implementation. That's a big job. Many (especially pdd) docs need updating. A Parrot Documentation Group would be really awesome.
There already are fairly large lists of items that need collation. That is, I am not creating any items on the list. Having them in a central location should make the project more manageable. That's really my goal here, to facilitate some PM.
I'd appreciate it if you opened TODO tickets in RT regarding which PDDs you think are currently out of date, btw.
Well, and the file isn't really a ROADMAP (yet).
Nope. But I'm not in a position to set policy or determine what is due in certain release. That's what you and Dan are for, I'm just trying to provide the ability to capture this information in a single location. (now docs/ROADMAP, eventually RT)
