Yogesh Kumar sees new Bugfest testers but number of claimed test cases is still low (~650); more people need to engage to reach our goal to finish Bugfest till end of month.
Jeremy is about to send out a notice on behalf of PC => sent by email.
Jana Freytag: RA SIG seeks new co-convenor (successor for Jana); Jana can do onboarding; should be announced on general slack channel and also reached out to individuals
Desired outcome: Jira dashboard of features identified as SIG priorities that may not be slated for a release, but can be picked up by development teams.
Questions for discussion:
Do you already have a mechanism for your SIG for collecting priorities?
Are priorities represented in Jira or through another means?
Do you keep a topic backlog/topic page that you can draw on to develop priorities?
Are there dormant features that should be revisited?
What barriers do you have in collecting priorities?
What do you think would be a good time frame for collecting priorities?
What can the PC do to help your SIG with this work?
Martina Schildt opens topic by quickly presenting how ACQ SIG is doing prioritisation:
Wiki page (see above) for implementer topics; every community member can add topics; topics will be discussed in SIG and wiki page item is updated
For each topic a Jira ticket is created; a ticket is given certain labels special to the SIG; each ticket can be voted with the like button (upper right)
High votes do not garantee timely development, but developers can orient on that if they have spare dev time
Jira dashboard with most voted tickets
Kristin: Roll out of this process to other SIGs; not necessarily exactly the same; every SIG has their own special situation; this shall start a discussion in rolling out prioritisation process
Discussion of Questions above: (not final, Martin needs to consult recordings)
Jana: RA SIG has gap list, every institutions picks theri 5 most important topics, work through it in meetings, no real voting process Gap list RA SIG
Existing Jira tickets are searched and linked
if no ticket exists in Jira, a ticket is created by person responsible for the gap
there are trainings for creating tickets => Kristin: it would be great to share this with others as well; in chat: there are wiki pages for that: Getting Started for Product Owners
Martina: if voting would be added, a Dashboard could be created for the list
are tags/labels used for tickets? => currently not; RA SIG has a lot of different apps/modules and providing tags would be a prerequisite for a meaningful dashboard
There is need for volunteers for tagging the tickets
Martina: ERM has similar system as ACQ SIG; more reluctant in creating Jira tickets; ERM SIG is willing to adjust process
Laura: LD SIG still has small parking lot, currently planning meetings is more of a topic and currently there are also no implementers; the prioritisation process will be future meeting topic, important for tracking community prios and community impact
Laura: MM SIG is more difficult, difficult to come to an agreement on priorities as institutions have very different needs; challenge to agree on SIG’s priority
Alexis: there need no necessary be agreement; priorities should surface needs
Kristin: AI SIG have spreadsheet;
more info from spreadsheet should go into Jira; tags should be used to appear in dashboards
Surface issues on Dashboards can help people get active if they’re unsatisfied in Folio
Martina: cleaning up the tickets is important
Laura: things that have been thin-threaded/half implemented should be revisited, what approaches are there?
Kristin: timing would be good now for that; but such things may not be visible in Jira as they may have been removed or be marked as done; some kind of survey/brainstorming would have to be done
Jana: going though backlogs and closing deprecated features was very helpful and removed load
Caitlin: Jira tickets can be bulk updated, eg. add labels; admin permissions are needed; Holly used to do it; Permissions may need to be adjusted. Peter can look into it. New feature in Jira cloud: Export/Import with Google sheets
=> there should be a recorded session about creating and maintaining tickets
Sharon: Reporting SIG use github issues, easier and faster to organise for their needs; with Reporting app SIG returns to Jira. Meta DB is managed through github issues.
Charlotte: mod-reporting, ui-ldp and mod-ldp all were managed with JIRA
Charlotte: It would be useful if all members had permissions to use tags to label tickets; ?
Kristin: Prioritisation rollout till Trillium; but usable beginning next year; standardized tagset for better search
Martina: How can the PC help convenors discuss / roll out this process in SIGs
Sharon: maybe there should be a Jira support group; Caitlin in chat: maybe a slack channel
nobody should not to get their things done because they don’t know Jira
Charlotte: When talking to devs: If it isn’t in Jira, it doesn’t exist
Tod: this topic parallels with lifecycle of definition of done in different teams