[gentoo-dev] ANNOUNCING: Great 2003 Gentoo Bug Hunt (with prizes)

[gentoo-dev] ANNOUNCING: Great 2003 Gentoo Bug Hunt (with prizes)

[Daniel Robbins]

[-- Attachment #1: Type: text/plain, Size: 3528 bytes --]

Hi All,

(please direct all replies to gentoo-dev only (if appropriate;) I'm
cross-posting this email so no one misses it.)

Today (Oct 1 2003) marks the beginning of the Great 2003 Gentoo Bug
Hunt. 

What makes this bug hunt so "Great," you ask? I don't know. Hmm. How
about... bunches of free hardware to be awarded to the top bug
squashers? Yep, sounds good.

Here's how it works. Starting today and ending 23:59:59 Dec 31 2003 UTC,
we will keep a tally of total number of bug reports closed by developers
(actually, we'll run a mysql query in 3 months on Jan 1, but "keeping a
tally" reads better.) The top bug squashers will take their pick from a
cache of hardware components. The #1 squasher will get first pick, the
number 2 squasher second pick, etc. 

The stash of things you can win will consist of new hardware components
(unless there's a really exceptional used component that is available --
the point is, all the stuff being raffled will be desirable, not
someone's old burnt-out Pentium 133): stuff like motherboards, CPUs
(maybe some mobo/cpu combos,) RAM, hard drives, video cards, etc. These
items will be purchased in late December in order to maximize the
up-to-dateness and yumminess of the to-be-awarded prizes. 

It gets better. Thanks to the success of the Gentoo Store, it looks like
we may be able to do twice a year in 2004 at the very least.

Want to get involved, squash some bugs and possibly get some free
hardware? Here are some tips:

1. Be sure to participate in the upcoming Gentoo Bug Day on Sat, Oct 4
2003, and on the first Satuday of every month (Nov, Dec.)

2. Scour bugzilla for bugs that you can fix and/or close. To get credit
for a bug, assign it to yourself before you close it. Don't close a bug
unless you've really fixed the issue. Don't blow off or be mean to bug
submitters just so that you can close a bug. Professionalism is
important.

3. If you close dups, each dup you close *will* count. You're helping to
keep bugzilla clean and usable.

4. For bugs that contain new ebuilds to be added to Portage, you can
close the bug after the ebuild has been QA checked (by you) and added to
the tree (to unstable.) Do not add new ebuilds blindly, and do not add
new versions of existing packages without diffing with the most-recent
version currently in the tree -- sometimes, people use version 1.2 to
create 1.5, but we have 1.3 which includes an important build fix. And
if you add 1.5 without looking at 1.3, you might accidentally omit the
build fix which would be bad. (just a quick example.)

5. Respect herds and existing maintainers. Look at the Changelog and
metadata.xml. If the last committer is not an active dev, it is
certainly OK to take some initiative and close the bug yourself. But see
if they're active first. If they are, you might want to get their input
first (depending on the complexity of the package.) Beware of important
libraries and system packages, which should be treated with the utmost
care and deferred to the official maintainer(s) (according to
metadata.xml or ChangeLog.)

6. Likewise, if you are a developer who has a lot of bugs assigned to
you, but you haven't had the time to tackle your bugs, please *allow
others to close them for you.* Smile when they do. Let others help you
out.

7. Have fun! The time you spend hacking on Gentoo is appreciated, and I
hope these prizes will help make bug squashing a bit more exciting...
and rewarding.

Sincerely,

Daniel

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-dev] ANNOUNCING: Great 2003 Gentoo Bug Hunt (with prizes)

[Chris Smith]

Hey Daniel,

This is an absolutely brilliant idea, briba^H^H^H^H^H rewards are a great way
to get things done! j/k :)

I don't know of any other project/distro that gives back to the developers
this way, it's a small step, but its a step in the right direction for
"putting food on the plate of open source developers".

On Wednesday 01 October 2003 18:53, Daniel Robbins wrote:
> 3. If you close dups, each dup you close *will* count. You're helping to
> keep bugzilla clean and usable.

Well... It looks like spanky has this one in the bag then ;)

You have every bit of support from me, I will definately donate next pay day.

Cheers,
Chris.

P.S. My apologies to Daniel whom I sent this mail to directly at first. Sorry.


--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] ANNOUNCING: Great 2003 Gentoo Bug Hunt (with prizes)

[Markus Nigbur]

[-- Attachment #1: Type: text/plain, Size: 1590 bytes --]

On Wed, 01 Oct 2003 00:53:18 -0600
Daniel Robbins <drobbins@gentoo.org> wrote:

> 5. Respect herds and existing maintainers. Look at the Changelog and
> metadata.xml. If the last committer is not an active dev, it is
> certainly OK to take some initiative and close the bug yourself. But
> see if they're active first. If they are, you might want to get their
> input first (depending on the complexity of the package.) Beware of
> important libraries and system packages, which should be treated with
> the utmost care and deferred to the official maintainer(s) (according
> to metadata.xml or ChangeLog.)

I'll take this opportunity to promote the script I'm currently
developing. One of its purposes is to find packages that don't have a
metadata.xml file. Another goody of its functions is the possibility to
search for the maintainer of a certain package.
For example, if you specify a package without a metadata.xml file, it
will parse the ChangeLog and return the developer with most ChangeLog
entries. On the other hand, if the package you specified has a
metadata.xml file, it will parse the information given in there.

It still needs some improvement and I'm currently in the middle of
rewriting it (possibly integrate the use portage.py's functions instead
of my own; but this will require some speed benchmarking...).
I'm open for suggestions and improvements you might come up with.

If you're interested you can check the current stable and pre releases
over here:
http://dev.gentoo.org/~pyrania/metadata/

-- Markus

-- 
Markus Nigbur
Gentoo Developer
http://www.gentoo.org

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-dev] ANNOUNCING: Great 2003 Gentoo Bug Hunt (with prizes)

[Tal Peer]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Wed, 1 Oct 2003, Daniel Robbins wrote:

> [snip]
> 
> 2. Scour bugzilla for bugs that you can fix and/or close. To get credit
> for a bug, assign it to yourself before you close it. Don't close a bug
> unless you've really fixed the issue. Don't blow off or be mean to bug
> submitters just so that you can close a bug. Professionalism is
> important.
> 

What about bugs assigned to herds (php-bugs@gentoo.org fex)?
Most of my bugfixing is done on bugs assigned to aliases.

- --
Tal Peer
Gentoo Developer

Public Key: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x253D2947
Key Fingerprint: C0B1 D91D 7323 6C0F 227A CBD6 D635 E53D 253D 2947

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE/esbG1jXlPSU9KUcRAs0FAKCFIixNAeTN+cMQfdjK1YeDjFK84QCffCRJ
8gWeSa4I949rtD4hipaL4XM=
=8pmc
-----END PGP SIGNATURE-----

--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] ANNOUNCING: Great 2003 Gentoo Bug Hunt (with prizes)

[Ned Ludd]

[-- Attachment #1: Type: text/plain, Size: 4631 bytes --]

Attn devs. Please I beg of you don't reassign security@ bugs to yourself
and close them but by all means please help get resolutions on them.

Why you ask yourself when you can get credit for closing bugs and some
free hardware. Well get over it security needs to override free hardware
and we/I need these closed while they are assigned to security@.

For those of you motivated by solely improving gentoo linux please take
a look at the following url
http://bugs.gentoo.org/buglist.cgi?bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&field0-0-0=product&type0-0-0=substring&value0-0-0=Security&field0-0-1=component&type0-0-1=substring&value0-0-1=Security&field0-0-2=short_desc&type0-0-2=substring&value0-0-2=Security&field0-0-3=status_whiteboard&type0-0-3=substring&value0-0-3=Security

thanks..


On Wed, 2003-10-01 at 02:53, Daniel Robbins wrote:
> Hi All,
> 
> (please direct all replies to gentoo-dev only (if appropriate;) I'm
> cross-posting this email so no one misses it.)
> 
> Today (Oct 1 2003) marks the beginning of the Great 2003 Gentoo Bug
> Hunt. 
> 
> What makes this bug hunt so "Great," you ask? I don't know. Hmm. How
> about... bunches of free hardware to be awarded to the top bug
> squashers? Yep, sounds good.
> 
> Here's how it works. Starting today and ending 23:59:59 Dec 31 2003 UTC,
> we will keep a tally of total number of bug reports closed by developers
> (actually, we'll run a mysql query in 3 months on Jan 1, but "keeping a
> tally" reads better.) The top bug squashers will take their pick from a
> cache of hardware components. The #1 squasher will get first pick, the
> number 2 squasher second pick, etc. 
> 
> The stash of things you can win will consist of new hardware components
> (unless there's a really exceptional used component that is available --
> the point is, all the stuff being raffled will be desirable, not
> someone's old burnt-out Pentium 133): stuff like motherboards, CPUs
> (maybe some mobo/cpu combos,) RAM, hard drives, video cards, etc. These
> items will be purchased in late December in order to maximize the
> up-to-dateness and yumminess of the to-be-awarded prizes. 
> 
> It gets better. Thanks to the success of the Gentoo Store, it looks like
> we may be able to do twice a year in 2004 at the very least.
> 
> Want to get involved, squash some bugs and possibly get some free
> hardware? Here are some tips:
> 
> 1. Be sure to participate in the upcoming Gentoo Bug Day on Sat, Oct 4
> 2003, and on the first Satuday of every month (Nov, Dec.)
> 
> 2. Scour bugzilla for bugs that you can fix and/or close. To get credit
> for a bug, assign it to yourself before you close it. Don't close a bug
> unless you've really fixed the issue. Don't blow off or be mean to bug
> submitters just so that you can close a bug. Professionalism is
> important.
> 
> 3. If you close dups, each dup you close *will* count. You're helping to
> keep bugzilla clean and usable.
> 
> 4. For bugs that contain new ebuilds to be added to Portage, you can
> close the bug after the ebuild has been QA checked (by you) and added to
> the tree (to unstable.) Do not add new ebuilds blindly, and do not add
> new versions of existing packages without diffing with the most-recent
> version currently in the tree -- sometimes, people use version 1.2 to
> create 1.5, but we have 1.3 which includes an important build fix. And
> if you add 1.5 without looking at 1.3, you might accidentally omit the
> build fix which would be bad. (just a quick example.)
> 
> 5. Respect herds and existing maintainers. Look at the Changelog and
> metadata.xml. If the last committer is not an active dev, it is
> certainly OK to take some initiative and close the bug yourself. But see
> if they're active first. If they are, you might want to get their input
> first (depending on the complexity of the package.) Beware of important
> libraries and system packages, which should be treated with the utmost
> care and deferred to the official maintainer(s) (according to
> metadata.xml or ChangeLog.)
> 
> 6. Likewise, if you are a developer who has a lot of bugs assigned to
> you, but you haven't had the time to tackle your bugs, please *allow
> others to close them for you.* Smile when they do. Let others help you
> out.
> 
> 7. Have fun! The time you spend hacking on Gentoo is appreciated, and I
> hope these prizes will help make bug squashing a bit more exciting...
> and rewarding.
> 
> Sincerely,
> 
> Daniel
-- 
Ned Ludd <solar@gentoo.org>
Gentoo Linux Developer

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 307 bytes --]

Re: [gentoo-dev] ANNOUNCING: Great 2003 Gentoo Bug Hunt (with prizes)

[Chris Bainbridge]

Instead of having the totals announced in 3 months why not make it a bit more 
exciting and have realtime charts on bugzilla? I always thought the kde 
bugzilla with its top resolvers table was a good way to motivate people, with 
prizes it would be even better. It would also be nice to have statistics like 
the "most buggy apps" available as well, so people can see where the most 
work is needed.


--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] ANNOUNCING: Great 2003 Gentoo Bug Hunt (with prizes)

[Markus Nigbur]

[-- Attachment #1: Type: text/plain, Size: 968 bytes --]

On Thu, 2 Oct 2003 10:19:45 +0000
Chris Bainbridge <C.J.Bainbridge@ed.ac.uk> wrote:

> Instead of having the totals announced in 3 months why not make it a
> bit more exciting and have realtime charts on bugzilla? I always
> thought the kde bugzilla with its top resolvers table was a good way
> to motivate people, with prizes it would be even better. It would also
> be nice to have statistics like the "most buggy apps" available as
> well, so people can see where the most work is needed.

The idea of real-time charting resolved bugs by developer, group and
probably other stuff sounds pretty nice. Maybe because I'm a statistics
freak anyway. ;-)

IMHO this could be implemented very easily and would, as Chris already
stated, increase the decent motivation of some people.
I'd like to hear some more voices concerning this topic and if no one
else is interested I would create those scripts.

-- Markus

-- 
Markus Nigbur
Gentoo Developer
http://www.gentoo.org

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-dev] ANNOUNCING: Great 2003 Gentoo Bug Hunt (with prizes)

[Caleb Tennis]

On Thursday 02 October 2003 07:46 am, Markus Nigbur wrote:
> The idea of real-time charting resolved bugs by developer, group and
> probably other stuff sounds pretty nice. Maybe because I'm a statistics
> freak anyway. ;-)

A few other front page links that could/should be added:


Unresolved bugs containing proposed patches
New Ebuilds waiting for portage inclusion
The most frequently reported bugs (as noted by dup count)

Show All Reports I own
Show All Reports I'm cced on
Show all Open Reports I've commented to



--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] ANNOUNCING: Great 2003 Gentoo Bug Hunt (with prizes)

[Jason Stubbs]

On Thursday 02 October 2003 22:02, Caleb Tennis wrote:
> On Thursday 02 October 2003 07:46 am, Markus Nigbur wrote:
> > The idea of real-time charting resolved bugs by developer, group and
> > probably other stuff sounds pretty nice. Maybe because I'm a statistics
> > freak anyway. ;-)
>
> A few other front page links that could/should be added:
>
>
> Unresolved bugs containing proposed patches
> New Ebuilds waiting for portage inclusion
> The most frequently reported bugs (as noted by dup count)

These would be great for devs. Even users who like to do a bit of hacking 
(like myself) would benefit from these too.

> Show All Reports I own
> Show All Reports I'm cced on
> Show all Open Reports I've commented to

These are necessary for any user of bugzilla. I've tried creating queries for 
these without any success.

Jason

--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] ANNOUNCING: Great 2003 Gentoo Bug Hunt (with prizes)

[Robin H. Johnson]

[-- Attachment #1: Type: text/plain, Size: 1010 bytes --]

On Fri, Oct 03, 2003 at 09:31:20AM +0900, Jason Stubbs wrote:
> > Show All Reports I own
All bugs I reported:
http://bugs.gentoo.org/buglist.cgi?query_format=&cmdtype=doit&remaction=run&field0-0-0=reporter&type0-0-0=substring&value0-0-0=robbat2@gentoo.org

All bugs assigned to me:
http://bugs.gentoo.org/buglist.cgi?query_format=&cmdtype=doit&remaction=run&field0-0-0=assigned_to&type0-0-0=substring&value0-0-0=robbat2@gentoo.org

> > Show All Reports I'm cced on
http://bugs.gentoo.org/buglist.cgi?query_format=&cmdtype=doit&remaction=run&field0-0-0=cc&type0-0-0=substring&value0-0-0=robbat2@gentoo.org

> > Show all Open Reports I've commented to
This one isn't possible in our bugzilla at the moment. As we can't
select by who commented in the query form afaik.

-- 
Robin Hugh Johnson
E-Mail     : robbat2@orbis-terrarum.net
Home Page  : http://www.orbis-terrarum.net/?l=people.robbat2
ICQ#       : 30269588 or 41961639
GnuPG FP   : 11AC BA4F 4778 E3F6 E4ED  F38E B27B 944E 3488 4E85

[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]

Re: [gentoo-dev] ANNOUNCING: Great 2003 Gentoo Bug Hunt (with prizes)

[Jason Stubbs]

On Friday 03 October 2003 09:55, Robin H. Johnson wrote:
> On Fri, Oct 03, 2003 at 09:31:20AM +0900, Jason Stubbs wrote:
> > > Show All Reports I own
>
> All bugs I reported:
> http://bugs.gentoo.org/buglist.cgi?query_format=&cmdtype=doit&remaction=run
>&field0-0-0=reporter&type0-0-0=substring&value0-0-0=robbat2@gentoo.org
>
> All bugs assigned to me:
> http://bugs.gentoo.org/buglist.cgi?query_format=&cmdtype=doit&remaction=run
>&field0-0-0=assigned_to&type0-0-0=substring&value0-0-0=robbat2@gentoo.org
>
> > > Show All Reports I'm cced on
>
> http://bugs.gentoo.org/buglist.cgi?query_format=&cmdtype=doit&remaction=run
>&field0-0-0=cc&type0-0-0=substring&value0-0-0=robbat2@gentoo.org

Thanks for that.

> > > Show all Open Reports I've commented to
>
> This one isn't possible in our bugzilla at the moment. As we can't
> select by who commented in the query form afaik.

That's a shame because that's the one I wanted the most and couldn't get to 
work.

Jason

--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] ANNOUNCING: Great 2003 Gentoo Bug Hunt (with prizes)

[Jussi Sirpoma]

On 3.10.2003 4:08 Jason Stubbs wrote:

> On Friday 03 October 2003 09:55, Robin H. Johnson wrote:
>> On Fri, Oct 03, 2003 at 09:31:20AM +0900, Jason Stubbs wrote:
>> > > Show all Open Reports I've commented to
>>
>> This one isn't possible in our bugzilla at the moment. As we can't
>> select by who commented in the query form afaik.
> 
> That's a shame because that's the one I wanted the most and couldn't get to 
> work.

Correct me if I misunderstood something but I think this will do what 
you want:

<http://bugs.gentoo.org/buglist.cgi?query_format=&short_desc_type=allwordssubstr&short_desc=&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&resolution=---&emaillongdesc1=1&emailtype1=exact&email1=robbat2%40gentoo.org&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&changedin=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0=>

Also, the cvs version on bugzilla lets you make graphs from any query.

Jussi Sirpoma


--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] ANNOUNCING: Great 2003 Gentoo Bug Hunt (with prizes)

[Thomas de Grenier de Latour]

On Thu, 2 Oct 2003 17:55:49 -0700
"Robin H. Johnson" <robbat2@gentoo.org> wrote:

> > > Show all Open Reports I've commented to
> This one isn't possible in our bugzilla at the moment. 

Here are opened bugs that are not yours but you have commented without
being in assignement or CC: 

http://bugs.gentoo.org/buglist.cgi?query_format=&short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=VERIFIED&emaillongdesc1=1&emailtype1=regexp&email1=robbat2&emailtype2=regexp&email2=&bugidtype=include&bug_id=&changedin=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&remaction=run&order=Reuse+same+sort+as+last+time&field0-0-0=assigned_to&type0-0-0=notregexp&value0-0-0=robbat2&field0-1-0=cc&type0-1-0=notregexp&value0-1-0=robbat2&field0-2-0=reporter&type0-2-0=notregexp&value0-2-0=robbat2

The trick is to check "Any off ... [x] commenter ..." in the "Email and
numbering" box of the query page. But it's true that it doesn't seems to
be any such field in the boolean query from the bottom of the page.

-- 
TGL.

--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] ANNOUNCING: Great 2003 Gentoo Bug Hunt (with prizes)

[Caleb Tennis]

On Thursday 02 October 2003 07:55 pm, Robin H. Johnson wrote:
> All bugs I reported:
> http://bugs.gentoo.org/buglist.cgi?query_format=&cmdtype=doit&remaction=run
>&field0-0-0=reporter&type0-0-0=substring&value0-0-0=robbat2@gentoo.org

<snip>

Now, can we get the Gentoo bugzilla folks to make these as clickable links off 
of Bugzilla's front page?  That would be very helpful indeed!

Caleb

--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] ANNOUNCING: Great 2003 Gentoo Bug Hunt (with prizes)

[Kevin Lacquement]

Caleb Tennis said:
> On Thursday 02 October 2003 07:46 am, Markus Nigbur wrote:
>> The idea of real-time charting resolved bugs by developer, group and
>> probably other stuff sounds pretty nice. Maybe because I'm a statistics
>> freak anyway. ;-)
>
> A few other front page links that could/should be added:
>

Something that I would probably find useful is a random bug link. 
Especially on bugdays, when there are several people trying to get the
bugs.  Click it, and get n random, non-resolved bugs.


--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] ANNOUNCING: Great 2003 Gentoo Bug Hunt (with prizes)

[Stuart Herbert]

[-- Attachment #1: signed data --]
[-- Type: text/plain, Size: 1271 bytes --]

Hi everyone,

As part of the 'Gentoo Bug Hunt', or Saturday's 'Bug Day', a personal plea ...

Please please *please* don't go closing any bugs assigned to the web-apps herd 
that involve adding yet more ebuilds to Portage.  The last thing we need is 
to end up with even more ebuilds to convert once the new web-app stuff is 
done.  After my request in September for information about existing ebuilds, 
I'm left with the opinion that most of the web-app ebuilds are abandoned (or 
maintained by very shy people ;-) - we've got enough stuff to port across as 
it is.

Work *is* progressing on implementing GLEP #11.  It'll appear in Portage when 
there's something ready for testing ;-)

By all means, fix bugs with existing apps - just don't add any more if you can 
help it!

Best regards,
Stu
-- 
Stuart Herbert                                              stuart@gentoo.org
Gentoo Developer                                       http://www.gentoo.org/
Beta packages for download            http://dev.gentoo.org/~stuart/packages/
Come and meet me in March 2004                 http://www.phparch.com/cruise/

GnuGP key id# F9AFC57C available from http://pgp.mit.edu
Key fingerprint = 31FB 50D4 1F88 E227 F319  C549 0C2F 80BA F9AF C57C
--

[-- Attachment #2: signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-dev] ANNOUNCING: Great 2003 Gentoo Bug Hunt (with prizes)

[Stuart Herbert]

[-- Attachment #1: signed data --]
[-- Type: text/plain, Size: 850 bytes --]

On Friday 03 October 2003 9:05 pm, Ian Leitch wrote:
> Have you taken a look at the amount of ebuilds that have 'hardcoded'
> /home/httpd/htdocs? Its no small list... :/

By the time we're done, every single ebuild that installs software to run via 
a webserver (except for web server mods, mind!) will have been edited.  We're 
gonna be busy for some time to come.

Best regards,
Stu
-- 
Stuart Herbert                                              stuart@gentoo.org
Gentoo Developer                                       http://www.gentoo.org/
Beta packages for download            http://dev.gentoo.org/~stuart/packages/
Come and meet me in March 2004                 http://www.phparch.com/cruise/

GnuGP key id# F9AFC57C available from http://pgp.mit.edu
Key fingerprint = 31FB 50D4 1F88 E227 F319  C549 0C2F 80BA F9AF C57C
--

[-- Attachment #2: signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-dev] ANNOUNCING: Great 2003 Gentoo Bug Hunt (with prizes)

[Ian Leitch]

On Fri, 2003-10-03 at 19:47, Stuart Herbert wrote:
> Hi everyone,
> 
> As part of the 'Gentoo Bug Hunt', or Saturday's 'Bug Day', a personal plea ...
> 
> Please please *please* don't go closing any bugs assigned to the web-apps herd 
> that involve adding yet more ebuilds to Portage.  The last thing we need is 
> to end up with even more ebuilds to convert once the new web-app stuff is 
> done.  After my request in September for information about existing ebuilds, 
> I'm left with the opinion that most of the web-app ebuilds are abandoned (or 
> maintained by very shy people ;-) - we've got enough stuff to port across as 
> it is.
> 
> Work *is* progressing on implementing GLEP #11.  It'll appear in Portage when 
> there's something ready for testing ;-)
> 
> By all means, fix bugs with existing apps - just don't add any more if you can 
> help it!
> 
> Best regards,
> Stu

Make sure you let me know when ebuilds can start being ported over. I
ported quite a few ebuilds over to the current web-app eclass some time
ago, they are currently sitting in bugzilla and I'd like to get them
closed when possible. 

Have you taken a look at the amount of ebuilds that have 'hardcoded' 
/home/httpd/htdocs? Its no small list... :/

Regards,
Ian. 


--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] ANNOUNCING: Great 2003 Gentoo Bug Hunt (with prizes)

[Stuart Herbert]

[-- Attachment #1: signed data --]
[-- Type: text/plain, Size: 1020 bytes --]

Daniel,

Okay, just wanted to mention something so you can take it into account when 
calculating the prizes.

As part of today's Bug Day, I've been catching up on the web-apps backlog 
(over 80 bugs so far :), and informing our users that we'll take ebuilds for 
new packages once the new web-app stuff is done.  I've been marking them as 
'RESOLVED: LATER', as it seemed the best option.

Thing is, they're not RESOLVED - just postponed.  I hope they don't count 
towards the final prizes, because that just wouldn't feel right to me.

Thanks,
Stu
-- 
Stuart Herbert                                              stuart@gentoo.org
Gentoo Developer                                       http://www.gentoo.org/
Beta packages for download            http://dev.gentoo.org/~stuart/packages/
Come and meet me in March 2004                 http://www.phparch.com/cruise/

GnuGP key id# F9AFC57C available from http://pgp.mit.edu
Key fingerprint = 31FB 50D4 1F88 E227 F319  C549 0C2F 80BA F9AF C57C
--

[-- Attachment #2: signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-dev] ANNOUNCING: Great 2003 Gentoo Bug Hunt (with prizes)

[Luke-Jr]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Saturday 04 October 2003 11:53 am, Stuart Herbert wrote:
> I've been marking
> them as 'RESOLVED: LATER', as it seemed the best option.
>
> Thing is, they're not RESOLVED - just postponed.
That's the reason I never use RESOLVED: LATER for anything. Such items are not 
actually resolved and marking them so removes them from my list of bugs. 
Could LATER be moved to a non-RESOLVED status perhaps?
- -- 
Luke-Jr
Developer, Gentoo Linux
http://www.gentoo.org/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQE/fsNrZl/BHdU+lYMRAursAJ9QRTceNMv2pdgatSjtjpNo06Id7QCeIudP
cNPSdLg4VuwvyGAYNllJUAk=
=HEwO
-----END PGP SIGNATURE-----


--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] ANNOUNCING: Great 2003 Gentoo Bug Hunt (with prizes)

[Stuart Herbert]

[-- Attachment #1: signed data --]
[-- Type: text/plain, Size: 823 bytes --]

On Saturday 04 October 2003 1:55 pm, Luke-Jr wrote:
> That's the reason I never use RESOLVED: LATER for anything. Such items are
> not actually resolved and marking them so removes them from my list of
> bugs. Could LATER be moved to a non-RESOLVED status perhaps?

Just fix your Bugzilla queries.  Bugs marked RESOLVED: LATER show up just fine 
for me.

Stu
-- 
Stuart Herbert                                              stuart@gentoo.org
Gentoo Developer                                       http://www.gentoo.org/
Beta packages for download            http://dev.gentoo.org/~stuart/packages/
Come and meet me in March 2004                 http://www.phparch.com/cruise/

GnuGP key id# F9AFC57C available from http://pgp.mit.edu
Key fingerprint = 31FB 50D4 1F88 E227 F319  C549 0C2F 80BA F9AF C57C
--

[-- Attachment #2: signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]