Here's a possible division of our list of proposals into "working groups" or "working areas" that we are using to organize our tradeoff decisions about the WikiDev '16 summit
- Content format (T119022) - This is about the format of our data, with a primary emphasis on the future of Wikitext & markup (or possibly, the future of eliminating it). The central problem in this area: "how do we make manipulating our data easier and more useful" (both for humans and computers)
- Content access and APIs (T119029) - this is about getting our data in-and-out of the system (e.g. rest.wikimedia.org). The central problem in this area: "how do we make accessing and distributing our data easier and more useful?"
- Collaboration (T119030) - this is about how we work together. Central problem: "how do we scale editing our code up to populations similar to editing our projects, proportionally increasing our positive impact and productivity?"
- Software engineering (T119032) - this is about building and delivering high quality code. Central problem: "how do we make software development more logical and obvious for all Wikimedia contributors, while simultaneously making Wikimedia software more useful and reliable for the Wikimedia sites?"
- User interface presentation (T119162) - improving our user interactions. Central problem: "How to we make our software beautiful and joyful to use?"
These are, of course, overlapping concerns. We have tasks for each of these working areas, which we assigned each WikiDev '16 proposal to a working area. As we've figured out the distinctions between the various areas, we have asked area owners to consider proposals we previously added outside of their original assignments.
These working areas may persist beyond WikiDev '16. Working groups may form in each of these areas.