Page Comparison

Ankita Sen is next, followed by Jakub Skoczen 

Reminder:  Please copy/paste the Zoom chat into the notes.  If you miss it, this is saved along with the meeting recording, but having it here has benefits.

All

Maccabee Levine Tod Olson  Jakub Skoczen  Craig McNally 

• CC: Maccabee Levine -  No meeting this week
• PC: Tod Olson - 
  • Presentation and discussion of current UAT practices and issues. There are sometimes practical issues of providing adequate test data. Some POs able to involve SME in UAT before BugFest. Trying to cultivate ongoing discussion about QA.

    • Current UAT Testing FAQs

      
      

• RMS Group: Jakub Skoczen -  Not Present
• Security Team: Craig McNally -  EBSCO has started using PRISMA for vulnerability scanning and the found security issues have been noted and hidden. The critical and high security issues are in priority and decision regarding whether these issues willbe embargoed is still being decided upon.

All

Quick updates only.  If we can't find volunteers for groups, we'll need to add the topic to our backlog and address it during dedicated discussion sessions.

Distributed vs Centralized Configuration - Florian Gleixner - no new updates, RFC is in progress

Architecture Subgroup - Jenn Colt  - Tri council meeting 1PM on Wednesday(08.11.2023). Craig McNally - this subgroup is not going anywhere for now so it's better to close it now and reopen it when we have something more conclusive.

Communicating Breaking Changes - Ankita Sen - No updates, no more volunteers, will pass on the participation message in a few other slack channels, if no response comes we can decide whether to have the group with just Zak Burke and I or push it and have a dedicated discussion on it.

Translation Subgroup - 

TCR Process Improvements - 

Nothing new

All

• 0004 Date-time values must comply with IETF RFC-3339
  • Update/Status?  Is this ready to be moved to the next stage?
• 0005 Application Formalization
  • Update/Status?  
  • What to do with non-technical questions?  Add them to the RFC "unanswered questions" section?  
    • If so, what happens if we later determine that these are out of scope?  Is it acceptable to update the scope later in the process?

RFC Process Improvements:

• /wiki/spaces/~cmcnally/pages/3834098
  • Those that attended 01 Nov 2023 refined this a bit and think it's ready to put into action.  We lacked a quorum, so we deferred making a formal decision until today (e.g. via lazy consensus or vote)

Notes:

• 06 Nov 2023 - Folio Chairs meeting
• 08 Nov 2023 - Topic TBD - Maccabee Levine - Want to finish off with the Officially supported technologies

Previous Notes:

Marc Johnson raised a point regarding the maintenance of the dev.folio.org website. He mentioned that in the early days of Folio, this website was managed by a small group of individuals who were working on the project. However, with the project's growth, keeping the site up to date has become a challenge. Marc suggested that the community should collectively decide whether to continue maintaining the website or explore alternative platforms for sharing development information, as there are differing preferences regarding resources such as the wiki. He also observed that the dev.folio.org site is not updated frequently due to the effort involved.

• RFCs are not searchable from the wiki or dev site.  
• DRs help, but may not be applicable or enough in some cases.
  Craig McNally proposed the use of Decision Records in the RFC process, emphasizing their role in formalizing decisions and creating a wiki presence, especially for handling breaking changes. Maccabee Levine  supported this.
• ...

Craig McNally and Marc Johnson  discussed the need for a central reference and documentation hub for Folio developers. Marc raised this topic, which had also been mentioned in the "Things Folio Can Do Better" discussion. He proposed creating a developer index on the wiki to guide developers, despite the potential complexity of the task. Craig supported the idea, highlighting the challenges of finding information and improvements in GitHub search. Concluded with plans to revisit the topic in future discussions.