Friday, April 3, 2020

Re: A Community Change process to mirror the System Change process

On Fri, Apr 3, 2020 at 3:12 PM Justin W. Flory <> wrote:
> Or, perhaps announce@? :)
That's a possibility, too. It's a change from how we've historically
used the announce mailing list, but that doesn't mean we're locked
into it forever.

> I do think community topics are tied directly or indirectly to
> development topics. Thinking of community topics as separate from the
> development folks creates different groups for software and non-software
> contributors. Which isn't a completely wrong assumption, but also not
> completely true either. The community is for everyone.

> For a mailing list that gets used a handful of times a year, this is a
> frequent reason not to use that list over the last 5-6 years I've been
> around. :) I wonder, what is the worst that could *really* happen?
You're right that we intentionally keep announce very low traffic. Too
low? Maybe. There may come a point when people unsubscribe, at which
point we lose the value of using the list. But I honestly have no idea
what the traffic rate that would drive off a non-trivial number of
people. We've traditionally been very conservative in this regard, and
I'm willing to believe that we're far too conservative. But I don't
want us to take the brakes off entirely. I think we should come up
with some intentional guidelines, if for no other reason than to
indicate to the community that "yes, your message qualifies".

Ben Cotton
He / Him / His
Senior Program Manager, Fedora & CentOS Stream
Red Hat
council-discuss mailing list --
To unsubscribe send an email to
Fedora Code of Conduct:
List Guidelines:
List Archives:

No comments:

Post a Comment