public inbox for gentoo-project@lists.gentoo.org
 help / color / mirror / Atom feed
From: Richard Yao <ryao@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re:  [gentoo-project] Corporate affiliations of Council members
Date: Thu, 2 Jul 2020 13:14:00 -0400	[thread overview]
Message-ID: <96F0D809-B3F7-442C-93ED-82D95595AC6F@gentoo.org> (raw)


> On Jun 22, 2020, at 12:18 PM, Michał Górny <mgorny@gentoo.org> wrote:
> 
> Hello,
> 
> Here's another question for the Council nominees.  I'd like to ask
> the Council members to disclose their corporate affiliations,
> in particular whether they are employed or in partnership with companies
> using Gentoo or Gentoo derivatives.
> 
> This is because I believe that the electorate deserves to know whether
> their elected Council member may end up being in conflict of interest
> between doing what's right by the wide community and what's requested by
> his employer.

I understand the motivation for having this information available, but I have full confidence that all council members will make decisions in the best interest the entire community regardless of conflicts of interest. I am not on the council, but I am receiving money from buurst inc for upstream work that is only superficially related to Gentoo. My statements are not influenced by third parties.

Also, acting in the best interest of the entire community requires considering everyone’s needs when making decisions. Corporate interests are a part of that and they therefore should be given some sort of weight in decisions. As a distribution, we generally do a good job of supporting various use cases, so conflicts are less of an issue for us than they are for others.

Lastly, I hope that in trying to avoid one extreme, we do not accidentally go into the opposite extreme. Becoming anti-corporation in the process of trying to avoid being anti-consumer helps no one, including consumers. Not that I think we are, but it is possible to go so far in the perceived direction of neutrality that we overshoot the point of neutrality and gain a bias that is the opposite of the bias that concerned us. Being aware of that is important .
> -- 
> Best regards,
> Michał Górny


             reply	other threads:[~2020-07-02 17:14 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-02 17:14 Richard Yao [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-06-22 16:18 [gentoo-project] Corporate affiliations of Council members Michał Górny
2020-06-22 17:07 ` Brian Dolbec
2020-06-22 17:36 ` Robin H. Johnson
2020-06-22 18:20   ` Rich Freeman
2020-06-22 18:15 ` Matt Turner
2020-06-22 18:56 ` Alec Warner
2020-06-22 20:17   ` Michał Górny
2020-06-23 21:17   ` Andreas K. Hüttel
2020-06-24  5:53     ` Michał Górny
2020-06-24 11:23       ` Rich Freeman
2020-06-22 19:36 ` Ulrich Mueller
2020-06-22 20:32 ` William Hubbs
2020-06-23 13:33 ` Thomas Deutschmann
2020-06-23 17:48 ` Patrick Lauer
2020-06-23 20:50   ` Andreas K. Hüttel
2020-06-24 19:30     ` Patrick Lauer
2020-06-24 20:00       ` David Seifert
2020-06-24 20:08       ` Andreas K. Hüttel
2020-06-24 20:22         ` Patrick Lauer
2020-06-26 13:39           ` Andreas K. Huettel
2020-06-23 21:02 ` Andreas K. Hüttel
2020-06-26  1:41 ` Max Magorsch
2020-06-26  3:23 ` Aaron Bauman
2020-06-27 13:51 ` Mikle Kolyada
2020-06-28 19:57 ` Georgy Yakovlev

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=96F0D809-B3F7-442C-93ED-82D95595AC6F@gentoo.org \
    --to=ryao@gentoo.org \
    --cc=gentoo-project@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox