[eclipse.org-architecture-council] AC Face-to-face at EclipseCon
I'm afraid that many of the AC members will want to lead BoFs themselves
on behalf of their projects, so an AC BoF might cause some conflicts. I
know that 2 years ago, there were some council meetings on Sunday
afternoon before EclipseCon.
Bjorn: you likely have the best overview on the conference schedule,
could you propose a meeting slot for the AC?
All: is anybody opposed to meeting on Sunday afternoon?
For the BoF, I have a different idea: what if we proposed an AC BoF as a
Community Event, where some (but not all) AC members are there for
answering questions. Title could be like "Ask the Mentors", or
"Challenge Eclipse". We might get some valuable input, and have the
chance to evangelize some concepts. What do you think?
Or, as an alternative what about an EclipseCon Panel with some AC
members on "hot chairs" for asking questions?
Martin Oberhuber, Senior Member of Technical Staff, Wind River
Target Management Project Lead, DSDP PMC Member
> -----Original Message-----
> From: eclipse.org-architecture-council-bounces@xxxxxxxxxxx
> On Behalf Of David Carver
> Sent: Friday, November 21, 2008 6:41 PM
> To: eclipse.org-architecture-council
> Subject: Re: [eclipse.org-architecture-council] Face-to-Face
> meeting at ESE
> Gunnar Wagenknecht wrote:
> > Oberhuber, Martin schrieb:
> >> For those who have not been there, I'm looking forward to
> seeing you at
> >> EclipseCon, but of course you can also join the offline
> discussions :-)
> > I'm not sure if I remember correctly but at the first ESE
> in Esslingen
> > all the councils met one day before the conference start on
> Monday. This
> > won't work for EclipseCon, though. (Because of the
> tutorials). But it
> > might be an option for next year to remember.
> Could do an Architecture Council BOF at EclipseCon.
> eclipse.org-architecture-council mailing list
> IMPORTANT: Membership in this list is generated by processes
> internal to the Eclipse Foundation. To be permanently
> removed from this list, you must contact emo@xxxxxxxxxxx to
> request removal.