Sounds good! For both the creative part and NY, so I’ll try to find a flight with a NY layover
J
I think regarding the talk, I would like to show some nice integration between Mangrove and Stardust by showing some of the monitoring work, for instance updating
diagrams (Mangrove viewer, BPMN2, potentially SCA) with monitoring data coming out from Stardust. This is incipient but I’m hopeful we’ll have interesting stuff to show.
Cheers,
Adrian.
From: soa-pmc-bounces@xxxxxxxxxxx [mailto:soa-pmc-bounces@xxxxxxxxxxx]
On Behalf Of Marc.Gille@xxxxxxxxxxx
Sent: 02 October 2013 23:55
To: soa-pmc@xxxxxxxxxxx
Subject: Re: [soa-pmc] FW: [eclipse.org-planning-council] Reminder of "First Wednesday" Meeting, 10/2, 12:00 Noon (Eastern)
Absolutely. May need to be a little bit more creative than SOA Symposium though. Make sure that you can stay in NYC for one night or so. I will
take you out.
Marc
Hello guys,
Should we plan a common submission for ECON US 2013?
Cheers,
Adrian.
From:
eclipse.org-planning-council-bounces@xxxxxxxxxxx [mailto:eclipse.org-planning-council-bounces@xxxxxxxxxxx]
On Behalf Of Ian Bull
Sent: 02 October 2013 17:36
To: Eclipse Planning Council private list
Subject: Re: [eclipse.org-planning-council] Reminder of "First Wednesday" Meeting, 10/2, 12:00 Noon (Eastern)
As an agenda item, I'd like to remind everyone that the EclipseCon 2014 (North America) Call for Proposals is now available and the submission system is open.
As usual, there will be an early bird deadline: November 4th 2013 and the final submission deadline is November 18th.
Please pass this information along to the PMCs, Projects and Organizations you represent.
On Wed, Oct 2, 2013 at 7:35 AM, Doug Schaefer <dschaefer@xxxxxxx> wrote:
As promised, here is my proposal for requirements on projects who wish to do minor releases at SR time.
-
First major releases not allowed. Projects must maintain backwards compatibility with the release.
-
Projects must follow the ramp down schedule for the SR. The bits for the release must be made available at RC1 and can not be introduced later than that. Bug fixes of course can be made during
the release candidate cycle.
-
Release review material must be available to the community by RC1 to document the changes and new features in the release.
Like to keep it short and succinct. We can discuss and adjust at the meeting or here on the mailing list.
BTW, in full disclosure, CDT will be doing this for Kepler SR-3 with CDT 8.3. So I am in a bit of a conflict of interest here. But I do have vested interest in being clear
about the process.
Remember our regularly scheduled meeting is tomorrow, Wednesday, 10/2, at 12 Noon (Eastern).
Please arrange for a delegate if you can not attend.
There's not much on the agenda (representatives are free to add items, if I've forgotten anything) so I hope to discuss "action items", and spend some time discussing "Kepler retrospective"
to see if there is anything we should document.
http://wiki.eclipse.org/Planning_Council/October_2_2013
Thanks,
_______________________________________________
eclipse.org-planning-council mailing list
eclipse.org-planning-council@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipse.org-planning-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.
--
R. Ian Bull | EclipseSource Victoria | +1 250 477 7484
http://eclipsesource.com |
http://twitter.com/eclipsesource
|