On Mon, Jun 2, 2008 at 11:18 AM, Raúl Porcel <[EMAIL PROTECTED]> wrote: > Ryan Hill wrote: >> >> On Sun, 01 Jun 2008 19:41:28 +0200 >> Raúl Porcel <[EMAIL PROTECTED]> 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: [EMAIL PROTECTED] ���^�X��� ��(��&j)b� b�
