I as a JSR contributor and not an EG member, but did some work on Soteria and also would like to join there.

I would like to join. Sent via the Samsung Galaxy S7, an AT&T 4G LTE smartphone

Hi David, I committed some code for Soteria and was a member of the EG. I also would like to be added as an initial committer of the EE4J projects. thx Rudy

I should also be on the list of initial committers at least I told Dmitry who asked for Oracle that I would like to join JSON-P, Security and JMS-related projects. Kind Regards, Werner

Hi I already volunteered separately, so my name should already be on the list, but to be sure I of course like to be involved again ;) I've got a list of small enhancements that are quite trivial to

If you could add me please, am actually also in the process or working on using the RI for WildFly - as I do that I expect I will have a lot of contributions related to the conversion from PicketBox

We're currently seeding two projects with initial committers we'd like to make sure the existing EG can get their names on the initial proposal. Of course everyone can join after, but it's always

Hi, I am currently helping a large client who needs Role and Identity Management in a Microservice environment using Java EE (Payara to be more precise, which helps because it got Soteria built-in

Inline. I'd say it's more than a proposal -- JSR-375 will definitely be moving to Eclipse as soon as we can make it happen. Perhaps. I can't guarantee a timeframe more

Will/all, I'm not sure, what Oracle plans for Java EE 8, but JTA just launched a MR 6 and that's clearly not yet targeting EE4J

Thanks a lot Will for taking care of this. That second batch of project donations would mean there's a proposal for an Eclipse project, which is far away from a repository we can contribute to, right?

Access to the branches shouldn't be an issue -- I can open it up or merge changes as needed. More of a problem is publishing to maven.java.net. I don't know how to get the maven release

Hi, There’s some things that could indeed go into an extended RI, but the API is just as frozen for the RI as for others. I don’t know at this point if it’s possible to release new RI versions

I can't speak to what was done with JSON-P, but I think Bill's point is that any changes to the spec/api at this point need to follow the JCP process, or they aren't "official" -- they can't be

While I see the point of the independent library, I still advocate for a good RI that goes beyond the spec. A 3rd party library reaches more people, but what's the benefit of having 5 different

I hope everyone is clear, that javax.json-api is the API/Spec, not implementation of JSR 374? I asked Dmitry, if they were intended to be merged into the EE4J project or a fix/Patch, etc. of Java EE

I hope everyone is clear on the difference between spec and implementation. Spec changes require use of the JCP, implementation changes do not. If there are bugs in the Soteria

Hi, I spoke with David Delabassee yesterday after his Java EE talk at JVM-Con. He sounded quite reluctant of a MR. So better wait for EE4J. However, if you look at JSON-P, at least 2 "patch" releases

Hi, First of all thanks for the reply, good to see you here again ;) There's some things that are best changed in the API, specifically the CDI 2.0 inspired annotation instances/builders. If I'm not

Hi All, I'm discussing this internally to figure out what the best way forward is. Conceptually, of course, an MR is what we want, but as Bill pointed out to me, an MR couldn't be