public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Robin H. Johnson" <robbat2@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Soliciting input for a non-maintainer update (NMU) GLEP
Date: Fri, 21 Jun 2013 18:50:54 +0000	[thread overview]
Message-ID: <robbat2-20130621T182855-619828737Z@orbis-terrarum.net> (raw)

Hi all,

From what I've read on the list recently, there's a lot of demand for
non-maintainer updates to ebuilds. Esp. with the upcoming Git migration,
I predict there will be a much larger influx of changes from users.

Some developers (eg myself) have a general policy [2] that we send out
to the list occasionally welcome everybody to touch our packages (so
long as they own their breakages). A few packages discouraged touching
due to fragility, but mostly we were a very open society.

Back in the days of "The Old Ones", this was a general practice for all
developers, but somewhere along the line, some developers seem to have
grown territorial of their ebuilds.

Debian has their own NMU process:
http://wiki.debian.org/NonMaintainerUpload
http://www.debian.org/doc/manuals/developers-reference/pkgs.html#nmu
With a long whitelist of devs/teams that welcome it:
http://wiki.debian.org/LowThresholdNmu

So I'd like to hear input on how developers & users (esp
proxy-maintainers) on maybe writing a NMU GLEP.

I'm open to all input, but here's some initial questions I'd like to
hear your answers to:
- How should developers, herds & teams communicate how welcome they are
  to NMU changes on their packages?
  - to humans?
  - to automated scripts?
  - where? metadata.xml?
- What sorts of changes (see Debian NMU):
  - Are welcome?
  - Are prohibited?
  - Are somewhere between the two?
  - Does this need to be controlled per-package?
  - What about upstream-rejected changes?
- How do we encourage responsible ownership of changes that cause
  breakage? [1]

1. I've been leading infra for a few years now, and I've got a few
ground rules, maybe we can run with parts of those:
- If you break something, own up ASAP; there will be no punishment, just
  help in getting it fixed.
- You're responsible for many people's systems/access/privacy, don't
  abuse it.
(Ciaranm: since you were talking about lack of honesty of corporate
cultures in response to my previous mail, here's your chance again).

2. This isn't entirely selfless, I want to have to tell people less that
they can go and touch most of my packages WITHOUT asking me or waiting
for me to reply to a bug.

-- 
Robin Hugh Johnson
Gentoo Linux: Developer, Trustee & Infrastructure Lead
E-Mail     : robbat2@gentoo.org
GnuPG FP   : 11ACBA4F 4778E3F6 E4EDF38E B27B944E 34884E85


             reply	other threads:[~2013-06-21 18:51 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-21 18:50 Robin H. Johnson [this message]
2013-06-21 19:04 ` [gentoo-dev] Soliciting input for a non-maintainer update (NMU) GLEP 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
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=robbat2-20130621T182855-619828737Z@orbis-terrarum.net \
    --to=robbat2@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