20181112 Community Meeting Minutes

How to shape the Community Standup

Welcome to the first meeting!
We will record the meetings. What about Live Streaming them on Youtube?
Let's be bold and just share the meetings link publicly.
Current time is good for EU + AU, but not for US. What about US? Shall we alternate? Let's wait for a US contributor before we worry about this.
Frequency: every 2 weeks at 11AM Amsterdam time.
Meeting notes: to the github wiki (here)

Marco reports: Build and CI moved to Azure DevOps
AppVeyor is now inactive
Every merged PR will now create a new alpha on the public MyGet feed
MyGet FHIR API-alpha stream: https://www.myget.org/F/fhir-net-api/api/v3/index.json
We have published beta1. From now on, not everything that gets pulled into develop will automatically make it into beta2. We'll do this using release branches

We will announce 1.0.0-beta1 publicly at DevDays Amsterdam
For the announcement we'll need to create the release notes, drawing attention to the changes in the parsing subsystem.
Brian still has several PRs (one posted, one only on his machine) that we want to integrate for beta2.

It's clear that DSTU2 and 3 won't go away, so we need to make it easier to re-use code amongst the DSTU2/3/4 branches to avoid merge conflicts when backporting functionality.
We will need to share more code across different versions of FHIR, so for the mid-longer term we need to isolate code that is really dependent on DSTU-functionality from stuff that can be shared.
We can do this by splitting up the Core and Specification assembly (totally version-specific now):
- POCO-dependent assemblies that contain truly version-specific classes and functionality
- POCO assemblies that can be shared across versions (e.g. one single Resource class, one set of ResourceResolver classes)
- Totally POCO-independent assemblies (FhirPath, ElementModel, Serialization, and in the future validation).

R4 publication is now in freeze, we can do a "final" generation of the POCO classes.
Unification of T4 macro .tt files
- Brian has merged all the separate .tt files (with lots of duplicate code generating both datatypes and resources) into one, so including generation of model info, enum generators.
- Brian found inconsistencies in the generation of datatypes, most notably the handling of markdown properties.
- Q: What to do with this .tt file -> EK likes to have it backported to DSTU2 because we need to maintain DSTU2 for a long time, and having different system will hurt us in the future. Argument against is that they are hardly ever changed, and it is real work, so you cannot easily backport the code, you have to manually merge the .tt files for the other FHIR versions.
- For R4 (the new .tt files) at least, we like switching to the new package files.
- There was an inconsistency in generating the Markdown property: both the xxxxElement : Markdown and xxxx were of type Markdown, we can now split it up into xxxElement:Markdown and xxxx:string. But that's a breaking change and it changes the IConformanceResource interface too. We discussed and don't mind doing this as a breaking change in the current R4 release.
Merging the non-poco stuff into the R4 branch
- All the changes from R3 have been merged into R4 into a separate branch
- Ewout has fixed the merge conflicts.
- Marco has started fixing the unit-tests

EK: Check whether we can stream zoom.us meetings to Youtube.
EK: Create release notes.
EK: Announce beta1, and alpha feed.
BP: Post new PR with bug fixes for beta2
BP/EK: will look at Brian's current R4 PR to split off stuff that is relevant for 2 and 3 too.
MV: Continue on fixing the unit-tests on R4