Re: Silence; Hope; Loss; squid-docs.sourceforge.net

I would propose 3 CVS modules

1. The docbook sources

2. The skeleton for the web site on squid-docs.sourceforge.net

3. Assorted scripts for generating the formatted versions from the
docbook sources. This is unless this is made part of the web site
module.

You are also correct in that sourceforge and CVS modules are different
entities with no forced connection between the two. How you use them is
up to you to define. The CVS modules is where you work and change stuff,
the SourceForge modules is where you publish downloadable files (one per
module at a time).

What permissions you need to assign to people depends a bit on what
you'd like them to fiddle around with. CVS commit permission would be
nice of course if that is controllable now...

/Henrik

Oskar Pearson wrote:
>
> Heya
>
> > Are you there?
>
> Yep.. sorry about the delay.
>
> > I am ready to deliver some comments clean up some parts, but not sure
> > how to deliver this. No CVS repository, and you have been very
> > quiet..
>
> I've been meaning to chat to ppl about the CVS stuff.
>
> We currently have a set of docbook source files. These files are
> the base for lots of differently-formatted versions of the source
> (html, pdf, postscript etc).
>
> I presume the way to do things is to simply check the docbook
> source into CVS. The output/compiled versions of the files won't be
> in CVS, and we won't create a "pdf module", right? Once in a while
> we will create a "pdf file release" of (say) version 1.0, and just
> upload that as a file.
>
> Am I on the right track? If so, I'll dump the files into the CVS
> tree soonest.
>
> By the way; am I right in saying that:
>
> "CVS modules do not necessarily tie in in any way with sourceforge
> modules"
>
> I've seen lots of things saying stuff like "don't add a module
> to sourceforge which you aren't going to use"... I was under the
> impression that sourceforge modules tied into CVS modules somehow:
> after working through your site's CVS tree, though, it seems like
> this isn't the case? Notably there's a website module in the CVS
> tree which isn't on the module list on the sourceforge side.
>
> Oh, by the way, I've added you to the sourceforge side of things;
> I don't know what permission changes I need to make?
>
> Cheers,
>
> Oskar
Received on Wed May 31 2000 - 06:13:35 MDT