public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Andreas K. Huettel" <dilfridge@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in dev-libs/confuse: confuse-2.7.ebuild ChangeLog
Date: Mon, 04 Mar 2013 09:19:58 +0100	[thread overview]
Message-ID: <1651541.M4DRSq5dKd@porto> (raw)
In-Reply-To: <20130304021917.10752.qmail@stuge.se>

[-- Attachment #1: Type: text/plain, Size: 1355 bytes --]

Am Montag, 4. März 2013, 03:19:17 schrieb Peter Stuge:
> 
> > > Again, I guess you have to make Mike go away now.
> > 
> > I never said that so please just stop it.
> 
> You threatened to preempt me if I wanted to become a developer and
> found his practise OK - meaning that the behavior is unacceptable.
> If you are to be the least consistent you really need to also
> threaten to remove him. (It would be pretty ridiculously hipocratic
> and of course harmful for project evolution if the rules apply only
> to aspiring devs.)
> 
> But I'd obviously prefer if you didn't do that to him.
> 

Seriously. While I'm all for sticking to the rules, I'm also sometimes glad 
that Gentoo is not as bad as proverbial German bureaucracy.

The fact is, people who have been around for a long time, do a lot of 
important work and are trusted by the dev community may be able to bend the 
rules *for good reason*. [I personally would prefer if that would occur less 
frequently though.]

This discussion is about whether it was really necessary (the "for good 
reason" part) or could have been done in other ways.

Starting as a developer or aspiring to become one with that attitude is not 
acceptable. No discussion of that needed.

-- 
Andreas K. Huettel
Gentoo Linux developer 
dilfridge@gentoo.org
http://www.akhuettel.de/

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2013-03-04  8:18 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20130301081602.D1F5D2171D@flycatcher.gentoo.org>
2013-03-01 12:45 ` [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in dev-libs/confuse: confuse-2.7.ebuild ChangeLog Markos Chandras
2013-03-03  1:44   ` Mike Frysinger
2013-03-03  1:50     ` Markos Chandras
2013-03-03  1:57       ` Mike Frysinger
2013-03-03  2:01         ` Markos Chandras
2013-03-03  2:41           ` Peter Stuge
2013-03-03 10:30             ` Markos Chandras
2013-03-03 12:01               ` Peter Stuge
2013-03-03 12:09                 ` Markos Chandras
2013-03-03 12:38                   ` Peter Stuge
2013-03-03 13:17                     ` Rich Freeman
2013-03-03 15:29                     ` Markos Chandras
2013-03-04  2:19                       ` Peter Stuge
2013-03-04  8:19                         ` Andreas K. Huettel [this message]
2013-03-04 13:58                           ` Peter Stuge
2013-03-04 15:49                             ` Alec Warner
2013-03-03  2:44           ` Mike Frysinger
2013-03-03 11:44             ` Tomáš Chvátal
2013-03-10 18:04               ` Jeroen Roovers
2013-03-10 18:11                 ` hasufell
2013-03-10 20:57                   ` Michael Orlitzky
2013-03-10 21:07                   ` Duncan
2013-03-11  6:36                 ` Samuli Suominen

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=1651541.M4DRSq5dKd@porto \
    --to=dilfridge@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