>>>>> On Sun, 17 Jul 2011 09:43:01 -0700, Jeffrey Kegler >>>>> <jeffreykeg...@mac.com> said:
> I'd like feedback on a question. My feeling is that internals documentation is > important, that disk is relatively cheap, and that I should include the PDF > file that contains Marpa's internal documentation with the CPAN distribution. > But I'd like to know if others agree. I have read three opinions for separating documentation and code. I myself am pretty indifferent, but I'd point out that potentially code and docs would not need the same update frequency. That would mean that a separate way of distributing could be taken. I think this is without precedent but maybe a separate distro like Marpa::Doc seems a pactical idea. A not very well known fact is that if you choose to upload a file matching /\.pdf$/, then you are able to overwrite it, i.e. upload it again with the same name. Only few people have chosen to publish PDFs so far, I found only these: AEPAGE/ptkdb.pdf EIKEG/doc/perl-tutorial-DE_2.01.pdf EIKEG/doc/perl-tutorial-DE_2.02.pdf GAAS/illguts-0.09.pdf GSLONDON/iperl.20040429.pdf HFB/grok-cpan-1.01.pdf MHX/CBC-0.71-A4.pdf MHX/CBC-0.71-Letter.pdf RURBAN/illguts-0.09.pdf TIMB/DBI_AdvancedTalk_200608.pdf TIMB/DBI_AdvancedTalk_200708.pdf TIMB/DBI_LightningTalk_2006.pdf TIMB/DBI_WhatsNewTalk_200607.pdf TIMB/Gofer-200707.pdf XIAODIAN/SVGLAB-10/SVGLAB_CN.pdf XIAODIAN/SVGLAB-10/SVGLAB_CN.pdf XIAODIAN/SVGLAB-10/SVGLAB_EN.pdf XIAODIAN/SVGLAB-10/SVGLAB_EN.pdf I think there is no obvious best solution. Probably people will complain whatever you choose:) -- andreas
