public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Rich Freeman <rich0@gentoo.org>
To: gentoo-dev <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-dev] [RFC] Future of gentoo's stable and unstable trees: what are your thoughts?
Date: Tue, 25 Jul 2017 07:26:10 -0400	[thread overview]
Message-ID: <CAGfcS_k1LOk0Vh=p8OZ+9U5RR2zMToYyH6NBN20dWJbLnFfR6g@mail.gmail.com> (raw)
In-Reply-To: <1500963512.25461.5.camel@gentoo.org>

On Tue, Jul 25, 2017 at 2:18 AM, Hans de Graaff <graaff@gentoo.org> wrote:
>
> On Mon, 2017-07-24 at 23:22 +0000, Peter Stuge wrote:
>
> > More troubleshooting and fixing "hard" problems, less routine work.
>
> Except that some of that routine work is actually what I enjoy doing in
> Gentoo. I already get plenty of the other two in my day job.
>

This goes to a principle of volunteer work - you can't really direct
the work of volunteers (at least not with anything close to 100%
efficiency).  If you tell a volunteer they aren't allowed to work on
x, that doesn't mean that the time they used to spend on x is now
available to the organization to work on higher priority projects.  It
just means that they won't work on x any longer.

If a volunteer wanted to be working on something they considered
higher priority, they would probably already be doing it, or they
would be the ones looking for somebody to take over the lower priority
jobs.

Paid work is an entirely different matter, because the project most
employees are really working on is the "collect a paycheck" project
and what they do to collect it tends to be secondary.  That obviously
isn't 100% the case and if you're trying to retain the next Elon Musk
the rules are different, but it holds for most normal work.

So, don't assume you can fix manpower problems by delivering less.
You might be able to fix them by relaxing rules so that you can
deliver the same with less effort, but keep in mind whether those
rules added some kind of value to the final product.

-- 
Rich


  parent reply	other threads:[~2017-07-25 11:26 UTC|newest]

Thread overview: 69+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-24 21:22 [gentoo-dev] [RFC] Future of gentoo's stable and unstable trees: what are your thoughts? Sergei Trofimovich
2017-07-24 21:52 ` [gentoo-dev] " Pacho Ramos
2017-07-24 23:22 ` [gentoo-dev] " Peter Stuge
2017-07-24 23:52   ` Rich Freeman
2017-07-25  4:34     ` [gentoo-dev] " Duncan
2017-07-25  6:26       ` Hans de Graaff
2017-07-25  6:18   ` [gentoo-dev] " Hans de Graaff
2017-07-25  9:18     ` Pacho Ramos
2017-07-25 11:54       ` Michał Górny
2017-07-25 12:15         ` Pacho Ramos
2017-07-25 13:19           ` Michał Górny
2017-07-25 13:23             ` Pacho Ramos
2017-07-25 11:26     ` Rich Freeman [this message]
2017-07-25  7:44   ` Sergei Trofimovich
2017-07-28 10:44   ` Andreas K. Huettel
2017-07-28 12:45     ` Marek Szuba
2017-07-28 13:10     ` Sam Jorna (wraeth)
2017-07-28 19:59       ` William L. Thomson Jr.
2017-07-28 21:21         ` David Seifert
2017-07-31  0:28         ` Sam Jorna
2017-07-31  0:40           ` Benda Xu
2017-07-31  2:44           ` William L. Thomson Jr.
2017-07-31  2:56             ` Sam Jorna
2017-07-31 15:00               ` William L. Thomson Jr.
2017-07-31 12:59             ` Andreas K. Huettel
2017-07-31 14:43               ` William L. Thomson Jr.
2017-07-31 14:47                 ` David Seifert
2017-07-28 19:44     ` Alec Warner
2017-07-29  1:05       ` Rich Freeman
2017-07-31 14:52         ` Alec Warner
2017-07-31 15:11           ` Rich Freeman
2017-07-31 16:51             ` Peter Volkov
2017-08-01  0:24             ` [gentoo-dev] " Duncan
2017-08-01  0:55               ` Rich Freeman
2017-08-01  1:45                 ` Duncan
2017-07-31 16:44           ` [gentoo-dev] " Michał Górny
2017-07-29  4:18       ` Daniel Campbell
2017-07-29 16:41         ` Mart Raudsepp
2017-07-29 19:10           ` David Seifert
2017-07-29 18:03     ` Andrew Savchenko
2017-07-25  7:22 ` Dirkjan Ochtman
2017-07-25 13:10   ` [gentoo-dev] " Michael Palimaka
2017-07-25 13:22     ` Rich Freeman
2017-07-25 20:16       ` Daniel Campbell
2017-07-25 13:36     ` Pacho Ramos
2017-07-25 14:15     ` Peter Stuge
2017-07-29 18:08   ` [gentoo-dev] " Christopher Head
2017-07-31  6:49     ` R0b0t1
2017-07-25  9:03 ` [gentoo-dev] " Agostino Sarubbo
2017-07-25 19:45   ` Markus Meier
2017-07-25 20:12     ` Rich Freeman
2017-07-26  5:49   ` Hans de Graaff
2017-07-25 12:59 ` Michael Palimaka
2017-07-25 13:30   ` Pacho Ramos
2017-07-25 13:51   ` Michał Górny
2017-07-25 14:13 ` [gentoo-dev] " Michał Górny
2017-07-25 14:28   ` Rich Freeman
2017-07-27 23:12 ` Denis Dupeyron
2017-07-27 23:41   ` Rich Freeman
2017-07-28  0:03     ` Denis Dupeyron
2017-07-28 21:24       ` William Hubbs
2017-07-29 10:24   ` Andrew Savchenko
2017-07-28 20:10 ` William L. Thomson Jr.
2017-07-28 21:12   ` A. Wilcox
2017-07-28 21:41     ` William L. Thomson Jr.
2017-07-29 13:41     ` Andreas K. Huettel
2017-07-28 21:45   ` [gentoo-dev] " Duncan
2017-07-28 21:56     ` William L. Thomson Jr.
2017-07-29 19:44       ` Walter Dnes

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='CAGfcS_k1LOk0Vh=p8OZ+9U5RR2zMToYyH6NBN20dWJbLnFfR6g@mail.gmail.com' \
    --to=rich0@gentoo.org \
    --cc=gentoo-dev@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