Re: [jakarta.ee-spec.committee] TCK process and committee operation docs

[Alasdair Nottingham <alasdair.nottingham@xxxxxxxxx>]

I’ve converted the project names and codes into an asciidoc and created a PR here: https://github.com/jakartaee/specification-committee/pull/6

There are a few things I’ve noticed (and this isn’t complete).

I can’t find the github repo for the following specs:

* Jakarta Debugging Support for Other Languages (part of ee4j.jsp)
* Jakarta Web Services Metadata (part of ee4j.jaxws)

I also notice there are a few places where the PR’s for the specs don’t follow the codes in the original spreadsheet. For example:

* tags -> JSTL
* xml-ws -> xml-web-services
* restful-ws -> restful-web-services

I don’t know if we want to update the project codes to match what is being used in the specs, or vice versa. I updates tags to jstl in the asciidoc, but I’m not sure if that was right.

The JAX-WS specs also have inconsistent spec names to codes:

* Jakarta SOAP Attachments -> soap
* Jakarta XML Web Services -> xml-ws
* Jakarta Web Services Metadata -> ws-metadata

it kind of seems to me that soap seems overly general for SOAP Attachments, and it kind of seems odd that they don’t all have a common prefix (either ws or xml-ws).

Not sure if any of this is important, but having noticed it I wanted to raise it.

Thanks
Alasdair

> On Jul 29, 2019, at 6:22 PM, Bill Shannon <bill.shannon@xxxxxxxxxx> wrote:
> 
> Alasdair Nottingham wrote on 7/29/19 3:01 PM:
>> Hi,
>> 
>> Last week I moved the TCK process google doc and the Committee Operation doc into the Jakartaee specification-committee git repository. There were a few things that I didn’t close out before it merged so I’d like to discuss briefly since I think they need to be fixed soon.
>> 
>> The TCK doc refers to this google doc:  https://docs.google.com/document/d/10Q8IPpnbU5E1671bnRkMZsPkLU1aWfL6PkP4kzVPqLE/edit#heading=h.njmsb6fbebb3
>> I don’t have access to it and I don’t think the info should be  hidden given the TCK process isn’t. If someone could give me access I’m happy to take a look and either move it to the github org or do a PR to link elsewhere.
> 
> Fixed. I changed the link to the public version of the document.
> 
>> The operations doc has 4 references to the Project Names and Codes spreadsheet: https://docs.google.com/spreadsheets/d/18SraPxRBCOyaS6w-UV6TR-UA1bWy1--sV0ky6msAjWY/edit#gid=0
>> 
>> I similarly would prefer this to be available either through github or elsewhere, but I didn’t want to presume and just move it so I’m emailing to get peoples views on this.
>> 
>> In general I’d prefer links from these docs to either be to jakarta.ee, eclipse.org, or somewhere else in the same github repo.
> 
> Yes, this should be translated into an AsciiDoc table and added to the
> jakarta.ee web site somewhere.