![\"contrib_day_teams_map\"](\"https:\/\/i0.wp.com\/2016.us.wordcamp.org\/files\/2016\/12\/contrib_day_teams_map.jpg?ssl=1\")
<\/a>\nFor lunch,<\/strong> teams should eat together and will head over to Reading Terminal (with gift cards we provide) at the following times to avoid long waits:
\n-11:20am \u2013 Training, Community, Marketing
\n-11:40am \u2013 Support, Design, and Flow
\n-12:00pm \u2013 Polyglots, Docs, Accessibility
\n-12:20pm \u2013 Core
\n-12:40pm \u2013 Theme Review, Meta, Plugins<\/p>\n
For all the details on the day and the teams (including descriptions of each team), see here: https:\/\/2016.us.wordcamp.org\/contributor-day\/<\/p>\n
Details<\/h2>\n
We’ll have representatives from 14 different teams at the contributor day. If you haven’t already, please edit your registration details<\/strong> (via the link provided in your ticket receipt) to indicate which team you’d like to contribute to<\/strong>. Choosing a team confirms your attendance, so don’t forget!<\/p>\n Please Note:<\/strong> If you plan to contribute to the core, design, or meta teams<\/strong>, you’ll likely need to set up a local development server, we recommend Varying Vagrant Vagrants (VVV). Setup instructions can be found in this handbook article<\/a>.<\/p>\n We’ll also have USB sticks available at the Contributor Day complete with copies of Vagrant, VirtualBox, and a specially pre-provisioned VVV box you can unpack and import quickly at the event.<\/p>\n Click the contributor day links for each team to find out what they’re about and what types of contributing they have available.<\/p>\n Team lead:<\/strong> Rian Rietveld, @rianrietveld on Slack<\/p>\n The a11y group provides accessibility expertise across the project. They make sure that WordPress core and all of WordPress\u2019 resources are accessible. Learn more about the Accessibility team \u00bb<\/a><\/p>\n Team lead:<\/strong> Josepha Haden, @chanthaboune on Slack<\/p>\n<\/div>\n If you\u2019re 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. Learn more about Community \u00bb<\/a><\/p>\n<\/div>\n Team lead:<\/strong> Jeremy Felt, @jeremyfelt on Slack<\/p>\n The core team makes WordPress. Whether you\u2019re a seasoned PHP or JavaScript developer or are just learning to code, we\u2019d love to have you on board. You can write code, fix bugs, debate decisions, and help with development. Learn more about the Core team \u00bb<\/a><\/p>\n Team lead:<\/strong> Tammie Lister, @karmatosed on Slack<\/p>\n The design group is focused on the designing and developing the user interface. It\u2019s a home for designers and UXers alike. There are regular discussions about mockups, design, and user testing. Learn more about the Design team \u00bb<\/a><\/p>\n Team lead:<\/strong> Jon Ang, @kenshino on Slack<\/p>\n Good documentation lets people help themselves when they get stuck. The docs team is responsible for creating inline documentation for core, as well as content for the theme and plugin development handbooks, and more recently, HelpHub. Learn more about the Documentation team \u00bb<\/a><\/p>\n Team leads:<\/strong> Sheri Bigelow, @sheri on Slack<\/p>\n 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. Learn more about the Flow team \u00bb<\/a><\/p>\n Team lead:<\/strong> Sara Rosso, @sararosso on Slack<\/p>\n<\/div>\n The Marketing team focuses on making WordPress marketable in all sorts of contexts, from the WordPress.org side all the way to core and the wider community. Learn more the about Marketing team \u00bb<\/a><\/p>\n<\/div>\n Team lead:<\/strong> Otto Wood, @otto42 on Slack<\/p>\n<\/div>\n The Meta team makes WordPress.org, provides support, and builds tools for use by all the contributor groups. Learn more the about Meta team \u00bb<\/a><\/p>\n<\/div>\n Team lead:<\/strong> Mika Epstein, @ipstenu on Slack<\/p>\n The Plugins team focuses on everything revolving around plugins submitted to the WordPress.org plugin repository. Learn more about the Plugins team \u00bb<\/a><\/p>\n Team lead:<\/strong> Petya Rakovska, @petya on Slack<\/p>\n WordPress is used all over the world and in many different languages. If you\u2019re a polyglot, help out by translating WordPress into your own language. You can also assist with creating the tools that make translations easier. Learn more about the Polyglots team \u00bb<\/a><\/p>\n Team lead:<\/strong> James Huff, @macmanx on Slack<\/p>\n<\/div>\n<\/div>\n<\/div>\n 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. Learn more about the Support team \u00bb<\/a><\/p>\n Team lead:<\/strong> Ulrich Pogson, @grapplerulrich on Slack<\/p>\n 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. Learn more about the Theme Review team \u00bb<\/a><\/p>\n Team lead:<\/strong> Beth Soderberg, @bethsoderberg on Slack<\/p>\n 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\u2019re doing and join our team! Learn more about Training \u00bb<\/a><\/p>\n<\/div>\n The WCUS Contributor Day will be held on Sunday, Dec. 4, 2016 at the Pennsylvania Convention Center. For lunch, teams should eat together and will head over to Reading Terminal (with gift cards we provide) at the following times to … Continue reading Contributor Day<\/span> The Teams<\/h2>\n
Accessibility<\/h3>\n
\n
\nCommunity<\/h3>\n
\n
\nCore<\/h3>\n<\/div>\n
\n
\nDesign<\/h3>\n
\n
\nDocumentation<\/h3>\n
\n
\nFlow<\/h3>\n
\n
\nMarketing<\/h3>\n
\nMeta<\/h3>\n
\n
\nPlugins\/Plugin Review<\/h3>\n
\n
\n<\/div>\nPolyglots<\/h3>\n
\n
\nSupport<\/h3>\n
\n
\nTheme Review<\/h3>\n
\n
\nTraining<\/h3>\n
\n
\n<\/div>\n","protected":false},"excerpt":{"rendered":"