iTC Meeting Minutes 2023 04 13 - DSC-iTC/cPP GitHub Wiki
Call started at 12:03pm EDT
-
The 1.1 first public draft will be targeted to be ready in mid-October before the ICCC
-
Brian will clear out the remaining issues from the Incoming Triage project and leave them for the v1.1 draft
The call started with a review of the current TD (DSC0005) that was ready to be published. It was agreed that this was good and so was merged to the IO site.
The next topic was a review of the Pull Requests for v1.1 based on the current TDs. These were reviewed on the call but need to be approved for merging. Brian will assign reviewers to look at them.
The next topic was then the remaining CCDB comments and whether any more need to be reviewed for TDs. It was agreed that the remaining issues can be handled in v1.1 as these were either minor enough to not be a concern or would possibly require enough changes to make the current evaluation problematic with a changing target.
The call then moved to a discussion of how to plan for the work on v1.1. It was agreed that the initial focus would be on the cPP updates and that after those were done, the focus would turn to the SD. While the cPP would be the focus, changes to the SD would not be disregarded, but generally would only be done during this time in conjunction with changes in the cPP as opposed to being from the SD itself. This would provide some additional focus. Brian thought that the easiest thing to do would be to start with the smaller editorial changes so everyone could get familiar with using GitHub and then move on to the larger projects.
Everyone has been asked to look over the cPP issues and to add labels to them for prioritization. Anything that looks to be a larger effort (such as those needing outside assistance) should be marked with a "2- Effort" so they can be noted as being larger.
Brian then asked what a good target date would be for having the first full draft ready for comments. He suggested being ready by the ICCC so it could be announced at that time it was open for public review. He said that based on the review process used by the Biometrics iTC it would be 3-6 months for the review process through to publication, and everything thought this would work. It was mentioned that last time this brought out a lot of questions about big changes, but Brian stated that we would scope the expectations to be focused on what was there, and no more, and that those would all be parked for v2. Brian marked the milestone for the v1.1 Draft as having a mid-October date so this can be seen.
There was then a review of the labels currently in the repository and some discussion about how to use them (mainly the numbered ones for determining priority by adding the scores together).
Lastly there was a brief discussion about using GitHub and some pointers for editing the documents. Brian pointed to the iTC WG Tools site for general documentation about creating the docs and general information. He also pointed to https://github.com/itc-wgtools/cPP-Tools/tree/master/User%20Guidance and the Syntax guide in that folder as providing a lot of examples for the documents. He did note though that the latest identifier codes in the cPP/SD may be more up to date than what is in that file, so it should always be double-checked (this is mainly for things like underline and line-through, pretty much everything else is good).
The next call will be next week and resume the normal biweekly schedule.
The call ended at 1:01pm EDT.