From: Tom Wijsman <TomWij@gentoo.org>
To: peter@stuge.se
Cc: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] open season on other-dev's packages -- policy change?
Date: Fri, 1 Nov 2013 22:13:47 +0100 [thread overview]
Message-ID: <20131101221347.36371d29@TOMWIJ-GENTOO> (raw)
In-Reply-To: <20131101194936.27426.qmail@stuge.se>
[-- Attachment #1: Type: text/plain, Size: 1813 bytes --]
On Fri, 1 Nov 2013 20:49:36 +0100
Peter Stuge <peter@stuge.se> wrote:
> You're changing the subject. Nobody was talking about really severe
> bugs, and those aren't really the common case.
Nobody has to for them to be an exception worth mentioning.
> Maybe delays don't matter to you, but you can't posit that the same
> is true for every other developer. I think the potentially significant
> delay matters a lot.
Do you have an example? Which actual problem are we trying to fix here?
> The whole point is that we cannot assume that maintainer has time.
We can, because we have the devaway system.
> The scenario is that I have taken a little time right now to fix a
> bug and get the fix committed so that I no longer experience said bug.
> I'm fixing this bug because it is blocking me in some way. It matters
> a whole lot if I have to wait for someone else to unblock me, in
> practice that completely demotivates me to contribute back, and I
> would simply work around the block.
Delay is to be expected with proxy maintenance.
Why do you need to wait for the actual commit? If you have it
fixed locally, it does no longer bother you; does it?
> QA has nothing to do with committing, don't confuse Gentoo policy
> with actual meaning of the terms. Testing, repoman and QA matters
> are of course part of creating the patch in the first place.
It does, the person whom commits has to do the testing / repoman / QA;
ensuring the changes are good is the responsibility of the person whom
commits and that cannot be transferred to the writer of the patch.
--
With kind regards,
Tom Wijsman (TomWij)
Gentoo Developer
E-mail address : TomWij@gentoo.org
GPG Public Key : 6D34E57D
GPG Fingerprint : C165 AF18 AB4C 400B C3D2 ABF0 95B2 1FCD 6D34 E57D
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 490 bytes --]
next prev parent reply other threads:[~2013-11-01 21:14 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-18 11:11 [gentoo-dev] Reminder: open season on robbat2's packages Robin H. Johnson
2012-11-18 16:11 ` Diego Elio Pettenò
2012-11-18 23:15 ` Robin H. Johnson
2012-11-18 18:13 ` Gilles Dartiguelongue
2012-11-19 5:13 ` Arun Raghavan
2012-11-19 5:30 ` Robin H. Johnson
2012-11-19 5:36 ` Arun Raghavan
2012-11-23 2:22 ` Donnie Berkholz
2012-11-23 4:22 ` Robin H. Johnson
2012-11-23 14:15 ` [gentoo-dev] open season on other-dev's packages -- policy change? Ian Stakenvicius
2012-11-23 14:28 ` Rich Freeman
2012-11-23 14:40 ` Ian Stakenvicius
2012-11-23 14:53 ` hasufell
2012-11-23 14:32 ` Thomas Sachau
2012-11-23 14:48 ` Ian Stakenvicius
2012-11-23 15:00 ` Thomas Sachau
2012-11-23 15:22 ` Ian Stakenvicius
2012-11-23 15:10 ` hasufell
2012-11-25 7:01 ` Patrick Lauer
2012-11-25 15:43 ` Rick "Zero_Chaos" Farina
2012-11-25 15:51 ` Rich Freeman
2012-11-25 17:55 ` Rick "Zero_Chaos" Farina
2012-11-25 19:59 ` Rich Freeman
2012-11-25 22:18 ` Rick "Zero_Chaos" Farina
2013-10-31 17:08 ` Peter Stuge
2013-11-01 15:18 ` Tom Wijsman
2013-11-01 19:49 ` Peter Stuge
2013-11-01 19:53 ` Peter Stuge
2013-11-01 20:00 ` Alon Bar-Lev
2013-11-01 20:06 ` Peter Stuge
2013-11-01 20:11 ` Alon Bar-Lev
2013-11-01 20:14 ` Ciaran McCreesh
2013-11-01 22:05 ` Richard Yao
2013-11-01 22:13 ` Ciaran McCreesh
2013-11-24 21:28 ` Maciej Mrozowski
2013-11-01 21:18 ` Tom Wijsman
2013-11-01 22:02 ` Richard Yao
2013-11-01 23:59 ` Tom Wijsman
2013-11-01 21:13 ` Tom Wijsman [this message]
2013-11-01 21:58 ` Richard Yao
2013-11-01 22:07 ` Richard Yao
2012-11-26 16:12 ` [gentoo-dev] Reminder: open season on robbat2's packages Donnie Berkholz
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=20131101221347.36371d29@TOMWIJ-GENTOO \
--to=tomwij@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=peter@stuge.se \
/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