Re: [eclipse.org-architecture-council] Fwd: [ec] 16 February 2016 EC bal

[Tom Schindl <tom.schindl@xxxxxxxxxxxxxxx>]

Hi,

I'm only listed as an interested party, but I'm not on the expert group!

I contributed to some discussion
(http://jsr377-api.40747.n7.nabble.com/) where I provided input how we
addressed things when we implemented/designed e4. I know Andres from
various conferences and he's fairly open minded although because he's
the author of griffon he might be trying to push this one forward.

What I think is interesting on the JSR is that it's targeting embedded
as well which e4 itself is most likely too heavy weight.

We (BestSolution) hoped to have more time to contribute to the JSR and
push it towards better alignment with e4 but decided to put our
resources solely on e4 (+JavaFX).

I would welcome if someone who really knows the Eclipse 4 Architecture
would contribute to the JSR because it would certainly be good if
Eclipse 4 applications could host components written against the JSR377
API without too much hassle.

Tom

On 18.02.16 15:31, Lars Vogel wrote:
> IIRC Tom Schindl is part of this JSR
> 
> On Thu, Feb 18, 2016 at 3:03 PM, Mike Milinkovich
> <mike.milinkovich@xxxxxxxxxxx <mailto:mike.milinkovich@xxxxxxxxxxx>> wrote:
> 
> 
>     Dear AC members,
> 
>     We would be particularly interested in your thoughts on JSR 377
>     <https://jcp.org/en/jsr/detail?id=377> the "Desktop|Embedded
>     Application API". This seems to be somewhat competitive with the
>     Eclipse RCP platform.
> 
>     -------- Forwarded Message --------
>     Subject: 	[ec] 16 February 2016 EC ballot reminder: 2 items for voting
>     Date: 	Tue, 16 Feb 2016 09:46:24 -0800
>     From: 	Harold Ogle <harold@xxxxxxx> <mailto:harold@xxxxxxx>
>     Organization: 	JCP
>     To: 	ec@xxxxxxx <mailto:ec@xxxxxxx>
> 
> 
> 
>     This is a courtesy reminder that the EC Ballot is available, and there are two items on the ballot for voting.
> 
>     https://jcp.org/en/ec/ballot
> 
>     ***NEW ITEMS***
>     JSR 377 - Desktop|Embedded Application API - JSR Renewal Ballot
>     Last day to vote: 29 February 2016
>     URL for JSR proposal:
>     https://jcp.org/en/jsr/detail?id=377
>     The Specification Lead has provided the following to demonstrate that the JSR should be approved to continue:
>     "Development of the JSR-377 spec was successfully started in early 2015 
>     and continued of to this date. Online discussions and face-to-face 
>     meetings have occurred during the whole year, this includes EG members 
>     and external contributors. A version of the current API design has been 
>     posted to the code repository. Still pending: posting updates to the 
>     specification documentation with more explanations of the overall design
>      and reasoning behind each of the API's elements."
> 
>     JSR 364 - Broadening JCP Membership - Final Approval Ballot
>     Last day to vote: 29 February 2016
>     URL for FAB materials:
>     https://jcp.org/aboutJava/communityprocess/final-draft/jsr364/index.html
> 
> 
>     -----------------------------------------------------------
> 
>     EC representatives can log in to the ballot page (http://jcp.org/en/ec/ballot) or on the EC private page (http://jcp.org/en/ec/my) using their own SSO logins. When there are ballot items, please try to log in and vote early, so that you can send us any questions about your login before the ballot closes. Ballots are usually two weeks long, so you have plenty of time to vote before the last day. 
> 
>     The voting deadline for any ballot is 23:59:59 Pacific Time of the last day to vote of the ballot. To be counted, your vote must be placed before that time. You are encouraged to verify that your vote has been recorded after you cast it: check to make sure that the log reflects your comments and the tally of votes updates to include your vote. If you have any difficulty casting your vote during the ballot, contact pmo@xxxxxxx <mailto:pmo@xxxxxxx> **immediately**, explaining the problem, and state what your vote is (along with any comments), so that it can be recorded if the problem persists. If the primary EC representative cannot cast the vote for whatever reason, it is the job of the alternate contact(s) to cast the vote instead. Making sure your votes are cast is a big reason why you have alternate representatives.
> 
>     EC accounts are tied to the individual EC representatives, and are the same login credentials used elsewhere on the site. Each EC Member representative - primary and alternates - has permissions to cast votes and access EC meeting agendas and other EC-private information. If your EC Member wishes to add or remove a particular representative, the primary EC representative should contact admin@xxxxxxx <mailto:admin@xxxxxxx> with the details of the change. New representatives will need to register their own SSO accounts on jcp.org <http://jcp.org> and verify their e-mail addresses before the PMO can add EC privileges. 
> 
> 
> 
> 
>     This email has been sent from a virus-free computer protected by Avast.
>     www.avast.com <https://www.avast.com/sig-email>
> 
> 
>     _______________________________________________
>     eclipse.org-architecture-council mailing list
>     eclipse.org-architecture-council@xxxxxxxxxxx
>     <mailto: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 <mailto:emo@xxxxxxxxxxx>
>     to request removal.
> 
> 
> 
> 
> -- 
> Eclipse Platform UI and e4 project co-lead
> CEO vogella GmbH
> 
> Haindaalwisch 17a, 22395 Hamburg
> Amtsgericht Hamburg: HRB 127058
> Geschäftsführer: Lars Vogel, Jennifer Nerlich de Vogel
> USt-IdNr.: DE284122352
> Fax (040) 5247 6322, Email: lars.vogel@xxxxxxxxxxx
> <mailto:lars.vogel@xxxxxxxxxxx>, Web: http://www.vogella.com
> 
> 
> _______________________________________________
> 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.
> 


-- 
Thomas Schindl, CTO
BestSolution.at EDV Systemhaus GmbH
Eduard-Bodem-Gasse 5-7, A-6020 Innsbruck
http://www.bestsolution.at/
Reg. Nr. FN 222302s am Firmenbuchgericht Innsbruck