We can ask session organizers to

• add links to any slides or presos to the Phabricator tasks
• document achievements in sessions' tasks as above
• estimate roughly how many people attended the session

problem is, who are the session organizers?

All tasks were created by someone, and that someone is likely to be the main presenter of the session and the person that should be assigned to the task.

As I read through feedback from the WMDS I will put some thoughts on Logistics here:

1. Dedicate and announce a "quite room" where people can go to get away from noise and people
2. Three day event - first two days meetings and discussions, third day optional space for hacking to begin executing on ideas and getting things going. Maybe hold the third day at Automatic (closer to the office).
3. New solutions for evening events/dinners, don't segregate the vegetarians. WMF 5th floor space will be a better venue than the 6th floor.
4. Reserve the board room and keep it for private meetings, discussions, and interviews that come up during the event.
5. Announce the availability of vegan/gf options

@Rfarrand, you might want to add them in the editable description instead of piling them up in new comments.

Currently they are just thoughts and not agreed upon improvements! I will edit the description once I have a bit more complete info. :)

Casual notes from a conversation with Robla and Greg:

• Have a list of questions beforehand. Damon's session on Architecture Committee was a good example.
• Pick on ongoing discussions during the year, and create sessions with the goal to decide on open discussion that we couldn't solve online.
• We expected that more tasks would be created as a consequence of the sessions, and all the open ends they left.

Next year should not be mandatory for WMF engineering/product. Only people who want to attend/want to be involved in the discussion should attend. Will save $ and save people's time.

Today I sent out a reminder to people who have not filled out the form. I will close the form one week from Today on March 2 and start compiling the results.

Feedback form no longer accepting responses. Will begin looking at the data soon. 64 responses received.

Started a page - have only included data from the survey so far. Will begin to add lessons shortly:
https://www.mediawiki.org/wiki/MediaWiki_Developer_Summit_2015/LessonsLearned

More updates added, not quite finished. Comments so far?

Thank you, this is very interesting.

I think the level of detail is enough. What I miss is a first section highlighting the very few most importants lessons learned, that should be addressed in our plans for the Wikimedia Hackathon, the Wikimania 2015 hackathon, and/or the next edition of the Summit.

Now you really need to read the entire document in order to assure that you are not missing anything important (i.e. "Three day event, two days is not enough" would be a very important change, and it only appears in the middle of the page under "Other").

I added some of the main changes I would make for next year to the top of the page:
https://www.mediawiki.org/wiki/MediaWiki_Developer_Summit_2015/Lessons_learned

Very good! Have you seen the graphs offered in the Discussion page by @Yurik? I haven't looked at them in detail, but it seems that you can simply substitute the current tables with those graphs.

Once you feel you are done, this task can be closed.