| 1 |
On Thu, Sep 25, 2014 at 11:00:32AM -0400, Rich Freeman wrote: |
| 2 |
> On Wed, Sep 24, 2014 at 12:31 PM, W. Trevor King wrote: |
| 3 |
> > On Wed, Sep 10, 2014 at 04:18:40PM +0200, Michał Górny wrote: |
| 4 |
> >> |
| 5 |
> >> 4. A mail alias that is not project :). For example, we have |
| 6 |
> >> clang@ for easily aggregating all clang-related build failures |
| 7 |
> >> and other bugs but it isn't a formal team. |
| 8 |
> > |
| 9 |
> > As an incremental solution, what about a <watcher> tag in |
| 10 |
> > metadata.xml with the same format as <maintainer> except that |
| 11 |
> > being a watcher doesn't imply a willingness to *do* anything about |
| 12 |
> > a project, it just means you want to be notified of changes and |
| 13 |
> > added to the CC list. |
| 14 |
> |
| 15 |
> I'd given some thought to this as well, but didn't think it was a |
| 16 |
> good idea. |
| 17 |
> |
| 18 |
> First, you can already create queries in bugzilla. |
| 19 |
|
| 20 |
Not all package activity has an associated bugzilla entry, but maybe |
| 21 |
enough of it does? |
| 22 |
|
| 23 |
> Or, would it make more sense to find a way for anybody to follow |
| 24 |
> issues in packages, assuming bugzilla queries aren't enough? |
| 25 |
|
| 26 |
What about a <list> entry in metadata.xml that points people to the |
| 27 |
suggested mailing list for discussing a package? Bugzilla could |
| 28 |
automatically add the list to its CC list, and both devs and non-devs |
| 29 |
could join the list without adding a lot of email addresses to the |
| 30 |
tree. |
| 31 |
|
| 32 |
Cheers, |
| 33 |
Trevor |
| 34 |
|
| 35 |
-- |
| 36 |
This email may be signed or encrypted with GnuPG (http://www.gnupg.org). |
| 37 |
For more information, see http://en.wikipedia.org/wiki/Pretty_Good_Privacy |
Archives