[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
RE: [eclipse-incubator-e4-dev] Summit preparation
|
Hello Jochen,
Thanks for the Strawman Agenda as a first step.
Note that it looks like some additional topics will result from
the E4 discussion that we had at the EAC Phone Call today:
http://wiki.eclipse.org/Architecture_Council/Minutes_May_15_2008
I will merge the relevant results into the E4 Summit Wiki
tomorrow (likely evening CET).
While it's certainly great if leaders for implementation of
certain aspects can be found at the Summit already, I wouldn't
think that this is a requirement.
First of all, some great people will not be able to join the
Summit; second, if there is sufficient demand or interest for
a topic we can certainly find people to implement it (Yeah,
I'm optimistic on that one!); third, even at the end of the
Summit there will not be a sufficient amount of requirements
clarified to start implementation right away, especially
given the fact that many topics are interdependent; fourth,
Discussion of a topic might steer it in an unforeseen
direction, after which a leader might volunteer, so it would
be silly to not even start a discussion.
That being said, please DO search volunteers to lead
initiatives, but don't make the existence of leaders
prerequisite for getting stuff discussed.
Instead of a full Position Paper, I'd suggest that people can
also simply add some comment (can be few lines of text only)
to a topic's Wiki page explaining their standpoint. That's
likely less overhead than a Position Paper, and ensures that
Stuff gets sorted into the right buckets right away.
Are there any news regarding the Video Bridge? Also, what
would people think about making the "Result Sessions" available
in a shared Phone Conference for offsite people to dial in?
It's currently unlikely that I can personally attend the Summit,
but Michael Scharf and Doug Schaefer will attend on behalf of
Wind River.
Cheers,
--
Martin Oberhuber, Senior Member of Technical Staff, Wind River
Target Management Project Lead, DSDP PMC Member
http://www.eclipse.org/dsdp/tm
> -----Original Message-----
> From: eclipse-incubator-e4-dev-bounces@xxxxxxxxxxx
> [mailto:eclipse-incubator-e4-dev-bounces@xxxxxxxxxxx] On
> Behalf Of Jochen Krause
> Sent: Donnerstag, 15. Mai 2008 18:17
> To: eclipse-incubator-e4-dev@xxxxxxxxxxx
> 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
>
