public inbox for gentoo-kernel@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alice Ferrazzi <alice.ferrazzi@gmail.com>
To: Gentoo Kernel List <gentoo-kernel@lists.gentoo.org>
Subject: Re: [gentoo-kernel] Gentoo Kernel Project Lead - 2018
Date: Mon, 15 Jan 2018 05:01:23 +0900	[thread overview]
Message-ID: <CANWzcUqnDSKJHG=fFiNfw4CnvbX35PFxJQV2Z5tC=awBmSPjUw@mail.gmail.com> (raw)
In-Reply-To: <4f7088a9-c623-c84e-bf40-7ec8e58f2345@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 3210 bytes --]

Hello Mike,

sound reasonable to me and I self-nominate myself.

My manifesto:

My aim is to make the Gentoo Kernel Project became more present (with a
visible and strong activity), collaborate more with upstream and taking
Gentoo kernel to a more high-quality level.
We can achieve better quality in the Gentoo kernel by automating the Gentoo
kernel release quality check.
For automating the release quality check I'm working on the Gentoo kernel
CI [1], that is providing feedback on the Gentoo Kernel Sources, for making
it fastly showing eventual problems.
In the future, I would like to add more feature and check tools to the
Gentoo Kernel CI.
I'm following most of the Gentoo Kernel bugs reports on bugzilla for giving
fast support and I usually work on releasing gentoo-sources in a responsive
manner. I'm also helping with rt-sources, git-sources, vanilla-sources and
every other package under the Gentoo kernel project responsibility.
To make the Gentoo kernel project more visible I'm doing conferences (Open
Source Summit 2017 (kernel developer panel), SOSP 2017, Open Source
Conference winter and spring 2017) and managing the Gentoo Kernel Public
relationships.
I'm keeping a strong collaboration with Kernel upstream, getting
information about new releases, future problems and also informing kernel
upstream of eventual problems with the gentoo-sources kernel.
I'm pre-testing upstream kernel pre-release for identifying problems before
we release gentoo-sources.
I'm creating and updating wiki pages under the Gentoo kernel project.
I'm working on the Gentoo kernel live patch service (Elivepatch [2]) and
live patch package (kpatch).
I'm part of the Gentoo Kernel Security, where I'm researching new security
issue, this helps me leading security responses for the Gentoo Kernel
Project.

[1] https://wiki.gentoo.org/wiki/Project:Kernel/Kernel_CI
[2] https://wiki.gentoo.org/wiki/Elivepatch

Thanks

On Mon, Jan 15, 2018 at 4:01 AM, Mike <mpagano@gentoo.org> wrote:
> Hello, Gentoo Kernel Project Members,
>
> It's that time of the year again where we need to elect a lead.  As
> there are only 5 of us, I am suggesting we open up nominations for 10
> days and allow 10 days for manifestos or discussion and then vote at a
> meeting where people who can't make the meeting can just submit their
> vote beforehand if they want.
>
> Our current member list from the wiki is:
>
> Alice Ferrazzi (alicef)
> Anthony G. Basile (blueness)
> Tony Vroon (Chainsaw)
> Greg Kroah-Hartman (gregkh)
> Mike Pagano (mpagano)
> Manuel Rüger (mrueg)
> Thomas Deutschmann (Whissi)
> Magnus Granberg (Zorry)
>
>
> Timing
> If we start nominations (please self-nominate yourself if you want too),
> then the nominations period would stop at 24/1/2017 19:00 UTC.
>
> The 10 days after that will put us at 3/2/2017 1900 UTC for voting.
> Maybe we can have a meeting that weekend.
>
> Does this sound reasonable to everyone?
>
> Mike
>



-- 
Thanks,
Alice Ferrazzi

Gentoo Kernel Project Leader
Gentoo Foundation Board Member
Mail: Alice Ferrazzi <alice.ferrazzi@gmail.com>
PGP: 2E4E 0856 461C 0585 1336 F496 5621 A6B2 8638 781A

[-- Attachment #2: Type: text/html, Size: 3705 bytes --]

  reply	other threads:[~2018-01-14 20:01 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-14 19:01 [gentoo-kernel] Gentoo Kernel Project Lead - 2018 Mike
2018-01-14 20:01 ` Alice Ferrazzi [this message]
2018-01-17 21:56   ` Tsukasa Mcp_Reznor
2018-01-19 13:30     ` Alice Ferrazzi
2018-01-14 20:02 ` Alice Ferrazzi
2018-01-17 18:51 ` Thomas Deutschmann
2018-01-23 12:59 ` Mike Pagano
2018-01-24 23:37   ` Mike
2018-01-25  0:43     ` Thomas Deutschmann

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='CANWzcUqnDSKJHG=fFiNfw4CnvbX35PFxJQV2Z5tC=awBmSPjUw@mail.gmail.com' \
    --to=alice.ferrazzi@gmail.com \
    --cc=gentoo-kernel@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