Roles for 25.05

Release team for the 25.05 development cycle. Available roles are documented in project roles, but are not limited to those on that page. 
If you feel there's room for improvement somewhere for Koha release management, please submit your proposal.
Elections will be held at the Development IRC meeting 13 November 2024
*Release Manager
**Katrin Fischer (continuing)
*RM Assistants
**Martin Renvoize (continuing)
**Jonathan Druart (continuing)
**Tomás Cohen Arazi (continuing)
*Release Maintainers
**24.11 (LTS): Paul Derscheid (new)
**24.05: Catalyst IT (Wainui + Aleisha and Alex)
**23.11: Fridolin Somers (continuing)
**22.11 (LTS): JesseM
*Release maintainer assistants
If you're willing to lend a hand to one of the release maintainers above, for example offering to cover during annual leave or aiding in staying on top of the queue
*Martin Renvoize, happy to help anyone as asked
**24.11 (LTS):
**24.05:
**23.11:
**22.11 (LTS): Laura Escamilla
*Quality Assurance Manager
**Martin Renvoize (continuing)
***Due warning: I intend to remove peoples listing on the QA team when they do not actually action any QA during a cycleWe need active QA people and filling the team with names of people who are not actively contributing is just diluting thepool and not highlighting the desperate need for more active QA people on the team.
*Quality Assurance Team Past members of the QA team may continue to QA and will be added into release documentation if they appear to be active during a cycle.
**Victor Grousset/tuxayo (continuing)
**Lisette Scheer/lisettebws
**Emily Lamancusa/emlam (continuing)
**David Cook/dcook (continuing)
**Jonathan Druart (continuing)
** Julian Maurice (continuing)
**Baptiste Wojtkowski (new)
**Paul Derscheid (continuing)
**Aleisha Amohia (continuing)
**Laura Escamilla (continuing)
** Tomás Cohen Arazi (continuing)
**Kyle Hall (continuing)
**Nick Clemens (continuing)
**Lucas Gass (continuing)
** Marcel de Rooy (continuing)
**Andrii Nugged [continuing]
**Petro V [continuing]
**Matt Blenkinsop (continuing)
**Pedro Amorim (continuing)
**Brendan Lawlor (new)
**Thomas Klausner (continuing)
*Security Release Manager NEW
** Tomás Cohen Arazi
*Topic Experts A second sign-off from a QA expert will count towards QA with additional code review from core team where needed (CAS, Shibboleth, LDAP, SIP2, Linked Data/RDF, Zebra, ...
**UI design: Owen Leonard [continuing]
**REST API: Tomás Cohen Arazi
** Zebra: Fridolin Somers
**ERM:
**ILL:
**SIP2:
**CAS:
**Elasticsearch:
*Bug Wranglers (the more the merrier!)
**Michaela Sieber
** Jacob O'Mara
** Jake Deery
*Documentation Manager
** Philip Orr (continuing)
*Documentation Team
**Aude Charillon
**David Nind
**Caroline Cyr La Rose
*Meeting facilitators
**Paul Derscheid (continuing)
*Translation Manager
**Jonathan Druart (continuing)
*KTD maintainer
** Tomás Cohen Arazi (continuing)
*Packaging Team 🎁
**Debian packages
*** Mason James (continuing) 🍕
**Docker images
*Continuous integration infrastructure maintainer
**Jonathan Druart
** Tomás Cohen Arazi (continuing)
** Jake Deery
*Website Maintainer
**David Nind (will post a more formal proposal if I get time before the voting)
***Proposal (draft) - things I would work on with others and the community:
****Develop a content strategy and communication plan (site purpose, types of content, sections, structure, and so on) (likely to more tweaks and progressive improvement, than a "big bang" change)
****Look at updating the theme, if considered required
**** Review the platform we use (Wordpress), and community requirements
****Maintenance tasks, such as user management, reviewing content, link checking, and keeping content for the ain sections up-to-date
****Look at how we manage the support providers section - particularly look at removing any listings where the contact information is no longer current
**Lauren Purton (New Marketing person at PTFS Europe)
***May not be ready yet for this, but wanted to get the name down in case she can be helpful to David for running idea's against etc. 
*Wiki Curator 📜
**George Williams (continuing)
**Thomas Dukleth (continuing)
*** Proposal complementary to Jonathan Druart and other's priority for marking pages obsolete:
****I Have already listed all pages not edited in a while
****Use MassEditRegex extension to do all the heavy lifting with careful testing at each step using wiki.test.koha-community.org
*****Please never use dangerous tools such as MassEditRegex, unless logged in as a purpose specific bot user with bot rights tied to your wiki username, not logged in as your ordinary wiki username.
****Important modification to proposal from Jonhathan Druart's good suggestion for hiding pages which have mostly historical understanding/ lost features use (as all non-spam/mistakenly created pages do)
*****When removing categories to hide them from category based browsing which misses the Obsolete category search exclusion transform the categories from [[[Category:CategoryName]]] to (Topic:CategoryName) with parenthesis instead of square brackets so that we actually have half a chance of finding something when specifically querying the archive. 
**Jonathan Druart
***Proposal:
****List the different pages
****Flag them (obsolete/do not use, obsolete/need adjustments, missing info, ok)
****Hide the useless pages (ie. remove the category if the page is obsolete, we don't want to see it display anywhere)
****Restore pages that have been marked obsolete but should be kept (eg https://wiki.koha-community.org/wiki/Backing_up_Koha)
****Edit (I will need help for this part)
**Martin Renvoize
***Proposal:
****As above, to support Jonathan's initiative and work through flagging obsolete pages etc
*Wiki manager
**Thomas Dukleth (continuing)
*Wiki team member
**Thomas Dukleth (continuing)
*Newsletter editor 📰
**Michael Kuhn (continuing)
*Social media managers
**Twitter/X: David Nind
**Mastodon: David Nind
**Facebook: David Nind
**Linkedin: David Nind
** Vimeo: David Nind
**Zotero: David Nind
**YouTube: David Nind
**Note: More than happy to hand over to others who are interested, or are interested in looking after a particular platform. For this cycle, I'd like to come up with an updated communication plan, and social media plan.
*Accessibility Advocates
** David Nind
 
Category:Release Management 
Category:Participation