| You beat me to it, Paul. What you describe is my memory as well. The minor tweak I'd make to the description of the process is that the compatible implementation themselves can do the work to send a PR to the specification page. As long as that PR comes with a link to an approved certification request, we're good. This is to keep it as scalable and self-serve as possible. If we have 100 implementations or 10 implementations filing a CCR every month, it doesn't create strain on one or two people in the spec project. The spec project only needs to slap an "accepted" label on the CCR and they're done. The Compatible Implementation does all the other work; creating their TCK results summary, filing their CCR, submitting PR to update the spec page once approved.
We should likely create a small half-page guide to getting yourself listed in N steps. It can have links to the appropriate process documents/sections.
Unrelated comment, I noticed the compatible implementation listed for JSON P is wrong. It says the compatible implementations name is "Jakarta JSON Processing 2.0.0." That's not appropriate. For 1.2 we used "Eclipse JSON Processing 1.1.5"
This is part of the Advance Implementation Neutrality topic in our 2021 plan. Thihup's implementation cannot be perceived as competing against "the official" Jakarta JSON Processing 2.0.0 implementation also called "Jakarta JSON Processing 2.0.0."
No implementation should be allowed to use the spec branding like that, even if it is in at Eclipse, a former RI, or happens to be in the same repo as the spec. The fact that the Eclipse implementation is in the same repo is something that needs to be fixed. Until we fix it, we still need to use neutral branding like "Eclipse JSON Processing" or "Eclipse Mail."
-- David Blevins 310-633-3852
I thought we agreed that a spec's project page would list all compatible implementations? Not just the implementation that was used for the ratification ballot.
The process is that any implementation that has passed the TCK for an individual specification and is in compliance with the EF TCK license can do a certification request against the spec project. The project reviews the request and if acceptable adds the implementation to the spec project page's Compatible Implementations list.
For example, if Jetty met the requirements for Jakarta Servlet they could do the certification request and be added to the list of Compatible Implementations
We loosely describe this process in the Jakarta EE TCK Process, see Certification of Compatibility. The language in that section needs to be tightened up in my opinion since it mixes considerations for getting listed on the Compatible Products page for compatible implementations of the Platform and Web Profile with what I described above.
Thanks ... Paul
Hi,
One of our Jakarta
EE users (@Thihup) has asked about publicizing his Compatible Implementation
for JSONP:
https://github.com/jakartaee/specifications/issues/326
As my remarks
in that Issue indicate, we have our Compatible Implementation page for
the Platform. But, we do not have a consistent means of publicizing
Compatible Implementations for individual Specifications.
- Do we
want to create a set of pages for the individual Specifications on jakarta.ee?
Letting it organically grow as new CIs become available... That
is, don't pre-populate a whole new set of pages. Just add pages as
these CIs become Accepted.
- Or, do
we want to push this down to each Specification Project to publicize as
they see fit? Maybe via github pages or the like.
- Or, other
ideas?
I'm leaning
towards option #1. Let's start the discussion. Thanks!
---------------------------------------------------
Kevin Sutter
STSM, Jakarta EE and MicroProfile architect @ IBM
e-mail: sutter@xxxxxxxxxx Twitter: @kwsutter
phone: tl-553-3620 (office), 507-253-3620 (office)
LinkedIn: https://www.linkedin.com/in/kevinwsutter
Part-time schedule: Tue, Wed, Thu (off on Mon and Fri)
_______________________________________________
jakarta.ee-spec.committee mailing list
jakarta.ee-spec.committee@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakarta.ee-spec.committee
_______________________________________________ jakarta.ee-spec.committee mailing list jakarta.ee-spec.committee@xxxxxxxxxxxTo unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakarta.ee-spec.committee
|
