From: William Hubbs <williamh@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] Gentoo Council nominee 2018/19 questions
Date: Sat, 30 Jun 2018 19:15:50 -0500 [thread overview]
Message-ID: <20180701001550.GA832@linux1.home> (raw)
In-Reply-To: <20180629051525.GD3190@angelfall.a21an.org>
[-- Attachment #1: Type: text/plain, Size: 1316 bytes --]
On Fri, Jun 29, 2018 at 08:15:25AM +0300, Eray Aslan wrote:
> Re-sending to gentoo-project
>
> On Tue, Jun 26, 2018 at 09:11:11AM +0200, Michał Górny wrote:
> > Since the nominees for the new Council aren't eager to publish
> > manifestos, and nobody seems to be asking questions (yet some people are
> > leaving hostile half-comments), I'd like to start a thread dedicated to
> > asking the nominees (who accepted) questions related to their views of
> > the upcoming term. At the same time, I'd like to ask all nominees to
> > answer all the questions provided by community members.
>
> Just a few sentences on the questions below would be nice.
>
> 1/ What do you think of closing gentoo-dev ML to the general public?
I am 100% against the decision to close gentoo-dev to the general
public. I feel that this is one of the worst things the council has done
recently.
> 2/ Where do you think Gentoo stands in the Linux ecosystem? Who do you
> think are its users?
Gentoo is probably the most customizable Linux distro out there. I tend
to see it as a power user distro. You can accept the default settings we
provide if you want, but its real strength is the ability to customize.
If you want a distro that you can customize very heavily, Gentoo is the
one for you.
William
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2018-07-01 0:15 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-26 7:11 [gentoo-project] Gentoo Council nominee 2018/19 questions Michał Górny
2018-06-26 7:12 ` Michał Górny
2018-06-26 16:27 ` Kristian Fiskerstrand
2018-06-26 16:54 ` Matthew Thode
2018-06-26 16:56 ` Michał Górny
2018-06-26 17:14 ` Matthew Thode
2018-06-26 17:00 ` Kristian Fiskerstrand
2018-06-26 17:20 ` Matthew Thode
2018-06-26 17:29 ` Kristian Fiskerstrand
2018-06-26 18:11 ` Matthew Thode
2018-06-26 23:02 ` Aaron Bauman
2018-06-26 23:07 ` M. J. Everitt
2018-06-27 5:35 ` Ulrich Mueller
2018-06-29 2:12 ` William Hubbs
2018-06-26 14:37 ` Christopher Díaz Riveros
2018-06-26 16:40 ` Kristian Fiskerstrand
2018-06-26 23:31 ` Aaron Bauman
2018-06-27 0:13 ` Georgy Yakovlev
2018-06-26 22:17 ` Aaron Bauman
2018-06-26 22:25 ` Kristian Fiskerstrand
2018-06-26 22:43 ` Kristian Fiskerstrand
2018-06-27 6:41 ` Michał Górny
2018-06-27 8:25 ` Michał Górny
2018-06-27 21:13 ` Aaron Bauman
2018-06-27 21:50 ` Thomas Deutschmann
2018-06-28 8:23 ` Kristian Fiskerstrand
2018-06-28 9:27 ` Ulrich Mueller
2018-07-02 15:03 ` William Hubbs
2018-07-11 14:35 ` Mart Raudsepp
2018-06-29 5:15 ` Eray Aslan
2018-06-29 13:13 ` Mart Raudsepp
2018-06-29 18:25 ` Kristian Fiskerstrand
2018-07-01 0:15 ` William Hubbs [this message]
2018-07-01 20:58 ` Aaron Bauman
2018-07-01 19:37 ` Michał Górny
2018-07-01 20:25 ` Aaron Bauman
2018-07-01 23:24 ` Mart Raudsepp
2018-07-02 15:38 ` William Hubbs
2018-07-01 21:04 ` Matthias Maier
2018-07-01 21:11 ` Matthias Maier
-- strict thread matches above, loose matches on Subject: below --
2018-07-02 3:48 M. J. Everitt
2018-07-03 0:37 ` Aaron Bauman
2018-07-11 13:13 ` Mart Raudsepp
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=20180701001550.GA832@linux1.home \
--to=williamh@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