Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: [eclipse.org-architecture-council] EAC / E4 phone meeting Thurs, May 15
Cool. Thanks, Fake Bjorn (???).
 
I can enter the moderator pin again if needed.

Cheers,
Doug.
 

From: eclipse.org-architecture-council-bounces@xxxxxxxxxxx [mailto:eclipse.org-architecture-council-bounces@xxxxxxxxxxx] On Behalf Of Bjorn Freeman-Benson
Sent: Thursday, May 08, 2008 12:19 PM
To: eclipse.org-architecture-council
Subject: Re: [eclipse.org-architecture-council] EAC / E4 phone meeting Thurs,May 15
Importance: High

Hello AC,

Bjorn isn't available until next Monday (May 12), but I checked his calendar and I don't see any conflict with the AC using his conference bridge at 8am PT on Thursday, May 15. Thanks.

On May 8, 2008, at 9:04 AM, Oberhuber, Martin wrote:
Hi Bjorn,
 
thanks to Doug Schaefer still having your conference bridge PIN, we ended up having
a pretty good EAC call today -- I will post meeting notes on the Wiki shortly. One
thing we decided was that we wanted another EAC phone call next week on
Thursday May 15, same time:
 
 
The topic should be around E4 Architectural Foundations, see the first Work Area on
 
We'd like to make the discussion open to anybody who wants to join, not EAC members only.
 
The question now is: Can we use your conference bridge for that meeting?
Or do you need it for another Foundation meeting next week?
 
Please let me know such that I can E-Mail and Blog the meeting details
including the call-in number.
 
Thanks,
--
Martin Oberhuber, Senior Member of Technical Staff, Wind River
Target Management Project Lead, DSDP PMC Member
 
 
_______________________________________________
eclipse.org-architecture-council mailing list
eclipse.org-architecture-council@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipse.org-architecture-council

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.

Back to the top