On Tuesday, November 29, 2022 at 12:57:14 AM UTC-7 Ullrich Hafner wrote:
> I am currently -1 for this change, but I do not yet have access to the > full governance board discussion yet. > > Basically, the reasoning for this change is not clear for me. Looking back > in the history of the governance board, we are 4 active members making all > the decisions. As far as I remember, Kohsuke did not participate in a > decision in the last couple of years. So in practice we have 4 votes in our > meetings, and if 2 of these votes are from one company this company can > block any decision. They have not majority, but we have a stalemate which > is a potential risk. So I would prefer to not change the current situation. > It would even make sense to update the current rule so that no company can > get 50% of the 4 elected seats. Then we do not need discuss if Kohsuke is > affiliated with Cloudbees or not. > > If the root of your concern is stalemate due to two people elected from a single company, then the current rules already create the potential for that situation today. If two people from Red Hat, JFrog, AWS, Google, Microsoft, or any other company (with two exceptions) were to be elected to the Jenkins board, that would be allowed by the current rules. They would not have a majority on the board (2 out of 5) but would be 50% of the active participating members of the board. There are two companies (CloudBees and Launchable) that are blocked from having two elected members of the board because the current rule disallows a majority of board members to be affiliated with a single company and the current practice has been to declare that Kohsuke is affiliated with CloudBees. I agree with Basil's observation that we've seen no example of stalemate in the several years that I've been involved with the board. The most controversial topic brought to the board recently was this proposal to change the rules related to membership of the board. It had 3 board members in favor, one board member opposed, and Kohsuke stated his support of the proposal separately. I'm far less concerned with the risk of stalemate than I am with the risk of work not being completed that helps the Jenkins project succeed. Mark Waite -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/e586f71e-5421-4e31-8383-16d2012915e1n%40googlegroups.com.
