1 |
Attn devs. Please I beg of you don't reassign security@ bugs to yourself |
2 |
and close them but by all means please help get resolutions on them. |
3 |
|
4 |
Why you ask yourself when you can get credit for closing bugs and some |
5 |
free hardware. Well get over it security needs to override free hardware |
6 |
and we/I need these closed while they are assigned to security@. |
7 |
|
8 |
For those of you motivated by solely improving gentoo linux please take |
9 |
a look at the following url |
10 |
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 |
11 |
|
12 |
thanks.. |
13 |
|
14 |
|
15 |
On Wed, 2003-10-01 at 02:53, Daniel Robbins wrote: |
16 |
> Hi All, |
17 |
> |
18 |
> (please direct all replies to gentoo-dev only (if appropriate;) I'm |
19 |
> cross-posting this email so no one misses it.) |
20 |
> |
21 |
> Today (Oct 1 2003) marks the beginning of the Great 2003 Gentoo Bug |
22 |
> Hunt. |
23 |
> |
24 |
> What makes this bug hunt so "Great," you ask? I don't know. Hmm. How |
25 |
> about... bunches of free hardware to be awarded to the top bug |
26 |
> squashers? Yep, sounds good. |
27 |
> |
28 |
> Here's how it works. Starting today and ending 23:59:59 Dec 31 2003 UTC, |
29 |
> we will keep a tally of total number of bug reports closed by developers |
30 |
> (actually, we'll run a mysql query in 3 months on Jan 1, but "keeping a |
31 |
> tally" reads better.) The top bug squashers will take their pick from a |
32 |
> cache of hardware components. The #1 squasher will get first pick, the |
33 |
> number 2 squasher second pick, etc. |
34 |
> |
35 |
> The stash of things you can win will consist of new hardware components |
36 |
> (unless there's a really exceptional used component that is available -- |
37 |
> the point is, all the stuff being raffled will be desirable, not |
38 |
> someone's old burnt-out Pentium 133): stuff like motherboards, CPUs |
39 |
> (maybe some mobo/cpu combos,) RAM, hard drives, video cards, etc. These |
40 |
> items will be purchased in late December in order to maximize the |
41 |
> up-to-dateness and yumminess of the to-be-awarded prizes. |
42 |
> |
43 |
> It gets better. Thanks to the success of the Gentoo Store, it looks like |
44 |
> we may be able to do twice a year in 2004 at the very least. |
45 |
> |
46 |
> Want to get involved, squash some bugs and possibly get some free |
47 |
> hardware? Here are some tips: |
48 |
> |
49 |
> 1. Be sure to participate in the upcoming Gentoo Bug Day on Sat, Oct 4 |
50 |
> 2003, and on the first Satuday of every month (Nov, Dec.) |
51 |
> |
52 |
> 2. Scour bugzilla for bugs that you can fix and/or close. To get credit |
53 |
> for a bug, assign it to yourself before you close it. Don't close a bug |
54 |
> unless you've really fixed the issue. Don't blow off or be mean to bug |
55 |
> submitters just so that you can close a bug. Professionalism is |
56 |
> important. |
57 |
> |
58 |
> 3. If you close dups, each dup you close *will* count. You're helping to |
59 |
> keep bugzilla clean and usable. |
60 |
> |
61 |
> 4. For bugs that contain new ebuilds to be added to Portage, you can |
62 |
> close the bug after the ebuild has been QA checked (by you) and added to |
63 |
> the tree (to unstable.) Do not add new ebuilds blindly, and do not add |
64 |
> new versions of existing packages without diffing with the most-recent |
65 |
> version currently in the tree -- sometimes, people use version 1.2 to |
66 |
> create 1.5, but we have 1.3 which includes an important build fix. And |
67 |
> if you add 1.5 without looking at 1.3, you might accidentally omit the |
68 |
> build fix which would be bad. (just a quick example.) |
69 |
> |
70 |
> 5. Respect herds and existing maintainers. Look at the Changelog and |
71 |
> metadata.xml. If the last committer is not an active dev, it is |
72 |
> certainly OK to take some initiative and close the bug yourself. But see |
73 |
> if they're active first. If they are, you might want to get their input |
74 |
> first (depending on the complexity of the package.) Beware of important |
75 |
> libraries and system packages, which should be treated with the utmost |
76 |
> care and deferred to the official maintainer(s) (according to |
77 |
> metadata.xml or ChangeLog.) |
78 |
> |
79 |
> 6. Likewise, if you are a developer who has a lot of bugs assigned to |
80 |
> you, but you haven't had the time to tackle your bugs, please *allow |
81 |
> others to close them for you.* Smile when they do. Let others help you |
82 |
> out. |
83 |
> |
84 |
> 7. Have fun! The time you spend hacking on Gentoo is appreciated, and I |
85 |
> hope these prizes will help make bug squashing a bit more exciting... |
86 |
> and rewarding. |
87 |
> |
88 |
> Sincerely, |
89 |
> |
90 |
> Daniel |
91 |
-- |
92 |
Ned Ludd <solar@g.o> |
93 |
Gentoo Linux Developer |