On 19/07/17 19:22, Rich Freeman wrote: > On Wed, Jul 19, 2017 at 1:34 PM, Ian Stakenvicius 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?