From: Georgy Yakovlev <gyakovlev@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] Corporate affiliations of Council members
Date: Sun, 28 Jun 2020 12:57:41 -0700 [thread overview]
Message-ID: <c4eb0668-0504-5c50-698a-271c8647ae45@gentoo.org> (raw)
In-Reply-To: <f6ccabba2bb9421a7d2e5de6c1f82a86a1f00225.camel@gentoo.org>
[-- Attachment #1.1: Type: text/plain, Size: 1927 bytes --]
On 6/22/20 9:18 AM, 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.
>
> 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.
>
Hi,
I'm a bit late to the party, was away without internet access most of
the week.
I work at Sony / PlayStation, like some other people do.
Things I do at dayjob have very little in common with gentoo work I'm
doing or interested in, but the following exceptions:
- I maintain handful of python packages, nothing critical here, some
will be dropped after py3.6 goes away completely.
- I maintain openjdk* for work purposes.
and icedtea*, because I have to and nobody else will.
While only one JDK variant I use at dayjob, I do extra work for
community, maintaining openjdk8 openjdk11 openjdk8-bin openjdk11-bin
openjdk-jre-bin icedtea(via proxying upstream) icedtea-bin on amd64 arm
arm64 ppc ppc64 ppc64le x86 with a mix of openjfx and musl(soon). That's
a lot of builds.
The equipment to maintain jdk on all those platforms is my own or
provided by Gentoo (qemu does not work for it, cross is questionable).
I don't receive guidance or requests from employer on how gentoo and/or
council work should be done, decisions are mine, community comes first.
The only real requirement is assigning copyright properly. That's it.
I almost never commit from work, because work done at my own time using
my or gentoo equipment, hence my commits are not copyrighted.
Feel free to ask questions if you have any.
Regards, Georgy.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-06-28 19:57 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
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 [this message]
-- 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=c4eb0668-0504-5c50-698a-271c8647ae45@gentoo.org \
--to=gyakovlev@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