Stream: social
Topic: Typos
Grahame Grieve (Dec 01 2016 at 00:27):
I've just had a run on typo tasks in gForge. I'd like to thank everyone who's taken the time to report typos when they've found them - it definitely helps to improve the spec. I remember typos reported by @François Macary @Richard Kavanagh @Michelle (Moseman) Miller @Melva Peters in this bunch, though I know there are 100s more. thanks all, whether listed or not
Andy (Jan 29 2019 at 23:32):
The FHIR docs have so many typos - what's the best way to help fix them? on the issue tracker I see many tickets reporting typos that aren't addressed
Lloyd McKenzie (Jan 30 2019 at 00:10):
When you say typos that aren't addressed, do you mean that they're being ignored or that they're marked as applied but you're not seeing the fixes? Typos are only fixed in the "next" release. We don't go back and fix previous releases - with HL7 processes and the work of publishing, it's just not worth it. All submitted typos should be auto-approved and should be applied for the next release, though occasionally we run out of bandwidth to apply some of them.
Grahame Grieve (Jan 30 2019 at 00:11):
currently open 33 of 1553 reported - I think we're addressing them ok ;-)
Lloyd McKenzie (Jan 30 2019 at 00:11):
In any event, the correct answer is: Check to make sure the typo still exists at http://build.fhir.org and that it's not already reported and then submit to gForge
Andy (Jan 30 2019 at 00:48):
Edit: how do threads work
Last updated: Apr 12 2022 at 19:14 UTC
