public inbox for gentoo-project@lists.gentoo.org
 help / color / mirror / Atom feed
From: "M. J. Everitt" <m.j.everitt@iee.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] The problem of defunct and undermanned projects in Gentoo
Date: Wed, 19 Jul 2017 19:48:10 +0100	[thread overview]
Message-ID: <082eb115-d47e-01fa-2ed5-2616e74965e8@iee.org> (raw)
In-Reply-To: <CAGfcS_=GT_DHBZXBsTD5orEm_9RYicqpa333XRGzfwZPc-Hp+w@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1359 bytes --]

On 19/07/17 19:22, Rich Freeman wrote:
> On Wed, Jul 19, 2017 at 1:34 PM, Ian Stakenvicius <axs@gentoo.org> wrote:
>> OK, so here's the flipside of this.  I'm a member of a few projects
>> because I help take care of just a couple of things or maybe even just
>> a gentoo-carried patch.  Being a project member is necessary as I do
>> want to have the commit rights on the project, but I'm -not- nor ever
>> meant to be a general project member or overall maintainer or dev.
>>
> You left out another use case - wanting to follow mail on the project
> alias.  I could see cases where somebody isn't interest in a project
> in general but works on something related and benefits from seeing the
> emails to the alias.
>
I would argue that's a better use for a mailing list than an alias then
.. or at least some kind of 'observer' status in a project ..
I'm not sure from my observations that being on a team alias requires
you to be a project member ..

I'm really not sure what the benefits of a closed alias are, apart from
keeping communications internal, which may be equally well-served being
in the public domain .. unless of course it really is confined to "hi,
I'm tackling bug 12345 this week, thanks,bye" type communications ...
What barriers are there for transferring some key projects to having
their own mailing lists?


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2017-07-19 18:48 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-16 21:12 [gentoo-project] The problem of defunct and undermanned projects in Gentoo Michał Górny
2017-07-16 21:39 ` Daniel Campbell
2017-07-17 23:32 ` Matt Turner
2017-07-18 19:56 ` Kent Fredric
2017-07-18 21:12   ` M. J. Everitt
2017-07-18 21:23     ` Kent Fredric
2017-07-18 21:35       ` M. J. Everitt
2017-07-18 21:40         ` Michał Górny
2017-07-18 21:44           ` M. J. Everitt
2017-07-19 17:25           ` Alec Warner
2017-07-19 20:11             ` James Le Cuirot
2017-07-19 17:34           ` Ian Stakenvicius
2017-07-19 18:22             ` Rich Freeman
2017-07-19 18:48               ` M. J. Everitt [this message]
2017-07-19 18:53               ` Mart Raudsepp
2017-07-20  2:15             ` Aaron Bauman

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=082eb115-d47e-01fa-2ed5-2616e74965e8@iee.org \
    --to=m.j.everitt@iee.org \
    --cc=gentoo-project@lists.gentoo.org \
    /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