WordPress Community Summit 2017: Final list of topics

The 2017 WordPress Community Summit (CS) in Paris (Tuesday, June 13th – Wednesday, June 14th) is less than 5 days away and here is the final list of topics submitted by teams.


  • 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)


  • 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?


  • 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)


  • 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
  • Considering the shift towards JS-based interfaces, we should consider to review and update the accessibility coding standards


  • 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


  • 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.


  • 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


  • 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)
  • Discuss opportunities for leadership and retainment of contributors to ensure longevity of Docs Team goals


  • Paying for speaker travel – following on from our existing discussion and reaching a consensus.
  • Regional camps – following on from our existing discussion and reaching a consensus.
  • WordCamps and Money – discussing guidelines for responsible use of funds and clearly outlining what will and will not pay for. Also looking at how this affects in-kind types of sponsorships.
  • Code of Conduct and harassment reports – Establishing a plan for training for organisers on how to deal with CoC violations, as well as reviewing the CoC to be more inclusive (possibly to be concluded at Contributor Day).
  • Marketing & Engagement – discussing a general marketing plan for WordCamp and meetups, especially to engage people outside of the WordPress bubble – (Marketing)
  • The 80/20 rule for local/international speakers – this is a sticking point for many camps and it will be worth defining what we mean and where the line is for this.
  • Communication tools for WordCamp organisers – discussion on how to handle third party newsletter tools/services and how organisers can more effectively communicate with their community.


  • 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)


  • None


  • 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


  • None

Flow / Test

  • None


  • 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
  • Problem in detecting updates of manually packaged WordPress (Meta, Core)


  • None


  • 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)

Thank you to all teams for great topics lists. We wish you wonderful and productive Summit and see you all next week in Paris.

“Such wow. So excited. Much joy.”

– friendly robot Pierre