Re: [gentoo-dev] Pinboard of outdated ports
> I whipped up this site because the herds I'm in have a gazillion > packages: > http://gentooexperimental.org/meatoo/ > > It needs some work but it'd be easy to send out mail to > subscribers by herd or maintainer email instead of subscribing to > dozens of individual freshmeat packages. Or when the command-line > tool is done you can check whenever you want by herd name. This is even cooler than the pinboard idea. Nice one! -- Today is Prickle-Prickle, the 71st day of Discord in the YOLD 3171 pgpaHQ9J8Npmv.pgp Description: PGP signature
Re: [gentoo-dev] Pinboard of outdated ports
Tom Martin wrote: Maybe it would be better to tell maintainers to just subscribe to projects on freshmeat? I whipped up this site because the herds I'm in have a gazillion packages: http://gentooexperimental.org/meatoo/ It needs some work but it'd be easy to send out mail to subscribers by herd or maintainer email instead of subscribing to dozens of individual freshmeat packages. Or when the command-line tool is done you can check whenever you want by herd name. -- Rob Cakebread Gentoo Linux Developer Public Key: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x96BA679B Key fingerprint = 5E1A 57A0 0FA6 939D 3258 8369 81C5 A17B 96BA 679B -- gentoo-dev@gentoo.org mailing list
Re: [gentoo-dev] Pinboard of outdated ports
On Tuesday 24 May 2005 16:47, Tom Martin wrote: > Maybe it would be better to tell maintainers to just subscribe to > projects on freshmeat? That doesn't work too well usually. Unfortunately I have at least two packages I maintain (one directly, one as video herd) which I'm subscribed to but sends the freshmeat emails just after one or two weeks. I usually subscribe to sf.net/berlios.de notify when present, if not, their own mailing lists, rss feed and if nothing is there, I just cycle through some of them every two days. -- Diego "Flameeyes" Pettenò Gentoo Developer (Gentoo/FreeBSD, Video, Gentoo/AMD64) http://dev.gentoo.org/~flameeyes/ pgp1RKsN2bTqG.pgp Description: PGP signature
Re: [gentoo-dev] Pinboard of outdated ports
On Tue, May 24, 2005 at 12:47:51AM +0200, Johannes Weiner <[EMAIL PROTECTED]> wrote: > On Mon, May 23, 2005 at 08:46:51PM +0100, Tom Martin wrote: > > On Mon, May 23, 2005 at 07:11:38PM +0200, Johannes Weiner <[EMAIL > > PROTECTED]> wrote: > > > * More staff needed > > > Despite the autodeletion of uptodate packages there has to be > > > someone attending the list. Remove real spam or uptodate packages > > > where the targetversion is principally right but not in the correct > > > format, so the autodeletion doesn't match. > > > > How does it fit in with metadata.xml, and the maintainers and herds > > listed therein? > > I don't get the context. Why metadata.xml? And why maintainers and herds > listed? Well, if this just creates an entry to the list with no mention of the email address of the maintainer, if given in metadata.xml, then it's pretty pointless in my opinion as no-one but the maintainer could/should bump software unless you've got a go-ahead from the maintainer or there are exceptional circumstances. My request is that when a new entry is added to the list, the software used checks the package's metadata.xml and includes the herd and maintainer on the list. If there is a maintainer specified, it sends an email to the maintainer. Maybe it would be better to tell maintainers to just subscribe to projects on freshmeat? Hope that makes sense now, Tom -- Tom Martin, http://dev.gentoo.org/~slarti AMD64, net-mail, shell-tools, vim, recruiters Gentoo Linux pgp3tqNx5PEdD.pgp Description: PGP signature
Re: [gentoo-dev] Pinboard of outdated ports
On Tue, 2005-05-24 at 07:26 +0200, Johannes Weiner wrote: > > What it seems like you're doing here is saying more work for the > > developers is fine, if it makes things easier for the users. (Developers > > will just cvs up, which is likely faster than dealing with a web interface.) > > I dunno if it's really big work to have a look at one site to see if > there are ebuilds you missed when they were updated. > It was not my intention to make really more work. It was just to find a faster > way for outdated ebuilds getting updated. There is really only one way to do this. Figure out how to give the developers more time to develop. Having to search through bugs.gentoo.org, plus some external site, would increase the time needed to find packages in need of upgrade, as some will be filed as bugs, which would need to be resolved, so they would have to be searched for *anyway* in bugzilla. The most productive thing you could do, would be to figure out a simple way of testing ebuilds, marking them as tested, and assigning them to the proper parties quicker than is being done now. What we really need is to have the AT program extended from just amd64 to every arch, including x86 (which desperately needs an arch team). -- Chris Gianelloni Release Engineering - Strategic Lead/QA Manager Games - Developer Gentoo Linux signature.asc Description: This is a digitally signed message part
Re: [gentoo-dev] Pinboard of outdated ports
On Tue, May 24, 2005 at 07:26:49AM +0200, Johannes Weiner wrote: > > What it seems like you're doing here is saying more work for the > > developers is fine, if it makes things easier for the users. (Developers > > will just cvs up, which is likely faster than dealing with a web interface.) > > I dunno if it's really big work to have a look at one site to see if > there are ebuilds you missed when they were updated. > It was not my intention to make really more work. It was just to find a faster > way for outdated ebuilds getting updated. If it is difficult for the users, maybe it needs to be documented better. Might be as simple as a "Report old ebuild" links on the Bugzilla homepage. Somehow I don't think it is all that difficult though. To make a clean separation for other Bugzilla content a new Component may be added. This should ease an searching issues as long as the users searching are aware of the new component. But then we'd probably still see a bunch of confused, headless chickens running around squaking "ebuilds, old ebuilds". -- David Stanek www.roninds.net GPG keyID #6272EDAF on http://pgp.mit.edu Key fingerprint = 8BAA 7E11 8856 E148 6833 655A 92E2 3E00 6272 EDAF pgp1w7iYtHEec.pgp Description: PGP signature
Re: [gentoo-dev] Pinboard of outdated ports
> What it seems like you're doing here is saying more work for the > developers is fine, if it makes things easier for the users. (Developers > will just cvs up, which is likely faster than dealing with a web interface.) I dunno if it's really big work to have a look at one site to see if there are ebuilds you missed when they were updated. It was not my intention to make really more work. It was just to find a faster way for outdated ebuilds getting updated. > Although that may be nice in concept, in reality developers may have > quite limited time. Most things that detract from the time they spend on > development rather than on searching around and figuring out what to do > makes Gentoo worse. It has yet to be proven that your suggestion would > take more time, but that's the feeling I have. > > If one knows how to search bugzilla and understands how maintainers are > indicated, this can be comparably easy already. Something like this > could give you a search: > > 1. Use herdstat to find the maintainer, if you aren't comfortable with > the metadata.xml files. > > $ herdstat --metadata xorg-x11 > Package: x11-base/xorg-x11 > Herds(1):x11 > Maintainers(0): none > Homepage:http://xorg.freedesktop.org/ > Description: X11 implementation by X.Org Foundation Will try this, my idea seems to be refused anyway. -- Today is Prickle-Prickle, the 71st day of Discord in the YOLD 3171 pgpyrB6iYDs9c.pgp Description: PGP signature
Re: [gentoo-dev] Pinboard of outdated ports
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Johannes Weiner wrote:
> One more tab in ${BROWSER}.. And it shouldn't make more work. It should
> ease the work already there.
> Having submitted an outdated port seems to be more comfortable to me
> than checking your portrepo everyday for actuality.
What it seems like you're doing here is saying more work for the
developers is fine, if it makes things easier for the users. (Developers
will just cvs up, which is likely faster than dealing with a web interface.)
Although that may be nice in concept, in reality developers may have
quite limited time. Most things that detract from the time they spend on
development rather than on searching around and figuring out what to do
makes Gentoo worse. It has yet to be proven that your suggestion would
take more time, but that's the feeling I have.
If one knows how to search bugzilla and understands how maintainers are
indicated, this can be comparably easy already. Something like this
could give you a search:
1. Use herdstat to find the maintainer, if you aren't comfortable with
the metadata.xml files.
$ herdstat --metadata xorg-x11
Package: x11-base/xorg-x11
Herds(1):x11
Maintainers(0): none
Homepage:http://xorg.freedesktop.org/
Description: X11 implementation by X.Org Foundation
2. Search for Enhancement bugs assigned to that herd/maintainer in
Bugzilla. In this case, it would be bugs assigned to [EMAIL PROTECTED]
3. Profit!
Thanks,
Donnie
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFCkmKxXVaO67S1rtsRArXJAJ4gx6G+v4CJkXxx2NCd6ZN1Yw/aBgCfTrGl
2wOH333zS11rgRLePRM3jxw=
=GV1a
-END PGP SIGNATURE-
--
gentoo-dev@gentoo.org mailing list
Re: [gentoo-dev] Pinboard of outdated ports
> I really like having all the Gentoo things I need to do in one location.
> Right now, that location is Bugzilla. Having to look in more places to
> figure out what to do seems like it would just waste more time.
One more tab in ${BROWSER}.. And it shouldn't make more work. It should
ease the work already there.
Having submitted an outdated port seems to be more comfortable to me
than checking your portrepo everyday for actuality.
--
Today is Prickle-Prickle, the 71st day of Discord in the YOLD 3171
pgpEP4vulwNtz.pgp
Description: PGP signature
Re: [gentoo-dev] Pinboard of outdated ports
On Mon, May 23, 2005 at 08:46:51PM +0100, Tom Martin wrote: > On Mon, May 23, 2005 at 07:11:38PM +0200, Johannes Weiner <[EMAIL PROTECTED]> > wrote: > > * More staff needed > > Despite the autodeletion of uptodate packages there has to be > > someone attending the list. Remove real spam or uptodate packages > > where the targetversion is principally right but not in the correct > > format, so the autodeletion doesn't match. > > How does it fit in with metadata.xml, and the maintainers and herds > listed therein? I don't get the context. Why metadata.xml? And why maintainers and herds listed? Confusion, hannes -- Today is Prickle-Prickle, the 71st day of Discord in the YOLD 3171 pgp5CTQPCGRPr.pgp Description: PGP signature
Re: [gentoo-dev] Pinboard of outdated ports
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Johannes Weiner wrote: > Outdated ebuild reporting system > > > Why > Reporting outdated ebuilds via bugzilla is in my opinion not the best > solution. > An outdated port isn't really a 'bug' and so there are many obsolete > reporting fields when posting a too old ebuild. The process should be > handled on its own, more efficient and specific way. I really like having all the Gentoo things I need to do in one location. Right now, that location is Bugzilla. Having to look in more places to figure out what to do seems like it would just waste more time. Donnie -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFCkjQDXVaO67S1rtsRAiOyAKDtJty+m/6QyCsxHA+jElVKDNOOpACfQkX0 HCEpo8HnioEpitTnRZkEoaA= =I0qo -END PGP SIGNATURE- -- gentoo-dev@gentoo.org mailing list
Re: [gentoo-dev] Pinboard of outdated ports
On Mon, May 23, 2005 at 07:11:38PM +0200, Johannes Weiner <[EMAIL PROTECTED]> wrote: > * More staff needed > Despite the autodeletion of uptodate packages there has to be > someone attending the list. Remove real spam or uptodate packages > where the targetversion is principally right but not in the correct > format, so the autodeletion doesn't match. How does it fit in with metadata.xml, and the maintainers and herds listed therein? Tom -- Tom Martin, http://dev.gentoo.org/~slarti AMD64, net-mail, shell-tools, vim, recruiters Gentoo Linux pgp3AQxB8vKgW.pgp Description: PGP signature
[gentoo-dev] Pinboard of outdated ports
Outdated ebuild reporting system Why Reporting outdated ebuilds via bugzilla is in my opinion not the best solution. An outdated port isn't really a 'bug' and so there are many obsolete reporting fields when posting a too old ebuild. The process should be handled on its own, more efficient and specific way. Concept A pinboard-like list that shows the developers outdated packages. For this we need a form with: * dropbox for the package category * dropbox for the packagename itself (perhaps incl. version?) * textbox for the target-version - This will be compared with the portage version. If the target-version and the portage version the same, the entry will be deleted. This helps to decrease the 0-days-spam. See below. There should be a page before this form with a software-news-ticker, like the Freshmeat RSS feed, and a note that nothing should be posted that is listed here. This will prevent at least some of the 0-days-spam. Also a textfield where users have to agree with the conditions: 18:06 include a textbox into which the user must type "I am not spamming. I have left this for at least a week following the announcement. I have checked that the package is not already in the tree. I have searched for existing bugs." Good idea. :) Problems * 0-days-spammer People who post all the most current news on freshmeat or other announcements. Noone needs this, the devs can read for themselves. To avoid 0-days-spamming there is the textbox ciaranm thought of. * Endless list growing To prevent the list from growing up like hell, there should be a mechanism that compares the list entrys' target-versions with the portage-version and removes the entry if the package is uptodate. * More staff needed Despite the autodeletion of uptodate packages there has to be someone attending the list. Remove real spam or uptodate packages where the targetversion is principally right but not in the correct format, so the autodeletion doesn't match. This is still expandable. This document will be updated at: http://hnaz.exa-ds.com/files/update-pinboard.txt For suggestions mail at: hannes <[EMAIL PROTECTED]> -- Today is Pungenday, the 70th day of Discord in the YOLD 3171 pgpvpQeqA2DIC.pgp Description: PGP signature
