On Fri, 2023-07-21 at 08:59 -0400, Ben Cotton wrote:
>
> To be fully transparent, the reason I said that at all was to mitigate
> potential "FESCo voting rules are changing in the next big step
> towards IBM's destruction of all things community" FUD. It's been a
> silly enough time to be online
On Fri, Jul 21, 2023 at 2:03 AM Kevin Kofler via devel
wrote:
>
> Ben Cotton wrote:
> > This will be helpful to people who aren't regularly involved in FESCo
> > votes. If that's you: the proposal presented here is largely
> > clarification. There's not much in the way of substance change.
>
>
On Fri, Jul 21, 2023 at 08:02:53AM +0200, Kevin Kofler via devel wrote:
> Ben Cotton wrote:
> > This will be helpful to people who aren't regularly involved in FESCo
> > votes. If that's you: the proposal presented here is largely
> > clarification. There's not much in the way of substance change.
Ben Cotton wrote:
> This will be helpful to people who aren't regularly involved in FESCo
> votes. If that's you: the proposal presented here is largely
> clarification. There's not much in the way of substance change.
Actually, it changes existing practice in that it changes the meaning of the
On Thu, Jul 20, 2023 at 3:46 PM Zbigniew Jędrzejewski-Szmek
wrote:
>
> Stephen Gallagher proposed a change to FESCo voting rules [1].
This will be helpful to people who aren't regularly involved in FESCo
votes. If that's you: the proposal presented here is largely
clarification. There's no
Hi,
Stephen Gallagher proposed a change to FESCo voting rules [1].
The latest draft:
--&<-
Ticket Votes (Preferred)
Once a formal proposal is made in a ticket, voting will proceed. A
Change ticket is assumed to be a a
