Gentoo Archives: gentoo-nfp

From: "Michał Górny" <mgorny@g.o>
To: gentoo-nfp@l.g.o
Subject: Re: [gentoo-nfp] [RFC] Bylaws change: extend inactivity removal to all members
Date: Mon, 04 Jun 2018 07:15:37
Message-Id: 1528096527.1215.21.camel@gentoo.org
In Reply to: Re: [gentoo-nfp] [RFC] Bylaws change: extend inactivity removal to all members by Matthew Thode
1 W dniu nie, 03.06.2018 o godzinie 14∶30 -0500, użytkownik Matthew Thode
2 napisał:
3 > On 18-06-01 20:22:36, Michał Górny wrote:
4 > > Hi, everyone.
5 > >
6 > > Following the recent discussion, I would like to propose updating
7 > > the Foundation bylaws to provide uniform 'removal for inactivity' for
8 > > all Foundation members.
9 > >
10 > > More specifically, I propose changing the first two paragraphs
11 > > of section 4.4 (Continuation of Membership) from:
12 > >
13 > > Full members who remain Gentoo developers shall have their membership
14 > > continued until it is terminated in accordance with 4.8 or 4.9.
15 > >
16 > > Full members who retire from the Gentoo project shall have there
17 > > membership continued while they indicate that they remain interested
18 > > in the affairs of the Foundation unless their membership is
19 > > terminated in accordance with 4.8 or 4.9.
20 > >
21 > > to:
22 > >
23 > > Full members shall have their membership continued while they indicate
24 > > that they remain interested in the affairs of the Foundation, unless
25 > > their membership is terminated in accordance with 4.8 or 4.9.
26 > >
27 > > (leaving the last paragraph unchanged)
28 > >
29 > >
30 > > This means to solve two problems:
31 > >
32 > > 1. Technically, the inactivity-removal procedure does not apply to non-
33 > > developer Foundation members, and given that unlike regular developers
34 > > they won't become 'retired developers', they would never be removed.
35 > >
36 > > 2. The active developer status restriction doesn't seem to have much
37 > > value. On one hand, it probably makes sense because the removed
38 > > developer could reapply for membership right away, so forcefully
39 > > removing him seems pointless. On the other hand, there's no point to
40 > > prevent Trustees from cleaning up the member list periodically if some
41 > > of the devs don't really want to stay.
42 > >
43 > > That said, I think the new wording would make the removal procedure
44 > > cleaner and more fair, as the removal rules would be the same for all
45 > > Foundation members and the list could be determined from a single data
46 > > source.
47 > >
48 > > [1]:https://wiki.gentoo.org/wiki/Foundation:Bylaws#Section_4.4._Continuation_of_Membership
49 > >
50 >
51 > Please present the full wording of what the new 4.4 bylaw would be (for
52 > clarity). I think simplifying the bylaw to one class makes sense. The
53 > same should probably be done for 4.3's admission procedures, having two
54 > forms of entry/exit doesn't make total sense.
55 >
56 > I think that Rich's proposal is good, we do need voting to ensure
57 > quorum. Though if the voting piece is removed from 4.4 it can be take
58 > up by the more generic 4.9 (or added to 4.8 as 'not voting in x
59 > elections will constitute a voluntary withdrawl').
60 >
61
62 Here you are:
63
64 https://gist.github.com/mgorny/66e6a3b72910162c8aaccbd0b12e3906
65
66 Followed up on your idea and changed 4.3 as well. Now all members are
67 admitted just the same, and added 'being a Gentoo developer'
68 as an obvious way of contributing to Gentoo.
69
70 I've also restored the old 4.4 'loss of interest' wording. I think it's
71 better to be explicit there.
72
73 --
74 Best regards,
75 Michał Górny