Title: Getting Started at a Contributor Day Author: Samuel Sidler Published: May 7, 2014 Last modified: August 12, 2022 --- # Getting Started at a Contributor Day ## In this article * [Group Responsibilities](https://make.wordpress.org/meta/handbook/getting-started/contributor-day/?output_format=md#group-responsibilities) * [Common Tasks](https://make.wordpress.org/meta/handbook/getting-started/contributor-day/?output_format=md#common-tasks) * [Prior Knowledge](https://make.wordpress.org/meta/handbook/getting-started/contributor-day/?output_format=md#prior-knowledge) * [Tools](https://make.wordpress.org/meta/handbook/getting-started/contributor-day/?output_format=md#tools) * [Essential Reading](https://make.wordpress.org/meta/handbook/getting-started/contributor-day/?output_format=md#essential-reading) * [First Steps](https://make.wordpress.org/meta/handbook/getting-started/contributor-day/?output_format=md#first-steps) * [Tasks](https://make.wordpress.org/meta/handbook/getting-started/contributor-day/?output_format=md#tasks) [↑ Back to top](https://make.wordpress.org/meta/handbook/getting-started/contributor-day/?output_format=md#wp--skip-link--target) _This guide is intended to help you get started contributing to the 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. team at a 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/](https://make.wordpress.org/) There are many teams that people can participate in, each with a different focus. [https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/](https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/). Below is an outline of what the meta team does and how to quickly get started with various projects that the meta team works on. If you need any help, talk to your contributor day organizer, or ask your question in #meta on [Slack](https://chat.wordpress.org)._ This is a work in progress so don’t be afraid to amend the document or leave comments, particularly if you’re at a contributor day and find that we’ve missed something. Regular Meeting Time: None, but occasional ticket triage sessions in #meta on Fridays at 17:00 UTC. Chat Room: [#meta](https://make.wordpress.org/chat/) ## 󠀁[Group Responsibilities](https://make.wordpress.org/meta/handbook/getting-started/contributor-day/?output_format=md#group-responsibilities)󠁿 The only responsibility of the meta team is to maintain and create 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/](https://wordpress.org/) sites. Some of these sites include: * WordPress.org theme, pluginPlugin A 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/](https://wordpress.org/plugins/) or can be cost-based plugin from a third-party., and pattern directories * TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.[https://core.trac.wordpress.org/](https://core.trac.wordpress.org/).( coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress., meta, etc) * WordPress.org support forums * profiles.wordpress.org * developer.wordpress.org * translate.wordpress.org * jobs.wordpress.net * wordcamp.org * learn.wordpress.org * WordPress.tv * Codex A [full list of sites and and projects](https://make.wordpress.org/meta/handbook/projects/) is available, though not all sites are open sourceOpen Source Open 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. yet. ## 󠀁[Common Tasks](https://make.wordpress.org/meta/handbook/getting-started/contributor-day/?output_format=md#common-tasks)󠁿 As a member of the meta team, some common tasks that you’ll carry out are: * Coding and programming tasks (PHPPHP PHP (recursive acronym for PHP: Hypertext Preprocessor) is a widely-used open source general-purpose scripting language that is especially suited for web development and can be embedded into HTML. [https://www.php.net/manual/en/index.php](https://www.php.net/manual/en/index.php), JS, CSSCSS CSS is an acronym for cascading style sheets. This is what controls the design or look and feel of a site., etc) * Design work * AccessibilityAccessibility Accessibility (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) work * Testing sites to find issues to be fixed * Adding and updating content ## 󠀁[Prior Knowledge](https://make.wordpress.org/meta/handbook/getting-started/contributor-day/?output_format=md#prior-knowledge)󠁿 To get involved with the meta team, you’ll need some prior knowledge, depending on your area of expertise. * For development, coding expertise is needed, specifically with WordPress themes and plugins. * Designers, writers, testers are all needed with skills in their respective specialties. * Everyone who wants to be involved with the meta team should know where the [meta trac](https://meta.trac.wordpress.org) is and read the [Meta Development Blog](https://make.wordpress.org/meta/) for the latest information. ## 󠀁[Tools](https://make.wordpress.org/meta/handbook/getting-started/contributor-day/?output_format=md#tools)󠁿 Since contributor days have limited time, and sometimes have slow WiFi, it’s best to setup your development environment _before_ you attend. * A version control system: either [SVN](http://sourceforge.net/projects/win32svn/) or [Git](http://git-scm.com/), depending on the project. [The Contributing with Git guide](https://make.wordpress.org/meta/handbook/documentation/contributing-with-git/) has more details about using GitGit Git is a free and open source distributed version control system designed to handle everything from small to very large projects with speed and efficiency. Git is easy to learn and has a tiny footprint with lightning fast performance. Most modern plugin and theme development is being done with this version control system. [https://git-scm.com/](https://git-scm.com/). * A local development environment - Many newer projects have a development environment bundled with their Git repository, which is the easiest way for newer contributors to get started. For example, [learn.w.org](https://github.com/WordPress/learn), [w.org/patterns](https://github.com/WordPress/pattern-directory/), [make.w.org/five-for-the-future](https://github.com/WordPress/five-for-the-future), [w.org/support](https://github.com/WordPress/HelpHub), and [wordcamp.org](https://github.com/WordPress/wordcamp.org). * - You can also build your own environment using [MAMP](http://www.mamp.info/en/index.html), [WAMP](http://www.wampserver.com/en/), Vagrant (e.g., [VVV](https://github.com/Varying-Vagrant-Vagrants/VVV), [Primary Vagrant](https://github.com/ChrisWiegman/Primary-Vagrant), etc), or [XAMPP](http://www.apachefriends.org/index.html), and then copy a specific plugin or theme into it. - [WordPress Meta Environment](https://github.com/iandunn/wordpress-meta-environment) is deprecated, but may be useful for some projects that don’t have a newer environment yet. ## 󠀁[Essential Reading](https://make.wordpress.org/meta/handbook/getting-started/contributor-day/?output_format=md#essential-reading)󠁿 * Meta [trac](https://meta.trac.wordpress.org/) * [Meta Development Blog](https://make.wordpress.org/meta/) * If you’re writing code, the [WordPress Coding Standards](https://make.wordpress.org/core/handbook/coding-standards/) ## 󠀁[First Steps](https://make.wordpress.org/meta/handbook/getting-started/contributor-day/?output_format=md#first-steps)󠁿 The first step is to [select a project](https://make.wordpress.org/meta/handbook/projects/) that you’re interested in working on, whether it’s the plugin directory or the developer hub, and start finding issues with it or ways it can be improved. If you want to contribute code, all open source projects are listed in the prior link and can be contributed to through the [meta trac](https://meta.trac.wordpress.org/). ## 󠀁[Tasks](https://make.wordpress.org/meta/handbook/getting-started/contributor-day/?output_format=md#tasks)󠁿 Some easy tasks for a first time contributor to get started at a contributor day are: * View the currently [open tickets](https://meta.trac.wordpress.org/report/1) and work on those if you’re a programmer. If you want something relatively easy to get your feet wet, focus on [tickets tagged with good-first-bug](https://meta.trac.wordpress.org/report/10). * If you’re a designer, concentrate on [the open tickets that need UI/UX](https://meta.trac.wordpress.org/report/9). * Testers can pick a website they’re interested in and find ways it can be improved * Regardless of whether the code for the meta site you’re testing is open source, getting tickets on file will help identify what needs to be fixed or designed better, and how to prioritize which components we should focus on open-sourcing first. * If you find an issue with one of the WordPress meta sites you can [open a ticket](https://make.wordpress.org/core/handbook/working-with-trac/opening-a-ticket/) on [meta trac](https://meta.trac.wordpress.org/newticket). First published May 7, 2014 Last updated August 12, 2022 [ Previous: Contribute with Docs](https://make.wordpress.org/meta/handbook/getting-started/contribute-with-docs/) [ Next: Tutorials & Guides](https://make.wordpress.org/meta/handbook/tutorials-guides/)