public inbox for gentoo-project@lists.gentoo.org
 help / color / mirror / Atom feed
From: Aaron Bauman <bman@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] Gentoo Council nominee 2018/19 questions
Date: Mon, 02 Jul 2018 20:37:58 -0400	[thread overview]
Message-ID: <1741695.4Dx37mZ9CX@monkey> (raw)
In-Reply-To: <a3eba25a-80c1-6fef-65fe-d4dea19ff905@iee.org>

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

On Sunday, July 1, 2018 11:48:05 PM EDT M. J. Everitt wrote:
> A couple of passing thoughts:-
> 
> 1) What is/are your own current use cases for using Gentoo? Server?
> Desktop? Cluster? Embedded? on what platforms/arches? And why Gentoo?
> 

I use Gentoo on my server (NextCloud instance) and I also use it as my desktop 
OS (laptops).  All of those systems are amd64 with the server running stable 
and my laptop running ~arch.

I began using Gentoo many years ago as a young teenager.  I had begun 
tinkering with my computer systems after attending an HTML summer camp and 
being intrigued.  My first system ran Slackware and then I began trying all the 
various flavors out there.  Eventually, I found Gentoo and spent countless days 
bootstrapping, compiling, and tinkering some more.  My interest was largely 
the ability to easily customize and "dig in" the OS.  I felt empowered and 
grew my understanding of Linux as a whole.  

Into adulthood I was exposed more to enterprise environments heavily reliant 
on Windows systems with the occasional Linux box for particular things.  I 
have always remained partial to Linux and Gentoo in particular.  I still 
checkout the latest releases of other distros, but nothing compares to Gentoo 
in my opinion.  We offer (see my previous emails) a unique ability to 
customize and control.  That is what has always kept me with Gentoo.

> 2) What improvements to the distro (ignoring all structural discussions)
> would you like to see, to enhance your experience of using Gentoo vs
> something else?
> 
> Cheers.

I see your point about ignoring structural discussions, but I believe some 
structural modifications are required in order to enhance the various aspects 
of Gentoo.  Given the recent discussions (c.f. GLEP63, Generel Resolution, 
etc), we need to begin *enforcing* standards.  An example, GLEP63 is 
important, but developers offer dissident views and refuse to comply.  Of 
course, enforcing these standards can cause turmoil and so recourse is 
important.  Thus, passing the general resolution is needed to ensure such 
avenues are available.

If these are addressed I believe the community can address concerns such as 
security.  This is important to me as a member of the security team and is not 
limited to the auditing of package vulnerabilities and ebuilds.  It extends to 
the entirety of the Gentoo infrastructure and the individual security of our 
members.  So, in this case, I would like to see the enforcement of GLEP63 not 
only for the health of Gentoo, but for the security of our developers.

-Aaron

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2018-07-03  0:38 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-02  3:48 [gentoo-project] Gentoo Council nominee 2018/19 questions M. J. Everitt
2018-07-03  0:37 ` Aaron Bauman [this message]
2018-07-11 13:13 ` Mart Raudsepp
  -- strict thread matches above, loose matches on Subject: below --
2018-06-26  7:11 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
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

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=1741695.4Dx37mZ9CX@monkey \
    --to=bman@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