This year, WordCamp Europe will have 25 Make WordPress teams at Contributor Day. WCEU will be welcoming more than 500 contributors, led by 37 experienced contributors and supported by WCEU organising and volunteer team.
You can also continue to contribute on the Friday and Saturday conference days in the dedicated Contributing Area.
Are you a new contributor?
GET SET UP
The Make WordPress teams use different tools for their contribution work, but as a start all contributors need a WordPress.org profile and access to the project’s Slack workspace. There will be volunteers available at a dedicated table in Room 1 to help anyone who doesn’t have these accounts.
Contributing to some teams requires setting up a local development environment. If you need one but don’t know how to set it up, you can visit the table in Room 2 for help installing VVV on your laptop before you join your selected team.
Varying Vagrant Vagrants is an open source Vagrant configuration focused on WordPress development. Thank you to Tom J Nowell and Lorelei Aurora for generously sharing their time and expertise to help new contributors get started in this area.
- Tom J Nowell, Twitter: @tarendai, WordPress.org: tjnowell
- Lorelei Aurora, Twitter: @LoreleiAurora, WordPress.org: loreleiaurora
Get to know the Teams
Let’s introduce you to the WCEU Contributor Day Team Leads and the current work of the Make WordPress teams.
The Accessibility Team will focus on WordPress 5.3 accessibility- related tickets from the WordPress Core and Gutenberg GitHub repository. These include:
- ticket triage
- making patches
- issues resolution
Tasks will also be related to the WP Campus Gutenberg Accessibility Audit. The team will collaborate with the Design and Triage Editor (Core: Editor) teams.
Other areas of focus will be: the WordPress Theme Accessibility Audit project, WordPress.org/Meta websites and the Accessibility Team Handbook.
Accessibility – WP Theme Auditor
The Accessibility – WP Theme Auditor will focus on accessibility auditing tools for WordPress themes.
Automated tests are not the only way to test accessibility, but it is good to include them in the development process. At Contributor Day, the team will look at tools including WP Theme Auditor and pa11y.
- Rocío Valdivia, Twitter: @rociovaldi, WordPress.org: _dorsvenabili
- Hugh Lashbrooke, Twitter: @hlashbrooke, WordPress.org: hlashbrooke
- Francesca Marano, Twitter: @FrancescaMarano, WordPress.org: francina
The Community Team will focus on improving existing documentation by moving tutorial posts to the Community Team Handbook, updating outdated pages and writing new docs that are still needed.
The team will also be working on:
- improving deputy training materials
- conducting a group Meetup orientation
- any blockers to the team’s daily work.
- a discussion on patterns developed in Gutenberg which may conflict or overlap with patterns in the broader wp-admin interface
- making Dispatch React hook available for use
- improvements to the @wordpress/scripts package tools.
The Core: PHP Team is focused on resolving open issues for the new WordPress release candidate. It is working on a minor release of WordPress and addressing between 20 and 35 issues. It will focus on issues that arise from new features and fixes in the major release 5.2. https://make.wordpress.org/core/2019/06/01/some-changes-to-the-5-2-2-release-schedule/
- Heather Burns, Twitter: @webdevlaw, WordPress.org: idea15
- Leo Postovoit, Twitter: @postphotos, WordPress.org: postphotos
- Peter Putzer, Twitter: @mundschenk_at, WordPress.org: pputzer
The Core: Privacy Team contributed 15 bug fixes and nine enhancements for the WP release 5.2 on 7 May 2019.
During Contributor Day, the team will focus on bug fixes and enhancements to their privacy tools for administrators. It will work on the 14 tickets in its 5.3 workflow and review new tickets.
The Core: Triage Team will focus on:
- ticket-scrubbing techniques
- Trac keywords
- and workflows.
It will also help contributors understand how and where to focus their efforts to help with triaging Core tickets in Trac. There will be some overlap with the work being done by other teams.
The Design Team will work through a range of tasks during the day to offer something for everyone. There will be a group focusing on:
- Figma components
- usability testing of the block directory
- triage for design.
All are welcome to get involved.
- Jon Ang, Twitter: @Kenshino, WordPress.org: kenshino
- Pieter Daalder, Twitter: @w1zz, WordPress.org: wizzard
The Documentation Team is responsible for areas including:
- the Codex (moving to HelpHub)
- admin help
- inline docs
- and other general documenting across the WordPress project.
This team is working on:
- content Migration from Codex to HelpHub and DevHub
- the Gutenberg Handbook
- a centralised API Handbook
The Core: Documentation Team is working to improve code reference with better usage of the More Info section. It also wants help in reviewing user’s code examples.
The Gutenberg Documentation Team will focus on helping developers by moving forward with developer’s documentation. The team wants to make sure its information and examples are up to date with the latest code.
Glotpress and Meta: i18n
- Dominik Schilling, Twitter: @ocean90, WordPress.org: ocean90
- Robert Windisch, Twitter: @nullbytes, WordPress.org: nullbyte
The Glotpress and Meta: i18n Team will work on:
- ticket triage for international sites
- the Translate site component
- reviewing the priority of each pending ticket
For GlotPress, the team will be checking on the status of the upcoming 3.0 release and trying to solve any open issues on 3.0 prior to enable its release.
The team also hopes to discuss the process of requesting or adding new translation editors for plugins and themes. It will explore how the meta team can help make the process easier and clearer from a technical perspective.
The Hosting Team will be creating PHP upgrade guidelines for hosts for communication with users. The goal is to reflect on last year’s PHP upgrade process and how several hosts managed this process to create guidelines to assist with timing, preparation and support. This will help improve how hosts work with users on future PHP updates.
There will be a live demonstration on how to help users upgrade their website’s PHP version.
- Siobhan Cunningham, Twitter: @siobhanseija, WordPress.org: siobhanseija
- Yvette Sonneveld, Twitter: @yvettesonneveld, WordPress.org: yvettesonneveld
The Marketing Team focus on marketing the WordPress open source project and its community to the wider world. At contributor events, you will be able to get involved in one-off or longer term tasks, work on your own or with others, and join a vibrant and energetic team.
Contributors will be able to choose from an extensive list of tasks. Just some of those available include:
- writing or editing case studies of WordPress sites
- reviewing and subtitling videos for marketing purposes
- interviewing and writing profiles about WordPress contributors to inspire others to get involved.
There will be help available on how to use the online tools and Google Drive editing process. A laptop or tablet will be useful to bring, and headphones if you would like to work on video or audio related tasks.
The Meta Team plans to work on open tickets on Meta Trac, review some patches for Support Forums and the Plugin Directory, and work on some good-first-bugs. The Team Lead will tailor tasks depending on members’ interests.
- Cate Huston, Twitter: @catehstn, WordPress.org: catehstn
- Eli Budelli, Twitter: @elibud, WordPress.org: elibud
- Anna Holland Smith, WordPress.org:
The Polyglots Team will assist new translators to get started and help teams who want to build style guides and glossaries. It will support existing contributors in their translation work and try and overcome any difficulties they may have faced.
There will also be an opportunity to share your story of being a translator, contact @TranslateWP on Twitter in advance or talk to representatives from WPTranslationDay who will be available to share with you a list of interview questions.
The Support Team will show you:
- the tools they use on a daily basis
- some of the support platforms available (there’s more than just forums)
- how to collaborate on questions and trying to find the best solutions for users.
No special skills or knowledge is required, but a laptop, tablet or similar would be useful. Contributors can also work together in pairs or small groups.
As the Support Team likes to say: “Support is one of the easiest, low barrier entries into contributing to WordPress!”
The Theme Review Team will focus on other open source projects including Theme Sniffer plugin and WPThemeReview coding standards.
If time allows, it will also go through open issues and work on a selection in small groups.
For coding standards, contributors will be able to work with Juliette, who will also be able to help newcomers.
The team has chosen to focus on these areas as it feels the better the review tool is, the quicker the theme review can be completed and reduce the number of themes waiting in the queue. More on the Theme Review Team’s plans for WCEU 2019.
- Derek Herman, Twitter: @valendesigns, WordPress.org: valendesigns
- Ulrich Pogson, Twitter: @grapplerulrich, WordPress.org: grapplerulrich
The Tide Team will be focusing on a theme/plugin standard, and there may be some cross team communication for this work.
The Training Team works to create Workshops and Lesson plans that can be used by organisers of Meetups, WordCamps, or educators to teach WordPress to learners so that we can work toward democratizing publishing for everyone. This involves:
- setting learning objectives
- determining assessments
- developing facilitation guides
- creating slides presentations that can be used in a classroom environment or presentation.
On Contributor Day, the team will run a ‘sprint’ to complete one of these lesson plans. The workshop training will focus on Best Practices for WordPress-Friendly Layout includes the lesson plans Introduction to CSS, Web Fonts, Using the Theme Customizer, and Using Child Themes.
Triage Editor (Core: Editor)
The Triage Editor (Core: Editor) Team’s goal is to make it easier to contribute to Gutenberg. There will be several tasks to work on throughout the day:
- onboard new contributors, collect feedback and work on documentation improvements to make the process smoother
- go through the list of open issues, trying to identify tasks which would be an excellent fit for new contributors
- explore how we could automate the detection of pull requests sent by new contributors to ensure they get enough support from others
- triage issues looking for those which can be closed because they are no longer relevant, are duplicates or should be moved somewhere else
- triage pull requests seeking for those which can be closed, need to be updated or can be merged after short review and testing session
The WordPress.TV Team has the following goals for Contributor Day:
- teach the upload procedure to new contributors and explain the WPTV ecosystem
- continue uploading enqueued videos from recent WordCamps, with at least one item to work on for each new contributor attending
WordPress Coding Standards
- Juliette Reinders Folmer, Twitter: @jrf_nl, WordPress.org: jrf
- Gary Jones, Twitter: @GaryJ, WordPress.org: GaryJ
The WordPress Coding Standards (WPCS) Team will focus on documentation. There will be some cross-over with other teams.
There are three areas related to documentation which people can work on improving:
1. the information about WPCS in the Make website(s).
2. the he documentation available about the sniffs. For this, some coding knowledge is required, but not much. This mostly involves creating XML documents with minimal code samples of good and bad code for each sniff currently in WPCS. This documentation can then be called up from the command-line by users of WPCS, as well as be used to generate HTML/Markdown pages which can be added to the WPCS wiki and/or Make.
3. would like to soon start improving the WPCS-Docs sniffs. To help with this, we would like to ask people to start creating the unit tests we will need for this. For this, people need to familiarize themselves with (or already have a good understanding of) the WPCS Docs standards so the docblock samples can be created
The WP-CLI Team is the official command line tool for interacting with and managing your WordPress sites.
Make use of the Contributing Area
Did you know you can contribute to WordPress during the main conference days at WordCamp Europe? All attendees will be able to use a dedicated space on 21 and 22 June 2019 to keep contributing to the open source project. You can continue tasks from Contributor Day or from your own contributing activity.
After the success of the Contributing Area at last year’s WordCamp Europe, we are bringing it back for 2019. This is a dedicated space where you can continue your work from Contributor Day or do some of your own work. Make WordPress teams are also welcome to use the room to meet with members, as the WordPress Coding Standards team did last year.
The dedicated space will be located close to the registration tables at the Estrel and signposted with a banner. There will be seating, tables and power sockets available for your use.
The Contributing Area is open to all WCEU attendees, sponsors, speakers and volunteers, and will be open to coincide with the talks and workshop sessions.
Try the Contributor Orientation Tool to find which of the Make WordPress teams you might like to work with.
Contributor Day and links to information and resources to help you start contributing to the global WordPress project, including frequently asked questions.
Find out more about the Contributor Orientation Tool and the plans for its future development
Benefits of contributing for everyone post with the Make WordPress Marketing team which features contributors’ stories from WCEU.