WordPress Community Summit 2017: Attendees and Agenda Summary

The 2017 WordPress Community Summit (CS) is almost here. It will take place on Tuesday, June 13th and Wednesday, June 14th, the two days before contributor day at WordCamp Europe in Paris, France. All attendees should have received an email with venue and other important details. If you haven’t received such an email, or if you’re not able to attend, please let us know asap at community@wp-europe.org

We would like to remind all teams and contributors the purpose and goal of the Community Summit:

“The main purpose of the summit is to move the WordPress project forward before and after the event, with the event being a milestone in a larger set of work.

With this main goal in mind, we’ll touch base with all team reps to figure out which of the topics proposed can be handled beforehand, and come up with topics that would be:

1) of importance to the project as a whole

2) would benefit from cross-team collaboration

3) will leave us in a better position than when we started”

 

How Attendees Were Selected

Unlike WordCamps or Contributor Days, the Community Summit has limited capacity both because of the venue size and the type of work that is required. The list of nominations was reviewed by a committee composed of experienced contributors, chosen for their broad overview of the project and its community: @aaroncampbell @petya @chanthaboune @helen @ipstenu and @_dorsvenabili

The committee reviewed the list of nominated contributors that we received from the original call for nominations (more info on the process and criteria).

In voting on each person, we kept several things in mind:

  • Active contributions to the WordPress.org project and that specific team
  • Influence/reach in the broader WordPress ecosystem (not just within WordPress.org)
  • Employer (to prevent an overwhelming presence by one or few select companies)
  • Location (to have a decent international contingent and not be solely US-focused)
  • Differing Points of View (to ensure minority voices can be heard)

 

Attendees

The list of attendees was formed from all those who were invited and confirmed their attendance:

Accessibility

@afercia @rianrietveld @davidakennedy @mor10 @samikeijonen

CLI

@schlessera @borekb @danielbachhuber @miyauchi

Community

@andreamiddleton @andrescifuentesr @iaaxpage @mbigul @courtneypk @thewebprincess @jennybeaumont @emanuel_blagonic @francina @mayukojpn @hlashbrooke @ibonazkoitia @miss_jwo @kcristiano @lanche86 @travel_girl @markgazel @imath @paolal @remediosgraphic @sptorabi @_dorsvenabili @mahype @thabotswana @00sleepy @xibe

Core

@adamsilverstein @boonebgorges @chriscct7 @desrosj @dd32 @iseulde @flixos90 @jjj @joehoyle @joemcgill @joen @johnbillion @kadamwhite @matt @marcs0h @matveb @voldemortensen @azaozz @swissspidy @rmccue @stevenkword @westonruter @peterwilsoncc @codebykat

Design

@empireoflight @folletto @michael-arestad @melchoyce @saracannon @sonjanyc @karmatosed @liljimmi

Docs

@atachibana @kenshino @milana_cap

Hosting

@aaroncampbell @andrewtaylor-1 @ddsucurinet @joostdevalk @mikehansenme @mikeschroder @stephdau

Meta

@tellyworth @coreymckrill @pento @iandunn @obenland @mapk

Mobile

@catehstn @mbiais @kwonye

Plugins

@ipstenu @otto42

Polyglots

@glueckpress @chiragpatel @carl-alberto @ocean90 @imnok @lasacco @openstream @petya @tacoverdo @vannkorn

Support

@bethannon1 @cristianozanca @imazed @macmanx @clorith @sergeybiryukov @zoonini

Themes

@acalfieri @grapplerulrich @sakinshrestha @ionutn @poena

Training

@wpaleks @chanthaboune

 

Summary of Community Summit Agenda

Day 1 (Tuesday, 13 June):

  • Individual team and cross-team discussions* which need in-person discussions

Day 2 (Wednesday, 14 June):

  • Continuing cross-team discussions*
  • Writing recaps for the make/summit p2 blog

 

Proposed Discussions

A few months ago, each team proposed topics that need in-person discussion ( List of proposed topics ). If teams need to amend or update their list, post any changes as a comment, please. The deadline is Friday, June 9th, at which point we will close comments and publish the list of topics for WordPress Community Summit 2017.

 

Travel Assistance Program Applicants

All guests, selected for the travel assistance program have been contacted via email by the organizing team, who will follow up in the next few days. Thanks so much to all our sponsors for making this Travel Assistance program possible!

#attendees, #summit-2017

The Community Summit Travel Assistance program still needs your support

There are less than 30 days until the 2017 WordPress Community Summit, and we are still looking for your support with the Summit’s travel assistance program.

This year we are expecting contributors coming from Zimbabwe, Thailand, Costa Rica, Philippines, USA and all over the world. Most event costs for the 2017 WordPress Community Summit are being paid for by WordCamp Europe 2017 (Thank you WordCamp Europe!!), however we still need to focus all our efforts on raising the remaining funds for the summit’s travel assistance program to ensure we can bring these active contributors together.

So far, we have received a great support from the community. However we still need an extra push to guarantee the success of this program.

If you’d like to sponsor the Community Summit, check out the Call for Sponsors and sign on as a sponsor. We will be more than happy to get back to you with all details.

Thanks for being the part of the WordPress Open Source Project!

Community Summit 2017 Sponsors

The WordPress Community Summit only works because of the participation of our amazing community members. This year we are expecting contributors coming from Zimbabwe, Indonesia, North America, Japan and all over the world.

WordCamp Europe covered mosts of the costs for the 2017 WordPress Community Summit (Thanks so much!), however we also needed to raise money to subsidize travel expenses for some of our community volunteers who don’t get paid for their work on WordPress and/or whose travel expenses are significantly higher than those living in Europe.

The following people sponsored this Summit and helped to build the future of WordPress Open Source Project.

Sponsorship Levels

Gold

Bluehost has been a WordPress partner since 2005 and powers over 1 million WordPress sites worldwide. Their objective is to help customers, whether novice or pro, create a thriving online presence at an affordable price. With a team of in-house tech experts available 24/7, Bluehost dedicates time and resources to providing the best support and services in the industry. Join millions of other site owners and see what Bluehost can do for you and your online presence.

Bronze

Human Made is a globally distributed WordPress development agency specialises in high-end WordPress development and consultancy for enterprise & big media.

Our knowledge of WordPress is extensive: many humans have been involved with the WordPress open source project for years, some since its very inception. Individually, we are skilled developers, driven project managers, dedicated account managers, organised event planners, and insightful product makers. Together, we are a friendly, enthusiastic, and approachable team, dedicated to finding problems, big or small, and doing what we can to fix them.

 

Since 1997 DreamHost has helped individuals, small businesses, entrepreneurs and developers the world over bring their dreams to life on the Internet. From domain registrations to traditional web hosting and highly-optimized managed WordPress hosting, more than 400,000 customers trust DreamHost to be their online home. DreamHost supports the WordPress project and community with dedicated resources and a passionate team. Packed with excellent value, DreamHost is a great place to launch a blog, website, or online application into the stratosphere!

 

At YITH we develop innovative WordPress themes and plugins for WooCommerce based sites. For years our philosophy has been based on simplicity and effectiveness as basic concepts required in any professional online business.

Our crown jewel, that makes us proud, is our high-quality support service, through which we take care of our customers day-by-day, never as a number, but as people with faces, names and a personal history that we deeply care for.

Individual

Ahoy! We are the pirates from ThemeIsle who believe that WordPress themes don’t need to be boring. That’s our primary motto and we’re doing everything we can to prove it—starting from our involvement in the community to developing Zerif Lite, one of the most popular themes out there.

 

SiteGround is a leading hosting provider internationally recognized for their unique approach to hosting. With a focus on performance, security and unmatched customer service, they provide solutions to protect your website from hacks and invented new technologies that can make your website run over one hundred times faster.

 

WP Site Care was founded in 2012 and was started with the focus of helping high profile bloggers and small business succeed online. We offer support and maintenance services for WordPress, along with a lot of other odds and ends. Our goal is to make sure you’re working on the business that you love, while we lift the technical burden behind the scenes. For less money than one part-time employee, you can have the technical expertise of our entire team, whenever you need help most. We’d love to talk more if you need a technical team that truly cares about the success of your business!

 

Thanks again to all these amazing companies who are contributing to the future of WordPress and its Open Source community!
We still haven’t covered the whole Travel Assistance Program, so if you’d like to sponsor the 2017 WordPress Community Summit, check out the Call for Sponsors and sign up. We will be more than happy to get back to you with all details.

List of topics proposed by teams

As said in the previous post, the following list of topics which need in-person discussions is not definitive as we’ll loop back in the next couple of months. Here’s the current list of topics proposed by teams:

Core

  • How can we increase Javascript contributions to Core?
  • What should be Core’s technology support policy (especially related to deprecating support)?
  • How can we better project manage contributors efforts in Core?
  • How can we improve the on-boarding experience for new contributors?
  • How can we improve the Security process from report through triage through disclosure? – (Security)

Design

  • Onboarding: How do we recruit and attract new designers to WordPress?
  • Retention: How do we retain new designers?
  • Process: How do we communicate a unified design process to contributors?
  • Collaboration: How do we work with other WordPress teams to supply design assistance? – (All)
  • Impact: How can WordPress impact the greater design community?

Mobile

  • WP API & the mobile apps
  • Possibly the new core block editor experience and how it can work with the upcoming Aztec native iOS & Android editors – (Core)

Accessibility

  • New developments for the the Editor, and how to safeguard it’s accessibility – (Core)
  • Technology version support policies – (Core)
  • How to involve more developers in helping with the accessibility tickets
  • How to proceed with the handbook

Polyglots

  • Increase outreach (Rosetta sites outreach, jump starting and upgrading our locale sites to best fit the community) – (Community)
  • Local contributor days – (Community)
  • Global contributor days (translation days)” – (Community)
  • Improvement of translation and communication tools 2.0 (we’ve already got the first phase of this going with the O2s, GlotPress improvements, etc) – (Meta)
  • Cross locale PTEs implementation discussions – (Meta)
  • Translating documentation (already mentioned above)” – (Meta)
  • New General Translation Editors onboarding/ Mentorship program and new translation contributors onboarding plan
  • Polyglots Leadership team growth plan in underrepresented regions

Support

  • Continue 2015’s discussion about how to make/keep the support community welcoming and open, while at the same time encouraging quality replies
  • Go through the remaining items on the lists of known issues and requested enhancements – (Meta)
  • Create a common style guide (best practices) that can be used across all forum language
  • Improved management of contributors with time to spare

Themes

  • How we improve the leadership of the TRT team?
  • How can we encourage and enable more people to lead new projects?
  • What is the vision and goals of the team?
  • What is the future of the theme review team, can we change it to become the Theme Team and be more involved in theme related activities like improving the theme directory or the theme developers handbook? – (Meta, Docs)
  • Future of the theme review theme and making it smoother and faster
  • How we can encourage creative designs and how to stop more of copy themes which can just be child theme

Docs

  • Game Plan for recruitment
  • Onboarding Plan
  • State of Doc Team’s own documentation
  • DevHub and Helphub Translation
  • Clear way of contributing to specific parts of documentation
  • Helping other teams with their documentation – (All)

Community

  • Global involvement
  • WordCamps & Money
  • Marketing & Engagement – (Marketing)
  • Paying for speaker travel
  • Regional camps
  • Improving deputy training
  • CoC and harrassment reports
  • Supporting other event types

Plugins

  • Tools plugin devs need to manage their plugin – (Meta)
  • Tools plugin devs need to manage reviews and support (crossover with forums) – (Meta, Support)
  • How to effectively handle contributor days
  • Dependencies and libraries – can we save WP from DLL Hell? (crossover with core team) – (Core)
  • Safely and responsibly improving communication of closed plugins (crossover with the meta and security team) – (Meta, Security)

Training

  • None

Meta

  • Translation of documentation on WordPress.org, including developer hub and (the future) help hub – (Polyglots, Docs, Support)
  • Participate in other team’s discussions to see how the Meta team can help them

TV

  • None

Flow / Test

  • None

CLI

  • WP-CLI Package Index / future of WP-CLI packages and new feature development
  • Improving the contributor workflow, and increasing the contributor pipeline
  • Generally, how to bring the WP-CLI experience closer to people

Marketing

  • None

Hosting

  • How can the Core Security Team work better with hosts? During the 4.7.2 release, our interactions with hosts were drastically expanded, but I would love to continue to pave a path between core security and hosts – (Security)

#teams, #topics

WordPress Community Summit 2017 announcement

The 2017 WordPress Community Summit (CS) will take place on Tuesday-Wednesday, 13-14 June, before WordCamp Europe in Paris, France and it’s a by-invitation conference.

The main purpose of the summit is to move the project forward before and after the event, with the event being a milestone in a larger set of work.

With this main goal in mind, we’ll touch base with all team reps  to figure out which of the topics proposed can be handled beforehand, and come up with topics that would be:
1) of importance to the project as a whole
2) would benefit from cross-team collaboration
3) will leave us in a better position than when we started

In order to get this goal, we’re asking all teams to figure out which topics really need an in-person planning day, and then start working on as many of these remaining topics as possible online and before the event. This way, we’ll be able to loop back in May to see if there are any obstacles for these goals to be achieved by your team and to identify better which cross-team collaboration is needed, anything we can do to help move things along!

So who is invited?

Based on the topics proposed, the nominations posted by all make.wordpress.org team reps, and those topic applications received through the sign-up request form, a committee of experienced team leads have reviewed the total list of nominations. This committee voted, taking into consideration involvement with the WordPress project, relevance and representation of different points of view for the topics listed, diversity, company for having a wide number represented, location for representing different origins with active communities.

The selected participants will receive an email or Slack message from their team reps or me during the next week (by March 29th at the most) with more details and with a RSVP link to confirm their attendance. The final list of attendees will be posted in this p2 blog as soon as we receive all RSVP.

List of volunteers to help with the organization of the event

The following contributors will be contacted via WP Slack at the end of next week to join the current organizing team to get the tasks done for the event – thanks for your help!

*Note: It’s been a very hard task winnowing the nomination lists, but the capacity and the nature of this event is to be as small as possible for the level of interaction needed. All teams will post the notes of their discussions at the end of the Community Summit in this blog and on June 15th (next day), all contributors will have a working day during the WordCamp Europe Contributor Day, so don’t hesitate to sign-up to it and to make WordPress better all together.

Call for Community Summit Travel Assistance Sponsorship

As the name suggests the Community Summit only works because of the participation of our amazing community members. But not everyone in our community has the financial support of their employer or the money to pay their own way. Without them we’d be losing out on input from people who are necessary to the conversations we will have at our upcoming event.

With that in mind we are opening a call for 2017 Community Summit sponsors to ensure that we meet our goal of Community inclusion. Most event costs for the 2017 WordPress Community Summit (venue and catering) are being paid by WordCamp Europe 2017 (Thank you WordCamp Europe!!). This allows us to focus our fundraising goals on supporting the Summit’s much needed travel assistance program, allowing us to subsidize travel for volunteer WordPress contributors from around the world who would not otherwise be able to attend.

If you’d like to sponsor the 2017 WordPress Community Summit, check out the Call for Sponsors and sign up. We will be more than happy to get back to you with all details.

Thanks for supporting the WordPress Open Source Project!

Travel Assistance Program

As the name suggests the Community Summit only works because of the participation of our amazing community members. But not everyone in our community has the financial support of their employer or the money to pay their own way. Without them we’d be losing out on input from people who are necessary to the conversations we will have at our upcoming event.

With that in mind we are happy to announce a travel assistance program for the 2017 WordPress Community Summit, which will take place on Tuesday-Wednesday, 13-14 June, before WordCamp Europe in Paris, France. Travel assistance will make it possible for more WordPress contributors to attend this event. This assistance may cover all or part of travel and/or lodging, based on need.

There are no specific requirements to apply for travel assistance — we won’t ask to see your tax returns — but we do have some goals in mind as we introduce the program.

Important note: Before you apply, please determine if you fall within one of the following categories.

  • Contributors selected based on the list recommended by the wp.org team reps: https://make.wordpress.org/summit/2017/01/26/community-summit-2017/
  • Non-active contributors that applied over Sign-Up form and finally selected by the Community Summit organizing team.
    https://make.wordpress.org/summit/2017/02/20/community-summit-2017-sign-up-request/

Our travel assistance team will be looking for applicants passionate about WordPress who would not be able to attend the event without financial assistance.

Please indicate in the application the level of financial assistance you need, keeping in mind that we strive to accommodate the maximum number of applicants that our budget will allow. In other words, please only apply if you really can’t afford the trip and your company will not pay for you to attend and ask only for the amount you need to fund your attendance.

Application deadline is April 14th, 2017

Things to consider before applying:

  • Please evaluate if you will really be able to attend the event.
    If you decide you can’t attend after receiving a travel assistance award (travel/hotel), you will not be eligible for a WordPress event assistance in the future. We understand that situations may come up last minute, but please be considerate of other applicants and consider family and job obligations before applying.
  • It is your responsibility to research the visa requirements for your country.
    Please research obtaining a visa for your country prior to submitting your application and let us know the anticipated wait time to hear back about a visa. The WordPress Foundation can provide an Invitation Letter if necessary, whether you are applying for a travel assistance or not.
  • You must have a current passport with an expiration date no earlier than 3 months after the conference to apply.
Apply here for the travel assistance program and if you’ve been selected, we’ll be back to you before April 24th.

#assistance, #program, #summit, #travel

Community Summit 2017: Sign-up Request

The Community Summit unconference is the event of conversations, so the time will be dedicated to group discussions prioritizing topics or tasks which are sensitive enough to specifically require in-person discussion and of importance to the open source project and plan for the coming year.

We know that lots of people contribute to the success of WordPress in ways that don’t fit into our current set of contributor teams, so we’ve also reserved some spots with those contributors in mind.

Summit attendees will be selected based on what topics are identified by contributor teams as sensitive or contentious enough to require an in-person discussion to resolve them. Or if you wish to submit a discussion topic for the 2017 summit, please fill out the form below. Note that you can nominate yourself or any other person who you think is required to reach agreement on the issue.

We’ll create a committee with all wp.org team reps to select the topics and participants submitted through this form and we’ll contact the selected attendees before March 15th.

Note: Promotional activities of any kind will not be welcome.The entire event is dedicated to the WordPress open-source project and its future.

If you’d like to submit a topic to be discussed at the summit, fill out the form here.

Update on March 7, 2017: This survey is now closed.

Community Summit 2017

The 2017 WordPress Community Summit (CS) will take place on Tuesday-Wednesday, 13-14 June, before WordCamp Europe in Paris, France (the venue will be in the XV district of Paris).

The CS is now in the planning stages, and this site will grow in the coming weeks to include information for attendees as well as event sponsorships, agenda, etc.

Based on the feedback and discussion p2 post (https://make.wordpress.org/community/2016/11/03/wordpress-community-summit-2017/) about a new approach for the 2017 CS, these are the next steps for every make.wordpress.org contributor team.

Next Steps:

Team reps, please post the following in a comment to this post.
The deadline is March 3rd, 2017.

  1. A list of topics/issues which are relevant for the progress of the team and the WordPress open source project as a whole, prioritizing topics or tasks which are sensitive enough to specifically require in-person discussion.
  2. A list of representatives to attend the Community Summit (not limit-determined, but please keep in mind that our venue capacity limit is of 130 attendees), with selections based on several factors, including: representation of a wide, diverse range of opinions (based on the agreed-upon topics selected by each team), diversity, inclusion, and activity of the contributors.
  3. One or two contributors who are willing to help with the organization of the event: posts, communication, travel assistance, finding sponsors, etc. The intention of this approach is to propose a more open and team-focused Community Summit with transparent participation from all active contributors and reps of each team. This way we can hopefully anticipate barriers and cross-team difficulties that might come up, and avoid them.

Notes:

  1. The contributors who are willing to work on the summit (referenced in #3, above) will join the WCEU team working on the Community Summit. If there are not enough contributors available to help organize, the WCEU team has volunteers available to help.
  2. We’ll work on finding sponsors to cover travel expenses for those contributors who face financial barriers. We’ll open a call for CS sponsors in the next days.
  3. For those teams with sub-teams, for example, Core: REST API, security, etc. the representation of these sub-teams will depend on the list of discussion topics provided by the team.
  4. In the next days, we’ll open an application form for people who aren’t invited as contributors, but who represent other interests within the wider WordPress Community.


Pinging all team reps:
Accessibility: @rianrietveld, @joedolson, and @afercia
Community: @francina and @hlashbrooke
Core: @jeffpaul, @helen
Design: @melchoyce, @karmatosed, @joen, @michaelarestad
Documentation: @kenshino
Test: @designsimply
Hosting: @mikeschroder
Marketing: @rosso99
Meta (WordPress.org Site): @samuelsidler
Mobile: @astralbodies, @rachelmcr
Plugins: @ipstenu
Polyglots: @petya, @ocean90, @nao, @chantalc, @deconf, @casiepa
Support: @macmanx
Themes: @jcastaneda, @grapplerulrich
Training: @bethsoderberg
TV: @jerrysarcastic, @roseapplemedia
Cli: @danielbachhuber

#2017, #summit-2017

Welcome to the Community Summit Workspace!

The Community Summit is a working day for face-to-face discussions of thorny or incendiary topics (the kind that frequently result in flame wars). Sometimes it is followed by 1-2 Team Days where each project team has time to complete targeted projects together. The Summit is a small event that isn’t owned by any one project team, so this space is where you can find information about planning, participate in discussions, and generally stay informed as the event takes shape.

After each event, we’ll also post anonymized notes here so that discussions are open and available to anyone participating in the project in the future. They aren’t necessarily held every year, though, so there will be times when this p2 is quieter than usual.

Subscribe to stay informed, and happy planning!

#summit #announcements