2020-11-13 - Sys Ops & Management SIG Agenda and Notes
Date
Attendees
- Ingolf Kuss
- Tod Olson
- Florian Gleixner
- Dennis Benndorf
- Michelle Suranofsky
- Former user (Deleted)
- Mike Gorrell
- Chris Rutledge
- Brandon Tharp
- Axel Dörrer
- Anton Emelianov (Deactivated)
- Johannes Drexl
- Hkaplanian
Meeting Link
- https://zoom.us/j/591934220
- Password: folio-lsp
Discussion items
Time | Item | Who | Notes |
---|---|---|---|
5 | Welcome | Ingolf | Note Taker today: Axel Dörrer |
10 | Review Action Items | Ingolf | |
Hey, this was on the meeting notes for the agenda item "Goldenrod update and release notes" of the Oct 16th meeting: "At the moment, there are three places of documentation to install a complete system:
Would definitely be nice to have the Release notes also on github. But then they should have some defined format, e.g. in JSON. Need JSON vocabulary for this. It is desired to have integration of github and JIRA. Commits in github should update JIRA automatically. There are plugins for JIRA and there are plugins for github. Anton will talk to John Malconian about this." So, I took "Need to have integration of github and JIRA" to the PC meeting. ... and they told me, that we already have that. So, what was going on there ? Do we still have a requirement ? | |||
FOLIO Governance Model | all | Purpose of this agenda item is to provide Feedback of the SysOps SIG to the FOLIO Governance Model. Slide presentation of the Governance Model is here: Feedback is to be provided here: | |
Support SIG representative |
Action items
- Type your task here, using "@" to assign to a user and "//" to select a due date
Governance Model
Mike presents the new governance model proposal by the governance task force:
Jono Bacon as consulter for the governance task force
- 3 founding organisations: EBSCO, IndexData, OLE
- Going through the slides
- ~100,000$ fixed costs per year (AWS, JIRA, etc.)
- Core Maintainance Team works for PC
Comments/Questions:
- Great step to open the community. generally agree to the proposal
- smooth transition. good to still have a maintaining core team
- better people to read/reflect the feedback document
- Q: Why do I want to be a diamond member?
Ultimatley it's more a marketing orpotunity. A strong commitment in the project and will help to sustain the costs in the future. - Membership dues does not fund personnal/development.
- Model is completly differently to other open source projects.
- SIGs are not reorganizied or change by that model, the PC will.
Addtional feedback can be added to the feedback dokument
To give the people more time to dive into all aspects the group should discuss further oppinions on the sysop channel and Ingolf will formulate an overall feedback of the SysOp group.
How does JIRA tickets relates to module versions
Fixed Versions are set manually which might cause a lack of mentioning an issue in the release notes. DevOPs team might help on it.
Pull requests are created with relying on JIRA issues. So merging PRs will automatically close JIRA issues but will not automatically add or change the fixed versions field.
Support SIG representative
Has not been chosen yet.