DRAFT - PENDING APPROVAL AT NEXT WG MEETING on 10/4
...
Attendees
Action Items
Tasks Identified and Assigned
- Present Use Cases at next FDC3 General Meeting (All)
- Page owners – add "page properties" module (All)
Overall Working Group Open Task List
| Task report |
|---|
| labels | fdc3_uc_working_group |
|---|
|
Decisions Made
- Use Case 1, 2, 3, 4, and 5 accepted
- Use Case 7 was rejected
...
| Time | Item | Who | Notes |
|---|
| 2 min | Commence Meeting & Select Scribe | group | Aaron Williamson volunteered to be scribe |
| 4 min | Review minutes from last meeting (9/6) and approve | group | Group agreed by acclamation to defer voting on 9/6 votes until next meeting, at which time meeting minutes for 9/6 and 9/20 (these minutes) will be reviewed and presented for approval. Kat agreed to include links in the next email to the group. |
| 3 min | Reviewing open action items | group | Kat marked the open item related to voting as complete. |
| 1 min | Housekeeping: Board Update, Meetup, OSSF | Rob U | Ben Gold from Wellington introduced himself . as a developer on the portfolio manager/investment side working on Wellington's integration with OpenFin. He said he'd just joined the group and would be working through the WG meeting notes to catch up. Rob Underwood mentioned that PMC program updates are due Tuesday 10/4. He also encouraged attendees to register for the 10/4 NYC Open Source in Fintech Event Series and the 11/14-11/15 Open Source Strategy Forum in London. |
| 10 min | Overview of approved FDC3 voting process | group | Standards Ratification Process- Saori
- It's very important that everyone reads these carefully
- Saori: What is this?
- We realized we need a process to govern how we approve standards, including how we approve items like use cases
- We realized that some of the steps required for other forms of technical standards were not needed to do approval of use cases
- What we do need to do for use cases that we approve we need to present to the general meeting
- Kat: I had a question → how do we want to manage this? Once it is approved, for each of the use cases, we will change the document status to "approved" going forward?
- Johan: How is that changed?
- Saori: I would suggest that the person that originally
- Rob: When you change status please use discussed the overall FDC3 voting procedures approved at the previous PMC meeting. She encouraged members to read the rules themselves and ask any questions they had. She noted that since the use cases produced by this group were not "standards" they would not go to the FDC3 leadership for a vote, but would simply be presented at the monthly FDC3 general meeting upon their approval.
- Kat asked how approved use cases would be marked and Saori suggested the original author should change the status flag on the use case upon acceptance by the WG.
- Johan asked how to change the flag and Tom said that it would be via a macro that would be included in the template for use cases.
- Rob suggested that when authors change the status flags, they include the date of ratification in the "What did you change?" field to reflect the vote itself related to the status change.
|
| 20 min | Next steps in use cases process - Confirm ownership
- Presentation to PMC and other WGs
| group | Voting ApprovalsUse Case 1Google Groups vote: All voted yes but Jonathan Teper, who voted to do "in review" I think we have acceptance. Kat made motion by acclamation to accept this use case. Hearing no objections the motion passed and use case 1 was accepted.
Use Case 2Use Case 3Use Case 44 votes 3 votes to approve 1 in review – uncertainty for the workflow comment from Johan. "It's the end application that is doing the work; I'm not sure where the interop functionality comes in" Kat made motion by acclamation to accept this use case. Hearing no objections the motion passed and use case 4 was accepted.
Use Case 5Use Case 6- Leslie: Needs to also consider situation where the app is already running
- Aaron: You might also set a date and action item for a 2nd vote to make it more likely to clearly reject/pass; or also create an expiration process
- Saori moved to keep in review and use case 6 was kept in review.
Use Case 7Google Group: 2 votes to reject, 1 to approve Kat made motion by acclamation to reject t this use case. Hearing no objections the motion passed and use case 7 was rejected.
Use Case 8
Use Case 9Use Case 10Use Case 13Use Case 15Next Steps- These need to presented at the next general meeting
Use "announce@" to share use cases beyond FDC3? |
| 15 min | Overview of Use Case template to be used going forward | Tom | Tom showed where the use case template would be in confluence. See screeshot below:
Tom then walked through the specific sections of the use case. See following screen shot:
Tom mentioned that Maurizio Pillitu has enabled a polling function to do voting on the use cases. Tom showed how a use cases table could be created, and could be used to process a larger list of use case items - "The table is a simple key value store"
Tom walked through the poll modal:
Leslie: Can you add a reason for rejecting? - Tom: can't do that directly yet
Tom: the power comes from the page properties report – anything you'd like to search and sort on Saori: Everyone needs to add the page properties macro.
Johan: Do we need to add an owner? or can we assume it's the author? What is the person drop off?
|
| 5 min | AOB | group | No other business to note. Leslie: Use Cases will be presented, and the other WGs will be told they need to respond. - Kat offered to draft something for the next stage in the process; next general meeting October 2
|
...