public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Michael Weber <xmw@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 22:31:08 +0200	[thread overview]
Message-ID: <51C4B80C.1020605@gentoo.org> (raw)
In-Reply-To: <robbat2-20130621T182855-619828737Z@orbis-terrarum.net>

On 06/21/2013 08:50 PM, Robin H. Johnson wrote:
[NMU]

Abstract: Be verbose about your preferences.

== TL;DR ==

I'm missing this kind of information since the beginning.
After 2 (?) years, i've learned some policies, like herd:desktop-* is
free for all, don't touch herd:base-system and so on. But I did not keep
records of every fella granting me full access.


As a maintainer and slacker (as flameeyes pointed out), I singularily
maintain my share of packages [1] with a rich variety of affection.

Less/singular affection (like the miredo/sbin/ip mishap, a package i
proxied for a friend), I work on rand maintainer-needed@g.o packages,
don't take maint and try to watch bugzie for follow ups.
-> just go ahead and do what you think is right

Total, regular affection, (cwm, ncdc, ncdu, mupdf (+derivates), llpp,
netsurf, jumanji) and basically my inital commits.
-> give me at least two days to review changes.

Either way, go ahead, BUT I __really__ like being informed about an NMU
carried out, nothing sucks more than doing the update and see
repoman+cvs reject the update (yeah, work on an fresh checkout blah blah).

As an impatient person with an urge to fix things, I often commit on
random stuff, after asking or timeout. I'd like to propose three
positions to post information about NMU-policy, preferred way of
communication, affection to bulk-mail|reports|...|euscan update|KEQWORDREQ

- Every dev as person, like an devaway.
- Every herd, somwhere in herds.xml
- Every Package-category (for project-categories like vim/kde/gnome/)
(it'd be usefull to fetch and provide this info as equery meta output).

(Yes, I've broken and will break things, my sincerest apologies, I
really try hard. Thanks for ssuominen being a encouraging example.)

At some point I'm really scared about reactions in the past and avoid
certain areas, persons and really basic|widespread stuff like zsh (bug
19924, [2]).

my 2 cents.

[1] http://euscan.iksaif.net/maintainers/48/
[2] https://bugs.gentoo.org/show_bug.cgi?id=19924

-- 
Michael Weber
Gentoo Developer
web: https://xmw.de/
mailto: Michael Weber <xmw@gentoo.org>


  parent reply	other threads:[~2013-06-21 20:31 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 [this message]
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=51C4B80C.1020605@gentoo.org \
    --to=xmw@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