Roles in CollabNet?

[Markus Neteler]

Hi again on this issue,

I still have the pending subscription and don't know how to process
it. Perhaps there are news which I am not aware of?
In this case I don't know the person. So I hesitate to grant write
access... You suggested to grant "observer" status, but the CN
system doesn't seem to permit a "downgrade" of the request.

thanks
Markus

On 6/30/06, Markus Neteler <neteler.osgeo at gmail.com> wrote:
> Auke,
>
> thanks for your quick reply.
>
> On 6/30/06, Auke Jilderda <auke at collab.net> wrote:
> > Markus,
> >
> > I am somewhat new to OSGeo.org and in the process of getting up to speed
> > so don't know the historic context of the current situation but I can
> > tell you how it works.
> >
> > The CollabNet infrastructure comes with a role based access model in
> > which a user account has access rights and permissions to resource via
> > having roles in projects.  Each role defines a (hopefully coherent) set
> > of access rights and permissions.  The standard, out-of-the-box set of
> > roles are described at [1].  In addition, the infrastructure lets
> > administrators define new and change existing roles.
> >
> > There currently are three roles defined that a user can request in your
> > project:
> > - Observer: Read-only access to project code; can also submit issues;
> >   'observer' of project.
> > - Contributor: Developer/User that contributes code via Project Tracker.
> > - User: User or application developer that makes use of the software in
> >   the project.
>
> thanks - I have added above list to our Wiki Collabnet FAQ.
>
> > Question is exactly how these roles are intended.  The current
> > implementations of these roles make no sense to me so I will figure out
> > who came up with this and sanitise the set up.  We need at the least a
> > project owner (full r/w access + ability to configure a project),
> > developer (full r/w access), and observer (mostly read-only access).
> >
> > That said, I suggest you grant this person the Co-Project Owner role if
> > you want him to have write access and Observer if you want him to have
> > read-only access.  I will keep you posted on the progress on this.
>
> In this case I don't know the person. So I hesitate to grant write
> access... I'll not assign a roles to this person till the situation
> is settled.
>
> thanks for taking care,
>
> Markus
>
> >
> > Auke
> >
> > PS: I am in the process of setting up a support project to organise and
> >     streamline site support.  That's why I already cc the help list that
> >     is not yet accessible.  It soon will be.
> >
> >  1. https://www.osgeo.org/scdocs/ProjectRoles
> >
> > On Friday, June 30, 2006 11:05, Markus Neteler wrote:
> > >
> > > Dear WebCom,
> > >
> > > I am not sure to whom send this question...: I got below request and
> > > would like to better understand the available CollabNet roles:
> > >
> > > The person requested "Project Contributor role" - what does that mean?
> > >
> > > The system suggests:
> > > - Project Owner
> > > - Co-Project Owner
> > > - User
> > > - Project Contributor
> > >
> > > as options, but the help explains something else:
> > >  https://www.osgeo.org/scdocs/ProjectRoles
> > > - Content Developer
> > > - Content Viewer
> > > - Developer
> > > - Executive (Project Level)
> > > - Observer
> > > - Project Owner
> > >
> > > The only identical one is "Project Owner"...
> > >
> > > Any ideas? Answers should be added here:
> > > http://wiki.osgeo.org/index.php/Collabnet_FAQ#Project_Owner_Questions
> > >
> > > thanks!
> > >  Markus
> >
>
>
> --
> Open Source Geospatial Foundation
> http://www.osgeo.org/
>


-- 
Open Source Geospatial Foundation
http://www.osgeo.org/