[gentoo-dev] Re: Monthly Gentoo Council Reminder for June
Hi, Luca Barbato [EMAIL PROTECTED]: Probably having 2-4 lines about this in the next newsletter could foster awareness. All for it. Will you write it? Having a smarter repoman and bugzilla integration to handle stabilization and keyword bugs automagically would be great but I think would require time (since such bugs could spare the dev some trips around bugzie) I'd like to point to app-portage/gatt again which can automate a lot of your everyday arch work. At least two amd64 arch testers, ranger and myself use it regularly. URL:http://gatt.sourceforge.net/ for details (it is the manual, the examples section has some work-flow snippets). V-Li -- Christian Faulhammer, Gentoo Lisp project URL:http://www.gentoo.org/proj/en/lisp/, #gentoo-lisp on FreeNode URL:http://www.faulhammer.org/ signature.asc Description: PGP signature
Re: [gentoo-dev] Re: Monthly Gentoo Council Reminder for June
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�
Re: [gentoo-dev] Re: Monthly Gentoo Council Reminder for June
Ryan Hill wrote: On Sun, 01 Jun 2008 19:41:28 +0200 Raúl Porcel [EMAIL PROTECTED] wrote: Requesting ~arch keywords: Is a maintainer able to request ~arch keywords, if the package is not a dependency of some other package which is keyworded, and the maintainer doesn't have that arch? Yes. Last time I looked anyone could request a keyword. 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? -- gentoo-dev@lists.gentoo.org mailing list
Re: [gentoo-dev] Re: Monthly Gentoo Council Reminder for June
On 6/1/08, Richard Freeman [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. ++ I'd like to comment that in theory a package maintainer should have a decent idea of what archs a particular package should work on. I can't imagine that the vmware maintainers are going to be sending keyword requests to the sparc team... Contrary to your theory I think in the past this has proven to be false; however I am not sure how often this was the case (eg. were just a few maintainers overzeallous or did we have widespread problems.) -- gentoo-dev@lists.gentoo.org mailing list -- gentoo-dev@lists.gentoo.org mailing list
Re: [gentoo-dev] Re: Monthly Gentoo Council Reminder for June
Santiago M. Mola wrote: 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. Good point and probably a good start to find a decent solution about getting the stuff needed by user keyworded but not overwork arch teams. Probably having 2-4 lines about this in the next newsletter could foster awareness. Having a smarter repoman and bugzilla integration to handle stabilization and keyword bugs automagically would be great but I think would require time (since such bugs could spare the dev some trips around bugzie) lu -- Luca Barbato Gentoo Council Member Gentoo/linux Gentoo/PPC http://dev.gentoo.org/~lu_zero -- gentoo-dev@lists.gentoo.org mailing list
[gentoo-dev] Re: Monthly Gentoo Council Reminder for June
On Sun, 01 Jun 2008 19:41:28 +0200 Raúl Porcel [EMAIL PROTECTED] wrote: Requesting ~arch keywords: Is a maintainer able to request ~arch keywords, if the package is not a dependency of some other package which is keyworded, and the maintainer doesn't have that arch? Yes. Last time I looked anyone could request a keyword. 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? -- fonts, gcc-porting, by design, by neglect mips, treecleaner,for a fact or just for effect wxwidgets @ gentoo EFFD 380E 047A 4B51 D2BD C64F 8AA8 8346 F9A4 0662 signature.asc Description: PGP signature
Re: [gentoo-dev] Re: Monthly Gentoo Council Reminder for June
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. ++ I'd like to comment that in theory a package maintainer should have a decent idea of what archs a particular package should work on. I can't imagine that the vmware maintainers are going to be sending keyword requests to the sparc team... -- gentoo-dev@lists.gentoo.org mailing list
