2018-06-14 - System Operations and Management SIG Agenda and Notes

2018-06-14 - System Operations and Management SIG Agenda and Notes

Date

Jun 14, 2018

Attendees

  • @Ingolf Kuss

  • @Wayne Schneider

  • @Hkaplanian

  • @Christopher Creswell

  • @Tod Olson

  • @Anne L. Highsmith

  • @Brandon Tharp

  • @Chris Manly

  • @patty.wanninger

  • @spampell

  • @Michael Winkler

  • @Greg Delisle

  • @Dale Arntson

Goals

Discussion items

Time

Item

Who

Notes

Time

Item

Who

Notes

 5

Welcome

Ingolf

  • determine note taker

  • review action items (in Wiki)

10

Determine new meeting time and date

Ingolf, group

based on Doodle poll .

Best time is Fridays 10:00am ET, overlap with early implementers call. We lose a few people, but no time is perfect. Decided to move to to Fridays 10:00 AM ET.

30

Review action items

Ingolf, @Hkaplanian, all

Jason and Brandon provided more detailed descriptions of action items . Thank you !

https://docs.google.com/spreadsheets/d/1Y52ltM_nVZsMM9dEVCkHAWuRZXjOykZfvoF-zLQ-YBg/edit#gid=0

Action Items will be presented in the PC meeting today.

@Hkaplanian and @Cate Boerema (Deactivated) reviewed and created new UXPROD issues or linked to existing issues.

Notes from WOLFCon will be linked into issues where appropriate (e.g. https://folio-org.atlassian.net/browse/UXPROD-850).

Additional comments will be reviewed and taken into account in the prioritization conversations.

Prioritization:

  • There are many P1 items – how do we know which to tackle first?

  • Prioritization in spreadsheet is relative within the spreadsheet– P1 not the same as a P1 in JIRA

  • @Dale Arntson raised concern – many things need to be worked on at once

    • Epics will be split into smaller issues that can be worked on in parallel

    • Additional developers/dev teams can be added more easily if work is divided up

    • Bug fixes/defects are prioritized and worked on outside of the feature backlog stream

  • Items that are labelled "P1" are blockers for implementation

    • Release management is the first blocker

    • Related: dependency resolution

Concerns (raised by @spampell):

  • Lines in spreadsheet are sometimes linked to what appear to be unrelated issues

    • There may be typos, will review

    • Details will be added to JIRA issues

Presentation (today) to Product Council (questions from @Ingolf Kuss):

  • Categories of issues

    • e.g. deployment, data loading, performance

    • Logging/instrumentation

      • How/who will broker the needed conversations between the SIG and developers?

 

Action items

@Ingolf Kuss post slide deck for Product Council presentation to SysOps wiki (see on the top of this wiki page)