Thanks for all the replies (and the offers of help, very comforting). I will no longer accept the excuse of 'I can't write GuideXML' since we have an army of volunteers to GuideXMLify stuff for us :)
As such, I don't need to learn (I know enough to get by, and with this glep index I'll soon know more than I want to most likely). The intent of my inquiry was really to get a bunch of viewpoints on how documentation is handled. We 'train' via a quiz and mentoring developers to do ebuild tasks but we slack on other things. Devs don't *need* to know GuideXML but it would be nice to have a small tutorial (see fex, the cvs 'tutorial' in the dev docs) so that a new dev could get somewhat familiar with the whole process of making or editing a page. I agree it is a manpower issue; we have had Gentoo Status projects in the past that all pretty much died and part of my thought is to basically force the project leads to write reports but thats not very nice either ;) Once again thanks for the input ;) -Alec -- gentoo-dev@gentoo.org mailing list
