This message attaches the first rough draft version of an outline for organizing this project. Please understand that I am not wedded to any language included in this draft. It is as much example as off-the-top brainstorming of approaches that might work. I contemplate that the outline is mere prelude to a project web portal on the OOo project wiki or some other web content management system that is conducive to hierarchical web site organization and navigation. I also hope that someone else might take on the responsibility of playing the role of web site administrator. I simply do not have enough time to fulfill that role.

I have annointed myself as the project coordinator for the moment, but likewise hope someone might take on that role soon as well. I am far more talented at designing office systems than I am at administering them (and even that says nothing about my available time on either front. I am also recovering from some serious medical issues and am operating under my physician's instruction -- and my own decision -- to put my health out in front of my other commitments.).

At this point, I hope we might begin discussion of the outline's approach in general terms and save the detail work for later. I would like to get a general structure nailed down before trying to nail shingles to the roof. So please think in terms of questions along the following lines.

* Is the work plan embodied in the outline something that looks do-able if refined and implemented with fairly minor modifications or is the whole thing so funky I should start over with a different approach?

* Are there major omissions at the topic and subtopic level?

* If you were limited to the three most sweeping criticisms of the outline you can think of, what are they?

* If you had carte blanche to make any changes in the outline you could complete within in one hour, how would you summarize in 10 minutes of keyboarding the changes you would want to make?

* Are there outline branches that need to move or be replaced, new branches that are needed?

In other words, let's leave the specifics of defining requirements alone until at least the next draft and focus this time around on getting a broad strokes work plan developed. My general approach to the next draft will be to incorporate any suggestion that doesn't seem baldly inappropriate, with optional approaches noted.

I apologize in advance for the sloppy line spacing in the draft outline. I am test driving an outliner I haven't tried before and its HTML export feature is not without bugs. However, what is there is well formatted, so it shouldn't take a lot of work to convert the outline to a web page complete with a hyperlinked table of contents once its major structure is nailed down. Hopefully, at that point we might make it a group project to translate the thing into a set of wiki pages, proclaim a portal administrator, and proceed from there.

I'll see how the pace of comments goes and later post a cut-off date and time for comments on draft 0.0001

Best regards,

-- Marbux
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to