Proposal for RM 24.05 Katrin Fischer

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
Currently known as your friendly neighborhood QA Manager

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 on IRC as always and through my work e-mail. 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.
I won't be around on IRC permanently, please don't rely on @laters. If it's urgent and I am not there, please e-mail instead and I'll get back to you as soon as possible.

I'll try to stick to a system as strictly as possible:
- Bugs will have first priority and be pushed first.
- 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 will keep its original priority at first. If it takes a longer while to hear back, it will move back into the queue waiting its turn.
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.

I'd like to create the road map a little differently:

I propose to start with 2 sections on the road map wiki page: proposals and accepted road map items.
A road map item will be accepted to the list, if it has a lead (someone who feels responsible and that I can reach out to) and at least 2 supporters (testing, QA, code golf).
All those people should expect to get emailed by me eventually :)

Contents