Getting more Learn WordPress Discussion Group leaders and attendees

Learn WordPress is getting closer to its full launch and more workshops are being published, worked on and planned. One essential idea with workshops are discussion groups, that are a great way to share thoughts and ideas between others that have watched the recorded workshop.

Discussion groups can be held via Zoom or in #community-events SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. channel by original workshop presenter(s) or anyone who wants to be a discussion group leader. Virtually anyone interested in leading a discussion group on any of the workshops on the site is welcome to do so.

To make the most out of workshops and discussion groups, it would be great to have at least two discussion groups per each workshop. These discussion groups can happen anytime and even after the workshop has been published already months ago – it’s up to the discussion group leaders interest.

Currently, discussion groups are a bit hidden in the Learn WordPress platform. I’m proposing the following additions in order to raise awareness about discussion groups happening and more attendees and discussion group leaders:

1. Add “Upcoming discussion groups” section between “Recent workshops” and workshop idea submission CTA on the front page.

This new section would list three next upcoming discussion groups and link to the meetup.com page where all upcoming discussion groups are listed. This way also older workshops get some attention on the front page if new discussions groups for those are scheduled.

We already have code to get meetups from meetup.com, so it shouldn’t be a big job to get scheduled discussion groups from there as well. Of course, it needs some dev time, but I’m sure it will be worth it.

2. Add “Interested in running a discussion group?” CTA next to current “Have an Idea for a Workshop?“ CTA on the front page.

I’d like to have many discussion group leaders, so running those won’t fall into the responsibility of a workshop presenter(s) and a small group of an active group of Learn WP deputies. With this new CTA in place, we make it more visible that virtually anyone can run a discussion group if they find a workshop they’re really interested in and there’s no scheduled discussion group for that workshop.

Quick mockup showing how upcoming discussion groups and new CTA could be places on the front page.

3. Add details about discussion groups in workshop pages.

Currently, the page of a single workshop only has a button “Join a Discussion Group” which is a bit vague. We should add a small blurb on top of the button explaining what is a discussion group. Below the button could be a small text, much like the CoC notice, saying that if there’s no scheduled discussion group for this workshop, apply to be a discussion group leader to run one.

4. Create a new “Be a Discussion Group leader” page

As you might notice, two previous proposals contain a link to a page that doesn’t exist at this time on Learn WP platform. We should create a new page where it is explained what discussion group is, what it means to be a discussion group leader and how to apply. Currently, this information exists only in this make/community posts.

Tracking all the upcoming discussion groups and keeping an eye that each workshop has at least two groups

It would be nice to have at least two discussion groups for each workshop. These can happen anytime after the workshop has been published, even months later.

To keep track of upcoming discussion groups, we’ll use meetup.com where all scheduled discussion groups are being added.

In parallel to public listing on scheduled groups, I suggest that we create a new Google sheet with each workshop listed on it. In the sheet we can track if;

  • Zoom discussion group has been scheduled/held
  • Slack discussion group has been scheduled/held
  • Additional discussion groups have been scheduled/held

It would fall mostly under my lap, as I promised to manage discussion groups, but everyone who schedules a new discussion group in meetup.com should update this sheet.

With this sheet, we can track if a workshop hasn’t had any discussion groups and we can reach out to our discussion group leaders and workshop presenter(s) (not too) regularly asking whether they would like to schedule one. In future, the list of workshops needing a discussion group leader, could be added to the new “Be a Discussion Group leader” in Learn WP platform.

What do you think? Thoughts, ideas, comments, questions? How we could attract more discussion group leaders and attendees in your opinion? Please share your feedback before 2020-11-09.

#discussion, #discussion-groups, #learn, #learn-wordpress, #learn-roadmap

Proposal: Changes to application workflow for better communication

Our MeetupMeetup All local/regional gatherings that are officially a part of the WordPress world but are not WordCamps are organized through https://www.meetup.com/. A meetup is typically a chance for local WordPress users to get together and share new ideas and seek help from one another. Searching for ‘WordPress’ on meetup.com will help you find options in your area. and WordCampWordCamp 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. vetting queue might sometimes be a bit long. It causes a delay, sometimes almost a month, between sending the application and deputy vetting it. The long gap between submitting the application and receiving an update might be frustrating for some applicants. Some do also come to #community-events SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. channel and ask to confirm that their application is received.

Public application report page helps a little with this, but not all applicants know about it. Even if they do, it does not feel like personal contact with Community Team.

I propose the following change to our application workflow, to keep applicants informed and to add a bit more personal touch after sending the application:

  • Create a HelpScout ticket and in that ticket:
  • Send a short warm confirmation that the Community Team has received the application.
  • Keep ticket open and mark it with the tag “application-confirmation.”
  • The application tracker on central.wordcamp.org is updated with a link to the ticket for later communication.

This can be done pragmatically leveraging HelpScout APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways., so manual deputy work is not needed.

After this process has been set up, we could use HelpScout workflows to do different things. For example, send a short message if there hasn’t been any activity for two weeks after the application was received. This message could contain an apology that we have a bit of queue right now and promise that we will vet the application as soon as possible.

Possible advantages for deputies:

  • Deputies can view the queue from HelpScout and not require to visit the application tracker queue to figure out which one to conduct a vetting
  • Easier and trackable way to assign applications to deputies

What do you think, is this a good idea? Do you already imagine how the messaged are phrased? Tell it in the comments! Deadline for comments is 2019-10-04.

Thanks to @adityakane for brainstorming this proposal with me and commenting the draft.

Discussion: continuity of Community Office Hours

Office hours are usually quite quiet, people ask their questions when it’s convenient for them and deputies forgot to open or close those (regardless of the bot we have to remind us). There is almost always deputy to answer questions or if there isn’t, the question will be caught up later when some deputy sees it.

So, I’d like to question if community hours are really needed and propose their retirement. In exchange there are few things we could do to encourage people to ask questions freely.

During the last community team meetings, few good ideas were conducted from the discussion:

  • replace the office hours sidebarSidebar A sidebar in WordPress is referred to a widget-ready area used by WordPress themes to display information that is not a part of the main content. It is not always a vertical column on the side. It can be a horizontal rectangle below or above the content area, footer, header, or any where in the theme. and welcome box text with something more general about #community-events channel and encouraging to ask questions at all times
  • having a random empathy bot that reminds #community-team that we should post something encouraging to #community-events if the channel has been quiet for some time

Some concerns were also raised:

  • some people are waiting for the office hours before asking their questions
  • we don’t want to loose a human touch so having a bot in #community-events opening/closing office hours, sending random reminder messages or auto-replying is not an option
  • we need to be very clear that people can ask their questions any time, but know that they may not get an immediate answer

Please share your thoughts about retiring office hours or ideas on how to evolve those! Comments will close 10.4., please leave your comment before that.

#discussion, #office-hours

Recap of the community team efforts at WordCamp Europe Contributor day.

A brief recap of our efforts at #WCEU contributor dayContributor Day Contributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of https://make.wordpress.org/ There are many teams that people can participate in, each with a different focus. https://2017.us.wordcamp.org/contributor-day/ https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/.:

  1. The Diversity Outreach Speaker Training group wrote some documentation and worked on videos with the TV team
  2. We welcomed two new WordCampWordCamp 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 😉
  3. There was a meeting of the WordCamp Nordic group. If you want to get involved in WordCamp Nordic, please join us in the #community-events channel on WordPress.orgWordPress.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/ SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/.
  4. After a first round of online round tables for meetupMeetup All local/regional gatherings that are officially a part of the WordPress world but are not WordCamps are organized through https://www.meetup.com/. A meetup is typically a chance for local WordPress users to get together and share new ideas and seek help from one another. Searching for ‘WordPress’ on meetup.com will help you find options in your area. organisers, we started work on putting together a second round.
  5. The team spent time working on documentation that are incomplete or don’t already exist.
  6. We had initial conversations with potential new meetup groups
  7. Thanks to some new community team members, we started working on diagrams for our many processes

 

Proposal for permanent change of word for Code of Conduct

A couple of days ago, there was a discussion on SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. #community-events about how communities in India address anti-caste discrimination for Meetups and WordCamps. Currently the word “caste” is not part of or mentioned in the Code of Conduct.

Discrimination on caste basis has been a historical problem for societies across India and much of South Asia. For example, in India there is a law against discrimination, yet bias and exclusion happens regularly. More context and information can be found at the Wiki article Caste System in India and Affrimative action.

I propose we add the word “caste” in the code of conduct wording.

The change will be from:

WordCampWordCamp 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. CITYNAMEHERE believes our community should be truly open for everyone. As such, we are committed to providing a friendly, safe and welcoming environment for all, regardless of gender, sexual orientation, disability, ethnicity, religion, preferred operating system, programming language, or text editor

to

WordCamp CITYNAMEHERE believes our community should be truly open for everyone. As such, we are committed to providing a friendly, safe and welcoming environment for all, regardless of gender, sexual orientation, disability, ethnicity, religion, caste, preferred operating system, programming language, or text editor

This change will acknowledge that discrimination or exclusion on caste basis is not acceptable at meetups, WordCamps and other WordPress events. Apart from serving as a deterrent, it would empower participants of WordPress events to be able to address violations in a more formal way.

Thoughts and comments welcome.

#code-of-conduct

Payment Intermission September 11-18

The Automattic sponsored staff members of the Global Community Team, who routinely handle WPCS banking, will be at a company offsite September 11-18. During this time we’ll halt WordCampWordCamp 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. and MeetupMeetup All local/regional gatherings that are officially a part of the WordPress world but are not WordCamps are organized through https://www.meetup.com/. A meetup is typically a chance for local WordPress users to get together and share new ideas and seek help from one another. Searching for ‘WordPress’ on meetup.com will help you find options in your area. vendor payments, reimbursements, and sponsor payment attribution. If you’ll need to pay for goods or services in mid-September, please submit all requests no later than 9am Pacific Friday, September 8, 2017. Payment requests submitted after that time will not likely be processed until Tuesday, September 19, 2017. Sponsor invoices paid September 11-18 won’t be marked paid until September 19.

If you have an urgent payment request that must be handled that week, but did not submit your request prior to September 8, please reach out to @kcristiano. He can be found on slackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/.@kcristiano“.

Deputies, mentors, and community members will still be available by email at support@wordcamp.org or on Slack in the #community-events channel.

Normal vendor payment and sponsorship attributions scheduled will resume Tuesday, September 19, 2017 though it may take us a day or two to get fully caught up.

#payments #afk #wordcamps #meetups-2

Community Team Slack Channels

Hi all,

I want to propose that we rename #outreach to #community-team and follow CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. and MetaMeta 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 slackSlack 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?

Screenshot of the result when you type Community into the Slack channel search. It responds with 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.orgWordPress.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 WordCampWordCamp 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