| 1 |
Hello Mike, |
| 2 |
|
| 3 |
sound reasonable to me and I self-nominate myself. |
| 4 |
|
| 5 |
My manifesto: |
| 6 |
|
| 7 |
My aim is to make the Gentoo Kernel Project became more present (with |
| 8 |
a visible and strong activity), collaborate more with upstream and |
| 9 |
taking Gentoo kernel to a more high-quality level. |
| 10 |
We can achieve better quality in the Gentoo kernel by automating the |
| 11 |
Gentoo kernel release quality check. |
| 12 |
For automating the release quality check I'm working on the Gentoo |
| 13 |
kernel CI [1], that is providing feedback on the Gentoo Kernel |
| 14 |
Sources, for making it fastly showing eventual problems. |
| 15 |
In the future, I would like to add more feature and check tools to the |
| 16 |
Gentoo Kernel CI. |
| 17 |
I'm following most of the Gentoo Kernel bugs reports on bugzilla for |
| 18 |
giving fast support and I usually work on releasing gentoo-sources in |
| 19 |
a responsive manner. I'm also helping with rt-sources, git-sources, |
| 20 |
vanilla-sources and every other package under the Gentoo kernel |
| 21 |
project responsibility. |
| 22 |
To make the Gentoo kernel project more visible I'm doing conferences |
| 23 |
(Open Source Summit 2017 (kernel developer panel), SOSP 2017, Open |
| 24 |
Source Conference winter and spring 2017) and managing the Gentoo |
| 25 |
Kernel Public relationships. |
| 26 |
I'm keeping a strong collaboration with Kernel upstream, getting |
| 27 |
information about new releases, future problems and also informing |
| 28 |
kernel upstream of eventual problems with the gentoo-sources kernel. |
| 29 |
I'm pre-testing upstream kernel pre-release for identifying problems |
| 30 |
before we release gentoo-sources. |
| 31 |
I'm creating and updating wiki pages under the Gentoo kernel project. |
| 32 |
I'm working on the Gentoo kernel live patch service (Elivepatch [2]) |
| 33 |
and live patch package (kpatch). |
| 34 |
I'm part of the Gentoo Kernel Security, where I'm researching new |
| 35 |
security issue, this helps me leading security responses for the |
| 36 |
Gentoo Kernel Project. |
| 37 |
|
| 38 |
[1] https://wiki.gentoo.org/wiki/Project:Kernel/Kernel_CI |
| 39 |
[2] https://wiki.gentoo.org/wiki/Elivepatch |
| 40 |
|
| 41 |
Thanks |
| 42 |
|
| 43 |
|
| 44 |
On Mon, Jan 15, 2018 at 4:01 AM, Mike <mpagano@g.o> wrote: |
| 45 |
> Hello, Gentoo Kernel Project Members, |
| 46 |
> |
| 47 |
> It's that time of the year again where we need to elect a lead. As |
| 48 |
> there are only 5 of us, I am suggesting we open up nominations for 10 |
| 49 |
> days and allow 10 days for manifestos or discussion and then vote at a |
| 50 |
> meeting where people who can't make the meeting can just submit their |
| 51 |
> vote beforehand if they want. |
| 52 |
> |
| 53 |
> Our current member list from the wiki is: |
| 54 |
> |
| 55 |
> Alice Ferrazzi (alicef) |
| 56 |
> Anthony G. Basile (blueness) |
| 57 |
> Tony Vroon (Chainsaw) |
| 58 |
> Greg Kroah-Hartman (gregkh) |
| 59 |
> Mike Pagano (mpagano) |
| 60 |
> Manuel Rüger (mrueg) |
| 61 |
> Thomas Deutschmann (Whissi) |
| 62 |
> Magnus Granberg (Zorry) |
| 63 |
> |
| 64 |
> |
| 65 |
> Timing |
| 66 |
> If we start nominations (please self-nominate yourself if you want too), |
| 67 |
> then the nominations period would stop at 24/1/2017 19:00 UTC. |
| 68 |
> |
| 69 |
> The 10 days after that will put us at 3/2/2017 1900 UTC for voting. |
| 70 |
> Maybe we can have a meeting that weekend. |
| 71 |
> |
| 72 |
> Does this sound reasonable to everyone? |
| 73 |
> |
| 74 |
> Mike |
| 75 |
> |
| 76 |
|
| 77 |
|
| 78 |
|
| 79 |
-- |
| 80 |
Thanks, |
| 81 |
Alice Ferrazzi |
| 82 |
|
| 83 |
Gentoo Kernel Project Leader |
| 84 |
Gentoo Foundation Board Member |
| 85 |
Mail: Alice Ferrazzi <alicef@g.o> |
| 86 |
PGP: 2E4E 0856 461C 0585 1336 F496 5621 A6B2 8638 781A |
Archives