Here's a possible division of our list of proposals into "working groups" or "working areas" that we can use to organize our thinking about the WikiDev '16 summit
- **Content format** - 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 ** - 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** - 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** - this is about building and delivering high quality code. Central problem: "how do we build high-quality software that we can dramatically increase the number of people that can understand it while increasing the reliability and maintainability of Wikimedia sites?"
These are, of course, overlapping concerns. My thought is that we can have Phab projects for each of these working areas, assigning each WikiDev '16 proposal to one primary area. For //some// proposals, it may be good to put them in multiple projects, but let's try to resist that urge.