| 1 |
On Sun, Nov 13, 2016 at 9:34 AM, William L. Thomson Jr. |
| 2 |
<wlt-ml@××××××.com> wrote: |
| 3 |
> On Sunday, November 13, 2016 8:59:40 AM EST Rich Freeman wrote: |
| 4 |
>> |
| 5 |
>> Why would we want people who don't make any significant contributions |
| 6 |
>> to the organization to be voting on how it ought to operate? |
| 7 |
> |
| 8 |
> You mean like you? |
| 9 |
> |
| 10 |
> git shortlog -sn |
| 11 |
> |
| 12 |
> 40 William L. Thomson Jr |
| 13 |
> 38 Richard Freeman |
| 14 |
> |
| 15 |
> Really interesting comment given I am not a developer and have more commits in |
| 16 |
> tree than a council member. Not to mention my overlay... |
| 17 |
> |
| 18 |
> I would recommend not weighing people by the contributions and instead using a |
| 19 |
> principle of the US, all are equal.... |
| 20 |
|
| 21 |
Your figures neglect history before the git migration, but are |
| 22 |
accurate for the last year. |
| 23 |
|
| 24 |
Believe it or not, not everybody who contributes to Gentoo writes |
| 25 |
ebuilds. You're not the first to point out that I don't have that |
| 26 |
many commits compared to many. I think the last time it was pointed |
| 27 |
out was before an election and it didn't seem to bother anybody. |
| 28 |
|
| 29 |
Again, I think you misunderstand the purpose of the Council. |
| 30 |
|
| 31 |
Anybody can start a project or lead a project. |
| 32 |
|
| 33 |
Anybody can author ebuilds. Anybody with commit access can commit them. |
| 34 |
|
| 35 |
Anybody can join PR and write news articles/etc. |
| 36 |
|
| 37 |
Ultimately the main power of Council members is to resolve conflicts |
| 38 |
with final decisions. That may not be the only thing they do, but |
| 39 |
when it comes down to it that is what they're basically empowered to |
| 40 |
do. My personal sense is that the people who are currently on the |
| 41 |
Council got there because people trust that when an issue comes up |
| 42 |
they're going to weigh all the options and come up with a reasonable |
| 43 |
solution that everybody can live with. I think most devs would prefer |
| 44 |
that the Council stay fairly hands-off. They don't want the Council |
| 45 |
telling every project how to do its thing, but we all recognize that |
| 46 |
sometimes there is some sort of conflict and a need to have a final |
| 47 |
call made so that we don't go band and forth endlessly on a mailing |
| 48 |
list about it. |
| 49 |
|
| 50 |
-- |
| 51 |
Rich |
Archives