Re: [gentoo-dev] [RFC] bugs.g.o supported overlays should register
On Sat, Jan 03, 2009 at 06:37:35PM +0100, Jeroen Roovers wrote: > On Sat, 3 Jan 2009 13:56:15 + > Ciaran McCreesh wrote: > > > What would really benefit Gentoo would be able to have the package > > manager aware of [...] > > I am sure you know of one that would provide... :) > > > jer I really don't think that's an issue. A good feature is a good feature regardless of who thought up the idea or who implemented it first. Please, let's not sidetrack the discussion of this idea with irrelevant stuff.
Re: [gentoo-dev] [RFC] bugs.g.o supported overlays should register
On Saturday 03 January 2009, Jeroen Roovers wrote: > On Fri, 02 Jan 2009 23:50:07 -0600 > > Jeremy Olexa wrote: > > So you are asking for the layman file to be updated properly or > > what? > > I specifically didn't go into the minor technical details (of files > and formats and so on) and described a basic process. Currently there > is no well-defined process, and frankly, 1) I don't use layman since > it hates the locations where I keep repos, 2) the implicit connection > between layman and overlays is lost on me, and 3) where is that > layman.txt file kept anyway (I'd like to have a look at it)? It's in the "gentoo" CVS repository under the overlays project, i.e.: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/overlays/ It is then exported to: http://www.gentoo.org/proj/en/overlays/layman-global.txt I think the filename ending in txt might have something to do with the web server processing xml files as guidexml, but renaming it to be something like "overlays.xml" would be preferable IMO. We'd also need to create a proper DTD for it (I was looking for that earlier today, without success). Robert signature.asc Description: This is a digitally signed message part.
Re: [gentoo-dev] [RFC] bugs.g.o supported overlays should register
On Fri, 02 Jan 2009 23:50:07 -0600 Jeremy Olexa wrote: > So you are asking for the layman file to be updated properly or what? I assume for now that you meant [1]. As far as I can tell, that file would be useable if it didn't just follow whatever policy is set up for layman access to overlays. There are a few minor problems with it, like the filename and filename extension both being misleading (yes, I know it really is a "txt" file :), and the fact that none of the Overlays project's documentation mentions it. I'd hate to introduce duplication and as it does seem like > layman -i will depend on that URL for a good while yet, the filename changes aren't important. It _is_ important to get the file documented by the Overlays project so that the Bug Wranglers project (a QA sub-project) can depend on that. > IMO, what would really benefit us is to have a site akin to > http://gpo.zugaina.org/ on a Gentoo host to *find* packages that are > in 'official' overlays. That sounds nice. Same goes for files -> packages, of course. Kind regards, jer [1] http://www.gentoo.org/proj/en/overlays/layman-global.txt
Re: [gentoo-dev] [RFC] bugs.g.o supported overlays should register
On Fri, 02 Jan 2009 23:50:07 -0600 Jeremy Olexa wrote: > So you are asking for the layman file to be updated properly or what? I specifically didn't go into the minor technical details (of files and formats and so on) and described a basic process. Currently there is no well-defined process, and frankly, 1) I don't use layman since it hates the locations where I keep repos, 2) the implicit connection between layman and overlays is lost on me, and 3) where is that layman.txt file kept anyway (I'd like to have a look at it)? Kind regards, jer
Re: [gentoo-dev] [RFC] bugs.g.o supported overlays should register
On Sat, 3 Jan 2009 13:56:15 + Ciaran McCreesh wrote: > What would really benefit Gentoo would be able to have the package > manager aware of [...] I am sure you know of one that would provide... :) jer
Re: [gentoo-dev] [RFC] bugs.g.o supported overlays should register
On Fri, 02 Jan 2009 23:50:07 -0600 Jeremy Olexa wrote: > IMO, what would really benefit us is to have a site akin to > http://gpo.zugaina.org/ on a Gentoo host to *find* packages that are > in 'official' overlays. What would really benefit Gentoo would be able to have the package manager aware of packages in overlays that it doesn't have configured. Shouldn't have to fire up a web browser just to get basic information on a third party package... -- Ciaran McCreesh signature.asc Description: PGP signature
Re: [gentoo-dev] [RFC] bugs.g.o supported overlays should register
On Saturday 03 January 2009, Robin H. Johnson wrote: > On Fri, Jan 02, 2009 at 11:50:07PM -0600, Jeremy Olexa wrote: > > So you are asking for the layman file to be updated properly or > > what? layman -i > > As a start: > > 1. How about somebody actually taking ownership of the layman.txt > file for changes? I've seen a couple of emails come to overlays@ > asking about the file, without answers. As far as I know, any dev can commit to the file. I've been meaning to answer the requests, but I was afk over the holidays. > 2. Include bug tracking details in the layman file or other overlay > listing. Good idea. Keeping a second list around with all overlays is just one more place to update. Do we want/have an extra product or component in Bugzilla as well (for all overlay issues)? Robert signature.asc Description: This is a digitally signed message part.
Re: [gentoo-dev] [RFC] bugs.g.o supported overlays should register
On Fri, Jan 02, 2009 at 11:50:07PM -0600, Jeremy Olexa wrote: > So you are asking for the layman file to be updated properly or what? > layman -i As a start: 1. How about somebody actually taking ownership of the layman.txt file for changes? I've seen a couple of emails come to overlays@ asking about the file, without answers. 2. Include bug tracking details in the layman file or other overlay listing. -- Robin Hugh Johnson Gentoo Linux Developer & Infra Guy E-Mail : robb...@gentoo.org GnuPG FP : 11AC BA4F 4778 E3F6 E4ED F38E B27B 944E 3488 4E85 pgpbl3uQjh2y7.pgp Description: PGP signature
Re: [gentoo-dev] [RFC] bugs.g.o supported overlays should register
Jeroen Roovers wrote: Hi folks, in light of some recent discussions where overlay maintainers found that bug reports had been assigned "incorrectly" and thought it was apt to inform the miscellaneous bug wranglers of the correct assignees, I thought it would be a good idea to introduce a new list, akin to metadata.xml and herds.xml, to resolve this issue once and for all. As with herds and metadata, this overlays.xml should list a repository's name, HOMEPAGE and the e-mail address(es) of its maintainers. In the absence of such information, a bug wrangler may assign the bug report to someone who has contributed to the overlay in question, or to anyone who might reasonably know whom to properly assign the bug report to. In case assignment goes awry, and when the assignee is part of the team of proper assignees, then the team or assignee should make sure overlays.xml is updated to reflect the current maintainance status and should add the remainder of the assignees themselves. Nothing else needs to be done in this case - the next time a different bug wrangler might be handling a bug report about that overlay, so CC'ing or pinging (on IRC) doesn't make sense - updating overlays.xml would. If the assignee is not part of the maintainer team of the overlay in question, then the bug may be bounced back to bug-wrangl...@g.o. Please discuss. Kind regards, jer So you are asking for the layman file to be updated properly or what? layman -i IMO, what would really benefit us is to have a site akin to http://gpo.zugaina.org/ on a Gentoo host to *find* packages that are in 'official' overlays. -Jeremy
[gentoo-dev] [RFC] bugs.g.o supported overlays should register
Hi folks, in light of some recent discussions where overlay maintainers found that bug reports had been assigned "incorrectly" and thought it was apt to inform the miscellaneous bug wranglers of the correct assignees, I thought it would be a good idea to introduce a new list, akin to metadata.xml and herds.xml, to resolve this issue once and for all. As with herds and metadata, this overlays.xml should list a repository's name, HOMEPAGE and the e-mail address(es) of its maintainers. In the absence of such information, a bug wrangler may assign the bug report to someone who has contributed to the overlay in question, or to anyone who might reasonably know whom to properly assign the bug report to. In case assignment goes awry, and when the assignee is part of the team of proper assignees, then the team or assignee should make sure overlays.xml is updated to reflect the current maintainance status and should add the remainder of the assignees themselves. Nothing else needs to be done in this case - the next time a different bug wrangler might be handling a bug report about that overlay, so CC'ing or pinging (on IRC) doesn't make sense - updating overlays.xml would. If the assignee is not part of the maintainer team of the overlay in question, then the bug may be bounced back to bug-wrangl...@g.o. Please discuss. Kind regards, jer
