On 4/3/20 12:56 PM, Matthew Miller wrote:
I'm just thinking out loud here but maybe we need a
community-announce list,
next to the devel announce list? Not all community topics are development
ones, and not all development topics are of general interest to the
community.
Or, perhaps announce@? :)
I think another mailing list is confusing. Also given there is no
community-focused equivalent for devel@. The closest is council-discuss@
which doesn't come near devel@ activity.
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.
On 4/3/20 1:49 PM, Ben Cotton wrote:
Agreed. We'll want to think about the scope because we want it to
be
broad enough that people will post to it, but not so busy that people
unsubscribe.
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?
--
Cheers,
Justin W. Flory (he/him)
justinwflory.com
TZ=America/New_York