Organisation: Project task list
akede
just a little update for me.
I saw that you are makeing extensive use of the forge-task list.
How do you work with this tool? Understanding how it is used could
make it possible for me to help you a bit.
~~~~~~
As an update:
I'm currectly working on the API and UML documentations for 1.5 and a
German book.
We have some issues with exchanging the XMI files which we couldn't
solve yet. I have to talk to the company that develops my tool again.
But there are some diagrams and other information done.
Hope to figure this out soon.
So far
Alex
Chris Davenport
Hope you are enjoying LinuxTag. Shouldn't that be LinuxTagen, plural?
Seems a contradiction to be reading your blog about the 3rd day of
LinuxDay! :)
In message
<20cda35d0605050022i5ac...@mail.gmail.com>, akede
<alex.k...@gmail.com> writes
>
>Hi folks,
>
>just a little update for me.
>
>I saw that you are makeing extensive use of the forge-task list.
>
>How do you work with this tool? Understanding how it is used could
>make it possible for me to help you a bit.
>
We have a workflow procedure document here
http://help.joomla.org/content/view/1571/106/ which explains how we use
the task manager to coordinate our writing of the API Reference pages.
The main purpose is to make sure we don't have two people trying to
document a particular class at once, and to keep track of where we are
with the quality assurance checks that we apply to each class.
I have to say it's not an ideal solution, but it's there and it works so
we use it. I keep having random thoughts about how it could be improved
from minor tweaks to the UI to more radical ideas like using
phpDocumentor to generate the task list and merging data from tags in
the pages themselves, but it would require the devotion of more brain
cells that I have spare at this moment in time :(.
Long term I'd like to think about having quality management data
embedded in the DocBook sources (I don't know if this is part of the
DocBook standard) so a program (like phpDocumentor) can merge data from
the code and the documentation to produce the management reports. At
the same time keeping it really simple for authors/reviewers to maintain
progress/quality data in each page/section of the docs. Of course, this
isn't a Joomla!-specific problem. It must surely be a problem for a lot
of open source projects. Maybe it has already been solved?
Hope this helps.
Regards,
Chris.
--
Chris Davenport
ch...@dcsnet.demon.co.uk
akede
:LOL:
Yea I was wondering this already the last years, but they stick to it :).
The event is already 10 years old and first it was just a day - now it
actually four days including tomorrow with a community day.
Some impressions: http://www.flickr.com/photos/30826926@N00/sets/1771239/