16 Jun
2005
16 Jun
'05
6:22 p.m.
Maxim Sobolev wrote:
Klaus Darilion wrote:
Thus, CVS users may not have an easy way to read documentation? Maybe we
should delete all init.d scripts from CVS as CVS users must be able
write them themself!
I tried once but failed installing the proper software and DTDs. When it
really that easy, maybe someone can help us adding a "make
documentation" to the Makefile.
Developers complain that too less users are WRITING documentation.
I'm willing to WRITE documentation, but I don't like DEVELOPING
documentation.
regards,
Klaus
Thus, CVS-users must read sgml files drectly from
the CVS to get
documentation :-(
Users of CVS version should know how to generate up to date
documentation from the sgml when necessary, otherwise there is no point
for them to use CVS version in the first place.
-Maxim
Generation of the README should be done automatically - e.g. every
night using a cron job.
I would prefer a webbased solution. Everytime I resolve an issue about
ser and I want to add a note to the documentation, I want to do it in
a fast way. I would go the the webpage (need not be a wiki), enhance
the existing document - done. Commiting the new documentation to CVS
and generating the README should be done automatically.
I do not know if such tools exist.
btw: why do developers enhance ser without updating the documentation?
I guess because it is too time-consuming.
regards,
klaus
Adding
documentation is to complex. I already added asterisk
documentation to voip-info because it is very easy to do.
Maybe we could find an easier way for providing documentation.
Suggestions welcome.