Hi all, While I was working on the new website, I realized that the info I was adding would work better as a manual rather than a few web pages. Therefore, in Feb (after 2.13 starts), I'll be creating a new manual: the Contributor's Guide.
(I /was/ going to call it the Developer's Guide, but then I realized that "DG" has rather a unfortunate meaning amongst computer geeks in my generation, and if my friends heard that I was working on the "new DG manual" I'd never live it down. :) This will contain the INSTALL docs, doc policy, "working with texinfo" stuff, the git guide, info about what all the branches are, where to find gub, any potential tips to translators or bugfixers, code style, policy for bug reports, checklist for normal and major releases, etc. Generally, I'll be combining all the README documents that nobody (including me) looks at and putting them all in one place. I'll also try to write down all the `oral tradition' knowledge about lilypond that various people have. ... actually, on second thought, perhaps I don't need to wait. I don't think that anything in there should be translated; the translators need to read enough English to understand the main docs so they should be able to handle their instructions, and (for better or worse) we do everything else in English. John, your opinions as both Translation Guy and the person who'd be adding the stubs for this to the build system? :) (starting from next Sep, I should have a linux machine powerful enough to build lilypond, so my excuse will be gone. However, until then... ;) Cheers, - Graham _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
