Re: [eclipse-incubator-e4-dev] Summit preparation

[Mike Wilson <Mike_Wilson@xxxxxxxxxx>]

W.r.t. start times, getting us fed, etc. Lynn has offered to help with the logistics (woot! something good will happen <g>).

I like the idea of working through as many of the topics as possible, but based on conversations with Jeff McAffer about his experiences with the Equinox summits, I don't want to be too optimistic about how many we can get to on the first day. What do you think Jeff?

I do think there are some fundamental questions that we have to get agreement on first, like formally what the structure/leadership of the project will be, whether we have (or will have) enough people to address all of the topics, timelines, etc.

McQ.

"Jochen Krause" ---05/15/2008 12:21:11 PM---The e4 summit is approaching fast and I think we need some more preparation to make it a success. I

From:	"Jochen Krause" <jkrause@xxxxxxxxxxxxxx>
To:	<eclipse-incubator-e4-dev@xxxxxxxxxxx>
Date:	05/15/08 12:21 PM
Subject:	[eclipse-incubator-e4-dev] Summit preparation

---

The e4 summit is approaching fast and I think we need some more
preparation to make it a success. I would like to propose that we assign
(self-select) a lead for every work package defined in the agenda. This
lead will have to prepare a write-up (on the wiki) that offers some
guidance for the break-out session (at least as verbose as here
http://wiki.eclipse.org/E4/Eclipse_Application_Model) and also lead it.
Everybody else interested in the topic can provide a position paper,
which will assure him the opportunity to get heard.

This will also help everybody to prepare for the summit. Topics that we
don't find anybody to lead could be moved to the end of the summit with
the risk of not getting addressed at all.

As a result of each break-out session we should have the key findings /
open issues written down. I think it is essential that we also have the
names of people that will implement the stuff. Probably we should make
sure that we have the people to implement stuff before we get into a
lengthly discussion of a topic at all.

Currently we have 16 topics planned, that is only one hour per topic if
we do not have multiple things going on at the same time. There are a
lot of things that are interdependent, so I am having a hard time
splitting up the topics into more than 2 break out sessions. 

Here is a strawman for an agenda:

Day 1
All: Welcome, introduction and personal motivation
All: Architecture Foundation (goals)
2 break outs: Modelling the workbench, client-server split
All: Results, lunch
2 break outs: RCP, Flexible Resource Model
All: Results
2 break outs: Eclipse Application Model, skripting Eclipse
All: Results
2 break outs: Plugins implemented in other languages, Declarative UI
All: Results, Summary of the day

Day 2
2 break outs: SWT Browser edition, Build and Distribution
All: Results
2 break outs: Styling/CSS, e4 tooling
All: Results, lunch
3 break outs: e4 embedded, Commands, web based ide
All: Results
All: Architecture Foundation (decisions)


Also, when do we start and end on Thursday / Friday?

Jochen
_______________________________________________
eclipse-incubator-e4-dev mailing list
eclipse-incubator-e4-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipse-incubator-e4-dev