1 |
On Wed, Sep 24, 2014 at 12:31 PM, W. Trevor King <wking@×××××××.us> wrote: |
2 |
> On Wed, Sep 10, 2014 at 04:18:40PM +0200, Michał Górny wrote: |
3 |
>> |
4 |
>> 4. A mail alias that is not project :). For example, we have clang@ for |
5 |
>> easily aggregating all clang-related build failures and other bugs but |
6 |
>> it isn't a formal team. |
7 |
> |
8 |
> As an incremental solution, what about a <watcher> tag in metadata.xml |
9 |
> with the same format as <maintainer> except that being a watcher |
10 |
> doesn't imply a willingness to *do* anything about a project, it just |
11 |
> means you want to be notified of changes and added to the CC list. |
12 |
|
13 |
I'd given some thought to this as well, but didn't think it was a good idea. |
14 |
|
15 |
First, you can already create queries in bugzilla. |
16 |
|
17 |
Second, if we wanted something more robust than being interested in a |
18 |
package isn't something that is limited to devs. If you're just going |
19 |
to look at bugs but not do anything about them, then you are really |
20 |
just a user who might happen to also have commit access. Do we really |
21 |
need to have a developer-only way of getting bug CC's for people who |
22 |
don't actually want to fix the bugs? Or, would it make more sense to |
23 |
find a way for anybody to follow issues in packages, assuming bugzilla |
24 |
queries aren't enough? |
25 |
|
26 |
Now, if something like clang@ isn't a formal team but does consist of |
27 |
people who are actually doing something, why not just make it a |
28 |
project? After all, a group of people interested in actually doing |
29 |
something basically is the definition of a project. Being a project |
30 |
isn't some kind of huge commitment. and I think it makes sense to just |
31 |
have devs and groups of devs instead of having 12 different kinds of |
32 |
groups of devs and we can't keep straight which kinds of groups do (or |
33 |
more typically don't do) what. |
34 |
|
35 |
-- |
36 |
Rich |