From: Rich Freeman <rich0@gentoo.org>
To: gentoo-project <gentoo-project@lists.gentoo.org>
Cc: Alec Warner <antarus@gentoo.org>
Subject: Re: [gentoo-project] Corporate affiliations of Council members
Date: Wed, 24 Jun 2020 07:23:04 -0400 [thread overview]
Message-ID: <CAGfcS_kpmmWMs_F13bH8h2ydvD1yU65Bx4MYOTFz+9oN5K7PHw@mail.gmail.com> (raw)
In-Reply-To: <c7fe22364165dce4fb626e151652f324e4e279f3.camel@gentoo.org>
On Wed, Jun 24, 2020 at 1:53 AM Michał Górny <mgorny@gentoo.org> wrote:
>
> On Wed, 2020-06-24 at 00:17 +0300, Andreas K. Hüttel wrote:
> > Am Montag, 22. Juni 2020, 21:56:06 EEST schrieb Alec Warner:
> > > I'm not sure why we would single out employment here; surely there are
> > > other potential relationships that could give rise to conflicts? Why are
> > > these excluded from disclosure?
> > >
> >
> > Because money is a powerful (and socially accepted) incentive.
> >
>
> To be honest, he's right. Money is not specific to employment. Imagine
> someone running a Gentoo fork, with its own community, donations or
> other source of income. It's still money, still potential source of
> conflict, but not employment ;-). Like when Gentoo implements something
> their distro boasted of, and now their users may choose vanilla Gentoo.
Most organizations have a policy around conflicts of interest (in part
because if you're 501c3 the IRS will ask you every year if you have
one). Receiving money from an organization certainly is on that list.
Usually ownership, being on a board or being an officer in an org is
listed as well (which might cover this). Family relationships with
people in those situations are also usually on the list.
Beyond that though I think that a lot of things that are considered a
"conflict of interest" around here are not considered conflicts in
most organization. I've beaten that horse to death and I suspect my
opinion is in the minority on that point (within Gentoo, but not
outside of this org), so I'll leave it at that.
--
Rich
next prev parent reply other threads:[~2020-06-24 11:23 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
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 [this message]
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_kpmmWMs_F13bH8h2ydvD1yU65Bx4MYOTFz+9oN5K7PHw@mail.gmail.com \
--to=rich0@gentoo.org \
--cc=antarus@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