On 2017-03-12 23:53, Kristian Fiskerstrand wrote: > On 03/11/2017 11:23 PM, Andrew Savchenko wrote: >> While the Deputy may be assigned, this still gives all power to >> single hands. Maybe it will be better to establish something like >> the Security Project Council (SPC)? E.g. three project members may >> be elected to this SPC, so that all serious decisions will require >> some team agreement from at least 2 SPC members. This way the >> Deputy will not be needed as well. > > Something like this has been discussed. I personally don't like the > approach too much given that it adds a certain degree of bureaucracy and > can remove responsibility. An important part of the GLEP is that the > project lead is responsible to the council for the changes that is made. > Having possibility to overrule that by members would mean that the lead > is not able to control the action, and as such, can't be responsible for > it. If the members disagree with the lead they can call for re-election > as per GLEP:39 already.
Looks like we are disagreeing about the role of a project lead. The primary goal of any Gentoo project is to group people working towards the same goal(s) in small, manageable groups. It shouldn't need a lead in most cases to control the project members. A lead is only needed if the team can't get a decision. Saying that the team could call for re-election if they don't like lead's decision is ridiculous from my view: Like said it isn't the lead who controls the direction. It is the lead who should step down if he/she doesn't feel comfortable with the team decision and no longer wants to represent the project anymore because he/she disagree so much with the team decision. -- Regards, Thomas
signature.asc
Description: OpenPGP digital signature
