Skip to content

Instantly share code, notes, and snippets.

@brandondove
Last active August 29, 2015 14:22
Show Gist options
  • Save brandondove/5bdf312aa4b8f1e41de8 to your computer and use it in GitHub Desktop.
Save brandondove/5bdf312aa4b8f1e41de8 to your computer and use it in GitHub Desktop.
Bullet Points for Contributor Corner

Contributing to the WordPress Project

What's in it for you?

Top reasons to get involved from a recent talk by former core contributor, John O'Nolan.

  • Learning: Get taught how to code using best practices by core contributors for FREE.
  • Recognition: Your name will be associated with WordPress, the most popular content management system on the planet. Whether you're trying to get a new job, land bigger projects, or find clients willing to pay you more money, being able to say that your work is used by millions of people to manage content on 23% of the web is kind of awesome.
  • Competitive Advantage: Get to know what's going in to core before anyone else.

How much should you contribute?

The short answer is that you should contribute whatever works for you. If you only have 1 hour a week to contribute, that's fine. If you have more, great! The key is to try to be consistent with your contributions so that other contributors know when they can count on you. The WordPress project can always use your help.

Where to Start

WordPress.org

Head to https://wordpress.org/support/register.php and register yourself a ".org username". This is your key to the castle. Your .org profile is the canonical resource for the history of your involvement with the WordPress project. You can view your profile (or the profile of anyone else at http://profiles.wordpress.org/)

Slack

At last year's WordCamp in San Francisco, Matt Mullenweg announced the move from Internet Relay Chat (IRC) to Slack. In the simplest terms, Slack is an interface to an IRC like method of communication that is more approachable than IRC. Every contribution group has a channel where they can discuss matters relevant to their group. As an example, the community group discusses things like Meetups, WordCamps, and general community relaations.

Make/WordPress

Once you've gotten your accounts in order, it's time to dive in and pick a group that you're interested in. You can join as many groups as you want, and participate as much or as little as you want. In addition to slack channels, each group has a corresponding site where the publicly publish recaps of meetings, topics for discussion, and other useful information. http://make.wordpress.org is the jumping off point for each of these sites, and are often referred to as things like "Make/WordPress" or "Make/Community".

Team Meetings

Each team holds regular meetings where contributors to that specific group can come together and "talk" in real-time. In my opinion, this is the best place to start. Get on slack at the time that your team is meeting and just sit and watch. You're watching for a few things:

  • Who are the team leaders?
  • What are the team dynamics?
  • How do you volunteer for things that interest you?

Lurking during team meetings will help you learn the etiquette for joining the global conversation. Remember, every group is made up of people from all walks of life, so be respectful of everyone else. The easiest way to get on the naughty list is to not show respect for other volunteers.

Helpful Tips

Core (Mike Hansen)

Definition: The core team makes WordPress. Whether you’re a seasoned PHP developer or are just learning to code, we’d love to have you on board. You can write code, fix bugs, debate decisions, and help with development.

Core contribution is often perceived as limited only to developers. This just isn't the case. Developers wouldn't have anything to build if no one ever reported bugs and feature requests. Additionally, no feature gets into WordPress without a fair amount of discussion and testing. Contributing your thoughts and ideas about new features is a very valid way to contribute to WordPress Core. Your experience with WordPress, short or long, is an invaluable asset to the WordPress project. The WordPress Core team meets weekly on Slack to discuss features and development that are in-progress for the next version of WordPress.

Team Meetings

  • Weekly chats: Wednesdays @ 20:00 UTC
  • #core on Slack

Next WordPress Version

  • 4.3 Release Lead: Konstantin Obenland
  • 4.3 Targeted Release Date: August 18, 2015

Getting on Trac

Related Groups/Subprojects

  • Passwords
  • Customize Component
  • Multisite
  • Editor
  • Admin UI
  • Dashicons
  • Design

Design (Robert Nienhuis)

Definition: The design group is focused on the designing and developing the user interface. It’s a home for designers and UXers alike. There are regular discussions about mockups, design, and user testing.

People don't say that WordPress is easy to use just because is sounds like a good thing to say. It takes thoughtful design and usability to carry out consistent interfaces throughout the editing experience. Do we make mistakes? Sure we do. Is WordPress the super easiest thing to use for everyone? No. The WordPress design team will always be tweaking and evolving the UI to make it even easier for users to get their work done. In the end, the best interface is one that doesn't get in your way, or feels natural to use.

Team Meetings

  • Weekly chats: Thursdays @ 17:00 UTC
  • #design on Slack

Related Groups/Subprojects

  • Image Flow - Team Meeting: Thursday at 20:00 UTC in #design-imageflow on Slack. Foundation framework and AngularJS knowledge required. There is a current prototype of workflows for working with images in WordPress. The goal of this group is to test the flows to make sure usability is strong. If you have a good eye for usability, this is a great group to get involved in.
  • Core CSS Roadmap - The core ideas are to document, establish a pattern library, integrate build tooling (grunt, sass, etc), pair down unused css, and establish naming conventions. At this point this is mostly discussion, so it's a great place to start if you have strong opinions about css conventions.
  • Admin UI - Team Meeting: Thursday, June 11, 2015 17:00 UTC in #design on Slack
  • Dashicons - Team Meeting: Thursday at 18:30 UTC in #design-dashicons on Slack. The goal is to switch Dashicons to a collection of SVGs, rather than a font. If you have an opinion on using SVGs in a cross-browser way, this would be a great group to contribute to.
  • Flow - The flow team tests the flow of WordPress across device available. We test, document, and report on the WordPress user experience. Through continuous dogfooding and visual records, we aim to understand not only what is wrong, but also what is right. We immerse ourselves in the context of what we are making and champion user experience. If you are interested in UI/UX and an impartial mindest, this would be a great project to get involved with.

Seemingly Related but Unrelated Groups

  • WordPress.org Themes - Theme Review Team
  • WordPress Default Themes - Core Team (probably starting 2016 theme over the summer)

Flow (Robert Nienhuis)

Definition: The Flow team patrols flow across the entire WordPress ecosystem on every device we have at hand. We test, document, and report on the WordPress user experience. Through continuous dogfooding and visual records, we understand not only what is wrong, but also what is right. We immerse ourselves in the context of what we are making and champion user experience.

Team Meetings

  • Weekly chats: Thursdays @ 14:30 UTC
  • #core-flow on Slack

Themes (Robert Nienhuis)

Definition: The Theme Review Team reviews and approves every Theme submitted to the WordPress Theme repository. Reviewing Themes sharpens your own Theme development skills. You can help out and join the discussion on the blog.

Team Meetings

  • Weekly chats: Tuesdays & Thursdays @ 18:00 UTC
  • #themereview on Slack

Support (John Hawkins)

Definition: Answering a question in the support forums or IRC is one of the easiest ways to start contributing. Everyone knows the answer to something! This blog is the place for discussion of issues around support.

Team Meetings

  • Weekly chats: Thursdays @ 16:00 UTC
  • #forums on Slack

How to get started

Documentation (John Hawkins)

Definition: Good documentation lets people help themselves when they get stuck. The docs team is responsible for creating documentation and is always on the look-out for writers. The blog has discussion around the team’s current projects.

Team Meetings

  • Weekly chats: Thursdays @ 18:00 UTC
  • #docs on Slack

Related Groups/Subprojects

  • Core - Inline docs
  • Team Handbooks

Community (Aaron Hockley)

Definition: If you’re interested in organizing a meetup or a WordCamp, the community blog is a great place to get started. There are groups working to support events, to create outreach and training programs, and generally support the community.

Team Meetings

  • Weekly chats: Thursdays @ 20:00 UTC
  • #outreach on Slack

Related Groups/Subprojects

  • WordPress.tv
  • Training
  • WordCamps
  • Meetups
  • Community Hub

Training (Aaron Hockley)

Definition: The training team creates downloadable lesson plans and related materials for instructors to use in a live workshop environment. If you enjoy teaching people how to use and build stuff for WordPress, immediately stop what you’re doing and join our team!

Team Meetings

  • Weekly chats: Tuesdays @ 17:00 UTC
  • #training on Slack

Related Groups/Subprojects

  • WordPress.tv
  • Community

Polyglots (Jeffrey Zinn)

Definition: WordPress is used all over the world and in many different languages. If you’re a polyglot, help out by translating WordPress into your own language. You can also assist with creating the tools that make translations easier.

In 2014, non-english downloads of WordPress exceeded English based downloads for the first time ever. The global user share for WordPress is growing every day. There are currently 147 different locales of which, 51 are up to date.

Team Meetings

  • Weekly chats: Wednesdays at 10:00 UTC
  • #polyglots on Slack

Related Groups/Subprojects

Utilities

  • Poedit - Mac Based Gettext Translations Editor

Meta (Brandon Dove)

Definition: The Meta team makes WordPress.org, provides support, and builds tools for use by all the contributor groups. If you want to help make WordPress.org better, sign up for updates from the Meta blog.

Team Meetings

  • Weekly chats: Fridays @ 17:00 UTC
  • #meta on Slack

Related Groups/Subprojects

  • *.WordPress.org
  • *.WordCamp.org
  • SupportFlow
  • SupportPress
  • Mobile

Mobile (Brandon Dove)

Definition: The mobile team builds the iOS, Android, Windows, and Blackberry apps. Lend them your Java, Objective-C, or C# skills. The team also needs designers, UX experts, and testers to give users an smooth experience on every device.

Due to the prevalance of mobile devices in the world today, the need for a new interface to WordPress arose. The mobile team deals with building apps for a variety of mobile platforms.

Team Meetings

  • Weekly chats: Mondays @ 16:00 UTC
  • #mobile on Slack

Related Groups/Subprojects

  • iOS
  • Android
  • Meta

Accessibility (Brandon Dove)

Definition: The a11y group provides accessibility expertise across the project. They make sure that WordPress core and all of WordPress’ resources are accessible.

Team Meetings

  • Weekly chats: Mondays @ 18:00 UTC
  • #accessibility on Slack
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment