public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Santiago M. Mola" <coldwind@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: Monthly Gentoo Council Reminder for June
Date: Mon, 2 Jun 2008 13:05:11 +0200	[thread overview]
Message-ID: <3c32af40806020405j62502e1ag1f8aa5e21b72b919@mail.gmail.com> (raw)
In-Reply-To: <4843BADF.8080800@gentoo.org>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=UTF-8, Size: 1474 bytes --]

On Mon, Jun 2, 2008 at 11:18 AM, Raúl Porcel <armin76@gentoo.org> wrote:
> Ryan Hill wrote:
>>
>> On Sun, 01 Jun 2008 19:41:28 +0200
>> Raúl Porcel <armin76@gentoo.org> wrote:
>>
>>> IMHO the packages should be keyworded if an arch team member or an
>>> user of that arch requests it. Keywording something if an user of
>>> said arch doesn't request it, is a waste of resources.
>>
>> How is making things available to your users a waste of resources?
>> Anyways, if you're so far behind that you don't think you can manage
>> keywording another package then just say so and deny the request.
>>
>> What does this have to do with council?
>>
>
> And whats the point of having some package keyworded if nobody is going to
> use it?
> I don't care anyway, i just want an official clarification, personally i
> tend to keyword stuff if i think its going to be useful.
>
> Thing is, whats the difference in a maintainer asking for a package to be
> keyworded and keywording all the packages in the tree?

You're not going to be asked to keyword the whole tree, that's the
difference ;-)

I think we have not enough feedback from users about this. Either
Bugzilla is not the right tool, or we don't encourage users enough to
ask for keywords when they need them. Currently, some people assume
that "if a user from $arch needed this package, he'd have requested
keywords", but that's wrong.

Regards,
-- 
Santiago M. Mola
Jabber ID: cooldwind@gmail.com
éí¢‡^¾X¬¶È\x1ežÚ(¢¸&j)bž	b²

  reply	other threads:[~2008-06-02 11:05 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-01  5:30 [gentoo-dev] Monthly Gentoo Council Reminder for June Mike Frysinger
2008-06-01  9:36 ` Alec Warner
2008-06-01 12:25 ` Mart Raudsepp
2008-06-01 17:41 ` Raúl Porcel
2008-06-01 21:54   ` [gentoo-dev] " Ryan Hill
2008-06-02  3:30     ` Richard Freeman
2008-06-02 12:21       ` Alec Warner
2008-06-02  9:18     ` Raúl Porcel
2008-06-02 11:05       ` Santiago M. Mola [this message]
2008-06-02 14:43         ` Luca Barbato
2008-06-03 15:54           ` Christian Faulhammer

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=3c32af40806020405j62502e1ag1f8aa5e21b72b919@mail.gmail.com \
    --to=coldwind@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