Proposal for RM 24.11 Katrin Fischer

From Koha Wiki
Jump to navigation Jump to search

About me

  • Librarian with some developer skills
  • Working at Bibliotheksservice-Zentrum Baden-Württemberg (BSZ)
  • Long term member of the Koha community
  • Had a lot of different Release Team roles over time, including one year as RMaint for 17.05/17.11 and Release Manager for 24.05

Goals

Organization

  • I'll try to spend time on RM tasks (pushing, communicating) every work day. The times might shift a little depending on my other responsibilities.
  • I'll be reachable in Koha chat and through my work e-mail address. I'll also try to follow the bug updates on Bugzilla, so leaving a comment there for non-urgent things will work just as well.
  • If it's urgent and I am not in chat, please try an e-mail instead and I'll get back to you as soon as possible.

Keep the queue moving

  • I will be reviewing bugs and pushing patches in the sequence of the "Patches ready to push" list on the dashboard. These are the basic criteria:
    • Anything that fixes Jenkins failures will be pushed with high priority.
    • Bugs will have second priority over enhancements.
    • Any enhancements and new features will be pushed chronologically, from oldest to newest in the queue.
    • If something fails in testing and needs a follow-up, it the query is set up so it jumps back to the top of the list. If things take a long while to bounce back, I might push them down in queue a bit.
  • My skill set is different to that of former Release Managers which means I will have to do some things differently. This will include asking for help and second opinions/additional reviews where I feel something needs deeper code/programming knowledge.

Roadmap

I'd like to refine the road map a bit more from the 24.05 (Road map 24.05) version.

  • We will have 2 different tables on the page: Planned projects and Community projects.
    • Planned projects can be anything that you want to advertise and to get more people interested in for this cycle. There will be no requirements for this item.
    • Community projects are supposed to be bigger goals that will need more resources from more people and may require agreeing on a project time frame and even freezing master. These will require backing from different community members to make the list.
  • You can add proposals to both tables at the beginning of the cycle and we will discuss about placement at the Development meetings.