Historically the SCs have been posting their update summaries in this Committers forum. So that is what I repeated while sharing our backlog of posts earlier today. They are publicly readable here, but only Committers can comment.
Now that we’ve hired a Communications Liason, it’d likely be easier and timelier to have Velda post these directly over in Core Development (as she is not a core dev so cannot post here in Committers).
Put future Steering Council Updates posts in Core Development
Keep Steering Council Updates posts here in Committers
0voters
If you feel strongly one way or another, consider sharing why below.
I believe the “Core Development” category allows anyone here on Discuss to post and comment. I’m personally happy with that. I’m asking mostly because I don’t want us to surprise anyone as I assume some people might subscribe to Committers in a more verbose mode than they do to Core Development.
It’s akin to the old mailing list split, where anything posted in Committers we really should be reading, while reading Core Development threads is more “if you’re so inclined and have the time”.
So keeping both categories makes sense, but moving the SC updates still seems reasonable.
I think the SC news are relevant to all contributors so the “Core Development” makes sense to me.
Are we sure we need both?
Perhaps this needs a different discussion thread.
where anything posted in Committers we really should be reading, while reading Core Development threads is more “if you’re so inclined and have the time”.
If that’s the case, can we @-mention the “Committers” group when posting, to get the core team’s attention? I believe this is supported on Discourse platform.
To me posting on “Committers” category/mailing list has the extra effect of non-committers are not allowed to engage/reply, which is a different meaning from “here are the things we really want the committers to read”.