This page is a DRAFT right now, but a public one. Will be following up with various people and specific team reps to confirm action items and get volunteers to follow up on each one. In some cases, the notetaker listed multiple action items instead of one, or was too vague or all-encompassing rather than identifying a single discrete action that could be taken relatively easily vs starting a giant project. In those cases, I’ve left myself notes in this list so I remember to follow-up with those groups. I’ll delete my notes to myself as these conversations happen and action items are confirmed. I’ll remove this intro paragraph as well once everything is confirmed. Feel free to use the comments on this page to correct action items that were recorded inaccurately, but let’s not use them to debate decisions… the contributor group blogs are a better place for that.

Action Items

  • Put a header on P2 themes telling you what to do to contribute to that area — “I Can’t Get No Traction”: Getting involved in core contributions, Trac/contribution culture, the idea of component leaders/owners
  • Make WordPress.org/accessibility which will talk about successes we’re having and ways people can get involved — How Do We Move Accessibility Forward [Jane note: Please use make.wordpress.org/accessibility for discussions, and be sure to include Esmi, the accessibility team rep, who couldn’t attend the summit]
  • Implement a stability index for our APIs like Node.js and create a development philosophy page on the codex — Getting to 100% of Websites on WP / WordPress as a Framework
  • Make a page that describes the apps, their place in the ecosystem, and their goals (for potential contributors) — Apps & Core: How do they fit together? (Mobile)
  • Review the draft handboook on UI processes, decisions, philosophies and publish it — UI Group: Growth/participation, diverse types, and projects 
  • Differentiate between security, major, minor releases (publish definitions?) — Updates: Faster, Smoother, Sexier?
  • Create a customizer roadmap for core; have theme review team recommend using the customizer — The Future of the Customizer
  • Define and publish the policy for taking over a plugin by another author and/or forking — Attracting developers to plugins and the plugin life cycle
  • Formalize methods of communication between the core teams about problem plugins Managed WP Hosts: What can we do better, differently, etc.
  • Better document the workflow for theme review to make that process more transparent and consistent — Theme guidelines, quality, and the directory
  • Create a codex page that lists the popular ways to deploy and discusses options that are available — How Can We Make Deployments Suck Less?
  • Codex page for standards, containers for common functionality, better communication — Theme functionality vs. plugins [Jane note: This is too many action items]
  • Continue the discussion (too long for session) —  Plugins & WP.org Integration (Dependencies, etc.)
  • Push findings to community and make plugin to bulk associated featured images to post, and core fix for widgets Elimination of Pain During Theme Switch [Jane note: This is too many action items]
  • Individual plugin reviews on wordpress.org, and Example of a bad plugin, checking of syntax errors pre commit — Helping plugin authors improve security and quality [Jane note: This is too many action items]
  • make./global Site with a forum WordPress: The Global Community  [Jane note: segregating the international community within the contributor arena will create more problems. It would be better to get more international involvement in the existing (and soon-to-be-created) contributor/action groups rather than marginalizing into a separate concern.]
  • Recent rockstars will be immediately to include non-coders — Recognizing non-code contributions and the contributor handbooks [Jane note: this is problematic, because then recent rockstars has different context than other sections. Should either do all of credits to include non-coders or come up with another solution rather than make only one section be cross-group]
  • Theme updates destroy translation files; this must fixed and a solution is currently under dev now — Better ways to solve i18n issues, WP multi-language
  • Create a road map for the Codex — Codex: update, contribute, reorganize
  • Encourage women to speak at local meetups — Women and WordPress
  • Blog more on make/core under JS tag — JavaScript: How do we increase JS proficiency in the WordPress community?
  •  wp-signup.php converted to theme templates, domain mapping in core — Multisite Roadmap [Jane note: This is two action items.]
  • Improved resources around GPL topics — GPL and its issues [Jane note: This action item is not specific enough.]
  • Publish make/events subcommittees list — Foundation transparency
  • Create a mailing list for agencies to combine resources on contributing — Helping WP-based companies contribute to core [Suggestion from Jane: Let’s do make.wordpress.org/business instead of a list, and make this an official contributor group.]
  • Open source the WordCamp base theme and plugins that we use so people can contribute to them — WordCamp issues and websites
  • Show top downloaded plugins within the past two months on the plugin repo to promote new authors. — How to be legit and still make money off of small plugins
  • Make meetup organizers authors on make/events — “What the Meetup”
  • WPORG support forums & Theme/Plugin directories direct users to commercial Theme resources (support, etc.) — How to better review commercial plugins and themes
  • Codex page (or perhaps wordpress.org page) that describes to publishers (and other different use cases) what we are and what we can do specifically for them. why.wordpress.org?// Figure out the future of the Code Poet directory. If it’s dying, let’s fork it and have it as a community resource — WordPress for Publishers [Jane note: This is two action items, and the first one is not a discrete action item but a large project.]
  • Start a discussion on Make.wordpress.org re how to handle plugin dependancies on themes/plugins/core — Plugin API Versioning [Jane note: where specifically?]

 

Missing Action Items:

  • The Downside of Theme Customizers and Plugin Options Screens: Oversimplification — Incomplete notes, pinged notetaker
  • WordPress.org Profiles and Transitioning to bbPress 2.X
  • What challenges do people face with release schedules and management?
  • Education Tools