This is an important change that I want to make, so please let me know if don't feel comfortable with my proposal.
I've developed a package that can handle a docset of sources (in pod and html currently, more formats to come) and generate an output in html/ps/pdf (more formats to come). It should be very simple to manage the source docset. The docsets can be nested. Therefore I propose to merge documentation with mod_perl site and make it one source docset, which is all properly linked and has an easy navigation and buildable from one spot. That's why I suggest to remove the modperl-site cvs repository and add the few docs from the site that we have to the modperl-docs rep. Alternatively, we can nest modperl-docs rep inside modperl-site rep on checkout. Currently to update the site we do: on our machines: 1. cvs up 2. apply changes 3. cvs ci on apache.org: 4. cvs up With my proposal we will have to do: on our machines: 1. cvs up 2. apply changes 3. cvs ci on apache.org: 4. cvs up 5. bin/build so there is one extra step to do. Is this OK? issues: - need to install TemplateToolkit and a few other packages on apache.org :( I guess we can do it locally, I don't want to pester Brian. - the package handles links so we have no problem linking to e.g. perl.apache.org/dist/ - embperl site, I suppose it can be folded into the docset, if Gerald doesn't mind. - anything else? p.s. please don't ask me about the code, as soon as I put it in a better shape, I'll announce it here: http://www.template-toolkit.org/mailman/listinfo/template-docset _____________________________________________________________________ Stas Bekman JAm_pH -- Just Another mod_perl Hacker http://stason.org/ mod_perl Guide http://perl.apache.org/guide mailto:[EMAIL PROTECTED] http://ticketmaster.com http://apacheweek.com http://singlesheaven.com http://perl.apache.org http://perlmonth.com/
