Slack notifications for WordCamp and Meetup application updates


In the WordPress project, multiple teams (#meta, #core, #polyglots, etc.) make use of 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/. notifications to surface new, interesting changes in their team’s respective channel. This includes notifications on new commits, tracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. issue updates, new translation strings availability, etc.

(Screenshot of a commit notification)
(Screenshot of a commit notification)


These notifications serve at least two purposes:

1. People interested in following these teams have a very convenient way to look at recent and ongoing activities.

2. It provides a way to acknowledge contributors.

In the WordPress community channels, we don’t currently use this tool, but there may be some cases where having these notifications would add lot of value for us.

These include:

  1. Someone sends a new application for a 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.
  2. Someone sends a new application for a WordPress chapter 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.
  3. A new WordCamp is set to Scheduled status
  4. A new WordPress meetup group is now active in the chapter
  5. A WordCamp application is declined
  6. A Meetup application is declined

For reference, you can see status of some active WordCamp applications here.

These notifications could include whether the event is a WordPress or a Meetup, city and country of the event, description of the update, and 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/ usernames of people who were involved in vetting the event application.

I have written some initial code for this, and it could look like:

(screenshot for when a new WordCamp application is submitted)
(screenshot for when a new WordCamp application is submitted)


(screenshot for when WordCamp is scheduled)
(screenshot when a WordCamp application is scheduled)


(screenshot for when a WordCamp application is declined)
(screenshot when a WordCamp application is declined)


A few more things to note and discuss here:

  1. We can perhaps send these notifications to #community-events,  #community-team, or both of these channels.
  2. The props section will include usernames of everyone who added notes to the application listing and/or changed the listing’s status.
  3. We would also want to send notifications when an application is declined, and not just when it is received or scheduled, in order to credit the deputies who nevertheless did the  work to vet and respond to it. It could normalize the process of declining the application, because it is not uncommon for subsequent applications to be approved.

What do you think? Should we have these notifications? If we have them, then should they be more granular, or less granular? What changes in language or overall appearance would you suggest? Leave your thoughts in a comment on this post!

#community, #slack

Community team on Slack

Hello! Now that we’ve been using 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/. for nearly two months, I’m reviewing where we can improve. Some other teams have made specific feature requests, and I’m happy to hear those in the #slackhelp channel. (If there’s anything that can be done to make Slack better for you, I’m all ears.)

Now, for this team in particular, there have been a few requests as it pertains to channels. Like most teams, you joined Slack to find an already created #community channel waiting for you. It turns out, #community isn’t a great name, as many think it is either a watercooler of sorts or for general discussion topics. Others think it pertains to local communities (half right). The “community” team is really a super-team composed of a number of wide-ranging initiatives.

There are a lot of users in the channel, and a decent amount of noise, especially if you only care about only one particular initiative or project. There’s lot of cross-talk. Meetings can run into each other or need to be carefully scheduled around each other.

Slack suggests you create channels only as you realize you need them, and we adopted this model. Before 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. San Francisco was over, a #training channel was created. Here’s my current proposal, based on the projects page and a review of all requests I’ve received:

  • #events — Rename the #community channel to #events. WordCamps, meetups, and other events. Includes sponsorships talk. Can have subdivisions for WordCamps and/or meetups at a later point.
  • #outreach — This would cover a number of projects that are mostly dormant or nascent. As things ramp up, this could divide further into channels for academic outreach, #diversity, #mentorship / #gsoc, etc.
  • #training — The training team; this channel already exists.
  • #wptv — WordPress.tv video moderation.

Of course, there will be stuff that takes place that spans multiple teams. I don’t think it’ll be difficult how to make that work, though. As an example: as most stuff focuses on events, community-team-wide housekeeping and updates could be covered during regular #events meetings. I think this is a very good trade-off.

#meta, #slack

Reminder we’re using slack instead of irc for…

Reminder: we’re using slack instead of irc for team chats now, so if you want to attend today’s meeting in half an hour, get your slack username setup going now if you haven’t already. https://make.wordpress.org/chat/

#slack