1 |
Hi |
2 |
|
3 |
On 2019/08/03 01:19, Jonas Stein wrote: |
4 |
> On 02/08/2019 22.55, Michał Górny wrote: |
5 |
>> Add two new maintainer types: 'proxied' for proxied maintainers, |
6 |
>> and 'watcher' for people who wish to be CC-ed on bugs but are not |
7 |
>> maintainers (e.g. upstream developers). |
8 |
> Can't we solve this simply in the bug tracker? The monitor setting of a |
9 |
> user does not belong into the tree. |
10 |
> |
11 |
> |
12 |
> The upstream maintainer and all other "watchers" have no write access to |
13 |
> the tree so they will consume manpower in adding and removing their |
14 |
> contacts to packages. |
15 |
> |
16 |
> The perfect solution would be that any user can add a watch filter to |
17 |
> my-cat/mypkg in the bugtracker. |
18 |
> |
19 |
> Between 2018-01-01 and 2018-12-31 we received and assigned 31280 bugs. |
20 |
> I am no fan of the descriptions in the form "please CC: If the bug is |
21 |
> about x but not y and the moon is in the third house of the lion" |
22 |
> |
23 |
> This consumes extra time for every assignment and prevents automagic |
24 |
> assignment in future. We should rather keep it simple instead of |
25 |
> extending the options. |
26 |
|
27 |
I agree. I was just thinking "I'd like to watch certain packages, be |
28 |
aware of commits et al, but not get involved in ongoing stuff" too. |
29 |
|
30 |
The rule should be simple: CC me on any bugs to this list of packages. |
31 |
|
32 |
I can then unsub myself from individual bugs I don't care about. |
33 |
|
34 |
Then there are packages that have changed in the past unexpectedly and |
35 |
bit me (badly sometimes), so on those I'd like to know about any commit |
36 |
going in. Guess I can set up a git pull + filter myself there, but if |
37 |
this is done upstream then it can work for everyone, and not waste |
38 |
duplication effort. |
39 |
|
40 |
Kind Regards, |
41 |
Jaco |