I think there are other areas, e.g. something similar to the Spec Lead Guide https://www.jcp.org/en/resources/guide the JCP had, where we can help together with the Jakarta EE Ambassadors. Our NoSQL talk yesterday at Percona Live was pretty well received and we have already been confirmed to hold it at 3 other online conferences including Devoxx Ukraine in the next 3 weeks. Together with what was discussed on Community Day this week I guess those may help understand what a NoSQL spec could need and what other solutions already exist on the JVM. Werner To be honest, I think the likelihood is very small Microsoft would help much with Jakarta NoSQL. From my personal perspective, it feels the basic focus now honestly is still on Java EE and strengthening the partnerships with the major Java EE runtimes vendors. Now, of course I know without moving Jakarta EE forward, the runway for that work stream may be pretty uncertain. I am trying to help Jakarta NoSQL from the community end the best I can. I think employees at vendors and users could seek to do the same. Where I think help is most needed right now is the website, documentation, samples, real world testing, evaluation and adoption. Based on my limited evaluation so far, the technology itself seems to be OK although it definitely feels immature. That's why I say it still needs about six months to really enter the Jakarta EE mainstream. For example, I am not sure how to reconcile that the entire graph communication layer has a heavy Apache project dependency. I do think it can get there with some real good faith help. Jakarta EE Ambassador, Author, Blogger, Speaker Please note views expressed here are my own as an individual community member and do not reflect the views of my employer. Sent via the Samsung Galaxy S7, an AT&T 4G LTE smartphone -------- Original message -------- From: Werner Keil <werner.keil@xxxxxxx> Date: 10/13/20 9:50 AM (GMT-05:00) To: Jakarta specification discussions <jakarta.ee-spec@xxxxxxxxxxx> Subject: Re: [jakarta.ee-spec] BALLOT: Approval of the plan for JakartaNoSQL 1.0 It was never targeting Jakarta EE 9 anyway and how the release Train Looks for 10 remains to be seen, also the exact Content, but the candidates are not so many right now, and MVC is not implemented by another Independent Project or Vendor either, plus it has massive Competition by Spring MVC. While not enough is known about production usage (most customers won’t use anything before 1.0) the supported DB Systems are quite impressive already: http://www.jnosql.org/ I know, Reza is not speaking for his employer, but many of them including NoSQL on Azure, Oracle NoSQL, Hazelcast, etc. are supported, so it seems beneficial for most vendors if a Jakarta EE application can also support them as easy as JPA or JDBC do there already. Werner This is a really tough one. I think Jakarta NoSQL needs a bit more time to mature - maybe about six months more or so. The best way to help it is to evaluate, contribute and use it in production. Reza Rahman
Jakarta EE Ambassador, Author, Blogger, Speaker
Please note views expressed here are my own as an individual community member and do not reflect the views of my employer. On 10/12/2020 2:53 PM, Scott Stark wrote: + 0 for Red Hat. We would like to see industry demand shape the specification and evolve additional implementations. Andrew Pielage Java Developer at Payara Services Ltd Open Source Enterprise Software & Support 
Greetings Jakarta EE Specification Committee. I need your vote to approve the plan for Jakarta NoSQL 1.0. The JESP/EFSP requires a successful ballot of the Specification Committee in order to ratify the products of this release as a Final Specification (as that term is defined in the EFSP). The relevant materials are available here: https://github.com/jakartaee/specifications/pull/236
https://deploy-preview-236--jakartaee-specifications.netlify.app/specifications/nosql/1.0/ Per the process, this will be a seven day ballot, ending on October 12, 2020 that requires a Super-majority positive vote of the Specification Committee members (note that there is no veto). Community input is welcome, but only votes cast by Specification Committee Representatives will be counted. The Specification Committee is composed of representatives of the Jakarta EE Working Group Member Companies (Fujitsu, IBM, Oracle, Payara, Red Hat, Tomitribe, and Primeton), along with individuals who represent the EE4J PMC, Participant Members, and Committer Members. Specification Committee representatives, your vote is hereby requested. Please respond with +1 (positive), 0 (abstain), or -1 (reject). Any feedback that you can provide to support your vote will be appreciated. Thanks … -- Ivar Grimstad Jakarta EE Developer Advocate | Eclipse Foundation, Inc. Community. Code. Collaboration. Join us at our virtual event: EclipseCon 2020 - October 20-22 _______________________________________________
jakarta.ee-spec mailing list
jakarta.ee-spec@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakarta.ee-spec
_______________________________________________ jakarta.ee-spec mailing list jakarta.ee-spec@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakarta.ee-spec |
