> > Also could you please elaborate a bit on the usage of the roles to prevent > this? There doesn't seem to be any role to fill the gap between full Owner > to Contributor. >
There is a "Committer" role between Owner and Contributor. From your description of events it sounds like the current project owner doesn't want anyone else having commit access? Of course, sorry. What I meant is that it doesn't seem possible to grant someone some of the permissions of an Owner (add new members) without giving the most sensitive permissions as well (remove members, delete project), in the same way Contributor and Committer permissions can be adjusted. Yes, the current owner removed two owners and a committer and doesn't want anyone else to commit but himself. His last commit is 5 months old. > > It may now be worth revisiting whether or not Project Hosting should adopt > differently-enforced administration transformations like enforced unanimity > or votes or whatnot - do you think you'd like to file a feature > request<http://code.google.com/p/support/wiki/FAQ#How_do_I_file_a_feature_request_for_Google_Code?> > ? > -Nathaniel > I will absolutely do so if it hasn't been requested already. A voting system does seem like a good solution for projects with several owners, or even better a delay system to prevent someone from removing several owners at once. Thank you. -- You received this message because you are subscribed to the Google Groups "Project Hosting on Google Code" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-code-hosting/-/usdqIkCwkOgJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-code-hosting?hl=en.
