On Thu, Jan 16, 2014 at 10:11 PM, legoktm <legoktm.wikipedia(a)gmail.com>wrote;wrote:
Given that the Configuration cluster had the second most number of
votes in the poll, why was it left of the agenda entirely?
We have been going back and forth between plenary session and breakout
session for Configuration, it's definitely on the table and I am 99.9% sure
that we will have a session dedicated to it. It's just not officially
slotted anywhere right now but I will check with Robla and see how we will
schedule this important cluster.
It not being in the program right now should not be seen as a sign that's
not important, on the contrary, we are just trying to find the most
appropriate slot for it.
On Thu, Jan 16, 2014 at 10:47 AM, Diederik van Liere
The Program Committee for the Architecture Summit has published a
Highlights of the Program:
1) We have tried to incorporate flexibility into the program by allowing
unconference break-out slots, 1 open plenary
session and a daily ‘agenda
bashing’ session to make adjustments to the program if the need arises.
2) There are 3 plenary sessions: HTML Templating (
Service Oriented Architecture (
and one open slot. Possible candidates for the
open session include
Performance and UI styling but this will be decided during the Summit.
short list will include the higher vote-getters
in the straw poll, so if
there’s one of the clusters you strongly feel should be part of the
program, now is your time to make that case.
Make that case where? Given that slidedecks are supposed to be
prepared, shouldn't this be decided beforehand rather than waiting?
* 4 unconference slots
There will be a round of Lightning Talks at the beginning of the plenary
session after the breakout session to summarize what happened by
the following questions:
a) What did you try to achieve?
b) What did you decide?
c) What are the next steps?
4) Architecture Panel and Value discussion. This is a plenary session for
the architects to share what they value in good architecture, as well as
talk about how they see the architecture of MediaWiki evolving, and what
role people other than our historical core group of three have to play in
the process. During this session, we hope to at least answer some of the
questions outlined in the recent discussion of the RFC process
5) RFC roulette: a one hour closing session for RFC’s that have not been
the spotlight during the Summit and where the
next step can be decided.
This is intended to be fast paced and slightly chaotic. If you would like
to hear what’s next for your RFC please participate with the roulette by
adding your name to
What does the Program Committee expect from summit participants?
a) If you are a participant, please familiarize yourself with the latest
version of the RFC’s that you care about.
b) If you are an author of an RFC that is scheduled in a plenary session,
please start preparing in collaboration with the other authors from the
same session on a short slidedeck that summarizes all the different
One slide that could be really useful is to have
a matrix that highlights
key differences between alternative / competing proposals. Diederik will
contact the folks who are invited for the plenary session to help
coordinate and organize.
c) If you are an author of an RFC that is scheduled in a breakout
please create maximum 3 slides that summarize
your RFC and think about
you want to get out of your session. The slides
are optional, but the
requisite level of preparation is not.
d) If you want to run an unconference slot then start thinking about a
theme and possible co-organizers. It’s okay to use an existing RFC
Two quick final notes:
The Program has been created using the input from the straw poll (
from the Program Committee and input from the
Engineering Community Team.
To see which RFC’s compose a cluster please have a look at
Looking forward to your feedback!
The Program Committee
 Discussion of the RFC process:
Wikitech-l mailing list
Wikitech-l mailing list