On 18/07/2008, at 3:05 PM, Alan Burlison wrote:

> Glynn Foster wrote:
>
>> They're called a Contributor too, but they have no attributes. They  
>> only
>> start building those attributes as their contributions and respect by
>> their peers grow.
>
> As I explained in the past, we are not storing sets of per-application
> rights for each member in the database, we are storing users ,
> collectives and the relationships (roles) between the two.

Can you give me some examples of some typical relationships please? It  
may well be that as soon as a peer has recognized you, you get access  
to web editing and a repository and whatever else - but that doesn't  
mean that you're the one deciding the direction of the project.


Glynn


Reply via email to