public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alexis Ballier <aballier@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Soliciting input for a non-maintainer update (NMU) GLEP
Date: Fri, 21 Jun 2013 15:04:11 -0400	[thread overview]
Message-ID: <20130621150411.6e951202@gentoo.org> (raw)
In-Reply-To: <robbat2-20130621T182855-619828737Z@orbis-terrarum.net>

Hi,

> 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?

The way I've been doing this is:
- packages I maintain through herd -> go ahead and be responsible.
- if I add myself explicitly in metadata.xml this means I prefer at
  least reviewing every change that gets in (with some exceptions for
  trivial changes, like e.g. qt moving category)

[...]
> - How do we encourage responsible ownership of changes that cause
>   breakage? [1]

That's something I'd like to get enlightened on. The, probably too
emotional, algorithm that doesn't scale I've been applying has been:

1. ask the committer to fix the problem
2. wait
3. if no fix comes in a timely manner, fix it myself, be clear that I've
  not liked it at all. Be a bit less polite in future steps 1. with
  said developer.

Alexis.


  reply	other threads:[~2013-06-21 19:04 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 [this message]
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=20130621150411.6e951202@gentoo.org \
    --to=aballier@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