If SourceForge before it went proprietary is configured in the same way as Savane, can anyone point me to pre-proprietary SF documentation that would cover Groups and Group Types and their config fields?
My questions and confusions can be boiled down into the following:
I can't tell what the difference is between a Group and Group Type - both
seem to allow configuration of specific paths for homepages, CVS, etc. What
would be the point of configuring two groups (projects) to use the same CVS
path, and so on?
What I think I want to do is set up a Group Type, Foo, but just have this be a label.
I want two groups, FooBar and FooBaz, both with independent (though
overlapping) memberships, and their own Savane pages, their own CVS, their
own mailing list(s), etc. Much like how Savane and Savane-Doc are different
projects at gna.org
On the Group Type and at the bottom of the Group pages, what are all of these
fields and how do they work?
Like "Project WWW Homepage". Won't Savane simply generate one
automatically? Are Homepage Dir, Homepage URL and Homepage CVSview URL
of what Savane does automatically?
How does one set up webcvs, viewcvs, archzoom, or the like to work with
Savane? What's the difference between them? Is any one such program more
recommendable than others?
Primary Source Code Manager: CVS - why can I pick subversion, etc., if this
is for CVS? What is a "Basic Directory" compared to a "Basic CVS
Directory"? What is a "CVS Attic/Gna" or "Savannah/GNU" compared to
"Basic CVS Directory"?
How does one set up CVS (which I have installed but have not done anything
with yet) to work with Savane? All INSTALL.verbose says on the topic is
"add 2 new directories... For Source CVS and HTML cvs", which isn't very
instructive, and doesn't seem to apply to having more than one project. I need to setup a FooBar Group for coders, and FooBaz Group for internal admin purposes (documents, not code, but tracked in CVS as if they were code) with differential access to each
group - most people in FooBar are not going to be in FooBaz. And I anticipate needing to set up multiple groups for multiple actual projects, e.g. FooBar and FooBaz dev and business purposes, respectively, for project 1, and QuuxBar & QuuxBaz for project 2. Should Foo and Quux be Group Types, or should all four Groups each be their own Group Type?
Do I have to manually set Repository Dir and a Repository View URL in Group
Type or Group at all?
What is the difference between Primary Source Code Manager: CVS - Repository
View URL, and Project WWW Homepage - Homepage View URL? Is the later CVS for
the HTML, etc., of the homepage itself? I don't want to create a custom
fancy homepage for any projects, just use Savane's interface to them, as athttps://gna.org/projects/savane
for example. I would like them
to have their
own URLs, e.g. https://my.site/projects/foobar
If I enabled both CVS and Subversion would Savane keep them in synch (e.g. if
one project member makes changes via CVS and another changes something via
Subversion, do the two repositories record both sets of changes and merge
them somehow through Savane?)
Basically, I am not understanding how this stuff works - the Group Type
config page says everything is "(created by the backend)"; but if this is
so, why do all these fields exist?
I do see how to integrate MailMan much more clearly than CVS; that part is
pretty obvious. Still, it is confusing that the Group config allows me to add mailinglists, as many as I like, while the Group Type config just has one.