nyuuzyou/wikis huggingface dataset:
Development IRC meeting 9 November 2022

The meeting was not held/postponed
=== Place ===
The #koha IRC channel (IRC server irc.oftc.net).
If you don't have an IRC client you can join the meeting using your web browser.
=== Time ===
* 9 November 2022, 15:00 UTC Time and Date.com converter for various local times
=== Agenda ===
* Introductions (please use "#info" in front of your introduction to have it show up in the automatic minutes)
* Announcements
* Update from the Release manager (22.11)
* Updates from the Release Maintainers
* Updates from the QA team
* Status of roadmap projects
* Actions from last meeting
** davidnind to send an email to the mailing lists on roles for 23.05: sent on 2 November 2022
** davdnind to send a request to the mailing list for someone to update LTS wiki page: still to do, please allocate action to davidnind
** Deferred until after the 22.11 release:
*** tcohen to schedule/call a "CSRF day" to work on related patches together - deferred until after the 22.11 release
*** tcohen [WAIT until after 21.11 release] to draft proposal for master→main change and draft of action list
*** oleonard ashimema draft in the developer handbook how to form our modals. With template of a simple case and a case with form inside.: focus is currently on staff interface redesign changes, see the draft style guide (WIP)
** Can we claim ES7 support now?
* Elections: Roles for 23.05
** Voting on Roles for 23.05
* General development discussion (trends, ideas, ...)
** git-bz is stuck on Python 2 which went end of life on January 1st 2020… should we start to consider alternatives? (Deferred from previous meeting(s).)
** git bz attach -e BUGNUMBER HEAD~X.. (where X = number of patches (davidnind): 
*** I've always done it this way when signing off patches as it is what I was told to do
*** There was some discussion on IRC on using -e or not, and obsoluting patches
*** Just seeking guidance on best practice, including whether old patches should be obsoleted (by adding the obsolete tag) to make the bug "cleaner"
*** There maybe a number of scenarios where different options are preferred (for example, sign off vs. passed QA)
* Review of coding guidelines
** SQL8 of our coding guidelines state that SQL should not be in .pl, but should be in the module in C4 or Koha. This would mean that SQL in the Koha namespace is allowed and there is no mention of DBIC in the coding guidelines right now. (Deferred from previous meeting(s).)
* Set time of next meeting
=== Apologies ===
Please list your name here if you would like to attend but cannot make this meeting:
* David Nind
===Minutes===
* Minutes: https://meetings.koha-community.org/2022/development_irc_meeting_9_november_2022.2022-11-09-23.35.html
* Minutes (text): https://meetings.koha-community.org/2022/development_irc_meeting_9_november_2022.2022-11-09-23.35.txt
* Log: https://meetings.koha-community.org/2022/development_irc_meeting_9_november_2022.2022-11-09-23.35.log.html
===Next meeting===
* Development IRC meeting 16 November 2022
Category:Developers_IRC_Meetings
Category:Developers_IRC_Meetings_2022
Development IRC meeting 9 October 2019

=== Place ===
The #koha IRC channel (IRC server irc.oftc.net).
If you don't have an IRC client you can join the meeting using your web browser.
=== Time ===
* 9 October 2019, 14:00 UTC Time and Date.com converter for various local times
=== Agenda ===
* Introductions (please use "#info" in front of your introduction to have it show up in the automatic minutes)
* Announcements
* Update from the Release manager (19.11)
* Updates from the Release Maintainers
* Updates from the QA team
* General development discussion (trends, ideas, ...)
* Review of coding guidelines
* Deprecate svc scripts and add a check to the QA scripts so they don't add new ones (vote)
* Set time of next meeting
=== Apologies ===
Please list your name here if you would like to attend but cannot make this meeting
* Jon Knight, Loughborough University
===Minutes===
* Minutes: http://meetings.koha-community.org/2019/development_irc_meeting_9_october_2019.2019-10-09-15.00.html
* Minutes (text): http://meetings.koha-community.org/2019/development_irc_meeting_9_october_2019.2019-10-09-15.00.txt
* Log: http://meetings.koha-community.org/2019/development_irc_meeting_9_october_2019.2019-10-09-15.00.log.html
===Next meeting===
Development_IRC_meeting_23_October_2019
Category:Developers_IRC_Meetings
Category:Developers_IRC_Meetings_2019
Development IRC meeting 9 September 2020

=== Place ===
The #koha IRC channel (IRC server irc.oftc.net).
If you don't have an IRC client you can join the meeting using your web browser.
=== Time ===
* 9 September 2020, 20:00 UTC Time and Date.com converter for various local times
=== Agenda ===
* Introductions (please use "#info" in front of your introduction to have it show up in the automatic minutes)
* Announcements
* Update from the Release manager (20.11)
* Updates from the Release Maintainers
* Updates from the QA team
* Actions from last meeting
** ashimema is collecting notes about bug 15522 and is going to review and dig a bit more into the code (postponed)
** tuxayo integrate the RMaint-handover-draft into the "release maintenance" wiki page (postponed)
*** Done, is the place in the page ok? Release_maintenance#Handover_between_two_cycles
** davidnind Find and update relevant places to record Perl version required, including release notes, manual and wiki (one source of the truth): update 2020-09-09 - still working on this, apologies (postponed)
** Joubu open a bug report for the QA script to catch input type number
*** See https://gitlab.com/koha-community/qa-test-tools/-/issues/38 - There is a merge request attached.
** ashimema write a guideline to forbid usage for type "number"
* General development discussion (trends, ideas, ...)
** Zebra search support and the future - summary from mailing list discussion: Zebra is still maintained, but no longer actively developed; many libraries will not have the resources and budget to run Elastic; work on a lightweight alternative, and until we have one support Zebra - don't leave people behind!
* Review of coding guidelines
* Set time of next meeting
=== Apologies ===
Please list your name here if you would like to attend but cannot make this meeting
===Minutes===
* Minutes: http://meetings.koha-community.org/2020/development_irc_meeting_9_september_2020.2020-09-09-20.09.html
* Minutes (text): http://meetings.koha-community.org/2020/development_irc_meeting_9_september_2020.2020-09-09-20.09.txt
* Log: http://meetings.koha-community.org/2020/development_irc_meeting_9_september_2020.2020-09-09-20.09.log.html
===Next meeting===
Development_IRC_meeting_23_September_2020
Category:Developers_IRC_Meetings
Category:Developers_IRC_Meetings_2020
Development IRC meeting Template

=== Place ===
This meeting is held as a video conference using Jitsi:
Jitsi Meeting Link
*The meetings are not recorded.
*You don't have to turn your camera on if you prefer not to be seen; but if you are able to use a microphone it will make things easier.
*To join the meeting, click on the meeting link.
**If you are on a desktop computer, it will open in a browser window. There is no need to install anything.
**To join on a mobile device, you will need to download the Jitsi Meet app (Google Play, Apple Store)
**Supported browsers | Mobile application
*Browsers will ask for permission to use video and audio devices: check or review these settings if you have audio or video issues.
We use Hedgedoc to record the meeting minutes, including introductions (formerly #info) and actions (formerly #action) information.
=== Time ===
__TIME__
=== Agenda ===
* Introductions (the convention is `- <NAME>, <ORG>, <PLACE>`)
* Announcements
* Update from the Release manager (25.05)
* Updates from the Release Maintainers
* Updates from the QA team
* Status of roadmap projects
** Road map 25.05
* Actions from last meeting
__ACTIONS__
* General development discussion (trends, ideas, ...)
* Review of coding guidelines
* Any other business
* Set time of next meeting
=== Apologies ===
Please list your name here if you would like to attend but cannot make this meeting
===Minutes===
__MINUTES__
===Next meeting===
__NEXT_MEETING__
__CATEGORIES__
Development Meeting 11 October 2023

NOTE: Informal meeting held a little later on the same day, next meeting 18 October 2023
=== Place ===
Video conference meeting using Jitsi at https://meet.jit.si/KohaDevelopmentMeeting
* IMPORTANT: The first person "in" the meeting needs to sign in as the "Moderator" using a Google, Facebook, or GitHub account; other attendees can then attend without any authentication - see the jitsi blog for more information.
* To decide: whether to record or stream meeting to YouTube
* Browsers will ask for permission to use video and audio devices: check or review these settings if you have audio or video issues
* Supported browsers | Mobile application
Use the #koha IRC channel (IRC server irc.oftc.net) to record the meeting minutes, including #info and #action information. (If you don't have an IRC client you can use your web browser.)
=== Time ===
* 11 October 2023, 12:00 UTC Time and Date.com converter for various local times
=== Agenda ===
* Introductions (please use "#info" in front of your introduction to have it show up in the automatic minutes)
* Announcements
* Update from the Release manager (23.11)
* Updates from the Release Maintainers
* Updates from the QA Team
* Status of roadmap projects
*KohaCon24 update
* Roles for 24.05
* Actions from previous meetings (please remove any items closed)
** CSRF fixes
** Other actions (so we don't forget):
*** cait and ashimema will put together the TODO notes from the hackfest on the Wiki
*** perldoc.koha-community.org update needed (tcohen and gmcharlt): 
**** Update from 28 June 2023 meeting: tcohen and gmcharlt met and agreed on a path for some services to get up to date and have community members access so we can help
*** Gitea -> Forgejo - tcohen and Joubu to update:
**** Update from 13 September 2023 meeting tcohen has tested update
* General development discussion (trends, ideas, ...)
** DMARC compatibility for mailing lists - see the 26 April 2023 agenda for details (maybe a bug should be created to track progress?): 
*** Update from the 28 June 2023 meeting: the main mailman list would benefit from some configuration tweaks that thd has proposed/mentioned. WE are contacting rangi to talk about that.
*** Update from 13 September 2023: need to get in touch with list admins to discuss changes to mailman configuration
** tcohen to have a look at renaming master branch to main
** Draft style guide - needs to include how to use modals
** Translation tools - move from Pootle to Weblate:
*** Test instance for Weblate
*** Feedback from anyone who has used this tool before welcome
*** Update from Joubu
* Review of coding guidelines
** ..
* Set time of next meeting
=== Apologies ===
Please list your name here if you would like to attend but cannot make this meeting
* -
===Minutes===
-
===Next meeting===
-
Category:Developers_IRC_Meetings
Category:Developers_IRC_Meetings_2023
Development Meeting 27 September 2023

=== Place ===
Video conference meeting using Jitsi at https://meet.jit.si/KohaDevelopmentMeeting
* IMPORTANT: The first person "in" the meeting needs to sign in as the "Moderator" using a Google, Facebook, or GitHub account; other attendees can then attend without any authentication - see the jitsi blog for more information.
* To decide: whether to record or stream meeting to YouTube
* Browsers will ask for permission to use video and audio devices: check or review these settings if you have audio or video issues
* Supported browsers | Mobile application
Use the #koha IRC channel (IRC server irc.oftc.net) to record the meeting minutes, including #info and #action information. (If you don't have an IRC client you can use your web browser.)
=== Time ===
* 27 September 2023, 12:00 UTC Time and Date.com converter for various local times
=== Agenda ===
* Introductions (please use "#info" in front of your introduction to have it show up in the automatic minutes)
* Announcements
* Update from the Release manager (23.11)
* Updates from the Release Maintainers
* Updates from the QA Team
* Status of roadmap projects
*KohaCon24 update
* Actions from last meeting (please remove any items closed at 13 September 2023 meeting)
** CSRF fixes
** Other actions (so we don't forget):
*** cait and ashimema will put together the TODO notes from the hackfest on the Wiki
*** perldoc.koha-community.org update needed (tcohen and gmcharlt): 
**** Update from 28 June 2023 meeting: tcohen and gmcharlt met and agreed on a path for some services to get up to date and have community members access so we can help
*** Gitea -> Forgejo - tcohen and Joubu to update:
**** Update from 13 September 2023 meetingL tcohen has tested update
* General development discussion (trends, ideas, ...)
** DMARC compatibility for mailing lists - see the 26 April 2023 agenda for details (maybe a bug should be created to track progress?): 
*** Update from the 28 June 2023 meeting: the main mailman list would benefit from some configuration tweaks that thd has proposed/mentioned. WE are contacting rangi to talk about that.
*** Update from 13 September 2023: need to get in touch with list admins to discuss changes to mailman configuration
** tcohen to have a look at renaming master branch to main
** Draft style guide - needs to include how to use modals
** Translation tools - move from Pootle to Weblate:
*** Test instance for Weblate
*** Feedback from anyone who has used this tool before welcome
*** Update from the 28 June 2023 meeting: Tomas had a chat with Bernardo. He is documenting how things currently all work, and then we're going to look at migrating to Weblate, what that involves, what we need to change at our side, etc. It shouldn't be too involved: * Update strings for each release * Migrate translations between branches at feature releases. 
* Review of coding guidelines
** ..
* Set time of next meeting
=== Apologies ===
Please list your name here if you would like to attend but cannot make this meeting
* ..
===Minutes===
__MINUTES__
===Next meeting===
* __NEXT_MEETING__ 
Category:Developers_IRC_Meetings
Category:Developers_IRC_Meetings_2023
Digital signs RFC

Live demo of work in progress: http://kohawip.libriotech.no/
==What to do==
===Intranet===
* Syspref for turning signs on/off
* Permission for working with signs
* A new tool under “Tools” (sannsynligvis) for adding, editing and deleting signs, including basic help texts. 
** Sorting of signs in any order
** Possibility to choose between “collage” mode and “bookshelf“ mode for each sign
** Unique “slugs”, for use in URLs (opac-sign.pl?sign=returned) 
===OPAC===
* Geared towards touch screens (interactive "signs" in the physical library)
* Once loaded, should work offline too
* Preloading images 
* Avoid scrolling in the signs
* Automatic flipping of signs after some period of inactivity
* Covers and reviews from multiple sources
* An arbitrary number of signs will be supported, and each sign can contain more than one page, dependent on the number of items returned by the report it is based on and the size of the available screen space. 
* The signs should work in full screen mode, without the need for browser functions, like the "Back" button
* The interface should be geared towards touch screens, with big clickable buttons etc
* It should be possible for libraries to style the signs to e.g. suit their overall graphical profile
* jQuery Mobile will probably be used both for styling and for interactions (like swiping, perhaps)
===Documentation===
* Some inline documentation in the staff interface
* Documentation for the manual
==Related bugs==
* - New theme for the OPAC with a mobile view
* - CSS and JS libs must be outside of translated paths
* - Koha themes broken
* - Prioritize cover image sources such as Amazon, Google and add fail over i.e. if first source fails, go to next
==Links==
* jQuery Mobile
Category:OPAC_RFCs
Category:Submitted_RFC
Discount rate at order level

Currently the discount rate is specified at a vendor level. This is not suitable in scenarios where different discount rates apply to different orders (titles).
We propose to change the discount rate at the vendor level to be the "default" discount rate for that vendor. In addition we will provide a discount rate field in the order entry/edit screen. This field will be populated with the default discount rate, but can be edited to a different value.
This is implemented here: http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5173
Category:Acquisitions_RFCs
Category:Koha_3.4_RFCs
Documentation - Contributing

There are many ways to support Koha! One of the ways library staff and library support people can take part in the Koha community is by contributing to user documentation. Who else can best explain how to make the most of Koha than the people working in or with libraries?! 
Whatever your background or experience, we are keen to have your help!
We welcome your thoughts, your presence and your contribution with planning, writing, editing the Koha manual, reviewing; and other tasks.
== What contributing looks like ==
Things you could take part in include:
* Editing the Koha manual - explaining how to use new Koha features, revising sections to make them more relevant, updating screenshots, adding examples to better help library teams make the most of Koha.
** This is the meaty bit of the Documentation work! Ideally, you would be doing all this via GitLab, writing in reStructuredText format. Useful pages: Editing the Koha manual and Koha reStructuredText - Tips and tricks. Help and guidance from experienced documenters is available!
* Giving your thoughts on Documentation issues - at Documentation meetings, we regularly need to solve issues, clarify processes and decide on solutions.
* Helping out with current Documentation projects - once in a while, we tackle something a bit different... It could be an overhaul of a specific section of the manual, testing a way to automate screenshots...
* Curating the wiki – reviewing and updating content about Koha documentation on the Koha wiki.
== Where to start: find like-minded people ==
=== Attend a Koha Documentation meeting ===
* These usually take place about once a month. They bring together people involved and interested in Koha user documentation.
* To find out the details of future meetings:
** Check the Koha community calendar.
** Check the Documentation IRC meetings category on the Koha wiki.
=== Join the Koha mailing list ===
* Subscribe to the main Koha list (also known as the "general list").
* Koha documentation meetings are often announced there.
* Information about major changes and about Documentation team projects are also posted to the list.
=== Get in touch with the Documentation team ===
* Check who is in the Documentation team for the current Koha development cycle.
* Chat with us in the Koha Community Mattermost: join the Documentation channel.
* Ask on the Koha mailing list.
== What you may need ==
# A free account on Bugzilla - we use Bugzilla to manage documentation tasks.
# A free account on GitLab - this is where the Koha Manual is maintained. Editing the manual will likely mean using the GitLab web interface - see Editing the Koha Manual.
# A free account on Mattermost - to chat with the Koha Community in general and the Documentation Team in particular.
# A Koha Wiki account - to add agenda items for future meetings, to add your name to the next Koha Documentation team... If you don't already have an account, request one.
# Some time to contribute!
Category:Documentation
Category:Participation
Documentation - Roles and Participants

== Documentation Team roles ==
* Manager
* Team member
* Wiki curator
* Technical support - continuous integration and publishing:
** Technology and processes for automating the manual publication on the Koha Community website
== Participants ==
Current Documentation Team members are:*
* See Roles for 22.05
* David Nind, Documentation Manager, IRC: davidnind, Email: david.nind@gmail.com or david@davidnind.com
(* Only add your details and information if you are comfortable putting your details here)
Documentation IRC meeting 13 April 2023

=== Place ===
The #koha IRC channel (IRC server irc.oftc.net).
If you don't have an IRC client you can join the meeting using your web browser.
=== Time ===
* 13 April 2023, 14:00 UTC Time and Date.com converter for various local times
=== Agenda ===
* Introductions (please use "#info" in front of your introduction to have it show up in the automatic minutes)
* Updates
**Review of action points
*** followup on mailing list close down
*** caroline to send an email to the mailing list about hackfest screenshot update details
*** caroline to ping docs team member friday march 17 to do a test run for screenshot update
*** all to look into their own docs for ES related info and submit it to have a starting point in the manual
*** caroline to add video calls to next agenda
**Project updates
*** Hackfest screenshot extravaganza (Aude)
*** Automated Screenshots (Aude)
*** Video calls (Martin?)
*** Progress updates for projects
**What's been done so far
*** ..please add a short update on what you've been working on since the last meeting...
*** ..
* Content development guidelines
** ..items for discussion, including any work flow issues..
* Next steps
** Bugzilla: General documentation tasks | Release changes: Needs documenting status (all releases since 22.05)
** Priorities:
*** ..
* Set time of next meeting
=== Apologies ===
Please list your name here if you would like to attend, but cannot make this meeting
* ..
=== Minutes ===
* Minutes: http://meetings.koha-community.org/2023/documentation_irc_meeting_13_april_2023.2023-04-13-14.01.html
* Minutes (text): http://meetings.koha-community.org/2023/documentation_irc_meeting_13_april_2023.2023-04-13-14.01.txt
* Log: http://meetings.koha-community.org/2023/documentation_irc_meeting_13_april_2023.2023-04-13-14.01.log.html
=== Next meeting ===
Documentation_IRC_meeting_9_May_2023
Category:Documentation_IRC_Meetings
Category:Documentation_IRC_Meetings_2023