This year, WordCamp Europe will have 25 Make WordPress teams at Contributor Day. We will be welcoming more than 500 contributors, led by 37 experienced contributors and supported by our organising and volunteer team. <\/p>\n\n\n\n
You can also continue to contribute on the Friday and Saturday conference days in our dedicated Contributing Area<\/a>.<\/p>\n\n\n\n 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\u2019s Slack workspace. There will be volunteers available at a dedicated table in Room 1 to help anyone who doesn\u2019t have these accounts.<\/p>\n\n\n\n Contributing to some teams requires setting up a local development environment. If you need one but don\u2019t 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<\/a> configuration focused on WordPress<\/a> 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.<\/p>\n\n\n\n Let\u2019s introduce you to the WCEU Contributor Day Team Leads and the current work of the Make WordPress teams.<\/p>\n\n\n\n Team Lead:<\/p>\n\n\n\n The Accessibility Team will focus on WordPress 5.3 accessibility- related tickets from the WordPress Core and Gutenberg GitHub repository. These include:<\/p>\n\n\n\n Tasks will also be related to the WP Campus Gutenberg Accessibility Audit<\/a>. The team will collaborate with the Design and Triage Editor (Core: Editor) teams.<\/p>\n\n\n\n Other areas of focus will be: the WordPress Theme Accessibility Audit project, WordPress.org\/Meta websites and the Accessibility Team Handbook.<\/p>\n\n\n\n Team Lead:<\/p>\n\n\n\n The Accessibility – WP Theme Auditor will focus on accessibility auditing tools for WordPress themes.<\/p>\n\n\n\n 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.<\/p>\n\n\n\n Team Leads:<\/p>\n\n\n\n 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.<\/p>\n\n\n\n The team will also be working on:<\/p>\n\n\n\n Team Lead:<\/p>\n\n\n\n The Core: Javascript Team is focusing on a number of topics, including:<\/p>\n\n\n\n Team Lead:<\/p>\n\n\n\n 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\/<\/a><\/p>\n\n\n\n Team Leads:<\/p>\n\n\n\n The Core: Privacy Team contributed 15 bug fixes and nine enhancements for the WP release 5.2 on 7 May 2019.<\/p>\n\n\n\n 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.<\/p>\n\n\n\n Team Lead:<\/p>\n\n\n\n The Core: Triage Team will focus on:<\/p>\n\n\n\n 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.<\/p>\n\n\n\n Team Lead:<\/p>\n\n\n\n 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:<\/p>\n\n\n\n All are welcome to get involved.<\/p>\n\n\n\n Team Leads:<\/p>\n\n\n\n The Documentation Team is responsible for areas including:<\/p>\n\n\n\n This team is working on:<\/p>\n\n\n\n Team Lead:<\/p>\n\n\n\n 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\u2019s code examples.<\/p>\n\n\n\n Team Lead:<\/p>\n\n\n\n The Gutenberg Documentation Team will focus on helping developers by moving forward with developer\u2019s<\/a> documentation. The team wants to make sure its information and examples are up to date with the latest code.<\/p>\n\n\n\n Team Leads:<\/p>\n\n\n\n The Glotpress and Meta: i18n Team will work on:<\/p>\n\n\n\n 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.<\/p>\n\n\n\n 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.<\/p>\n\n\n\n Team Lead:<\/p>\n\n\n\n The Hosting Team will be creating PHP upgrade guidelines for hosts for communication with users. The goal is to reflect on last year\u2019s 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.<\/p>\n\n\n\n There will be a live demonstration on how to help users upgrade their website\u2019s PHP version.<\/p>\n\n\n\n Team Leads:<\/p>\n\n\n\n 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. <\/p>\n\n\n\n Contributors will be able to choose from an extensive list of tasks. Just some of those available include:<\/p>\n\n\n\n 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. <\/p>\n\n\n\n Read more details about the plans and tasks for the marketing table at WCEU 2019<\/a>. <\/p>\n\n\n\n Team Lead:<\/p>\n\n\n\n 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\u2019 interests.<\/p>\n\n\n\n Team Leads:<\/p>\n\n\n\n The Mobile Team invites contributors to set up their development environment in advance. Instructions can be found at: Team Lead:<\/p>\n\n\n\n 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.<\/p>\n\n\n\n There will also be an opportunity to share your story of being a translator, contact @TranslateWP<\/a> on Twitter in advance or talk to representatives from WPTranslationDay<\/a> who will be available to share with you a list of interview questions.<\/p>\n\n\n\n Team Lead:<\/p>\n\n\n\n The Support Team will show you:<\/p>\n\n\n\n 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.<\/p>\n\n\n\n As the Support Team likes to say: \u201cSupport is one of the easiest, low barrier entries into contributing to WordPress!\u201d<\/p>\n\n\n\n Team Lead:<\/p>\n\n\n\n The Theme Review Team will focus on other open source projects including Theme Sniffer plugin and WPThemeReview coding standards.<\/p>\n\n\n\n If time allows, it will also go through open issues and work on a selection in small groups.<\/p>\n\n\n\n For coding standards, contributors will be able to work with Juliette, who will also be able to help newcomers.<\/p>\n\n\n\n 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\u2019s plans for WCEU 2019<\/a>.<\/p>\n\n\n\n Team Leads:<\/p>\n\n\n\n The Tide Team will be focusing on a theme\/plugin standard, and there may be some cross team communication for this work.<\/p>\n\n\n\n Team Lead:<\/p>\n\n\n\n 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:<\/p>\n\n\n\n On Contributor Day, the team will run a \u2018sprint\u2019 to complete one of these lesson plans. The workshop training will focus on Best Practices for WordPress-Friendly Layout<\/em> includes the lesson plans Introduction to CSS, Web Fonts, Using the Theme Customizer<\/em>, and Using Child Themes<\/em>.<\/p>\n\n\n\n Team Lead:<\/p>\n\n\n\n The Triage Editor (Core: Editor) Team\u2019s goal is to make it easier to contribute to Gutenberg. There will be several tasks to work on throughout the day:<\/p>\n\n\n\n Team Lead:<\/p>\n\n\n\n The WordPress.TV Team has the following goals for Contributor Day:<\/p>\n\n\n\n Team Leads:<\/p>\n\n\n\n The WordPress Coding Standards (WPCS) Team will focus on documentation. There will be some cross-over with other teams.<\/p>\n\n\n\n There are three areas related to documentation which people can work on improving:<\/p>\n\n\n\n 1. the information about WPCS in the Make website(s).<\/p>\n\n\n\n 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.<\/p>\n\n\n\n 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<\/p>\n\n\n\n Team Llead:<\/p>\n\n\n\n The WP-CLI Team is the official command line tool for interacting with and managing your WordPress sites.<\/p>\n","protected":false},"excerpt":{"rendered":" This year, WordCamp Europe will have 25 Make WordPress teams at Contributor Day. We will be welcoming more than 500 contributors, led by 37 experienced contributors and supported by our organising and volunteer team. You can also continue to contribute on the Friday and Saturday conference days in our dedicated Contributing Area. Are you a […]<\/p>\n","protected":false},"author":15025730,"featured_media":0,"parent":10532,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"jetpack_post_was_ever_published":false,"footnotes":""},"class_list":["post-10997","page","type-page","status-publish","hentry"],"jetpack_shortlink":"https:\/\/wp.me\/Pa076x-2Rn","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/europe.wordcamp.org\/2019\/wp-json\/wp\/v2\/pages\/10997","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/europe.wordcamp.org\/2019\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/europe.wordcamp.org\/2019\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/europe.wordcamp.org\/2019\/wp-json\/wp\/v2\/users\/15025730"}],"replies":[{"embeddable":true,"href":"https:\/\/europe.wordcamp.org\/2019\/wp-json\/wp\/v2\/comments?post=10997"}],"version-history":[{"count":19,"href":"https:\/\/europe.wordcamp.org\/2019\/wp-json\/wp\/v2\/pages\/10997\/revisions"}],"predecessor-version":[{"id":11125,"href":"https:\/\/europe.wordcamp.org\/2019\/wp-json\/wp\/v2\/pages\/10997\/revisions\/11125"}],"up":[{"embeddable":true,"href":"https:\/\/europe.wordcamp.org\/2019\/wp-json\/wp\/v2\/pages\/10532"}],"wp:attachment":[{"href":"https:\/\/europe.wordcamp.org\/2019\/wp-json\/wp\/v2\/media?parent=10997"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}Are you a new contributor?<\/h2>\n\n\n\n
Get set up<\/h4>\n\n\n\n
Get to know the Teams<\/h3>\n\n\n\n
Accessibility<\/h2>\n\n\n\n
Accessibility – WP Theme Auditor<\/h2>\n\n\n\n
Community<\/h2>\n\n\n\n
Core: Javascript<\/h2>\n\n\n\n
Core: PHP<\/h2>\n\n\n\n
Core: Privacy<\/h2>\n\n\n\n
Core: Triage<\/h2>\n\n\n\n
Design<\/h2>\n\n\n\n
Documentation<\/h2>\n\n\n\n
Core: Documentation<\/h2>\n\n\n\n
Gutenberg Documentation<\/h2>\n\n\n\n
Glotpress and Meta: i18n<\/h2>\n\n\n\n
Hosting<\/h2>\n\n\n\n
Marketing<\/h2>\n\n\n\n
Meta<\/h2>\n\n\n\n
Mobile<\/h2>\n\n\n\n
GitHub – WordPress Mobile on iOS<\/a>
GitHub – WordPress Mobile on Android<\/a>.<\/p>\n\n\n\nPolyglots<\/h2>\n\n\n\n
Support<\/h2>\n\n\n\n
Theme Review<\/h2>\n\n\n\n
Tide<\/h2>\n\n\n\n
Training<\/h2>\n\n\n\n
Triage Editor (Core: Editor)<\/h2>\n\n\n\n
WordPress.tv<\/h2>\n\n\n\n
WordPress Coding Standards<\/h2>\n\n\n\n
WP CLI<\/h2>\n\n\n\n