Hi. Just adding my two cents: I never knew that you guys had a tracking document. So, maybe it doesn't get used because no one knows it's there?
I like Rania's idea of a spreadsheet--something up front where it's easily found, and everyone can see what's going on. I had noticed too that there are a lot of things that one person might have started but never completed. Why not hold volunteers to task? Have them do only one thing at a time and not start on another until the first one is completed and okay'd. This could give the project more focus and at least give the appearance of progress. Of course, people like me are part of the problem too. A lot of volunteers really don't know what's going on or what to do, and we don't necessarily have the technical writing backgrounds. I don't recall ever seeing a rubric of what exactly should be in each section, so you kind of leave us bewildered while at the same time lose uniformity. Each section should have A, B, C, and D regardless of topic, and with a basic rubric there would be less time holding the hands of us n00bs. Just some thoughts. De Angela On 4/29/15, Keith N. McKenna <keith.mcke...@comcast.net> wrote: > jonathon wrote: >> On 29/04/15 17:09, Keith N. McKenna wrote: >> > Jonathon; >>> We have a tracking document that is supposed to be used so all members of >>> the team know where things are and what is needed but it rarely gets >>> used. >> >> I'd suggest the tracking document is rarely used, because nobody is >> creating documentation. >> > Not entirely true. Work has been on certain pieces of the documentation > but the status document has never been updated, and no mention of the > work having been done ever came to the list. >>> do we really want to have the documentation done "in house"; and if we do >>> is the process we started 2+ years ago still the correct way to go? >> >> How much do you know about documentation, when the project was under the >> auspices of Sun, and later Oracle? >> > I know a fair amount about how the documentation was done then. >> That history has a lot to do with the lack of documentation for Apache >> OpenOffice today. > > The former process may have some bearing on the problem, but more recent > history also has a great deal to do with it. > > Regards > Keith >> >> jonathon >> > > > --------------------------------------------------------------------- To unsubscribe, e-mail: doc-unsubscr...@openoffice.apache.org For additional commands, e-mail: doc-h...@openoffice.apache.org
