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 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/ There are many teams that people can participate in, each with a different focus. https://2017.us.wordcamp.org/contributor-day/ https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/. at WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. 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.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/ 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:

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)

@afercia @rianrietveld @davidakennedy @mor10 @samikeijonen

CLICLI Command Line Interface. Terminal (Bash) in Mac, Command Prompt in Windows, or WP-CLI for WordPress.

@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

CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.

@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

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.

@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

Marko Heijnen 4:38 pm on May 23, 2017

I’m still curious why I wasn’t selected to attend this summit for the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. team as I have been working on features like PDF thumbnails. You can say this publicly as well as privately.

I also want to note that that the employer criteria doesn’t seems that well looked at since some companies do seem to overwhelm this smaller summit (then usual). I do like the criteria here.

Another note is that I believe that this should have been published way sooner then now and that it should have been more opener. Now it feels like a secret selection.
- Rocio Valdivia 5:40 pm on May 24, 2017
  
  Hi Marko,
  The process of identifying participants for this year’s Community Summit started in January:
  https://make.wordpress.org/summit/2017/01/26/community-summit-2017/
  
  For this iteration of the summit, our approach was to nominate and select contributors based on the topics which contributor teams identified as needing to be discussed at the summit — “topics or tasks which are sensitive enough to specifically require in-person discussion.” This means that if an active contributor didn’t have any reason to participate in the discussion of a sensitive/polarizing topic, then that active contributor wouldn’t participate in the summit.
  
  To say this a different way, not every active contributor to WordPress will be attending this year’s summit.
  
  There were two ways to be nominated for attending the Summit:
  1) By the wp.org team, as the contributor will provide a specific voice and point of view for the topics proposed
  2) Submitting a topic via this form, which was published on February: https://make.wordpress.org/summit/2017/02/20/community-summit-2017-sign-up-request/
  
  Looking at the list of topics identified by the CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. team, none of them seem to be related with the PDF thumbnails which you’ve been working on, so I’d assume that’s why your name didn’t show up on any topic-based nomination lists. Based on what I’m seeing, it doesn’t look like you applied to participate through the Sign Up Request form — is that correct?
  
  Thanks for the feedback about the employer criteria, as well as about the timing of the announcement and the transparency of the selection process. We’ll include it in our list of recommendations for future summit organizers.
  - Marko Heijnen 9:31 pm on May 24, 2017
    
    I have been already warned before February that I would most likely not be selected. I also was never aware of a sign up request form so I haven’t applied through that.
    
    What is weird is that I have attended all the previous summit and when it’s finally in Europe, I don’t hear anything or get selected.
    
    Also I do a lot around media which always have been a topic and the PDF thumbnail feature was just a part of it.
- Jeffrey Paul 5:57 pm on May 24, 2017
  
  @markoheijnen we solicited originally for input on Make/CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.: https://make.wordpress.org/core/2017/02/23/planning-for-community-summit-2017/
  …and then discussed in two subsequent dev chats:
  https://make.wordpress.org/core/2017/02/24/dev-chat-summary-february-22nd-4-7-3-week-4/
  https://make.wordpress.org/core/2017/03/03/dev-chat-summary-march-1st-4-7-3-week-5/
  
  So, apologies if you missed the nomination process but I’m open to ideas you have in how we could better capture input from others that were missed via the process we followed this year.
  
  Please let me know what else you would have liked to have been done and I’ll make note to work on that next time… thanks!
  - Marko Heijnen 9:38 pm on May 24, 2017
    
    The assumption that people have the time to attend dev chats is really wrong as for all timezones except the US, the timeslot just sucks. In my case I can’t make the meeting anymore since January because of training.
    
    The only thing that needs to be fixed is that the nomination should not be personal. And the chance of my nomination is. Specially after the previous summit.
    
    What I would expect is a personal note towards people who have contributed a lot of their time towards WordPress. I believe that they deserve that respect from WordPress.