2022-03-23 Meeting notes

To Dos

follow ups 

• Anya will ask Anton if there is a possiblity for getting a SIG rank field

Tools for voting and visualization:

• Miro
• https://uservoice.com/ 
• https://lucidspark.com/
• https://airtable.com/

Discuss proposal

• everyone should be able to bring up requests
• raise topics with SIG and/or PO
• Jacquie: That sounds right to me, but occasionally, the PO might request that I write up the issue, after SIG discussion, which she then manages in JIRA
• There are templates for Jiras
• Thomas in chat: It is difficult sometimes to know under what area it should be added.
• Jacquie in chat: yes, that is why we need to work with the POs to get them right.
• PO rank with R1-R5 or with numbers? → TBD
• original request = request by institution
• draft request = request that has been cleared by the PO (PO = gatekeeper)
• bypass the SIG: in cases where something is really needed and needs no discussion
• requests could be epics or a small feature, e.g. a cancel button to requests form
• requests can bypass voting, e.g. core functionality, NFRs, industry standards (e.g. Or data synchronization, major blocks to workflows, data collision avoidance)
• institutions that are going live or that are live
  • what do we consider as live?
  • Thomas in chat: It could be area by area, or if being used at all, or the core apps.
• OLF members / paying institutions → marketing for membership - development needs funding
• institutions active in the community
• weighting for implemented partially vs. full vs planned, consortia vs. single
• Thomas in chat: I think all institutions should be allowed to vote, just the weight of their votes maybe different.
• Implemented libraries can be members, but may not be, right? So perhaps we should think about implemented, actively planning implementation, or other categories should be used rather than members?
  
   

• postponed