This is the home of the Make Community 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!
Here is where we have policy debates, project announcements, and assist community members in organizing events.
Everyone is welcome to comment on posts and participate in the discussions regardless of skill level or experience.
Get Involved
If you love WordPress and want to help us do these things, join in!
There is a complete list at make.wordpress.org, but below is a list, along with sub-groups and links to how to get started with that team at a contributor dayContributor DayContributor 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/.. For each team you are planning on supporting at your contributor day, you will want to have someone familiar with contributing to that group and familiar with the contributor day page (a group lead).
Different groups will do different things, but your group lead should be prepared for both experienced contributors and new contributors.
[in progress]
Core – There are generally two different groups at a contributor day: those who have contributed to coreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. before and those who have not. It is usually best to split the core group into two, letting previous contributors work on new contributions and teaching new contributors how to contribute. You will probably want two leads here, but it will depend on attendance at your 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.. For new contributors, you need to go through a number of things, most of which are listed in the sidebarSidebarA 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. of the core contributor handbook. Be sure to cover how to use tracTracTrac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/., what makes a good ticket, how to setup a local development environment (if needed), and general best practices (coding standards).
Support – Most contributions here will be to the support forums. You should go through what the support team does and focus on answering questions in the support forums. Be sure to give information on stock answers and help users setup a 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/ account.
Docs – At contributor days, docs contributions are generally editing and improving the theme and pluginPluginA plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party developer handbooks. However, some people may want to improve the codex or contribute examples to the developer hub. Talk to a docs contributor ahead of time to make sure someone is around to give out Editor status on make/docs.
Themes Team – A full walkthrough on how to review themes is important. Likewise, be sure to contact a TRT admin so they can be around during your contributor day and can assign tickets to new contributors.
Mobile – The mobile handbook is generally up-to-date. For contributors to either the iOSiOSThe operating system used on iPhones and iPads. or Android apps, they should have a knowledge of development on their respective platform. Following the handbook at that point should not be hard.
Polyglots – Contributing string translations to a current localization of WordPress is a great way to get started. The document linked to walks through how that should be done. If you are hosting a WordCamp in a language that does not have a full translation of WordPress (or related projects), it can be good to set one up ahead of time with the polyglots teamPolyglots TeamPolyglots Team is a group of multilingual translators who work on translating plugins, themes, documentation, and front-facing marketing copy. https://make.wordpress.org/polyglots/teams/. and kick off your translation work there. The first step there will be requesting a new locale.
Meta – The metaMetaMeta 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. team is programming-based, for the most part. The WordPress Meta Environment (based on VVV) is the best way to get setup and contribute to the open sourced projects that the meta team manages, including wordcamp.org, global.wordpress.org (rosetta), jobs.wordpress.net, developer.wordpress.org, and apps.wordpress.org.
Accessibility – Generally, we group the accessibilityAccessibilityAccessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) team with core so they can contribute their testing or programming expertise to core tickets with the “accessibility” focus.