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] Soliciting input for a non-maintainer update (NMU) GLEP
Date: Sat, 22 Jun 2013 06:39:11 -0400	[thread overview]
Message-ID: <CAGfcS_kvTc9t5tD_PYCDP1H0iq-W6ZNUojN__V5aMkg7hhDR=Q@mail.gmail.com> (raw)
In-Reply-To: <51C57A66.70801@gentoo.org>

On Sat, Jun 22, 2013 at 6:20 AM, Michael Weber <xmw@gentoo.org> wrote:
> Bottom line: I think we need more of a culture of mutual trust than a
> ton of metadata.
>

I have to agree with this.  The culture should be that we're doing
this work FOR GENTOO.  Sure, we're getting benefits out of it as well
so it should be a win/win, but we're all in this together.

I do think there is some metadata that would be useful.  Rather than
capturing a "keep out" flag, perhaps it would make more sense to
capture more "factual" information, like a comment for humans to read,
and maybe a status for scripts.  This shouldn't be about who is and
isn't allowed to touch things, but rather WHY somebody might think
twice about touching things.

For example, many system packages should get the white glove treatment
because they're, well, system packages.  I'd like to think that even
the greenest of recruits would appreciate that glibc isn't the best
package in the world to experiment on, but a script might not catch
that.

Useful and informative comments to humans might be useful as well.
For example, I might mark my package as "do-not-stabilize" for the
scripts and add a comment "game client interfaces with external game
server that changes API without warning and requires instant updates."

Anybody running scripts on the tree should be careful from the start -
perhaps we should even require pre-announcement on -dev.  Manual
changes are less of a risk, especially if there is warning.

All that said, I'm not opposed to there being some kind of flag.
However, I think we need to set the expectation that this is about
helping us all to collaborate better, and not about putting up
razorwire.

Rich


  reply	other threads:[~2013-06-22 10:39 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-21 18:50 [gentoo-dev] Soliciting input for a non-maintainer update (NMU) GLEP Robin H. Johnson
2013-06-21 19:04 ` Alexis Ballier
2013-06-21 19:07   ` Robin H. Johnson
2013-06-21 19:31     ` Alexis Ballier
2013-06-22  1:11   ` Tom Wijsman
2013-06-21 20:31 ` Michael Weber
2013-06-21 20:41   ` Michael Weber
2013-06-22  1:21     ` Tom Wijsman
2013-06-21 23:40 ` Mike Frysinger
2013-06-22  0:06   ` Robin H. Johnson
2013-06-22  0:17     ` Mike Frysinger
2013-06-22  0:26       ` Robin H. Johnson
2013-06-22  1:06         ` Mike Frysinger
2013-06-22  1:42           ` Robin H. Johnson
2013-06-22  3:28             ` Rick "Zero_Chaos" Farina
2013-06-22  9:00             ` Ulrich Mueller
2013-06-22  9:05               ` hasufell
2013-06-22  9:38                 ` [gentoo-dev] Herds (was: Soliciting input for a non-maintainer update (NMU) GLEP) Ulrich Mueller
2013-06-22  9:48                   ` [gentoo-dev] Herds hasufell
2013-06-22  9:46               ` [gentoo-dev] Soliciting input for a non-maintainer update (NMU) GLEP Ulrich Mueller
2013-06-22 10:43               ` Rich Freeman
2013-06-22  9:01             ` hasufell
2013-06-22 10:20               ` Michael Weber
2013-06-22 10:39                 ` Rich Freeman [this message]
2013-06-22 10:52                 ` Tom Wijsman
2013-06-22 17:59                 ` Mike Frysinger
2013-06-22  9:16             ` Markos Chandras
2013-06-22 10:19             ` Tom Wijsman
2013-06-22 13:42             ` [gentoo-dev] " Michael Palimaka
2013-06-22 15:13             ` [gentoo-dev] " hasufell
2013-06-22 16:56               ` Robin H. Johnson
2013-06-22 10:11     ` Pacho Ramos
2013-06-23  3:01       ` Rick "Zero_Chaos" Farina
2013-06-27 18:18         ` hasufell
2013-06-27 19:29           ` Rick "Zero_Chaos" Farina

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_kvTc9t5tD_PYCDP1H0iq-W6ZNUojN__V5aMkg7hhDR=Q@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