[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [ee4j-community] JCP and existing specs
- From: "Markus KARG" <markus@xxxxxxxxxxxxxxx>
- Date: Fri, 1 Dec 2017 13:19:50 +0100
- Delivered-to: email@example.com
- Organization: Markus KARG, Staatl. gepr. Inf.
- Thread-index: AdNqlLiuv6LJpxa7SJyVI4gPptXK5gACZgZg
I second that, but additionally it was said that the Eclipse Foundation is
not a standardization organization, so this should be done elsewhere. As
currently there is only one other instituation allowed to use the word
"Java", this implies -at least currently- that the JCP is that "elsewhere".
Anyways, I think that Oracle should speak clear words now. Either shutdown
the JCP and strengthen it. But it makes no sense that people like us discuss
this. We have no say in that. Java (still) is Oracle's trademark.
[mailto:ee4j-community-bounces@xxxxxxxxxxx] On Behalf Of Heiko Rupp
Sent: Freitag, 1. Dezember 2017 12:08
To: EE4J community discussions
Subject: Re: [ee4j-community] JCP and existing specs
On 1 Dec 2017, at 11:57, Markus KARG wrote:
> The plan to code first and then ask another institution for
> standardization was publicly confirmed at EclipseCon 2018
I did not understand it that way. Rather that a EE4JCP would still need to
Code first was meant, from how I understood it, to have something to discuss
with users so that it gets "hardened" before cast in stone^wspec text.
ee4j-community mailing list
To change your delivery options, retrieve your password, or unsubscribe from
this list, visit https://dev.eclipse.org/mailman/listinfo/ee4j-community