EST Work Group Agenda / Minutes
Date: July 25, 2017
Facilitator: Brian Pech
Note Taker: Brian Pech
|Andy Stechishin||CANA Software & Services|
|x||Lorraine Constable||Cognitive Medical Systems|
|Michael van der Zel||HL7 Netherlands|
|Nat Wong||HL7 Australia|
|x||Brian Pech||Kaiser Permanente|
|Wayne Kubrick||HL7 International|
|x||Laura Mitter||HL7 International|
|x||David Johnson (DJ)|
|Dave Hamill||HL7 International|
|Agenda Outline||Agenda Item||Meeting Minutes from Discussion|
|Insert Adgenda Topic in this column.|
2.) Motion to accept July 11 minutes. DJ/Lorraine. 3-0-0
3.) Deferred till next call.
4.) Motion to approved updated mission and charter. Lorraine/Laura. 3-0-0.
Chair will send updated M&C to Anne W. and EST & T3SD co-chairs.
5.) GitHub repository for HL7 organization.
People have to request access through DJ. Then work teams can add members to project specific repositories. For example, the Composite-KNART repo can add HL7 members who have been added to the HL7 repository. We want to have a designated team repository maintainer who manages the repository for the team.
The existing request form for gForge access was used as a starting point for designing a request process for GitHub access. Currently the form goes to firstname.lastname@example.org (alias for Anne Wizauer) this likely is not what we want on the GitHub site.
On the HL7 GitHub page the info says to email the email@example.com. for access. Is this what we to happen going forward? How can we streamline and keep the process simple? For now we want requests for HL7 GitHub access to go to the webmaster.
Comment - We want active projects to maintain current contact information on their repository information pages. Older completed projects would be archived.
All the HL7 GitHub repositories are currently publicly searchable. We do have the policy of 90 day exclusive use of HL7 members (of FhIR IP) but how we enable this has not been explicated.
It was noted that work group minutes and other supporting documents are on the GitHub/FHIR repository and really should be on GitHub HL7.
Do we want to come up with standards around how people name GitHub projects and project teams? Likely we do. We want the work group included in the name.
There are legacy HL7 items in private Git repositories we would expect them to move their materials to the official HL7 GitHub.
We probably want a page on the HL7 website with links to HL7 GitHub projects. (May be off the tools and resources page?)
6.) JIRA/Confluence - permalinks are ready, self registration is working, consult with Wayne for site easy of use.
7.) No website updates.
8.) Disaster Recovery - no updates.
9.) Next call - Aug. 8.
|Outline Reference||Supporting Document|
|Minutes from July 11|