Hi, this is how far the organization of the MediaWiki Developer Summit will go pre-scheduling plenary sessions and other sessions in the main room:

https://www.mediawiki.org/wiki/MediaWiki_Developer_Summit_2015#Schedule

There might be still adjustments driven by the owners of these sessions, but we have gone through enough planning discussions.

Regardless of whether you are attending the Summit or not, you can help making the most of each of these sessions -- and any Summit session. They all have a related task in Phabricator where the stuff that matters should be discussed and documented in their descriptions. Here are some ideas to raise the bar:

* Is the goal of the session declared, and is it the best goal we can aim for? * Is the scope of the session clear in itself and in relation to other sessions? * Is the description useful to understand the topic and be ready for a productive session? * Are there links to wiki pages, etherpad, slides, related sessions...? * Is the task associated to the appropriate projects in addition to #MWDS15? * Are there blocker/blocking tasks this session should be associated with? * After the event, is there an evaluation of the achievements of the session, and related notes?

Also, why waiting to the Summit when you can start to discuss / collaborate in the task itself? And why stopping after the event if there are open topics and actions left?

In other words, don't let anybody miss an opportunity like the MediaWiki Developer Summit in the topics that matter to you. Except supplanting the speakers, you have good tools to influence a session and drive it to the most successful outcome. Use them!