2020-10-12 Meeting notes

Group approved proposed changes to Support Wiki pages as outlined below:

Proposed Support SIG – Wiki Page Structure

• About the Support SIG – who, what where, when,etc
• Charge? Or is this better on the “About” page - seems a lot of redundancy here
• Operational support – Bugs – links to Support Dashboard, Bug ranking, Dev pages, apps in production
• Process for Production libraries
• Bug reporting workflow
• Info for Pos and Devs – how to respond when tagged, etc
• Process for POs and Devs on logging bugs that keep the support sig aware even when not being reported by a live library
• Implementation and training support – list of vendors with contact info
• Bugfest links by directional 
• Documentation – these are set aside for Marcia’s pages but in the meantime we could link to the Apps and Information/tips and Tricks pages. Release notes page
• Development – ?
• Meeting notes -  with caveat that meetings do not generally have notes as we just do bug review

Kelly Drake  to make it happen.  Everyone to review

Discussed issues related to bugs that might actually be features.  Current examples include the stuck data imports  - UIDATIMP-655 - Getting issue details... STATUS /    UXPROD-2615 - Getting issue details... STATUS .   And Users needing the ability, via the UI, to delete a crosslisted course.    UICR-102 - Getting issue details... STATUS

Bugs have been defacto defined as issues that need immediate resolution but sometimes that is not possible?  As a feature, the "bug" is ranked and included in capacity plan. 

Discussed the issue of bugs for which there is no dev team. What should be the process for resolving them?

It was determined that while it is the role of the Support SIG to raise this issue, it should be referred to the Exec Committee  Charlotte Whitt and Kelly Drake to bring to the attention of Mike Gorrell   Anton Emelianov to discuss with Harry Kaplanian