From: Brian Dolbec <dolsen@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] Gentoo Council 2020 / 2021 Election - Questions for Candidates
Date: Mon, 22 Jun 2020 12:24:28 -0700 [thread overview]
Message-ID: <20200622122428.2e85d036@storm> (raw)
In-Reply-To: <XRBTEONG.3ENZJVMC.LLOFZIJQ@PQOE3MWY.SXQ3U27I.2KTPKL6U>
On Fri, 19 Jun 2020 20:25:15 +0100
Roy Bamford <neddyseagoon@gentoo.org> wrote:
> Team,
>
> Its been my impression that this last years council has had a fairly
> easy life compared to previous years.
>
> Some context ...
> The council is now 15 years old. Some concepts were worked out
> over a few beers at FOSDEM 2005, formalised over the next six
> months and the first council met in quarter 4 2005.
>
> I have memories of the council being set up as a disputes
> resolution body, not a leadership body but that was 15 years ago.
>
> Some questions ...
> 1. What do candidates see the councils role as in Gentoo today?
Since I have been around Gentoo since before the council was formed. I
do not see it really any different than it is currently. It's primary
role is to help steer Gentoo when competeing technologies come to
fruition that can not be implemented side by side. Make decisions on a
direction to aim for future and evolving policies.
>
> 2. How do candidates see the role of the Gentoo council
> changing in the short term .. say the next few years?
Barring any issues, policiy changes, etc. to be worked out. We should
be working on other ways to help Gentoo progess and evolve. Be it
helping poorly staffed projects get recruits. Promoting Gentoo at
meetups, or initiating new dialog on shelved ideas, inactive/incomplete
GLEPs... or establishing more automation helpers so that more developer
time can spent on imrpoving Gentoo rather than just trying to maintain
the status quo.
> 3. Why is this role change required?
I don't think of the previous answer as a role change. But something
that should have been always there for council members. Just a lower
priority when technical issues are needed to be dealt with.
>
> 4. How will candidates work to bring this change about during
> their term of office, should they be elected?
>
I intend to work towards establishing some addtional services that can
help with keywording, pkg bumping, stage building/testing. Personally
I have experience with buildbot. But if anyone comes to me with
experience with other build/automation systems and ides how it may help
Gentoo. Provided that it meets our guidelines, I will research those
and do what I can to make those projects come to fruition.
> Please start new threads for new questions,
>
>
next prev parent reply other threads:[~2020-06-22 19:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-19 19:25 [gentoo-project] Gentoo Council 2020 / 2021 Election - Questions for Candidates Roy Bamford
2020-06-22 11:17 ` Mikle Kolyada
2020-06-22 19:24 ` Brian Dolbec [this message]
2020-06-23 13:55 ` Thomas Deutschmann
2020-06-24 11:47 ` Mikle Kolyada
2020-06-26 14:06 ` Thomas Deutschmann
2020-06-23 17:27 ` Patrick Lauer
2020-06-26 1:40 ` Max Magorsch
2020-06-26 6:28 ` Joonas Niilola
2020-06-27 16:30 ` William Hubbs
2020-06-26 3:28 ` Aaron Bauman
2020-06-27 16:04 ` William Hubbs
2020-06-30 19:23 ` William Hubbs
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=20200622122428.2e85d036@storm \
--to=dolsen@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