2017-09-05 Meeting notes
- Dennis Wisnosky
Date
Attendees
Agenda
1) Where we are on our road map.
2) Open Action Items
3) JIRA Issues Review - https://jira.edmcouncil.org/projects/RDFKIT/issues
4) Todays content discussion.
5) For next week.
Proceedings:
20170905 FIBO FPT RDF ToolKit
PR has made comments to DA's Publication notes. DA is aware but has not reviewed. The need is to provide advice to publishing from the FCT to the FLT Desire is to provide the publish process document as agnostic to tool.
DA - the Quality tools in the toolkit should keep tool errors from reaching the ontology. DA, Hygiene test are implemented but not deployed. Most banks enter the process through Protege which represents the higher risk for errors, however it may be the most common method to start.
DA - need Jacobus and Jim, and they are not present. Need to work the headless CCM effort
DA aware of discussion about release notes. Not a fan of automated release notes. TC It is important to have the resources to make the notes work. DA - It probably shouldn't or couldn't be anyone person, which shows a little issue with discipline for release notes. DA - Issue is having release notes for next FIBO release. JG believes release notes can be generated from JIRA and GitHub comments - DA They need to be organized. DW - had suggested notes for dev, the problem is for prod. MB/JA - use JIRA issue type to organize notes - MB suggest that closing comments could suggest the use for release notes in a way they can be automated for capture. This method requires an amount of discipline. PR - The pull request has comments as well. MB - User issue should have final say in what was done. TC This may be enforceable in JIRA. DA - I don't think so. It runs the risk of never closing the issue. JIRA admin can override problem with users not closing. PR - Let the pull request identify the reason why the pull represents the need for a change. The pull request can reflect the state of the process including the level of agreement. Requires no work flow for change. Represents final gate.
DA - this is a decision - release notes will be generated from pull requests. This is a mechanism that allows users to recognize the difference between the pull and FIBO Prod. DA will add to the publishing guidance.
DA - there should be a JIRA tix for getting the release notes comments in to the guidance. DA - thinks this is for the FPT to decide, FLT will need to be aware - maybe get FLT approval - rationale however is technical. DA - let FPT approve and give the FLT an opportunity to object.
PR will make the issue in Infra.
New issue - MagicDraw issue, DA work with Jim.
DA any new issues? Drop dead date for FIBO release should be 9/25. OMG is 29th - goal to make announcement. 29th is an opportunity to coordinate.
MB - roundtripping not going as quickly as would like. Progress is slow. issue is about .ext. requires a lot of changes for round tripping. DA - maybe need to review the process to make sure that expectations are not breaking the round tripping flow. DA - need to coordinate with EK. MB - change of domain case created a lot of work. DA - maybe this is not right - don't spin wheels on something that shouldn't have happened - check with JG.
PR remembered keeping with upper case. MB - EK made a lot of changes in FND relative to .ext. Need to clarify if changes are FIBO 2 or a longer term view. DA - maybe it is more 1.x until we get clarification of expectations for FIBO 2.
Pete - I raised INFRA-192 for the 4th maturity level. DA - MB write up task that DA needs to make to URI to support process policy change for hygiene.
RC - Not sure what that last discussion was related to.
MB will raise a JIRA on the disposition of W3CTime.
DA will get back to CCM issue - PR raise issue in Infra 192.
Decisions:
Generate release notes from GitHub Pull requests. Each person will need to document what is the effect of their Pull Request.