nyuuzyou/wikis huggingface dataset:
General IRC meeting 4 February 2025

=== 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 will use Hedgedoc to record the meeting minutes, including introductions (formerly #info) and actions (formerly #action) information.
The convention for introductions is:
- <NAME>, <ORG (optional)>, <PLACE (optional)>, <COUNTRY (optional)>
=== Time ===
* 4 February 2025, 14:00 UTC Time and Date.com converter for various local times
=== Agenda ===
* Introductions
* Announcements
** Kohacon25: 
*** Dates: 17-23 November 2025
*** Call for presentations now open, close on 1 March 2025
* Actions from last meeting
** cait: to get in touch with Biblibre on retiring unused mailing lists
** paulderscheid: to document the new process for chairing and managing meetings on the Wiki
* KohaCon26
=== Apologies ===
===Next meeting===
General_IRC_meeting_8_April_2025
===Minutes===
 * Minutes: https://koha-hedgedoc.servers.llownd.net/General_IRC_meeting_4_February_2025
Category:General_IRC_Meetings
Category:General_IRC_Meetings_2024
General IRC meeting 4 May 2022

=== 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 ===
* 4 May 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
** We will vote roles for 22.11 cycle
* Actions from last meeting
** ashimema add Koha Community Challenge, Bug Squashing Event in May to the community calendar
=== Apologies ===
===Next meeting===
General_IRC_meeting_7_September_2022
===Minutes===
* Minutes: http://meetings.koha-community.org/2022/general_irc_meeting_4_may_2022.2022-05-04-15.01.html
* Minutes (text): http://meetings.koha-community.org/2022/general_irc_meeting_4_may_2022.2022-05-04-15.01.txt
* Log: http://meetings.koha-community.org/2022/general_irc_meeting_4_may_2022.2022-05-04-15.01.log.html
Category:General_IRC_Meetings
Category:General_IRC_Meetings_2022
General IRC meeting 5 April 2023

Note: Meeting not held and deferred to 19 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 ===
* 5 April 2023, 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
** No proposals for KohaCon24 KohaCon24 Proposals
* Actions from last meeting
** tuxayo call in the lists for volunteer to open the bidding for KohaCon24 - completed, caroline volunteered
** cait add to next meeting agenda the topic of opening the bidding for KohaCon24 - completed
** tuxayo request Andrew N. an update about KohaCon23
=== Apologies ===
===Next meeting===
* General IRC meeting 19 April 2023
=== Minutes ===
* Minutes: http://meetings.koha-community.org/2023/general_irc_meeting_5_april_2023.2023-04-05-15.21.html
* Minutes (text): http://meetings.koha-community.org/2023/general_irc_meeting_5_april_2023.2023-04-05-15.21.txt
* Log: http://meetings.koha-community.org/2023/general_irc_meeting_5_april_2023.2023-04-05-15.21.log.html
Category:General_IRC_Meetings
Category:General_IRC_Meetings_2023
General IRC meeting 5 February 2014

=== 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 ===
5th February 2014 at 02:00 UTC
Conversions to your local time: 
* 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 on 3.8
* Update on 3.10
* Update on 3.12
* Update on 3.14
* Update on 3.16
* Kohacon14
* Actions from General IRC meeting 8 January 2014
* Set time of next meeting
===Apologies===
* Magnus Enger - sleeping
* Katrin Fischer - sleeping
===Next meeting===
General IRC meeting 5 March 2014
===Minutes===
* Minutes: http://meetings.koha-community.org/2014/koha_general_meeting__5_february_2013.2014-02-05-02.04.html
* Minutes (text): http://meetings.koha-community.org/2014/koha_general_meeting__5_february_2013.2014-02-05-02.04.txt
* Log: http://meetings.koha-community.org/2014/koha_general_meeting__5_february_2013.2014-02-05-02.04.log.html
Category:General_IRC_Meetings_2014
General IRC meeting 5 March 2014

=== 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 ===
5th March 2014 at 19:00 UTC
Conversions to your local time: 
* 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 on 3.8 
*Update on 3.10 
*Update on 3.12 
*Update on 3.14 
*Update on 3.16 
*KohaCon14 
*KohaCon15 - is it time to send an email to the list, asking potential hosts to start thinking about stepping forward? 
*Developers: How should we be handling preprocessing of client-side assets in the future? (LESS compiling, JS minification, etc). Should this be the developer's job or should the RM be running a build task?
*Actions from General IRC meeting 5 February 2014 
*Set time of next meeting
===Apologies===
===Next meeting===
===Minutes===
* Minutes: http://meetings.koha-community.org/2014/koha_general_meeting__5_march_2014.2014-03-05-19.05.html
* Minutes (text): http://meetings.koha-community.org/2014/koha_general_meeting__5_march_2014.2014-03-05-19.05.txt
* Log: http://meetings.koha-community.org/2014/koha_general_meeting__5_march_2014.2014-03-05-19.05.log.html
Category:General_IRC_Meetings_2014
General IRC meeting 6 July 2023

Note: The meeting originally planned for 5 April 2023, and then deferred to 19 April 2023, was not held.
=== 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 ===
* 6 July 2023, 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
* KohaCon23: 14-18 August 2023, Helsinki, Finland
** Registration now open
* KohaCon24
**KohaCon24 Proposals: one proposal received
** The 'different continent' rule for KohaCon24 no longer applies, as no eligible proposals were received (see the Development IRC Meeting 7 June 2023 minutes)
* Actions from previous meetings
** None
* General business
** ..
* Set date and time for the next meeting
=== Apologies ===
===Next meeting===
General_IRC_meeting_17_January_2024
===Minutes===
* Minutes: http://meetings.koha-community.org/2023/general_irc_meeting_6_july_2023.2023-07-06-14.53.html
* Minutes (text): http://meetings.koha-community.org/2023/general_irc_meeting_6_july_2023.2023-07-06-14.53.txt
* Log: http://meetings.koha-community.org/2023/general_irc_meeting_6_july_2023.2023-07-06-14.53.log.html
Category:General_IRC_Meetings
Category:General_IRC_Meetings_2023
General IRC meeting 7 December 2022

=== 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 ===
* 7 December 2022, 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 on KohaCon23, Helsinki
* Schedule KohaCon24 bidding
* Actions from last meeting
** No actions from the last meeting.
* General discussion
** FYI: Fediverse/Mastodon channel created @KohaILS@mastodon.world (David Nind)
=== Apologies ===
===Next meeting===
General_IRC_meeting_5_April_2023
===Minutes===
* Minutes: http://meetings.koha-community.org/2022/general_irc_meeting_7_december_2022.2022-12-07-14.02.html
* Minutes (text): http://meetings.koha-community.org/2022/general_irc_meeting_7_december_2022.2022-12-07-14.02.txt
* Log: http://meetings.koha-community.org/2022/general_irc_meeting_7_december_2022.2022-12-07-14.02.log.html
Category:General_IRC_Meetings
Category:General_IRC_Meetings_2022
General IRC meeting 7 July 2021

=== 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 ===
* 7 July 2021, 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 on releases:
** 21.11 (next release)
** 21.05 (stable release)
** 20.11 (old stable release)
** 20.05 (old old stable release)
** 19.11 (old old old stable release)
* KohaCon21 / KohaCon22
* Actions from last meeting
No actions from the last meeting.
=== Apologies ===
===Next meeting===
General_IRC_meeting_4_August_2021
===Minutes===
* Minutes: http://meetings.koha-community.org/2021/general_irc_meeting_7_july_2021.2021-07-07-14.05.html
* Minutes (text): http://meetings.koha-community.org/2021/general_irc_meeting_7_july_2021.2021-07-07-14.05.txt
* Log: http://meetings.koha-community.org/2021/general_irc_meeting_7_july_2021.2021-07-07-14.05.log.html
Category:General_IRC_Meetings
Category:General_IRC_Meetings_2021
General IRC meeting 7 September 2022

=== 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 ===
* 7 September 2022, 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
* Actions from last meeting: no actions from the last meeting.
* KohaCon23: consider proposals
=== Apologies ===
===Next meeting===
General IRC meeting 7 December 2022, 14 UTC 
===Minutes===
* Minutes: https://meetings.koha-community.org/2022/general_irc_meeting_7_september_2022.2022-09-07-14.04.txt    
* Minutes (text): https://meetings.koha-community.org/2022/general_irc_meeting_7_september_2022.2022-09-07-14.04.log.txt    
* Log: https://meetings.koha-community.org/2022/general_irc_meeting_7_september_2022.2022-09-07-14.04.html
  
Category:General_IRC_Meetings
Category:General_IRC_Meetings_2022
General IRC meeting 8 April 2025

=== 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 will use Hedgedoc to record the meeting minutes, including introductions (formerly #info) and actions (formerly #action) information.
The convention for introductions is:
- <NAME>, <ORG (optional)>, <PLACE (optional)>, <COUNTRY (optional)>
=== Time ===
* 8 April 2025, 13:00 UTC Time and Date.com converter for various local times
=== Agenda ===
* Introductions
* Announcements
* Actions from last meeting
** thd: copy over the old KohaCon page for proposals for 2026, announce on the mailing list
=== Apologies ===
===Next meeting===
__NEXT_MEETING__
===Minutes===
__MINUTES__
Category:General_IRC_Meetings
Category:General_IRC_Meetings_2025
General IRC meeting 8 January 2014

=== Place ===
The #koha IRC channel (IRC server irc.oftc.net).
=== Time ===
8th January 2014 at 10:00 UTC
Conversions to your local time: 
* 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 on 3.8
* Update on 3.10
* Update on 3.12
* Update on 3.14
* Update on 3.16
* Kohacon14
* Actions from General IRC meeting, 4 December 2013
* Set time of next meeting
===Apologies===
===Next meeting===
General IRC meeting 5 February 2014
===Minutes===
* Minutes
* Minutes (text)
* Log
Category:General_IRC_Meetings_2014
General IRC meeting 8 November 2024

=== 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 will use Hedgedoc to record the meeting minutes, including introductions (formerly #info) and actions (formerly #action) information.
The convention for introductions is:
- <NAME>, <ORG (optional)>, <PLACE (optional)>, <COUNTRY (optional)>
=== Time ===
* 8 November 2024, 14:00 UTC Time and Date.com converter for various local times
=== Agenda ===
* Introductions
* Announcements
* Actions from last meeting
** cait: to get in touch with Biblibre on retiring unused mailing lists
** paulderscheid: to document the new process for chairing and managing meetings on the Wiki
=== Apologies ===
===Next meeting===
General_IRC_meeting_4_February_2025
===Minutes===
 * Minutes: https://koha-hedgedoc.servers.llownd.net/General_IRC_meeting_8_November_2024
Category:General_IRC_Meetings
Category:General_IRC_Meetings_2024
General IRC meeting 9 June 2021

=== 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 ===
* 09 June 2021, 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
** The 21.11 Roadmap is now available to guide development for the 21.11 cycle - https://annuel.framapad.org/p/koha_21.11_roadmap
* Update on releases:
** 21.11 (next release)
** 21.05 (stable release)
** 20.11 (old stable release)
** 20.05 (old old stable release)
** 19.11 (old old old stable release)
* Actions from last meeting
No actions from the last meeting.
=== Apologies ===
* Martin Renvoize - Sorry, I have a clash with company meeting :(
===Next meeting===
General_IRC_meeting_7_July_2021
===Minutes===
* Minutes: http://meetings.koha-community.org/2021/general_irc_meeting_9_june_2021.2021-06-09-14.08.html
* Minutes (text): http://meetings.koha-community.org/2021/general_irc_meeting_9_june_2021.2021-06-09-14.08.txt
* Log: http://meetings.koha-community.org/2021/general_irc_meeting_9_june_2021.2021-06-09-14.08.log.html
Category:General_IRC_Meetings
Category:General_IRC_Meetings_2021
General 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 will use Hedgedoc to record the meeting minutes, including introductions (formerly #info) and actions (formerly #action) information.
The convention for introductions is:
- <NAME>, <ORG (optional)>, <PLACE (optional)>, <COUNTRY (optional)>
=== Time ===
__TIME__
=== Agenda ===
* Introductions
* Announcements
* Actions from last meeting
__ACTIONS__
=== Apologies ===
===Next meeting===
__NEXT_MEETING__
===Minutes===
__MINUTES__
__CATEGORIES__
General improvements for holds requests RFC

==RFC 3.2 - General hold request improvements==
I've already sent out a couple of RFCs about hold requests and friends, and will be sending out some more that relate to specific customer projects for LibLime, but I wanted to toss out a few ideas for general improvement. A large number of bugs have been turned up recently, most of which were postponed to 3.2, so I think the module is in need of some attention beyond the specific enhancements to be proposed.
First, the reserves table needs at least one more column to handle item-level requests properly. Right now, reserves.itemnumber serves two purposes: (a) identifying the requested item if the hold is item-level and (b) identifying the item selected to fill a title-level request. This is a problem because it can be hard to distinguish between bib- and item-level requests, and impossible to do so once the request is filled and the item is waiting on the hold shelf. I propose to replace reserves.itemnumber with two columns:
requested_itemnumber (NULL for bib-level requests, non-NULL otherwise)
supplied_itemnumber (non-NULL once the request is filled)
During a version upgrade, the value of reserves.itemnumber would be moved to requested_itemnumber if the priority > 0, and to supplied_itemnumber if the priority is 0. This is not a perfect heuristic, as a filled item-level request should set both columns, but I'm not sure we can do much better.
Second, i think the reserveconstraints table needs to be removed. It appears to date to a time when a biblio could have more than one bilbioitem, but now that the relationship is one-to-one, it cannot serve its original purpose of limiting a request to only specific formats attached to a bib. Removing reserveconstraints would leave Koha supporting bib-level and item-level requests. If something in between bib-level and item-level is still needed, I suppose that it would have to be based on selecting which item types are suitable for filling a request on a given bib - for example, if the library attaches codex and audiobook items to the same bib and gives them different item types, reservecontraints (or its successor) might contain a list of item types.
Third, since larger Koha libraries can have hold request queues a couple hundred patrons long or longer, I'm going to experiment with ways of managing the priority value so that it is possible to fill hold requests without having to touch every request in the queue, both to aid performance and to possibly avoid bugs where multiple requests for a given bib have the same priority.
Fourth, I want to add an auto_increment reserve_id column to reserves to give us an opaque request ID to simplify FK relationships with tables such as the successor to reserveconstraints and additional tables that we may need as we extend the request system to handle recalls and other types of requests.
Fifth, I want to do some work with C4::Reserves to cleanup the FIXMEs, improve the POD, and add functions to separate handling when items can be requested versus when they are available to fill hold requests.
Category:Abandoned_RFC
Generalise the use Template Toolkit plugins

= Generalise the use Template Toolkit plugins =
== Decision ==
This discussion reached a consensus of "use it on a volunteer basis", but also "encourage the use of plugins".
For bug 4078, the RM (paul) has asked to have a plugin version of this -nice- feature, as it's really a perfect candidate for plugins
== Introduction ==
Chris_c recently has added a plugin to manage the display of dates into Koha (see http://wiki.koha-community.org/wiki/Coding_Guidelines#Displaying_dates), that is very interesting.
Do we want to generalise this mechanism ? When do we want to use it ?
For example, the patch for bug http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=4078 could nicely use this mechanism
== Possible solutions ==
<<PP: i'm not really happy with the following chapters I wrote, but can't find a better organisation, feel free to update !>>
=== Use is as much as possible ===
It means we define a strict rule saying "every display that could be done through a plugin must", and any patch not respecting this rule would be discarded.
For example, we could have a plugin to display "patron basic information", from borrowernumber.
Everytime we must display a patron firstname-surname-category-zipcode-phone, we use this plugin.
=== Pros ===
*highly consistent : if we want, in my example, add the number expiry date, just change the plugin, and the expiry date will appear everywhere !
=== Cons ===
=== Use it on a volunteer basis ===
It means patch submitters could use this plugin system, but it won't be mandatory
=== Pros ===
=== Cons ===
Category:Development
Generating Public SSH Keys

For some git servers you will need to provide the host with a Public SSH Key. Below are the instructions for generating these keys.
== On Linux and MacOS X ==
* ssh-keygen - you can probably run it as "ssh-keygen -t dsa" and the public key will be in a file called something like id_des.pub (its reply will tell you).
== On Windows ==
* PuTTYgen - choose SSH2 DSA and most Linux-based servers will want the "Public key for pasting into authorized_keys file" (most use openssh).
Category:Tips_&_Tricks
Category:Tips_&_Tricks
Getting Started

= Roadmap =
* Learn what Koha is
* Learn about Koha development and the Koha community development workflow
* Join the community mailing lists and IRC, introduce yourself! Get to know who's who on IRC. Put faces to those names.
* Check out the Community dashboard.
* Test patches using the Koha Sandboxes.
* Get yourself set up with your own testing environment.
* Find yourself an editor or IDE you are comfortable with.
* Sign off on patches.
* Submit patches of your own.
* Join the QA Team.
* Become a Release Maintainer.
* Become a Release Manager.
* Master all of time and space.
= Foundational technologies used in Koha =
== Git ==
The Koha community uses Git for version control.
GitHowTo
Oh My Git!
Git Immersion
== MariaDB/MySQL ==
Koha uses MariaDB/MySQL as it's primary data store. As such it's important to understand SQL in order to interact with the database.
=== SQL Tutorials ===
Codecademy
LearnSQLOnline.org
SQLZOO
== Perl ==
Koha uses Perl for all server-side development. Koha's REST API is powered by the Mojolicious Perl Framework.
=== Perl Tutorials ===
learn.perl.org
Educative.io
Perltuts
== JavaScript ==
Koha uses Javascript for all front-end development, with an emphasis on jQuery.
Vue.js will be used in Koha once the ERM module is part of Koha.
=== Javascript Tutorials ===
learn-js.org
Codecademy
=== jQuery Tutorials ===
jquery.com
=== Vue.js Tutorials ===
VueJs.org
== Zebra/Elastic ==
Koha's catalog search is powered by Zebra and/or Elastic depending on a server's specific configuration.
Unless you are specifically interested in modifying Koha's searching abilities, it is unlikely you will need to understand Zebra or Elastic internals.
== Apache ==
Like Zebra and Elastic, it's less likely you'll need to modify Koha's Apache configurations, but it necessary sometimes!
=== Apache Tutorials ===
Geek University