public inbox for gentoo-project@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Andreas K. Huettel" <dilfridge@gentoo.org>
To: gentoo-project@lists.gentoo.org
Cc: "Michał Górny" <mgorny@gentoo.org>
Subject: Re: [gentoo-project] Questions for Gentoo Council nominees: Gentoo as hobbyist distro
Date: Thu, 20 Jun 2019 16:48:15 +0200	[thread overview]
Message-ID: <3841736.iLVNZJJye5@pinacolada> (raw)
In-Reply-To: <b7200fbcc9f0f34df3e4c10e254fd9c4e3806d5e.camel@gentoo.org>

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

Am Sonntag, 16. Juni 2019, 20:09:38 CEST schrieb Michał Górny:
> 
> Some developers were recently complaining that we're turning Gentoo into
> a hobbyist distro and that's apparently bad.
> 
> Do you think Gentoo should allow for experimental and unstable features,
> and possibly breaking changes that make Gentoo more interesting for
> hobbyists?  Or should we block breaking changes and become more
> conservative for users who prefer stable distribution with minimal
> maintenance burden?

We're torn between extremes here, and I think nothing we do will make 
*everyone* happy. That said, we do have the duality stable/~arch, and that 
should already answer a large part of that question. In an ideal world, stable 
should be rock-solid and production worthy, and ~arch should be bleeding edge 
with occasional bugs and compile failures that come with that.

Where that doesnt work (say, profiles) ...

Let's start with the following assumption: Our main objective should be that 
Gentoo has a vivid, productive, and growing developer community. (If you think 
that doesnt sound right, you can try replacing "developer" with "productive 
contributor".)

Developers exist in two overlapping types, broadly speaking:
1) hobbyists who do something because it's interesting and cool
2) employees who are paid to do something because it's useful

So, we need to find a compromise between these two, with weight on the group 
that contributes to Gentoo most.

Right now my personal feeling is that we're trying to set long deprecation 
times when something is going away, and that nevertheless migration to, say, a 
new profile tends to only *start* when we threaten that the deprecation time 
will be over soon and the old one will go away.

We can't be stuck at the same level forever. Occasionally we will have to 
change something that requires manual intervention. Hey, if you have a big 
server farm, that's what all these horrible automation tools (puppet, rex, 
...) are good for. I think. Let's do it carefully, announce it, announce 
deprecation times, and give people time to do it. And then move on.


-- 
Andreas K. Hüttel
dilfridge@gentoo.org
Gentoo Linux developer
(council, toolchain, base-system, perl, libreoffice)

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

  parent reply	other threads:[~2019-06-20 14:48 UTC|newest]

Thread overview: 110+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-15  9:42 [gentoo-project] Questions for Gentoo Council nominees Andrew Savchenko
2019-06-15  9:49 ` [gentoo-project] Questions for Gentoo Council nominees: GLEP 76 Andrew Savchenko
2019-06-15 10:20   ` Ulrich Mueller
2019-06-15 16:17   ` Kristian Fiskerstrand
2019-06-16 22:01   ` Thomas Deutschmann
2019-06-18 14:12   ` William Hubbs
2019-06-18 15:43     ` Luca Barbato
2019-06-18 15:47       ` William Hubbs
2019-06-24 22:18   ` Andrew Savchenko
2019-06-25  6:15     ` Michał Górny
2019-06-28 11:49       ` Andrew Savchenko
2019-06-28 12:09         ` Rich Freeman
2019-06-28 17:51           ` Andrew Savchenko
2019-06-30  4:48           ` desultory
2019-06-30 18:53             ` Rich Freeman
2019-07-01  5:02               ` desultory
2019-07-01 11:59                 ` Rich Freeman
2019-07-02  4:24                   ` desultory
2019-07-02 11:57                     ` Rich Freeman
2019-07-03  4:31                       ` desultory
2019-07-03 11:13                         ` Rich Freeman
2019-07-04  4:32                           ` desultory
2019-06-30  7:11   ` Patrick Lauer
2019-06-30  7:42     ` Michał Górny
2019-06-30  8:03       ` Patrick Lauer
2019-06-30 22:27         ` Robin H. Johnson
2019-07-01  1:31           ` Thomas Deutschmann
2019-06-15 10:00 ` [gentoo-project] Questions for Gentoo Council nominees: Power balance Andrew Savchenko
2019-06-15 10:34   ` Ulrich Mueller
2019-06-15 21:25   ` Andreas K. Huettel
2019-06-16  7:31   ` Mikle Kolyada
2019-06-16 15:56   ` Roy Bamford
2019-06-16 22:18   ` Thomas Deutschmann
2019-06-17  1:38   ` Kristian Fiskerstrand
2019-06-18 14:41   ` William Hubbs
2019-06-30  7:26   ` Patrick Lauer
2019-06-15 10:24 ` [gentoo-project] Questions for Gentoo Council nominees: Bringing new people Andrew Savchenko
2019-06-15 16:24   ` Kristian Fiskerstrand
2019-06-15 21:23   ` Andreas K. Huettel
2019-06-16 18:51   ` Mikle Kolyada
2019-06-16 22:21   ` Thomas Deutschmann
2019-06-19  2:39   ` William Hubbs
2019-06-16 18:09 ` [gentoo-project] Questions for Gentoo Council nominees: Gentoo as hobbyist distro Michał Górny
2019-06-16 19:13   ` Kristian Fiskerstrand
2019-06-16 22:39   ` Thomas Deutschmann
2019-06-19  6:24   ` Mikle Kolyada
2019-06-19 15:45     ` William Hubbs
2019-06-21 14:55       ` Mikle Kolyada
2019-06-19 14:32   ` William Hubbs
2019-06-20 14:48   ` Andreas K. Huettel [this message]
2019-06-21 13:21 ` [gentoo-project] Questions for Gentoo Council nominees: your achievements Michał Górny
2019-06-21 20:46   ` Kristian Fiskerstrand
2019-06-21 22:59   ` Georgy Yakovlev
2019-06-22  6:44   ` Ulrich Mueller
2019-06-22  7:06     ` Michał Górny
2019-06-22 22:57   ` Mikle Kolyada
2019-06-24 11:05     ` Mart Raudsepp
2019-06-24 11:25 ` [gentoo-project] Questions for Gentoo Council nominees: traits of a good Council member Michał Górny
2019-06-24 23:23 ` [gentoo-project] Questions for Gentoo Council nominees: Gentoo Foundation Robin H. Johnson
2019-06-26 19:45   ` Kristian Fiskerstrand
2019-06-26 21:54     ` Matthew Thode
2019-06-26 22:03       ` Kristian Fiskerstrand
2019-06-26 22:06         ` Kristian Fiskerstrand
2019-06-26 22:13           ` Matthew Thode
2019-06-26 22:28             ` Kristian Fiskerstrand
2019-06-30 19:21             ` Andreas K. Huettel
2019-06-26 22:08         ` Matthew Thode
2019-06-26 22:15         ` Michael Everitt
2019-06-26 22:22           ` Kristian Fiskerstrand
2019-06-28 23:49           ` Andreas K. Huettel
     [not found]             ` <20190630215422.GA22747@bubba.lan>
2019-06-30 21:55               ` Aaron Bauman
2019-07-01  7:50                 ` Michał Górny
2019-07-01  9:31                   ` Roy Bamford
2019-07-01  9:52                     ` Michał Górny
2019-07-01 10:02                       ` Michael Everitt
2019-07-01 10:04                         ` Michael Everitt
2019-07-01 19:42                         ` Andreas K. Huettel
2019-07-01 19:44                           ` Andreas K. Huettel
2019-07-01 20:10                             ` Alec Warner
2019-07-01 21:14                               ` Roy Bamford
2019-07-02 12:40                                 ` Kristian Fiskerstrand
2019-07-01 11:26                       ` Roy Bamford
2019-07-01 12:07                         ` Rich Freeman
2019-07-01 19:34                         ` Andreas K. Huettel
2019-07-03  4:42                           ` desultory
2019-07-03  6:12                           ` [gentoo-project] Questions for Gentoo Council nominees: Gentoo Foundation - Treasurer Response! Robin H. Johnson
2019-07-03  9:51                             ` Michael Everitt
2019-07-03 10:47                             ` Rich Freeman
2019-07-03 11:05                               ` Michael Everitt
2019-07-03 11:22                                 ` Rich Freeman
2019-07-03 11:27                               ` Kristian Fiskerstrand
2019-07-03 12:27                                 ` Rich Freeman
2019-07-03 13:45                                   ` Kristian Fiskerstrand
2019-07-03 12:56                             ` [gentoo-nfp] " Michał Górny
2019-07-03 13:08                               ` Rich Freeman
2019-07-03 13:17                                 ` Michał Górny
     [not found]                                 ` <20190703143429.yfieiru7cyykr5ca@gentoo.org>
     [not found]                                   ` <6b84c0a026551472a05e776921182ba8dae6fb1e.camel@gentoo.org>
     [not found]                                     ` <138757e484f751d567fb2702ce27de3e3e215a15.camel@gentoo.org>
2019-07-04  2:05                                       ` [gentoo-nfp] Re: [gentoo-project] Questions for Gentoo Council nominees: Gentoo Foundation - Treasurer Response! (part 2) Robin H. Johnson
2019-06-30 10:36 ` [gentoo-project] Questions for Gentoo Council nominees Roy Bamford
2019-06-30 16:48   ` Thomas Deutschmann
2019-06-30 20:17   ` Andreas K. Huettel
2019-07-04  2:14 ` [gentoo-project] Questions for Gentoo Council nominees: Council demands on maintainers & council legal liability Robin H. Johnson
2019-07-04  6:26   ` Michał Górny
2019-07-04  8:03   ` Kristian Fiskerstrand
2019-07-04 20:33     ` Alec Warner
2019-07-04 23:46       ` Kristian Fiskerstrand
2019-07-06  2:54         ` desultory
2019-07-04 13:36   ` Thomas Deutschmann
2019-07-04 16:37     ` Ulrich Mueller
2019-07-04 18:49       ` Thomas Deutschmann
2019-07-04 19:22         ` Ulrich Mueller

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=3841736.iLVNZJJye5@pinacolada \
    --to=dilfridge@gentoo.org \
    --cc=gentoo-project@lists.gentoo.org \
    --cc=mgorny@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