On Aug 1, 2007, at 17:04 , Carsten Ziegeler wrote:
Additional question: do we ensure that only people with a cla get
access
to the felix site in confluence?
Good question. We should really set up FELIXxSITE and use that for
the
website, then FELIX is our wiki. We then create felix-committers
group,
and only add committers to that.
Yepp, I think this makes sense - I already set up the site at
http://felix.apache.org/FELIX :)
As far as I understand correctly, we need to have a site that is only
editable by people that have signed a CLA if we ship whole copies of
the website as part of our releases. We might want to do that (or at
least parts of the site) so it makes sense to ensure that only people
with a CLA end up in our group.
At the moment, we have three groups that have rights to this space:
- confluence-users (that can view, create comments and create
attachments); this is a group that anybody who registers with
Confluence ends up in, so we only allow those peopel very basic
rights (comments do not get exported anyway, attachments is something
we could argue about, since those are exported, so we might want to
change the rights on that point);
- felix-users (full edit rights on pages, comments and
attachments); for everybody that is a committer in the project and
maintains part of the site (we indeed should make 100% that everybody
in this group has a CLA on file);
- felix-admins (admin rights); which mainly means these users can
administer the space.
So rights wise, as long as we make sure all "felix-users" have a CLA
on file, we're fine, even if we distribute (part of) the site in our
releases.
The second question, whether we want a separate wiki apart from our
website, is a different matter. I would say, our FELIX space IS our
website, from that sense we simply use Confluence as our CMS for the
site.
We could setup a second space (let's say FELIXWIKI) if we feel there
is a need for a separate wiki. To be honest, I personally don't feel
a strong need to have a wiki, but if others in the community feel we
do, then let's create one and come to some kind of consensus about
what should be on our site and what should be on our wiki.
Unfortunately, there is a slight problem with this right now, most
links
and references (to images etc) are absolute and therefore pointing
back
to the cwiki instance. I have currently no clue how to change this.
The links in the menu are simply hardcoded in the template. I can fix
those. It might take a bit of fiddling to make sure the relative
paths we use always work, but that should be fixable.
I'll report back as soon as I've done that. :)
Greetings, Marcel
