public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Rich Freeman <rich0@gentoo.org>
To: "W. Trevor King" <wking@tremily.us>
Cc: gentoo-dev <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-dev] RFC: Deprecating and killing the concept of herds
Date: Thu, 25 Sep 2014 11:00:32 -0400	[thread overview]
Message-ID: <CAGfcS_myk73g0T-PBxXRJppZ7MEqzUrskXEUTSRjX6DNLixOZA@mail.gmail.com> (raw)
In-Reply-To: <20140924163113.GA20130@odin.tremily.us>

On Wed, Sep 24, 2014 at 12:31 PM, W. Trevor King <wking@tremily.us> wrote:
> On Wed, Sep 10, 2014 at 04:18:40PM +0200, Michał Górny wrote:
>>
>> 4. A mail alias that is not project :). For example, we have clang@ for
>> easily aggregating all clang-related build failures and other bugs but
>> it isn't a formal team.
>
> As an incremental solution, what about a <watcher> tag in metadata.xml
> with the same format as <maintainer> except that being a watcher
> doesn't imply a willingness to *do* anything about a project, it just
> means you want to be notified of changes and added to the CC list.

I'd given some thought to this as well, but didn't think it was a good idea.

First, you can already create queries in bugzilla.

Second, if we wanted something more robust than being interested in a
package isn't something that is limited to devs.  If you're just going
to look at bugs but not do anything about them, then you are really
just a user who might happen to also have commit access.  Do we really
need to have a developer-only way of getting bug CC's for people who
don't actually want to fix the bugs?  Or, would it make more sense to
find a way for anybody to follow issues in packages, assuming bugzilla
queries aren't enough?

Now, if something like clang@ isn't a formal team but does consist of
people who are actually doing something, why not just make it a
project?  After all, a group of people interested in actually doing
something basically is the definition of a project.  Being a project
isn't some kind of huge commitment. and I think it makes sense to just
have devs and groups of devs instead of having 12 different kinds of
groups of devs and we can't keep straight which kinds of groups do (or
more typically don't do) what.

--
Rich


  reply	other threads:[~2014-09-25 15:01 UTC|newest]

Thread overview: 64+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-09 19:45 [gentoo-dev] RFC: Deprecating and killing the concept of herds Michał Górny
2014-09-09 19:56 ` Rich Freeman
2014-09-09 20:46   ` Anthony G. Basile
2014-09-09 22:23     ` Michał Górny
2014-09-09 22:54       ` Kent Fredric
2014-09-10 11:37         ` Rich Freeman
2014-09-10 11:33 ` Pacho Ramos
2014-09-10 11:53   ` Rich Freeman
2014-09-10 14:18     ` Michał Górny
2014-09-10 16:28       ` Rich Freeman
2014-09-24 16:31       ` W. Trevor King
2014-09-25 15:00         ` Rich Freeman [this message]
2014-09-25 15:29           ` W. Trevor King
2014-09-25 15:49             ` Rich Freeman
2014-09-25 16:10               ` W. Trevor King
2014-09-10 16:03     ` [gentoo-dev] " Steven J. Long
2014-09-10 14:01 ` [gentoo-dev] " Tom Wijsman
2014-09-10 20:21   ` Markos Chandras
2014-09-11  2:07     ` [gentoo-dev] " Duncan
2014-09-11 18:30     ` [gentoo-dev] " Tom Wijsman
2014-09-11 20:00       ` Markos Chandras
2014-09-15  9:05         ` Tom Wijsman
2014-09-27  8:58 ` Jeroen Roovers
2014-09-27 10:25   ` Rich Freeman
2014-09-27 10:51     ` Jeroen Roovers
2014-09-27 13:11       ` Rich Freeman
2014-09-27 18:40         ` Jeroen Roovers
2014-09-27 21:41         ` Tom Wijsman
2014-09-27 21:47           ` Andreas K. Huettel
2014-09-27 18:21       ` [gentoo-dev] " Michael Palimaka
2014-09-27 21:35     ` [gentoo-dev] " Tom Wijsman
2014-09-27 21:54       ` Anthony G. Basile
2014-09-27 22:13         ` Tom Wijsman
2014-09-27 22:21           ` Michał Górny
2014-09-28 16:55             ` Tom Wijsman
2014-09-27 22:45           ` Rich Freeman
2014-09-28 17:30             ` Tom Wijsman
2014-09-27 23:01           ` Ulrich Mueller
2014-11-04 13:55   ` Rich Freeman
2014-09-29 16:42 ` [gentoo-dev] RFC: Deprecating and killing herds in metadata.xml Jeroen Roovers
2014-09-29 17:20   ` Ulrich Mueller
2014-09-29 17:27     ` Michał Górny
2014-09-29 18:13       ` Ulrich Mueller
2014-09-29 18:21         ` Michał Górny
2014-09-29 21:16   ` Tom Wijsman
2014-09-29 22:40     ` Jeroen Roovers
2014-09-29 23:09       ` Ulrich Mueller
2014-09-30  1:42         ` Rich Freeman
2014-09-30  7:00           ` Ulrich Mueller
2014-09-30 13:12             ` Rich Freeman
2014-10-01 18:39               ` Tom Wijsman
2014-09-30  8:51         ` Jeroen Roovers
2014-09-30 11:01           ` Ulrich Mueller
2014-09-30 21:03             ` Jeroen Roovers
2014-10-01 18:43               ` Tom Wijsman
2014-10-03  2:51               ` [gentoo-dev] " Steven J. Long
2014-10-03  2:55                 ` Peter Stuge
2014-10-04  7:18                 ` Jeroen Roovers
2014-10-05 16:30                   ` Tom Wijsman
2014-10-05 20:53                     ` Jeroen Roovers
2014-10-07 22:07                       ` Tom Wijsman
2014-10-08  7:22                         ` Jeroen Roovers
2014-10-09 19:29                           ` Tom Wijsman
2014-10-01 18:27       ` [gentoo-dev] " Tom Wijsman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAGfcS_myk73g0T-PBxXRJppZ7MEqzUrskXEUTSRjX6DNLixOZA@mail.gmail.com \
    --to=rich0@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=wking@tremily.us \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox