| Re: [jakarta.ee-spec] [Ballot] - Denoting which implementation was used to ratify a specification |
Hi,
On 23.03.21 20:51, David Blevins wrote:
> Quick community note based on offline feedback I got. Yes, everyone can vote. Like our release votes only the Spec Committee member votes are binding, but hearing from everyone is encouraged and welcome.
>
> If you have thoughts, go ahead and vote!
as non-binding vote, I vote for option 2.
I don't care which implementation was used for ratification because I'm using the one provided by my application server anyway. In my opinion the information about the implementation used for ratification detracts from the more important links to the documents and the implementations so it should not be listed at the top.
The information should be on the page, so I'm opposed to option 4.
>
>
> --
> David Blevins
> http://twitter.com/dblevins <http://twitter.com/dblevins>
> http://www.tomitribe.com
>
>> On Mar 22, 2021, at 11:00 AM, Paul Buck <paul.buck@xxxxxxxxxxxxxxxxxxxxxx <mailto:paul.buck@xxxxxxxxxxxxxxxxxxxxxx>> wrote:
>>
>>
>> The Specification Committee has discussed the proposal to demote on a specification page which open source implementation was used during ratification of the specification during a Release Review. There have been robust discussions on the mailing list and in meetings. Four options emerged which I have listed below. They have been mocked up by Ivar, see the PRs. Option 4 has no PR since it is the "do nothing" choice. Options:
>>
>> 1. Place an asterisk beside implementation in the list of Compatible Implementations (https://deploy-preview-338--jakartaee-specifications.netlify.app/specifications/jsonp/2.0/ <https://deploy-preview-338--jakartaee-specifications.netlify.app/specifications/jsonp/2.0/>)
>> 2. Provide a link to the Compatibility Certification Requests used for the Ballot at the bottom of the page (https://deploy-preview-337--jakartaee-specifications.netlify.app/specifications/jsonp/2.0/ <https://deploy-preview-337--jakartaee-specifications.netlify.app/specifications/jsonp/2.0/>)
>> 3. Include the compatible implementation in the list of release artifacts at the top of the spec page (https://deploy-preview-329--jakartaee-specifications.netlify.app/specifications/jsonp/2.0/ <https://deploy-preview-329--jakartaee-specifications.netlify.app/specifications/jsonp/2.0/>)
>> 4. Do nothing, as is, no denotation (https://jakarta.ee/specifications/jsonp/2.0/ <https://jakarta.ee/specifications/jsonp/2.0/>)
>>
>> Specification Committee members, please respond with your choice: 1, 2, 3, or 4.
>>
>> Thanks ... Paul
>> _______________________________________________
>> jakarta.ee-spec mailing list
>> jakarta.ee-spec@xxxxxxxxxxx <mailto: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
>
_______________________________________________
jakarta.ee-spec mailing list
jakarta.ee-spec@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakarta.ee-spec