Hi all,
I want to propose that we rename #outreach to #community-team and follow Core Core is the set of software required to run WordPress. The Core Development Team builds WordPress. and Meta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. in their sub team channel naming convention which for the Community team would be #community-usage.
For example, the events room would be renamed to #community-events. The way slack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. works means that any channel name changes will not effect or kick anyone out of any room they are currently a part of, just that they will see the name has changed.
Part of the reason why is because many people who are looking for the community team do not look or realise we are in #outreach. This includes a core committer who i would label as an advance Slack user. In fact, when I told them the community team uses #outreach for our community channel their response was
Oh, that’s what that channel is
Weird
I’d expect #community and #community-usage
#events I can see potentially being different
But #outreach I always thought was like for engagement with the wider community
Kinda like #marketing
They also pointed out that when searching for a channel, people automatically search for community and get a response of No match found. Did you spell it correctly?
I have also noticed that the #outreach gets messages regarding people doing outreach for their products. Although not often, the mistake is understandable considering what the channel is called. Back when WordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ took to Slack, we were called #community – but many people thought it was a water-cooler location for anyone to have a natter. This was the reasoning behind the switch to #outreach. Instead, I would like to propose we call it #community-team which makes it clear that the channel is for the Community team.
The other reason why I would like to propose these changes is because I’ve been trying to get into updating the handbook, but it’s a really boring process to do on your own and talking about it in #events or #outreach, the conversation gets lost in all the other conversations that are happening in there.
I think that the Core team and the Meta team’s use of #team-thing has meant that conversations are kept focused on the channel topic. It allows for people to only follow conversations that they are interested in and helps with the timezone issue where we have people across the world wanting to follow one particular topic.
At a minimum i can in vision the following channels
It could be extended to – if people feel like it could be helpful to WordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. mentors #community-mentors – a support location for people mentoring WordCamps in a similar vein to the forum support for the moderators.
And later maybe #community-deputies – a support location for people who are doing deputy work in a similar vein to #community-mentors. It would also give a clearer view of what it is that deputies do for anyone wanting to join the deputy program as they can see the things deputies discuss and talk about.
All these channels will still be accessible to everyone so there is no issue with transparency.
I would love to hear your thoughts about this.
Jenny
#deputies
