Welcome to the official blog of the community/outreach team for the WordPress open sourceOpen SourceOpen Source denotes software for which the original source code is made freely available and may be redistributed and modified. Open Source **must be** delivered via a licensing model, see GPL. project!
This team oversees official events, mentorship programs, diversity initiatives, contributor outreach, and other ways of growing our community.
If you love WordPress and want to help us do these things, join in!
Getting Involved
We use this blog for policy debates, project announcements, and status reports. Everyone is welcome and encouraged to comment on posts and join the discussion.
You can learn about our current activities on the Team Projects page. These projects are suitable for everyone from newcomers to WordPress community elders.
You can use our contact form to volunteer for one of our projects.
We also have regular Community Team meetings on the first and third Thursdays of every month at 12:00 UTC and 21:00 UTC in #community-team on Slack (same agenda).
Events WidgetWidgetA WordPress Widget is a small block that performs a specific function. You can add these widgets in sidebars also known as widget-ready areas on your web page. WordPress widgets were originally created to provide a simple and easy-to-use way of giving design and structure control of the WordPress theme to the user.
Slack notifications for WordCamp and Meetup application updates
In the WordPress project, multiple teams (#meta, #core, #polyglots, etc.) make use of SlackSlackSlack 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, tracTracTrac 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)
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:
Someone sends a new application for a WordCampWordCampWordCamps 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.
Someone sends a new application for a WordPress chapter meetupMeetupAll 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.
A new WordCamp is set to Scheduled status
A new WordPress meetup group is now active in the chapter
A WordCamp application is declined
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.orgThe 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 when a WordCamp application is scheduled)
(screenshot when a WordCamp application is declined)
A few more things to note and discuss here:
We can perhaps send these notifications to #community-events, #community-team, or both of these channels.
The props section will include usernames of everyone who added notes to the application listing and/or changed the listing’s status.
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!