Stream: fhir/infrastructure-wg
Topic: Volunteers needed
Lloyd McKenzie (Feb 16 2021 at 04:10):
As discussed on today's call, FHIR-I has over 700 changes waiting to be applied to the core specification. @Alexander Zautke has agreed to take those related to StructureMap/Mapping language. I've taken all those related to Questionnaire, QuestionnaireResponse and schematron. I've left all the tooling-related ones to Grahame. That still leaves about 500 changes, many of which can be done by anyone. We need volunteers to assist because there's no way Grahame can do all of them (or probably even half).
I've categorized them in 4 priority levels:
Highest priority are the technical corrections for R4 that ought to be included in R4B. These need to be applied to the R4B branch by about the end of February (and should be applied to R5 at the same time - just submit your branch as a PR against both).
Very High priority are the changes to normative artifacts which are either substantive, or occasionally non-compatible. We really want those applied before our final freeze deadline for the R5 "for comment" ballot by end of March
High priority are all other changes to normative artifacts wish should be in by end of March and definitely needed before the R5 ballot deadline mid-July
Medium priority are all changes to non-normative artifacts which are substantive or breaking and must be in by mid-July
Low priority are all non-substantive changes to non-normative artifacts which should be made by mid-July, but in theory we could apply later
If you find something you're sure that only Grahame can do, assign it to him. He'll likely tackle these first.
When working on a resource or page to do higher-priority items, please scan for other stuff on the same page/in the same artifact. If you can knock off some easy low priority items at the same time, please do. Please tie your commits to the tracker items fixed and be sure to mark them as 'Applied'.
When you're working on something, assign it to yourself so we don't duplicate work. (But don't assign something to yourself unless you're actually going to work on it and commit it in a reasonable timeframe.)
If you don't have commit privileges or ability to mark things as 'Applied' in Jira and would like to help out, send me a PM.
The list of outstanding tracker items is here: https://jira.hl7.org/issues/?filter=13755
If you have questions, shout.
Gino Canessa (Feb 16 2021 at 14:57):
I'll go through the subscriptions-related ones this week; most are applied (from before I had access to update the tickets). I think that's about 25 more off the list (if my local count is correct).
Josh Mandel (Feb 16 2021 at 15:54):
Regarding changes that need to be applied to R4B as well as R5 -- I don't think it will be possible to submit a single pull request for both purposes, but we can "git cherry-pick" specific commits once they have been merged into R4B. For example, we might want to create pull requests against R4B and apply a specific label like "needs R5 cherry pick" in github. Then we can go through and update the labels to indicate status as we perform the cherry picking.
Yunwei Wang (Feb 18 2021 at 01:49):
Hi @Lloyd McKenzie : I would like to confirm the process:
1) select a ticket from https://jira.hl7.org/issues/?filter=13755
2) assign the ticket to myself
3) create a branch from master@HL7/fhir repo
4) fix StructureDefinition xml
5) create a PR review (I am not sure here. Is it one PR per ticket or not necessary?)
6) change the ticket to applied (is this before PR or after merge?)
Lloyd McKenzie (Feb 18 2021 at 01:57):
- Commit your branch and in your commit, indicate the ticket(s) addressed
- Create a pull request against the core spec from your branch
- Add a comment indicating the PR # associated with the ticket(s)
- Once merged, mark the tickets as applied
Yunwei Wang (Feb 20 2021 at 15:16):
I saw some of them were already fixed in R5, like this one: https://jira.hl7.org/browse/FHIR-25262 though the ticket status is still "RESOLVED - CHANGE REQUIRED". What do we do with those ticket?
Lloyd McKenzie (Feb 20 2021 at 17:29):
If it's already done, just mark it as applied
Lloyd McKenzie (Feb 20 2021 at 17:29):
(in Jira)
Last updated: Apr 12 2022 at 19:14 UTC
