Topic on Talk:Wikimedia Developer Summit/2017/Program committee

Sprint completed.

The next deadline:

• 2016-11-28: Deadline for consolidating a discussion, regularly summarized in the proposal.

What is expected for each main area (this is my own opinion, feel free to disagree):

• Go through the proposals missing active discussion and try to push the conversation in those that you think should be pre-scheduled

To be clear, tasks missing an interesting discussion will have a very hard time getting one of the ~18 slots for pre-scheduled sessions. Currently we have 49 proposals, and 3 of them (Community Wishlist) have their slot assured. This means that today we have 46 sessions competing for 15 slots:

• A plan for the Community Wishlist 2016 top results: 3 proposals (to be scheduled)
• Handling wiki content beyond plaintext: 12
• Building a sustainable user experience together: 5
• Building on Wikimedia services: APIs and Developer Resources: 4
• How to manage our technical debt: 4
• Artificial Intelligence to build and navigate content: 7
• How to grow our technical community: 9
• None (all of them related to editorial collaboration): 5

We will send a communication to all the registered participants and the main mailing lists encouraging everybody to participate in their preferred proposals, and also to award Phabricator tokens to the sessions they are interested about. All this regardless of whether they will attend the Summit or not (since we want to improve remote participation). Tokens will be considered a complement to register "proven interest"about a session.

After a conversation with @Sherah (WMF), we have agreed to close "Building a sustainable user experience together" due to a lack of critical mass and push in the topic as a whole. Specific session proposals still might be pre-scheduled, based on their own merit.

I have started moving proposals to either "On track" (when they had a clear track of support and discussion) or "Unconference". At the end of today, the "Missing proven interest" column should be empty. If there are any proposals left by tomorrow, I will deal with them (the worst thing that might happen is that someone disagrees and then we discuss and eventually change something).

I didn't really touched any of the "beyond plaintext" proposals, since there is @Cscott and other Program committee members involved. I didn't decide on a few other proposals belonging to other main topics because I wasn't sure whether they should be evaluated as having enough interest or not. For instance, there are several proposals with a relative high number of subscribers and tokens, but no discussion at all. Please help triaging those. As Program committee members, you can also weigh in at the proposal itself by adding a comment with your own opinions.

In other words, there are still 21 proposals to triage, and if all Program committee members help, this will be an easy task. If not, the risk of me making mistakes will be a lot higher.  :)