Sorry for cutting in so late on this topic. I am not sure what problem this proposal is trying to solve. I am against the idea of putting the website in the main code branch, for the following reason:
The docs are specific to a given lilypond version, and should therefore always be part of the main branch that contains the code. The website is a a living 'document' that talks about several lilypond versions, and that changes independently of the code repository. For example, the website may be updated to link to appearing or disappearing news articles. You may recall that, in a distant past, the website was really generated from the source code that we had, and I have no fond memories of the scheme; see http://lilypond.org/doc/v1.6/Documentation/out-www/index.html >From a developer perspective, merging both means adding a lot of noise commits that hinder both website development and lilypond development. On Fri, Jun 5, 2009 at 3:18 PM, Graham Percival<gra...@percival-music.ca> wrote: > Do we need a separate branch (or even repository) for web/ stuff? > I propose that we merge this with the main branch. > > PRO: > + one less branch/repo to track > + easier to fix typos in the web pages > + we can direct everybody to look at the CG (no more README in the > newweb/ branch) > + allows better integration with the other docs (this is more a > post-GOP feature) > > CON: > - adds 30 megs to the main branch (including the .git dir) > - makes translations harder? (maybe? ... I don't know if this is > true, but IMO this is the only real reason to avoid doing this) > > > > If we agree with this proposal, then we'll be left with: > lilypond repo > . master branch > . individual testing branches > . archive branches of old stables > . translation branch > > gub repo > . master > > > Cheers, > - Graham > > > _______________________________________________ > lilypond-devel mailing list > lilypond-devel@gnu.org > http://lists.gnu.org/mailman/listinfo/lilypond-devel > -- Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
