public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Donnie Berkholz <dberkholz@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: Rich Freeman <rich0@gentoo.org>
Subject: Re: [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in dev-python/PyZilla: PyZilla-0.1.0.ebuild ChangeLog metadata.xml
Date: Sun, 27 Mar 2011 20:58:06 -0500	[thread overview]
Message-ID: <20110328015805.GA27772@comet> (raw)
In-Reply-To: <AANLkTikX_RCB_jpof9fK1gG9u=GKzLaOCP2+vWux1oz8@mail.gmail.com>

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

On 02:39 Mon 28 Mar     , Nirbheek Chauhan wrote:
> Where did this come from? My entire argument was based around the fact
> that unmaintained packages that may or may not be broken fundamentally
> constitute a *bad* experience for the user. If we cannot guarantee
> that bugs for a package will be fixed, we should not take up the
> responsibility of the package!
> 
> Which is worse? Suddenly pulling a package from underneath the feet of
> users when it inevitably breaks or telling them upfront that it's
> *completely not* supported by us so they can do something about it
> before it breaks?

Here's the key point: "may or may not." Arbitrary criteria with no 
relevance to whether a package works for users are not helpful.

The mere existence of a maintainer-needed package doesn't mean it should 
be removed. The existence of the same thing with numerous serious, 
unfixed bugs or tinderbox errors means something much different.

We have the ability to do these kinds of intersections today, since our 
wonderful bug wranglers normally insert the $CAT/$PN into summaries and 
Diego has tinderbox bugs filed.

-- 
Thanks,
Donnie

Donnie Berkholz
Sr. Developer, Gentoo Linux
Blog: http://dberkholz.com

[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2011-03-28  1:58 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20110326055210.E906D20054@flycatcher.gentoo.org>
2011-03-27  4:45 ` [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in dev-python/PyZilla: PyZilla-0.1.0.ebuild ChangeLog metadata.xml Jeremy Olexa
2011-03-27  7:47   ` Nirbheek Chauhan
2011-03-27 10:29     ` Markos Chandras
2011-03-27  9:39       ` Nirbheek Chauhan
2011-03-27 13:04         ` Treeclean all maintainer-needed packages, was: " Chí-Thanh Christopher Nguyễn
2011-03-27 15:37         ` Ryan Hill
2011-03-27 13:30     ` Jeremy Olexa
2011-03-27 13:43       ` Nirbheek Chauhan
2011-03-27 19:17         ` Alec Warner
2011-03-27 19:40           ` Nirbheek Chauhan
2011-03-27 20:17             ` Alec Warner
2011-03-27 21:25               ` Nirbheek Chauhan
2011-03-27 23:34                 ` Ryan Hill
2011-03-28  1:59                   ` Donnie Berkholz
2011-03-27 20:44             ` Rich Freeman
2011-03-27 21:09               ` Nirbheek Chauhan
2011-03-28  1:58                 ` Donnie Berkholz [this message]
2011-03-27 21:28               ` René 'Necoro' Neumann
2011-04-05  4:26                 ` Jeroen Roovers
2011-04-05 10:58                   ` Alec Warner
2011-04-05 15:08                     ` Jeroen Roovers
2011-04-18 17:56                   ` Andreas K. Huettel
2011-03-27 13:44       ` Rich Freeman
2011-03-27 14:54         ` Tomáš Chvátal
2011-03-27 16:18           ` Rich Freeman
2011-03-27 14:08       ` Maintainership offering; was: " René 'Necoro' Neumann
2011-03-27 19:05         ` Jeremy Olexa
2011-03-27 20:20       ` Proxy maintainership of app-misc/pwsafe, was " Christopher Head
2011-03-27 20:47         ` Nirbheek Chauhan
2011-03-27 20:55           ` René 'Necoro' Neumann
2011-03-27 20:55           ` David Abbott
2011-03-27 21:32             ` Nirbheek Chauhan
2011-03-29 17:50       ` Dirkjan Ochtman
2011-03-29 13:33     ` Jeroen Roovers

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=20110328015805.GA27772@comet \
    --to=dberkholz@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=rich0@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