1 |
+1 |
2 |
|
3 |
I was an user very interested by the bug day event, but the timing was |
4 |
never right. A permanent effort where everyone can help whenever they |
5 |
can seems more interesting. The only thing needed then is documentation |
6 |
on exactly what can be done by users with varying skills. |
7 |
|
8 |
Damien |
9 |
|
10 |
On 11/16/2013 06:16 AM, Tom Wijsman wrote: |
11 |
> Hello |
12 |
> |
13 |
> This is a request for comments on a new project: |
14 |
> |
15 |
> http://wiki.gentoo.org/wiki/Project:Bug_Cleaners |
16 |
> |
17 |
> The Gentoo Bug Cleaners project aims to clean up the oldest bugs in |
18 |
> Bugzilla. Our goal is twofold, the main purpose of this project is to |
19 |
> close bugs on Bugzilla that do no longer apply due to versions and/or |
20 |
> packages that are no longer present in the Portage tree; as a side |
21 |
> effect, it also tries to look for solutions to the oldest bugs. |
22 |
> |
23 |
> For those that still have use, it attempts to inform the persons |
24 |
> involved in the bug that the bug is still open if the bug is important; |
25 |
> inviting them to take a decision on it. |
26 |
> |
27 |
> Because one cannot just rush in and go hunt at random bugs and expect |
28 |
> people to agree with one's actions; the very first steps we will take |
29 |
> is to raise the necessary discussion here with you to receive feedback |
30 |
> on what you as the community want us to do, which clarifies the further |
31 |
> limits and scope of this project. |
32 |
> |
33 |
> There are some questions that need further discussion: |
34 |
> |
35 |
> * How old is "oldest"? |
36 |
> |
37 |
> While we intend to work from the back of the bug queue, we might or |
38 |
> might not get closer to more recent bugs; so, one would wonder if we |
39 |
> need a limit on which bugs we can and can't touch. |
40 |
> |
41 |
> * When is a bug considered still useful? |
42 |
> |
43 |
> There are clear cases like a bug that's no longer reproducable and |
44 |
> thus clearly doesn't apply; however, there are cases where one might |
45 |
> be in doubt (eg. Do people still want it resolved? Do we still want |
46 |
> to add a package that stopped its development X years ago?) that |
47 |
> might not be so clear cut. I'd like to get clearer borders defined. |
48 |
> |
49 |
> * Are there other types of bugs we could or need to look into? |
50 |
> |
51 |
> We start with the oldest bugs; but the project name does not include |
52 |
> "Old", are there other types of bugs you would like to see cleaned? |
53 |
> |
54 |
> * Do we need a mail alias so we can get assigned or CC-ed on bugs? |
55 |
> |
56 |
> This one gets me in doubt, the only case I can come up with is that |
57 |
> being able to CC bug-cleaners@g.o allows users to effectively |
58 |
> help us out as well by marking bugs they consider old. |
59 |
> |
60 |
> Another reason might be that we can assign related trackers to it. |
61 |
> |
62 |
> * Do you have any useful resources that we should be aware of? |
63 |
> |
64 |
> I know of the QA bug reports and the ability to search queries, are |
65 |
> there any other tools already made to indicate or deal with old bugs? |
66 |
> |
67 |
> * Can this effort replace the Bug Day that didn't receive interest lately? |
68 |
> |
69 |
> At the last Bug Days, I did not see much users join us; which makes |
70 |
> me wonder if that concept (still) works. Since this project does a |
71 |
> very similar thing, I am wondering if we can perhaps make the Bug |
72 |
> Day concept obsolete and form a more permanent effort than a monthly |
73 |
> meeting; in order to allow for more effort on every single day. |
74 |
> |
75 |
> -- The rest of the mail shows results of cleaning, feel free to skip. -- |
76 |
> |
77 |
> I've walked through a few old bugs in the past as part of the Bug Day |
78 |
> efforts as well as some moments outside of that, I've closed and pinged |
79 |
> some bugs without any negative feedback on them which appeared to be a |
80 |
> good thing; under the form of a project, I like to invite more people |
81 |
> to join forces as well as do this in a more organized way to avoid |
82 |
> future conflicts and get more work done. |
83 |
> |
84 |
> One tracker that resulted out of the above effort is: |
85 |
> |
86 |
> https://bugs.gentoo.org/show_bug.cgi?id=472746 |
87 |
> |
88 |
> Which covers old interesting conceptual, abstract and unimplemented |
89 |
> ideas and feature requests; it gathers a lot of ideas together, let me |
90 |
> list some examples: |
91 |
> |
92 |
> * Offload work by distributing trivial ebuild maintenance to users, |
93 |
> introduce a simple stability voting system and have a core team |
94 |
> approve them to the Portage tree. |
95 |
> |
96 |
> * (portage / gentoolkit) Show dependencies in detail; clarifying |
97 |
> whether they are DEPEND, RDEPEND or PDEPEND and optional. |
98 |
> |
99 |
> * Implement a reverse dependency tracker using LDD information and |
100 |
> compare it against the run-time dependencies listed in the ebuild. |
101 |
> |
102 |
> * Checkpointing and restoring packages states, e.g. `emerge undo`. |
103 |
> |
104 |
> * Please add GraphViz output to equery depgraph. |
105 |
> |
106 |
> * Automatic testing infrastructure (send build erros to Gentoo Infra) |
107 |
> |
108 |
> I think that if we identify more of such bugs we get together a very |
109 |
> useful list for people that want to contribute to Portage to look into |
110 |
> for ideas; perhaps also useful for GSoC, to be inspiring for students. |
111 |
> |
112 |
> Feel free to raise any other questions, comments or remarks. |
113 |
> |
114 |
> Thank you very much in advance. |
115 |
> |