From: Rich Freeman <rich0@gentoo.org>
To: gentoo-project <gentoo-project@lists.gentoo.org>
Subject: Re: [gentoo-project] Corporate affiliations of Council members
Date: Mon, 22 Jun 2020 14:20:54 -0400 [thread overview]
Message-ID: <CAGfcS_kxqHaM1YKpHDkpVP3riLK6y7Cxh+MQrUBENT2RhFG7Eg@mail.gmail.com> (raw)
In-Reply-To: <robbat2-20200622T172513-273056617Z@orbis-terrarum.net>
On Mon, Jun 22, 2020 at 1:36 PM Robin H. Johnson <robbat2@gentoo.org> wrote:
>
> On Mon, Jun 22, 2020 at 06:18:43PM +0200, Michał Górny 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.
> While I would like to know this information, I'm not sure that it can be
> disclosed in every case.
>
> I would consider it entirely possible that a council member works for a
> company, that has then bound via NDA, to not be permitted to make public
> statements about what their company uses or does not use.
>
> Further, for larger companies, I would see it entirely possible that the
> council member does not know about Gentoo usage in every corner of the
> company: the company is just too large.
I would leave it to individuals to disclose what they can.
I think the main concern is with people affiliated with companies who
are paying them to develop for Gentoo since the company uses Gentoo.
Ie their employer has a direct interest in what we're doing.
If you work in a mailroom at Airbus you probably wouldn't know if
somebody is using Gentoo in the A380 flight control system, but really
that isn't the kind of relationship most here are likely to care about
anyway.
I don't think there should be an expectation that people disclose all
their other affiliations if they have nothing at all to do with
Gentoo. The concern is that some company is paying somebody to run
for the Council/etc.
--
Rich
next prev parent reply other threads:[~2020-06-22 18:21 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2020-07-02 17:14 Richard Yao
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=CAGfcS_kxqHaM1YKpHDkpVP3riLK6y7Cxh+MQrUBENT2RhFG7Eg@mail.gmail.com \
--to=rich0@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