| Re: [science-iwg] Unconference at EclipseCon Europe 2016 |
|
Hello, Matthew Webber or build and test senior engineer and one of the people pushing through e4 platforms for us, as well as many other upgrades, will be at Eclipse
Con this year. I asked the DAWN team and because of the proximity of the NoBUGS conference there will not be anyone from them. Best Regards, Matt From: science-iwg-bounces@xxxxxxxxxxx [mailto:science-iwg-bounces@xxxxxxxxxxx]
On Behalf Of Jay Jay Billings Okay, final thing for real and then I gotta check out of my hotel and hit the road! ;) Erwin and I were just talking and he shook loose a thought - there should probably be a plan to discuss migration of our projects from the Technology TLP to the Science TLP. That is probably a necessary prerequisite to the Eclipse for Scientists build. Jay On Sep 14, 2016 6:57 AM, "Jay Jay Billings" <jayjaybillings@xxxxxxxxx> wrote: One other thing - I think it is also important to keep in mind that the new Science TLP PMC will be in charge of dealing with the technical details of that type of "Eclipse for Scientists and Engineers" release, which was one of the major goals of creating
that project. It just so happens that most of this group will be on the PMC! ;) Jay On Sep 14, 2016 6:46 AM, "Jay Jay Billings" <jayjaybillings@xxxxxxxxx> wrote: Nice list guys! I'm sorry I'll miss the meeting. I think you already know this, but for some of the things like "road map for the next x months," please keep in mind that they affect the whole group and you should consider what you discuss provisional until the steering committee and the whole group has
a chance to review it. Also, for the Eclipse for scientists thing, we have discussed this many times. The answer is yes and the plan has been to do that for our second release, or a later one, if possible. That's why our first release is about unifying so much of our architecture;
we need to make everything work together to create that big, combined product. After we can make that big product, we would basically join up with the simrel. My hope is that we can do all of this for Oxygen next year, but that might be pushing it. Some of
the challenges include getting all the participating projects on the same dev version/target, identifying all the pieces, providing some amount of common API, etc. With the latter, we don't want a situation where, for example, we have multiple tools with the
exact same functionality (like multiple plotting tools) crammed into the product with multiple APIs. Apologies for typos; I just woke up! Jay On Sep 14, 2016 4:31 AM, "Erwin de Ley" <erwin.de.ley@xxxxxxxxxx> wrote: great. I've added some topics to discuss. Just some ideas. Hi all,
-- This e-mail and any attachments may contain confidential, copyright and or privileged material, and are for the use of the intended addressee only. If you are not the intended addressee or an authorised recipient of the addressee please notify us of receipt by returning the e-mail and do not use, copy, retain, distribute or disclose the information in or attached to the e-mail. |