One of the weaknesses of Issue-Tracker -- I think we'd all agree -- is the lack of substantial documentation. This is a gap that we, the ET developers, definitely need to fill. To move forward with writing the documentation, how should we go about it? Should we 'draw straws' on sections? Should we each focus on a particular module? Should 1 developer do the whole enchilada?
I'm very open to discussing this!
Thanks, everybody.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I just responded to a Support Request (see http://sourceforge.net/tracker/index.php?func=detail&aid=1110798&group_id=126639&atid=706387\) that was submitted due to confusion about how to use the Custom Fields feature of EnterTrack. This got me thinking about documentation for the project.
One of the weaknesses of Issue-Tracker -- I think we'd all agree -- is the lack of substantial documentation. This is a gap that we, the ET developers, definitely need to fill. To move forward with writing the documentation, how should we go about it? Should we 'draw straws' on sections? Should we each focus on a particular module? Should 1 developer do the whole enchilada?
I'm very open to discussing this!
Thanks, everybody.
The documentation wiki is at http://etdocs.v.igoro.us