From kohanews at gmail.com Sat Apr 1 00:12:41 2017 From: kohanews at gmail.com (kohanews) Date: Fri, 31 Mar 2017 15:12:41 -0700 Subject: [Koha-devel] Koha Community Newsletter: March 2017 Message-ID: Fellow Koha users: The Koha Community Newsletter for March 2017 is here: https://koha-community.org/koha-community-newsletter-march-2017/ Many thanks to the folks who submitted articles and news to this month's newsletter. Please feel free to email me with any corrections or suggestions. Thanks! -- Chad Roseburg Editor, Koha Community Newsletter -------------- next part -------------- An HTML attachment was scrubbed... URL: From barton at bywatersolutions.com Sat Apr 1 00:28:17 2017 From: barton at bywatersolutions.com (Barton Chittenden) Date: Fri, 31 Mar 2017 18:28:17 -0400 Subject: [Koha-devel] Documenting notices and scripts Message-ID: I've been working on documenting all of the possible notices in the letter table, in terms of letter_code, available markup, and which tables we can pull data from. this is collected here: https://wiki.koha-community.org/wiki/Customising_Notices_and_Slips#Notice_Specific_Markup I updated the wiki page this morning, everything is up-to-date with master... but there's one thing I don't understand: SendAlerts. It looks like the letter code is passed in via cgi param, and I don't know what letter_codes are available for the calls in C4/Serials.pm, acqui/ lateorders.pl and serials/claims.pl Searching for enlightenment, --Barton -------------- next part -------------- An HTML attachment was scrubbed... URL: From tomascohen at gmail.com Mon Apr 3 14:49:01 2017 From: tomascohen at gmail.com (Tomas Cohen Arazi) Date: Mon, 03 Apr 2017 12:49:01 +0000 Subject: [Koha-devel] KohaDevBox refatoring Message-ID: Hi everyone, this wekend I took the time to reorganize the tasks that are ran to get KohaDevBox up and running. The main task was splitting some steps (like koha-common install, instance creation and gitifying) This makes it easier to spot potential order issues. As usual, I hope you can have some time to test it and file bugs if needed. I'll try to fix them ASAP. Thanks! -- Tom?s Cohen Arazi Theke Solutions (https://theke.io ) ? +54 9351 3513384 GPG: B2F3C15F -------------- next part -------------- An HTML attachment was scrubbed... URL: From jonathan.druart at bugs.koha-community.org Tue Apr 4 15:54:58 2017 From: jonathan.druart at bugs.koha-community.org (Jonathan Druart) Date: Tue, 04 Apr 2017 13:54:58 +0000 Subject: [Koha-devel] What's on in koha-devel #11 Message-ID: Hello librarians and developers, Not much has happened this month in terms of development. Things are going very slowly at the moment, despite the hackfest in Marseille. We see a lot of new people on the mailing list and the IRC channel asking for questions, but we need more people to be involved in the discussions and the signoff process. There are hundreds of people on this list, you need to know that the Koha community needs you to make the project moving forward. I know that nobody has enough time, but you know one hour per week of even per month can help a lot. It is very easy, fun and interesting :) = How to get involved? = The first action would be to join us on the #koha IRC channel and the koha-devel mailing list. Start by presenting yourself, where do you come from, what do you do? For how long have you been using Koha? How do you think you can help? Attend meetings! We have two kinds of monthly meeting. There is a general one to talk about koha-related stuffs, and the development meeting to talk about technical stuffs. It is important for the community to have a place to be all together and try to make things move. If you are a librarian, we need you to tell developers the directions they need to go. Open bug reports It is important to know that everybody can open new bug reports on our bug tracker (https://bugs.koha-community.org). It is useful for the development team to know the new bugs. And it is also important for you to search for known bugs. A lot of bugs are known from developers but we do not know how to fix them because we are waiting for feedbacks from users. The dashboard (http://dashboard.koha-community.org) is very helpful to know the "hot" bugs that need to be fixed/tested/QAed. The "Overall bug traker health status" section displays the number of new bugs that are important to follow, make moving. If a developer submits a patch for the bug you opened, try and test it! Test bugs Here is how you can really makes things move for the community. You become involved in the development process and make the Koha project better. Sandboxes (https://wiki.koha-community.org/wiki/Sandboxes) are available to test patch easily. You do not need to install anything on your computer and do not need any technical skills. If you are a Koha user, you can test patches! Write patches If you are a developer or have a minimum of technical skills you can write your own patches and fixes bugs or develop new feature. Our dedicated wiki page (wiki.koha-community.org/wiki/Submitting_A_Patch) will guide you over the different steps. It is very easy to get a development environment using KohaDevBox ( https://github.com/digibib/kohadevbox) Start with small patches :) = Refactoring = If you have read my previous "what's on in koha-devel" emails, you may have noticed I talked a lot of "refactoring" bugs. And maybe you do not know what it is and what it brings. The Koha codebase is aged/old, and has grown very quickly since 2006. Since the last few years the development team decided to make the code more robust and slow the integration of patches, getting a stronger integration process. That's why we need to have at least one tester validating the patches, then one QAer to review the patch technically and finally the Release Manager to push it. That's mean 4 independent persons for a single patch. That made our codebase stronger and less regression prone. Some part of the code now needs to be rewritten, and it is why I have focussed on the "refactoring" work over the last year. The goal is to rewrite modules of Koha, step by step. It cleans the code, makes it more readable, reduces the number of lines, centralise the responsibilities, homogenise the code, fixes bugs, adds test coverage, etc. On the mid-long term it means a modern application, easy to maintain, robust, flexible. The bugs will be easier to fix, the enhancements will be quicker to develop and so less expensive. Do you start to understand how it is useful? So yes, it's boring to test because it does not bring anything new to the interface, but the project needs it. If you have been using Koha for months or years, it made you save money, it makes you happy to use it and you love it. If you already got answer from people on the mailing lists or the IRC channel, it's time to say thank you, by getting involved! If you have any specific questions on how to get involved, you can join me on the IRC channel or by email. I can help and guide you if necessary. A developer that loves Koha but needs help, Jonathan -------------- next part -------------- An HTML attachment was scrubbed... URL: From chrisc at catalyst.net.nz Wed Apr 5 00:36:42 2017 From: chrisc at catalyst.net.nz (Chris Cormack) Date: Wed, 5 Apr 2017 10:36:42 +1200 Subject: [Koha-devel] What's on in koha-devel #11 In-Reply-To: References: Message-ID: <20170404223642.vnaqside2cshuhvv@rorohiko.wgtn.cat-it.co.nz> Hi All I want to second what Jonathan has written, we really do appreciate the people who take the time to test, file bugs, document, translate etc. Who knows, you might even become an Unsung hero, https://blog.bigballofwax.co.nz/2017/04/05/unsung-heroes-of-koha-32-josef-moravec/ Chris * Jonathan Druart (jonathan.druart at bugs.koha-community.org) wrote: > Hello librarians and developers, > Not much has happened this month in terms of development. Things are going > very slowly at the moment, despite the hackfest in Marseille. > We see a lot of new people on the mailing list and the IRC channel asking > for questions,?? but we need more people to be involved in the discussions > and the signoff process. There are hundreds of people on this list, you > need to know that the Koha community needs you to make the project moving > forward. I know that nobody has enough time, but you know one hour per > week of even per month can help a lot. It is very easy, fun and > interesting :) > = How to get involved? = > The first action would be to join us on the #koha IRC channel and the > koha-devel mailing list. Start by presenting yourself, where do you come > from, what do you do? For how long have you been using Koha? How do you > think you can help? > Attend meetings! > We have two kinds of monthly meeting. There is a general one to talk about > koha-related stuffs, and the development meeting to talk about technical > stuffs. It is important for the community to have a place to be all > together and try to make things move. If you are a librarian, we need you > to tell developers the directions they need to go. > Open bug reports > It is important to know that everybody can open new bug reports on our bug > tracker (https://bugs.koha-community.org). It is useful for the > development team to know the new bugs. And it is also important for you to > search for known bugs. A lot of bugs are known from developers but we do > not know how to fix them because we are waiting for feedbacks from users. > The dashboard (http://dashboard.koha-community.org) is very helpful to > know the "hot" bugs that need to be fixed/tested/QAed. The "Overall bug > traker health status" section displays the number of new bugs that are > important to follow, make moving. > If a developer submits a patch for the bug you opened, try and test it! > Test bugs > Here is how you can really makes things move for the community. You become > involved in the development process and make the Koha project better. > Sandboxes (https://wiki.koha-community.org/wiki/Sandboxes) are available > to test patch easily. You do not need to install anything on your computer > and do not need any technical skills. If you are a Koha user, you can test > patches! > Write patches > If you are a developer or have a minimum of technical skills you can write > your own patches and fixes bugs or develop new feature. > Our dedicated wiki page (wiki.koha-community.org/wiki/Submitting_A_Patch) > will guide you over the different steps. > It is very easy to get a development environment using KohaDevBox > (https://github.com/digibib/kohadevbox) > Start with small patches :) > = Refactoring = > If you have read my previous "what's on in koha-devel" emails, you may > have noticed I talked a lot of "refactoring" bugs. > And maybe you do not know what it is and what it brings. > The Koha codebase is aged/old, and has grown very quickly since 2006. > Since the last few years the development team decided to make the code > more robust and slow the integration of patches, getting a stronger > integration process. That's why we need to have at least one tester > validating the patches, then one QAer to review the patch technically and > finally the Release Manager to push it. That's mean 4 independent persons > for a single patch. That made our codebase stronger and less regression > prone. > Some part of the code now needs to be rewritten, and it is why I have > focussed on the "refactoring" work over the last year. The goal is to > rewrite modules of Koha, step by step. It cleans the code, makes it more > readable, reduces the number of lines, centralise the responsibilities, > homogenise the code, fixes bugs, adds test coverage, etc. > On the mid-long term it means a modern application, easy to maintain, > robust, flexible. The bugs will be easier to fix, the enhancements will be > quicker to develop and so less expensive. > Do you start to understand how it is useful? > So yes, it's boring to test because it does not bring anything new to the > interface, but the project needs it. > If you have been using Koha for months or years, it made you save money, > it makes you happy to use it and you love it. If you already got answer > from people on the mailing lists or the IRC channel, it's time to say > thank you, by getting involved! > If you have any specific questions on how to get involved, you can join me > on the IRC channel or by email. I can help and guide you if necessary. > A developer that loves Koha but needs help, > Jonathan >_______________________________________________ >Koha-devel mailing list >Koha-devel at lists.koha-community.org >http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel >website : http://www.koha-community.org/ >git : http://git.koha-community.org/ >bugs : http://bugs.koha-community.org/ -- Chris Cormack Catalyst IT Ltd. +64 4 803 2238 PO Box 11-053, Manners St, Wellington 6142, New Zealand -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: not available URL: From julian.maurice at biblibre.com Mon Apr 10 10:39:44 2017 From: julian.maurice at biblibre.com (Julian Maurice) Date: Mon, 10 Apr 2017 10:39:44 +0200 Subject: [Koha-devel] Plack and CGI : where to put initialization code ? Message-ID: Hello developers, I need to execute code at the beginning of every request. For now it's in a BEGIN block. It works well in CGI mode, but not at all with plack (it's only executed once). I tried moving the BEGIN block into a sub init(), calling this sub in the BEGIN block and in the PSGI file (in CGI::new wrapper). It works but it doesn't feel "right". Is there a common place to put this kind of code ? Should I use the L1 cache (which is flushed at every request) to store some state (initialized or no) and call init() in every method of the module or something like that ? -- Julian Maurice BibLibre From oha at oha.it Mon Apr 10 10:42:48 2017 From: oha at oha.it (Francesco Rivetti) Date: Mon, 10 Apr 2017 10:42:48 +0200 Subject: [Koha-devel] Plack and CGI : where to put initialization code ? In-Reply-To: References: Message-ID: On 10. april 2017 10:39, Julian Maurice wrote: > I need to execute code at the beginning of every request. For now it's > in a BEGIN block. It works well in CGI mode, but not at all with plack > (it's only executed once). > I tried moving the BEGIN block into a sub init(), calling this sub in > the BEGIN block and in the PSGI file (in CGI::new wrapper). It works but > it doesn't feel "right". probably the best way in plack is to "enable" it in the build chain, like it is happening with Koha::Middleware::SetEnv in plack.psgi HTH F From julian.maurice at biblibre.com Mon Apr 10 12:00:12 2017 From: julian.maurice at biblibre.com (Julian Maurice) Date: Mon, 10 Apr 2017 12:00:12 +0200 Subject: [Koha-devel] Plack and CGI : where to put initialization code ? In-Reply-To: References: Message-ID: <6c4c22d5-bb84-6fdb-27d4-45ec4a173642@biblibre.com> Le 10/04/2017 ? 10:42, Francesco Rivetti a ?crit : > On 10. april 2017 10:39, Julian Maurice wrote: >> I need to execute code at the beginning of every request. For now it's >> in a BEGIN block. It works well in CGI mode, but not at all with plack >> (it's only executed once). >> I tried moving the BEGIN block into a sub init(), calling this sub in >> the BEGIN block and in the PSGI file (in CGI::new wrapper). It works but >> it doesn't feel "right". > > probably the best way in plack is to "enable" it in the build chain, > like it is happening with Koha::Middleware::SetEnv in plack.psgi > > HTH > > F I haven't thought of that. I'll give it a try. Thanks! -- Julian Maurice BibLibre From kyle.m.hall at gmail.com Mon Apr 10 12:57:59 2017 From: kyle.m.hall at gmail.com (Kyle Hall) Date: Mon, 10 Apr 2017 06:57:59 -0400 Subject: [Koha-devel] Koha 17.05 Dates Message-ID: Here is my planned timeline for the Koha 17.05 release: May 5 - Feature Slush May 12 - 1st Draft of Release Notes May 19 - Feature Freeze, Release Beta, 2nd Draft of Release Notes May 26th - Final Release If anyone sees a need to modify this timeline, please let me know! Kyle http://www.kylehall.info ByWater Solutions ( http://bywatersolutions.com ) Meadville Public Library ( http://www.meadvillelibrary.org ) Crawford County Federated Library System ( http://www.ccfls.org ) -------------- next part -------------- An HTML attachment was scrubbed... URL: From Katrin.Fischer.83 at web.de Mon Apr 10 13:47:59 2017 From: Katrin.Fischer.83 at web.de (Katrin Fischer) Date: Mon, 10 Apr 2017 13:47:59 +0200 Subject: [Koha-devel] Koha 17.05 Dates In-Reply-To: References: Message-ID: An HTML attachment was scrubbed... URL: From kyle.m.hall at gmail.com Mon Apr 10 16:58:11 2017 From: kyle.m.hall at gmail.com (Kyle Hall) Date: Mon, 10 Apr 2017 10:58:11 -0400 Subject: [Koha-devel] Koha 17.05 Dates In-Reply-To: References: Message-ID: Based on feedback, I'm tweaking the release dates a bit, here are the updated dates: May 5 - Feature Slush May 12 - Feature Freeze, String Freeze, 1st Draft of Release Notes May 19 - Release Beta, 2nd Draft of Release Notes May 26th - Final Release http://www.kylehall.info ByWater Solutions ( http://bywatersolutions.com ) Meadville Public Library ( http://www.meadvillelibrary.org ) Crawford County Federated Library System ( http://www.ccfls.org ) On Mon, Apr 10, 2017 at 6:57 AM, Kyle Hall wrote: > Here is my planned timeline for the Koha 17.05 release: > May 5 - Feature Slush > May 12 - 1st Draft of Release Notes > May 19 - Feature Freeze, Release Beta, 2nd Draft of Release Notes > May 26th - Final Release > > If anyone sees a need to modify this timeline, please let me know! > > Kyle > > http://www.kylehall.info > ByWater Solutions ( http://bywatersolutions.com ) > Meadville Public Library ( http://www.meadvillelibrary.org ) > Crawford County Federated Library System ( http://www.ccfls.org ) > -------------- next part -------------- An HTML attachment was scrubbed... URL: From kyle.m.hall at gmail.com Mon Apr 10 18:03:20 2017 From: kyle.m.hall at gmail.com (Kyle Hall) Date: Mon, 10 Apr 2017 12:03:20 -0400 Subject: [Koha-devel] Roles for Koha 17.10 Message-ID: Hey all, it's about that time of year again! I've created a skeleton wiki page for the Koha 17.10 roles! I've left it nearly all TBD so if you want to continue your role, please update this page! https://wiki.koha-community.org/wiki/Roles_for_17.11 Kyle http://www.kylehall.info ByWater Solutions ( http://bywatersolutions.com ) Meadville Public Library ( http://www.meadvillelibrary.org ) Crawford County Federated Library System ( http://www.ccfls.org ) -------------- next part -------------- An HTML attachment was scrubbed... URL: From kyle.m.hall at gmail.com Mon Apr 10 18:03:50 2017 From: kyle.m.hall at gmail.com (Kyle Hall) Date: Mon, 10 Apr 2017 12:03:50 -0400 Subject: [Koha-devel] Roles for Koha 17.10 In-Reply-To: References: Message-ID: I just wanted to make sure everyone knows that 17.10 was a typo and I meant 17.11 ; ) http://www.kylehall.info ByWater Solutions ( http://bywatersolutions.com ) Meadville Public Library ( http://www.meadvillelibrary.org ) Crawford County Federated Library System ( http://www.ccfls.org ) On Mon, Apr 10, 2017 at 12:03 PM, Kyle Hall wrote: > Hey all, it's about that time of year again! I've created a skeleton wiki > page for the Koha 17.10 roles! I've left it nearly all TBD so if you want > to continue your role, please update this page! > > https://wiki.koha-community.org/wiki/Roles_for_17.11 > > Kyle > > http://www.kylehall.info > ByWater Solutions ( http://bywatersolutions.com ) > Meadville Public Library ( http://www.meadvillelibrary.org ) > Crawford County Federated Library System ( http://www.ccfls.org ) > -------------- next part -------------- An HTML attachment was scrubbed... URL: From jonathan.druart at bugs.koha-community.org Mon Apr 10 20:43:47 2017 From: jonathan.druart at bugs.koha-community.org (Jonathan Druart) Date: Mon, 10 Apr 2017 18:43:47 +0000 Subject: [Koha-devel] Roles for Koha 17.10 In-Reply-To: References: Message-ID: TBD for "Totally Brain Dead", right? http://acronyms.thefreedictionary.com/TBD On Mon, 10 Apr 2017 at 13:03 Kyle Hall wrote: > Hey all, it's about that time of year again! I've created a skeleton wiki > page for the Koha 17.10 roles! I've left it nearly all TBD so if you want > to continue your role, please update this page! > > https://wiki.koha-community.org/wiki/Roles_for_17.11 > > Kyle > > http://www.kylehall.info > ByWater Solutions ( http://bywatersolutions.com ) > Meadville Public Library ( http://www.meadvillelibrary.org ) > Crawford County Federated Library System ( http://www.ccfls.org ) > _______________________________________________ > Koha-devel mailing list > Koha-devel at lists.koha-community.org > http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > website : http://www.koha-community.org/ > git : http://git.koha-community.org/ > bugs : http://bugs.koha-community.org/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From tomascohen at gmail.com Tue Apr 11 12:25:24 2017 From: tomascohen at gmail.com (Tomas Cohen Arazi) Date: Tue, 11 Apr 2017 10:25:24 +0000 Subject: [Koha-devel] Koha 17.05 Dates In-Reply-To: References: Message-ID: Excelente! El lun., 10 de abr. de 2017 11:58 AM, Kyle Hall escribi?: > Based on feedback, I'm tweaking the release dates a bit, here are the > updated dates: > May 5 - Feature Slush > May 12 - Feature Freeze, String Freeze, 1st Draft of Release Notes > May 19 - Release Beta, 2nd Draft of Release Notes > May 26th - Final Release > > > > > http://www.kylehall.info > ByWater Solutions ( http://bywatersolutions.com ) > Meadville Public Library ( http://www.meadvillelibrary.org ) > Crawford County Federated Library System ( http://www.ccfls.org ) > > On Mon, Apr 10, 2017 at 6:57 AM, Kyle Hall wrote: > > Here is my planned timeline for the Koha 17.05 release: > May 5 - Feature Slush > May 12 - 1st Draft of Release Notes > May 19 - Feature Freeze, Release Beta, 2nd Draft of Release Notes > May 26th - Final Release > > If anyone sees a need to modify this timeline, please let me know! > > Kyle > > http://www.kylehall.info > ByWater Solutions ( http://bywatersolutions.com ) > Meadville Public Library ( http://www.meadvillelibrary.org ) > Crawford County Federated Library System ( http://www.ccfls.org ) > > > _______________________________________________ > Koha-devel mailing list > Koha-devel at lists.koha-community.org > http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > website : http://www.koha-community.org/ > git : http://git.koha-community.org/ > bugs : http://bugs.koha-community.org/ -- Tom?s Cohen Arazi Theke Solutions (https://theke.io ) ? +54 9351 3513384 GPG: B2F3C15F -------------- next part -------------- An HTML attachment was scrubbed... URL: From M.de.Rooy at rijksmuseum.nl Tue Apr 11 13:49:42 2017 From: M.de.Rooy at rijksmuseum.nl (Marcel de Rooy) Date: Tue, 11 Apr 2017 11:49:42 +0000 Subject: [Koha-devel] Roles for Koha 17.10 In-Reply-To: References: , Message-ID: To be discontinued ________________________________ Van: koha-devel-bounces at lists.koha-community.org namens Jonathan Druart Verzonden: maandag 10 april 2017 20:43:47 Aan: Koha Devel Onderwerp: Re: [Koha-devel] Roles for Koha 17.10 TBD for "Totally Brain Dead", right? http://acronyms.thefreedictionary.com/TBD On Mon, 10 Apr 2017 at 13:03 Kyle Hall > wrote: Hey all, it's about that time of year again! I've created a skeleton wiki page for the Koha 17.10 roles! I've left it nearly all TBD so if you want to continue your role, please update this page! https://wiki.koha-community.org/wiki/Roles_for_17.11 Kyle http://www.kylehall.info ByWater Solutions ( http://bywatersolutions.com ) Meadville Public Library ( http://www.meadvillelibrary.org ) Crawford County Federated Library System ( http://www.ccfls.org ) _______________________________________________ Koha-devel mailing list Koha-devel at lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From nick at bywatersolutions.com Tue Apr 11 22:33:20 2017 From: nick at bywatersolutions.com (Nick Clemens) Date: Tue, 11 Apr 2017 20:33:20 +0000 Subject: [Koha-devel] Koha Development Meeting Reminder Message-ID: Hi All, Just a friendly reminder that the next Koha Development IRC meeting is tomorrow, 12 April 2017, at 19UTC And a reminder that April is quickly followed by May so now is a good time to come and mention anything of import for 17.05. Here is a converter for local date and time: https://www.timeanddate.com/worldclock/fixedtime.html?msg=Koha+Developers+IRC+Meeting&iso=20170412T19 The agenda is on the wiki, please add any topics you wish to discuss https://wiki.koha-community.org/wiki/Development_IRC_meeting_12_April_2017#Apologies I will try to send an ES update before or after the meeting, hope to see you all there :-) -Nick -------------- next part -------------- An HTML attachment was scrubbed... URL: From joy at bywatersolutions.com Tue Apr 11 23:11:36 2017 From: joy at bywatersolutions.com (Joy Nelson) Date: Tue, 11 Apr 2017 16:11:36 -0500 Subject: [Koha-devel] Linked Data Discussion from Hackfest Message-ID: Here's a quick recap of the linked data discussion we had at Hackfest in Marseille. It's a two part email: a little linked data background by me and technical discussion by Nick Clemens. Thanks! joy & nick Joy Nelson I gave a brief presentation on linked data and the benefits and potential challenges inherent in moving towards a linked data system. It was based loosely on the presentation given at KohaCon 2016 which can be viewed here: https://www.slideshare.net/talljoy/kohacon2016 We discussed some of the challenges in linked data. One of those is "Choice of Linked Data Vocabulary". In the U.S. the Library of Congress is developing BibFrame as a MARC replacement. Ideally, the system created would be 'vocabulary agnostic'. The Koha linked data system should allow users the ability to utilize one of many vocabularies or *any* vocabulary they wish. (bibframe, bf:lite, schema.org, dublin core, etc) Identifying the purpose of Linked Data is another area that needs discussion and some consensus. How do libraries envision themselves using this kind of data/system? -Do we create triplestores converted from MARC to store and allow those stores to be crawled? Thereby making a collection visible on the web in search results. -Do we concentrate on creating a system that allows for libraries to connect their data to other libraries, data stores external or internally? For example, Is the goal to link our authors and subject tags to URIs on the web that we can pull in to Koha and display more information to the user? -Do we create linked data URIs for special libraries (museums, academic institutions) to provide to other institutions and allow others to link into their system to gather data to display to their users? Linked Data is a fundamental shift in how we think about our data and how we will use that data. It is a much more cooperative venture in cataloging that will provide benefits to both staff and patrons. Nick Clemens I presented the basic work I have done on implementing a triplestore backend for Koha which can be found on github here: https://github.com/bywatersolutions/bywater-koha-devel/tree/RDF The code is very basic so far and does a few things: 1 - Implements Koha::RDF::Store as a base for which all individual backend implementations will be built 2 - Adds a beginning implementation of RDF::Trine to allow storage and retrieval of RDF triples 3 - A very basic form on the intranet details page to enter a predicate and subject (assuming the URL of the details page) as the object The code is a start and begins to raise a few of concerns which I see and what we need to do to continue. I am very interested in developing Koha/RDF in a way that is backend agnostic and allows for differing front end implementations. The next steps I see are: 1 - We must agree on a common set of subroutines that any backend will support. They will require basic CRUD and options for retrieving in various formats 2 - We will need to develop endpoints: A SPARQL endpoint, and REST endpoints for CRUD, and OAI endpoints 3 - We need to decide on how we will mint and serve URIs - we could continue to use the current details URLs and add parameters for format to supply triples or xml, however, for things like works and authors we will need some method of linking. Links with parameters are not as 'cool' as named or numbered URIs but provides the ability for linking our data out to other resources, making it crawlable, and internally linking. Once we can agree on building a base together, than we can all proceed to develop in different directions as we see fit and provide various options that can all be pursued without conflict or duplicated effort. -- Joy Nelson Director of Migrations ByWater Solutions Support and Consulting for Open Source Software Office: Fort Worth, TX Phone/Fax (888)900-8944 What is Koha? -------------- next part -------------- An HTML attachment was scrubbed... URL: From marka at pobox.com Wed Apr 12 14:57:23 2017 From: marka at pobox.com (Mark Alexander) Date: Wed, 12 Apr 2017 08:57:23 -0400 Subject: [Koha-devel] Roles for Koha 17.10 In-Reply-To: References: Message-ID: <1492001807-sup-5885@t60p> Excerpts from Jonathan Druart's message of 2017-04-10 18:43:47 +0000: > TBD for "Totally Brain Dead", right? Perhaps "to be determined"? From kyle.m.hall at gmail.com Wed Apr 12 20:25:25 2017 From: kyle.m.hall at gmail.com (Kyle Hall) Date: Wed, 12 Apr 2017 14:25:25 -0400 Subject: [Koha-devel] Roles for Koha 17.10 In-Reply-To: <1492001807-sup-5885@t60p> References: <1492001807-sup-5885@t60p> Message-ID: We have a winner! Enjoy your karma Mark! : ) Kyle http://www.kylehall.info ByWater Solutions ( http://bywatersolutions.com ) Meadville Public Library ( http://www.meadvillelibrary.org ) Crawford County Federated Library System ( http://www.ccfls.org ) On Wed, Apr 12, 2017 at 8:57 AM, Mark Alexander wrote: > Excerpts from Jonathan Druart's message of 2017-04-10 18:43:47 +0000: > > TBD for "Totally Brain Dead", right? > > Perhaps "to be determined"? > _______________________________________________ > Koha-devel mailing list > Koha-devel at lists.koha-community.org > http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > website : http://www.koha-community.org/ > git : http://git.koha-community.org/ > bugs : http://bugs.koha-community.org/ > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dcook at prosentient.com.au Thu Apr 13 09:35:00 2017 From: dcook at prosentient.com.au (David Cook) Date: Thu, 13 Apr 2017 17:35:00 +1000 Subject: [Koha-devel] RDF Dereferencing/tracing/following links Message-ID: <000c01d2b428$74efa680$5ecef380$@prosentient.com.au> Hi all, The key to Linked Data is obviously the links, but I don?t think any of us quite know how the links actually work. In theory, I imagine having a record (ie a set of triples), in a local triplestore, which links to records available on the Internet. Periodically, those records are downloaded, and stored in a local triplestore as a cache. Then we somehow follow the links as they are stored in our local triplestore and have a set of string literals which we can show to users on a web page. In practice, I don?t know how that would work. I can see us getting a list of record subjects in our local triplestore, and then iterating through each one to download the links in its objects. But I don?t know where we?d put that content. I also don?t know if we?d recurse into that content to follow more links or not. Let?s say that we store that content in named graph called ?cache?. When it comes time to re-trace the links for our list of record subjects, how do we know what local content to delete? In theory, we could use the URI from the object, but many records contain many subjects, so even if we did delete that subject from ?cache?, we haven?t deleted the other subjects that it links to internally in the triplestore. I?m going to ask around to see if anyone can enlighten me. I?m hoping Petter might be able to shed light on how Oslo Public Library makes it work, especially in the context of ls.ext interfacing with Koha! David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Direct: 02 8005 0595 -------------- next part -------------- An HTML attachment was scrubbed... URL: From kohanews at gmail.com Fri Apr 14 18:00:10 2017 From: kohanews at gmail.com (kohanews) Date: Fri, 14 Apr 2017 09:00:10 -0700 Subject: [Koha-devel] Call for news: April 2017 Newsletter Message-ID: <1d98b579-3eef-f69b-0163-8e325613ae73@gmail.com> I'm collecting news for the April newsletter. Send anything noteworthy to: k o h a news AT gmail dot com News criteria: --------------------------- ** For events **: - Please include dates for past events. If I can't find dates I may not add it. - Announcements for future events with dates T.B.A. are fine ...Eg., Kohacon - For past events , **** one month back is the cut-off ****. * News items can be of any length. * Images are fine * Anything and everything Koha. * Submit by the 26th of the month. If you are working on an interesting project or development related to Koha, please let me know and I'll include it in the development section. -- Chad Roseburg Editor, Koha Community Newsletter From ephetteplace at cca.edu Wed Apr 19 02:25:53 2017 From: ephetteplace at cca.edu (Eric Phetteplace) Date: Tue, 18 Apr 2017 17:25:53 -0700 Subject: [Koha-devel] Gender-neutral pronouns Message-ID: Hi list, I opened bug #18432 https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18432 because I saw several places in the Koha codebase where the pronoun "he" was being used to refer to a generic third person who could be of any gender. Jonathan Druart noted that this should be a coding guideline, as otherwise new instances of gendered pronouns might continue to be added. Perhaps it belongs on the "Terminology" page of the wiki? So here's my proposal. I'm trying to be concise. ---- *Use gender neutral pronouns* When referring to a person who could be of any gender, you should use the words they/them/their. This goes for code comments, text in templates, and strings in tests. For example, here's a string from a patrons test updated to be gender neutral. Before*:* is( $total, $enrolmentfee_K + $enrolmentfee_J, "Kid growing and become a juvenile, he should pay " . ( $enrolmentfee_K + $enrolmentfee_J ) ); After: is( $total, $enrolmentfee_K + $enrolmentfee_J, "Kid growing and become a juvenile, they should pay " . ( $enrolmentfee_K + $enrolmentfee_J ) ); Gender neutral terms are preferable for a few reasons. They're more welcoming, showing that Koha expects users and contributors to be of any gender. They're also more accurate. Inappropriately using a particular gender can cause confusion, leading someone to believe that code operates differently based on the value of borrowers.sex, for instance. ---- I hope that's clear. I'm happy to reword it, and to attend the next Koha developers meeting to explain further if need be. Best, Eric Phetteplace Systems Librarian California College of the Arts libraries.cca.edu | vault.cca.edu 510.594.3660 2>/dev/null -------------- next part -------------- An HTML attachment was scrubbed... URL: From alex.sassmannshausen at gmail.com Wed Apr 19 09:23:29 2017 From: alex.sassmannshausen at gmail.com (Alex Sassmannshausen) Date: Wed, 19 Apr 2017 09:23:29 +0200 Subject: [Koha-devel] Gender-neutral pronouns In-Reply-To: References: Message-ID: <874lxkeu8e.fsf@gmail.com> Hi Eric, Eric Phetteplace writes: > Hi list, > > I opened bug #18432 https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18432 because I saw several places in the Koha codebase where the pronoun "he" was being used to refer to a generic third person who could be of any > gender. Jonathan Druart noted that this should be a coding guideline, as otherwise new instances of gendered pronouns might continue to be added. Perhaps it belongs on the "Terminology" page of the wiki? > > So here's my proposal. I'm trying to be concise. > > ---- > > Use gender neutral pronouns > > When referring to a person who could be of any gender, you should use the words they/them/their. This goes for code comments, text in templates, and strings in tests. For example, here's a string from a patrons test updated to be gender > neutral. > > Before: > > is( $total, $enrolmentfee_K + $enrolmentfee_J, "Kid growing and become a juvenile, he should pay " . ( $enrolmentfee_K + $enrolmentfee_J ) ); > > After: > > is( $total, $enrolmentfee_K + $enrolmentfee_J, "Kid growing and become a juvenile, they should pay " . ( $enrolmentfee_K + $enrolmentfee_J ) ); > > Gender neutral terms are preferable for a few reasons. They're more welcoming, showing that Koha expects users and contributors to be of any gender. They're also more accurate. Inappropriately using a particular gender can cause confusion, > leading someone to believe that code operates differently based on the value of borrowers.sex, for instance. > > ---- I like the proposal, thanks for putting it together! Best wishes, Alex From abesottedphoenix at yahoo.com Wed Apr 19 10:52:24 2017 From: abesottedphoenix at yahoo.com (BWS Johnson) Date: Wed, 19 Apr 2017 08:52:24 +0000 (UTC) Subject: [Koha-devel] Gender-neutral pronouns In-Reply-To: <874lxkeu8e.fsf@gmail.com> References: <874lxkeu8e.fsf@gmail.com> Message-ID: <54941852.4256389.1492591944234@mail.yahoo.com> +1 :D From: Alex Sassmannshausen To: Eric Phetteplace Cc: koha-devel at lists.koha-community.org Sent: Wednesday, April 19, 2017 3:23 AM Subject: Re: [Koha-devel] Gender-neutral pronouns Hi Eric, Eric Phetteplace writes: > Hi list, > > I opened bug #18432 https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18432 because I saw several places in the Koha codebase where the pronoun "he" was being used to refer to a generic third person who could be of any > gender. Jonathan Druart noted that this should be a coding guideline, as otherwise new instances of gendered pronouns might continue to be added. Perhaps it belongs on the "Terminology" page of the wiki? > > So here's my proposal. I'm trying to be concise. > > ---- > > Use gender neutral pronouns > > When referring to a person who could be of any gender, you should use the words they/them/their. This goes for code comments, text in templates, and strings in tests. For example, here's a string from a patrons test updated to be gender > neutral. > > Before: > > is( $total, $enrolmentfee_K + $enrolmentfee_J, "Kid growing and become a juvenile, he should pay " . ( $enrolmentfee_K + $enrolmentfee_J ) ); > > After: > > is( $total, $enrolmentfee_K + $enrolmentfee_J, "Kid growing and become a juvenile, they should pay " . ( $enrolmentfee_K + $enrolmentfee_J ) ); > > Gender neutral terms are preferable for a few reasons. They're more welcoming, showing that Koha expects users and contributors to be of any gender. They're also more accurate. Inappropriately using a particular gender can cause confusion, > leading someone to believe that code operates differently based on the value of borrowers.sex, for instance. > > ---- I like the proposal, thanks for putting it together! Best wishes, Alex _______________________________________________ Koha-devel mailing list Koha-devel at lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From z.tajoli at cineca.it Wed Apr 19 11:26:22 2017 From: z.tajoli at cineca.it (Tajoli Zeno) Date: Wed, 19 Apr 2017 11:26:22 +0200 Subject: [Koha-devel] Update of SQL files transaltion for 17.05 and bug 18039 Message-ID: Hi to all, Now 17.05 is near, we need to think how to transalte SQL files. In fact we have a huge change with bug 18039: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18039 So, what do we do ? Do you want 18039 inside 17.05 or not ? IMHO we don't have the resources to insert it into 17.05 Bye Zeno Tajoli -- Zeno Tajoli /SVILUPPO PRODOTTI CINECA/ - Automazione Biblioteche Email: z.tajoli at cineca.it Fax: 051/6132198 *CINECA* Consorzio Interuniversitario - Sede operativa di Segrate (MI) From Katrin.Fischer.83 at web.de Wed Apr 19 13:33:44 2017 From: Katrin.Fischer.83 at web.de (Katrin Fischer) Date: Wed, 19 Apr 2017 13:33:44 +0200 Subject: [Koha-devel] Update of SQL files transaltion for 17.05 and bug 18039 In-Reply-To: References: Message-ID: An HTML attachment was scrubbed... URL: From tomascohen at gmail.com Wed Apr 19 14:21:40 2017 From: tomascohen at gmail.com (Tomas Cohen Arazi) Date: Wed, 19 Apr 2017 12:21:40 +0000 Subject: [Koha-devel] Gender-neutral pronouns In-Reply-To: <874lxkeu8e.fsf@gmail.com> References: <874lxkeu8e.fsf@gmail.com> Message-ID: +1 El mi?., 19 de abr. de 2017 4:23 AM, Alex Sassmannshausen < alex.sassmannshausen at gmail.com> escribi?: > Hi Eric, > > Eric Phetteplace writes: > > > Hi list, > > > > I opened bug #18432 > https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18432 because I > saw several places in the Koha codebase where the pronoun "he" was being > used to refer to a generic third person who could be of any > > gender. Jonathan Druart noted that this should be a coding guideline, as > otherwise new instances of gendered pronouns might continue to be added. > Perhaps it belongs on the "Terminology" page of the wiki? > > > > So here's my proposal. I'm trying to be concise. > > > > ---- > > > > Use gender neutral pronouns > > > > When referring to a person who could be of any gender, you should use > the words they/them/their. This goes for code comments, text in templates, > and strings in tests. For example, here's a string from a patrons test > updated to be gender > > neutral. > > > > Before: > > > > is( $total, $enrolmentfee_K + $enrolmentfee_J, "Kid growing and become a > juvenile, he should pay " . ( $enrolmentfee_K + $enrolmentfee_J ) ); > > > > After: > > > > is( $total, $enrolmentfee_K + $enrolmentfee_J, "Kid growing and become a > juvenile, they should pay " . ( $enrolmentfee_K + $enrolmentfee_J ) ); > > > > Gender neutral terms are preferable for a few reasons. They're more > welcoming, showing that Koha expects users and contributors to be of any > gender. They're also more accurate. Inappropriately using a particular > gender can cause confusion, > > leading someone to believe that code operates differently based on the > value of borrowers.sex, for instance. > > > > ---- > > I like the proposal, thanks for putting it together! > > Best wishes, > > Alex > > _______________________________________________ > Koha-devel mailing list > Koha-devel at lists.koha-community.org > http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > website : http://www.koha-community.org/ > git : http://git.koha-community.org/ > bugs : http://bugs.koha-community.org/ > -- Tom?s Cohen Arazi Theke Solutions (https://theke.io ) ? +54 9351 3513384 GPG: B2F3C15F -------------- next part -------------- An HTML attachment was scrubbed... URL: From z.tajoli at cineca.it Wed Apr 19 15:08:40 2017 From: z.tajoli at cineca.it (Tajoli Zeno) Date: Wed, 19 Apr 2017 15:08:40 +0200 Subject: [Koha-devel] Update of SQL files transaltion for 17.05 and bug 18039 In-Reply-To: References: Message-ID: <4681a9ad-7bb7-a5ad-d951-b9968049a5ab@cineca.it> Hi Katrin, In fact I'm working only about this point: > 2) Bug 18039 is about the translated installers. Afaikt what it does aim > to do is to have the translated installer directories structure matching > the English installer directory structure, so files and directories are > named the same - this should not require any new translations or a > change of the workflow. So I am not sure why this would be a problem? > Wonder what I am missing. I have done now a patch to update italian SQL setup: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18456 If anyone push into master bug 18039 BEFORE my bug 18456, I need to rewrite the patch, as I know. In fact now 18456 is a blocker on 18039. Bye Zeno Tajoli -- Zeno Tajoli /SVILUPPO PRODOTTI CINECA/ - Automazione Biblioteche Email: z.tajoli at cineca.it Fax: 051/6132198 *CINECA* Consorzio Interuniversitario - Sede operativa di Segrate (MI) From tomascohen at gmail.com Wed Apr 19 15:34:02 2017 From: tomascohen at gmail.com (Tomas Cohen Arazi) Date: Wed, 19 Apr 2017 13:34:02 +0000 Subject: [Koha-devel] Elasticsearch < 2.x support Message-ID: Hi, I would like to ask what would the support status will be in 17.05 for Elasticsearch 1.x (and maybe 2.x). According to the official docs [1], 1.x is already deprecated, and 2.x will be supported until 2018-02-28. I propose deprecating ES 1.x support officially, and also remove it from kohadevbox. Maybe something to discuss next dev meeting, but I suppose there's no point supporting unsupported versions. Regards [1] https://www.elastic.co/support/eol -- Tom?s Cohen Arazi Theke Solutions (https://theke.io ) ? +54 9351 3513384 GPG: B2F3C15F -------------- next part -------------- An HTML attachment was scrubbed... URL: From mtompset at hotmail.com Wed Apr 19 15:42:53 2017 From: mtompset at hotmail.com (Mark Tompsett) Date: Wed, 19 Apr 2017 13:42:53 +0000 Subject: [Koha-devel] Let's avoid antecedent confuson too (was Gender-neutral pronouns) In-Reply-To: References: Message-ID: Greetings, +1 to the idea of gender neutral pronouns. However, the example confused half-awake me. Sometimes the antecedent is not always clear when using a pronoun, and the pronoun should be avoided. --- BEGIN SNIP --- Before: is( $total, $enrolmentfee_K + $enrolmentfee_J, "Kid growing and become a juvenile, he should pay " . ( $enrolmentfee_K + $enrolmentfee_J ) ); After: is( $total, $enrolmentfee_K + $enrolmentfee_J, "Kid growing and become a juvenile, they should pay " . ( $enrolmentfee_K + $enrolmentfee_J ) ); --- END SNIP --- Who is to pay? The kid? The guarantor? We also need to avoid antecedent confusion. ?Kid growing and become a juvenile, they should pay? might be better worded ?A child growing and becoming a juvenile has a fee of ?. Because frankly, a library doesn?t care who pays a fee. They only care that a fee charged for a particular reason is paid. This would also clarify that it is the change of class, not a particular gender that affects the fees, because ?[i]nappropriately using a particular gender can cause confusion, leading someone to believe that code operates differently based on the value of borrowers.sex, for instance.? Just some random morning thoughts. GPML, Mark Tompsett From paul.a at navalmarinearchive.com Wed Apr 19 17:42:04 2017 From: paul.a at navalmarinearchive.com (Paul A) Date: Wed, 19 Apr 2017 11:42:04 -0400 Subject: [Koha-devel] Gender-neutral pronouns In-Reply-To: References: Message-ID: On 2017-04-18 08:25 PM, Eric Phetteplace wrote: > Hi list, > > I opened bug [snip] > Before*:* "Kid growing and become a juvenile, he should pay " > After: "Kid growing and become a juvenile, they should pay " Political correctness has never been my strong point (although I try to understand it), but I'm proficient in grammatical rigour. [1] "Kid" is a singular noun, "a" is a singular article -- "they" is a plural pronoun. Perhaps replace "they" with "[s]he"? or "Kids growing and becoming juveniles, they should pay"? From a code maintenance p.o.v., it's easier to find and replace 'he' with '[s]he' if really this becomes a priority for Koha. Best -- Paul [1] I am aware of the so-called "singular third person epicene 'they'", but academically object to it -- it often suggests androgyny rather than gender neutrality. From ephetteplace at cca.edu Wed Apr 19 18:56:06 2017 From: ephetteplace at cca.edu (Eric Phetteplace) Date: Wed, 19 Apr 2017 09:56:06 -0700 Subject: [Koha-devel] Gender-neutral pronouns In-Reply-To: References: Message-ID: Hi Paul, English has a singular "they". It doesn't suggest androgyny, either, from the definitions I've seen. For instance, Oxford English Dictionary: 2. In anaphoric reference to a singular noun or pronoun of undetermined gender: he or she. The first usage example OED provides is from 1375. I don't think replacing "he" with "she" addresses the problem, it's still assuming a default gender. It's not too much tricker to search code for he/him & replace with they/them but that's also just an implementation issue, not a policy one. It sounds like people are otherwise supportive but I'm not sure what the next step should be. Best, Eric Phetteplace Systems Librarian California College of the Arts libraries.cca.edu | vault.cca.edu 510.594.3660 2>/dev/null On Wed, Apr 19, 2017 at 8:42 AM, Paul A wrote: > On 2017-04-18 08:25 PM, Eric Phetteplace wrote: > >> Hi list, >> >> I opened bug >> > [snip] > >> Before*:* >> > "Kid growing and become a juvenile, he should pay " > >> After: >> > "Kid growing and become a juvenile, they should pay " > > Political correctness has never been my strong point (although I try to > understand it), but I'm proficient in grammatical rigour. [1] > > "Kid" is a singular noun, "a" is a singular article -- "they" is a plural > pronoun. Perhaps replace "they" with "[s]he"? or "Kids growing and becoming > juveniles, they should pay"? > > From a code maintenance p.o.v., it's easier to find and replace 'he' with > '[s]he' if really this becomes a priority for Koha. > > Best -- Paul > > [1] I am aware of the so-called "singular third person epicene 'they'", > but academically object to it -- it often suggests androgyny rather than > gender neutrality. > > _______________________________________________ > Koha-devel mailing list > Koha-devel at lists.koha-community.org > http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > website : http://www.koha-community.org/ > git : http://git.koha-community.org/ > bugs : http://bugs.koha-community.org/ > -------------- next part -------------- An HTML attachment was scrubbed... URL: From cgdavis at uintah.utah.gov Wed Apr 19 19:08:17 2017 From: cgdavis at uintah.utah.gov (Christopher Davis) Date: Wed, 19 Apr 2017 11:08:17 -0600 Subject: [Koha-devel] Gender-neutral pronouns In-Reply-To: References: Message-ID: Dear Colleagues, Why don't we just get rid of the pronouns all together with, "Kid growing and becoming a juvenile, that kid must pay"? FWIW, Christopher Davis, MLS Systems & E-Services Librarian Uintah County Library cgdavis at uintah.utah.gov (435) 789-0091 ext.261 uintahlibrary.org basinlibraries.org facebook.com/uintahcountylibrary instagram.com/uintahcountylibrary On Wed, Apr 19, 2017 at 10:56 AM, Eric Phetteplace wrote: > Hi Paul, > > English has a singular "they". It doesn't suggest androgyny, either, from > the definitions I've seen. For instance, Oxford English Dictionary: > > 2. In anaphoric reference to a singular noun or pronoun of undetermined > gender: he or she. > > The first usage example OED provides is from 1375. I don't think replacing > "he" with "she" addresses the problem, it's still assuming a default gender. > It's not too much tricker to search code for he/him & replace with they/them > but that's also just an implementation issue, not a policy one. > > > It sounds like people are otherwise supportive but I'm not sure what the > next step should be. > > Best, > Eric Phetteplace > Systems Librarian > California College of the Arts > libraries.cca.edu | vault.cca.edu > 510.594.3660 > 2>/dev/null > > On Wed, Apr 19, 2017 at 8:42 AM, Paul A > wrote: >> >> On 2017-04-18 08:25 PM, Eric Phetteplace wrote: >>> >>> Hi list, >>> >>> I opened bug >> >> [snip] >>> >>> Before*:* >> >> "Kid growing and become a juvenile, he should pay " >>> >>> After: >> >> "Kid growing and become a juvenile, they should pay " >> >> Political correctness has never been my strong point (although I try to >> understand it), but I'm proficient in grammatical rigour. [1] >> >> "Kid" is a singular noun, "a" is a singular article -- "they" is a plural >> pronoun. Perhaps replace "they" with "[s]he"? or "Kids growing and becoming >> juveniles, they should pay"? >> >> From a code maintenance p.o.v., it's easier to find and replace 'he' with >> '[s]he' if really this becomes a priority for Koha. >> >> Best -- Paul >> >> [1] I am aware of the so-called "singular third person epicene 'they'", >> but academically object to it -- it often suggests androgyny rather than >> gender neutrality. >> >> _______________________________________________ >> Koha-devel mailing list >> Koha-devel at lists.koha-community.org >> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel >> website : http://www.koha-community.org/ >> git : http://git.koha-community.org/ >> bugs : http://bugs.koha-community.org/ > > > > _______________________________________________ > Koha-devel mailing list > Koha-devel at lists.koha-community.org > http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > website : http://www.koha-community.org/ > git : http://git.koha-community.org/ > bugs : http://bugs.koha-community.org/ From jonathan.druart at bugs.koha-community.org Wed Apr 19 19:16:25 2017 From: jonathan.druart at bugs.koha-community.org (Jonathan Druart) Date: Wed, 19 Apr 2017 17:16:25 +0000 Subject: [Koha-devel] Gender-neutral pronouns In-Reply-To: References: Message-ID: The next step would be to provide a check to our QA tests to make sure we will not introduce future occurrences. I am pretty sure they will not be caught manually by QAers. On Wed, 19 Apr 2017 at 13:56 Eric Phetteplace wrote: > Hi Paul, > > English has a singular "they". It doesn't suggest androgyny, either, from > the definitions I've seen. For instance, Oxford English Dictionary: > > 2. In anaphoric reference to a singular noun or pronoun of undetermined > gender: he or she. > > The first usage example OED provides is from 1375. I don't think replacing > "he" with "she" addresses the problem, it's still assuming a default > gender. It's not too much tricker to search code for he/him & replace with > they/them but that's also just an implementation issue, not a policy one. > > > It sounds like people are otherwise supportive but I'm not sure what the > next step should be. > > Best, > Eric Phetteplace > Systems Librarian > California College of the Arts > libraries.cca.edu | vault.cca.edu > 510.594.3660 > 2>/dev/null > > On Wed, Apr 19, 2017 at 8:42 AM, Paul A > wrote: > >> On 2017-04-18 08:25 PM, Eric Phetteplace wrote: >> >>> Hi list, >>> >>> I opened bug >>> >> [snip] >> >>> Before*:* >>> >> "Kid growing and become a juvenile, he should pay " >> >>> After: >>> >> "Kid growing and become a juvenile, they should pay " >> >> Political correctness has never been my strong point (although I try to >> understand it), but I'm proficient in grammatical rigour. [1] >> >> "Kid" is a singular noun, "a" is a singular article -- "they" is a plural >> pronoun. Perhaps replace "they" with "[s]he"? or "Kids growing and becoming >> juveniles, they should pay"? >> >> From a code maintenance p.o.v., it's easier to find and replace 'he' with >> '[s]he' if really this becomes a priority for Koha. >> >> Best -- Paul >> >> [1] I am aware of the so-called "singular third person epicene 'they'", >> but academically object to it -- it often suggests androgyny rather than >> gender neutrality. >> >> _______________________________________________ >> Koha-devel mailing list >> Koha-devel at lists.koha-community.org >> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel >> website : http://www.koha-community.org/ >> git : http://git.koha-community.org/ >> bugs : http://bugs.koha-community.org/ >> > > _______________________________________________ > Koha-devel mailing list > Koha-devel at lists.koha-community.org > http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > website : http://www.koha-community.org/ > git : http://git.koha-community.org/ > bugs : http://bugs.koha-community.org/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From katrin.fischer.83 at web.de Wed Apr 19 19:58:21 2017 From: katrin.fischer.83 at web.de (Katrin) Date: Wed, 19 Apr 2017 19:58:21 +0200 Subject: [Koha-devel] Update of SQL files transaltion for 17.05 and bug 18039 In-Reply-To: <4681a9ad-7bb7-a5ad-d951-b9968049a5ab@cineca.it> References: <4681a9ad-7bb7-a5ad-d951-b9968049a5ab@cineca.it> Message-ID: <444d268b-aaee-f99a-f5fd-8b78359b34de@web.de> Hi Zeno, sorry, it was a confusing day - you are right, the subject was clear. :) Katrin On 19.04.2017 15:08, Tajoli Zeno wrote: > Hi Katrin, > > In fact I'm working only about this point: > >> 2) Bug 18039 is about the translated installers. Afaikt what it does aim >> to do is to have the translated installer directories structure matching >> the English installer directory structure, so files and directories are >> named the same - this should not require any new translations or a >> change of the workflow. So I am not sure why this would be a problem? >> Wonder what I am missing. > > I have done now a patch to update italian SQL setup: > https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18456 > > If anyone push into master bug 18039 BEFORE my bug 18456, I need to > rewrite the patch, as I know. > > In fact now 18456 is a blocker on 18039. > > Bye > Zeno Tajoli > > From philippe.blouin at inlibro.com Wed Apr 19 20:12:57 2017 From: philippe.blouin at inlibro.com (Philippe Blouin) Date: Wed, 19 Apr 2017 14:12:57 -0400 Subject: [Koha-devel] Gender-neutral pronouns In-Reply-To: References: Message-ID: How many of "these" are there to change? Not that the work itself will be massive, but putting a 'they' in the middle of a sentence does not make it easy to translate intuitively, I would think. If it's a consideration (it is for non-English users, at least). Philippe Blouin, Responsable du d?veloppement informatique T?l. : (888) 604-2627 philippe.blouin at inLibro.com inLibro | pour esprit libre | www.inLibro.com On 04/19/2017 01:16 PM, Jonathan Druart wrote: > The next step would be to provide a check to our QA tests to make sure > we will not introduce future occurrences. > I am pretty sure they will not be caught manually by QAers. > > On Wed, 19 Apr 2017 at 13:56 Eric Phetteplace > wrote: > > Hi Paul, > > English has a singular "they". It doesn't suggest androgyny, > either, from the definitions I've seen. For instance, Oxford > English Dictionary: > > 2. In anaphoric reference to a singular noun or pronoun of > undetermined gender: he or she. > > The first usage example OED provides is from 1375. I don't think > replacing "he" with "she" addresses the problem, it's still > assuming a default gender. It's not too much tricker to search > code for he/him & replace with they/them but that's also just an > implementation issue, not a policy one. > > > It sounds like people are otherwise supportive but I'm not sure > what the next step should be. > > Best, > Eric Phetteplace > Systems Librarian > California College of the Arts > libraries.cca.edu | vault.cca.edu > > 510.594.3660 > 2>/dev/null > > On Wed, Apr 19, 2017 at 8:42 AM, Paul A > > wrote: > > On 2017-04-18 08:25 PM, Eric Phetteplace wrote: > > Hi list, > > I opened bug > > [snip] > > Before*:* > > "Kid growing and become a juvenile, he should pay " > > After: > > "Kid growing and become a juvenile, they should pay " > > Political correctness has never been my strong point (although > I try to understand it), but I'm proficient in grammatical > rigour. [1] > > "Kid" is a singular noun, "a" is a singular article -- "they" > is a plural pronoun. Perhaps replace "they" with "[s]he"? or > "Kids growing and becoming juveniles, they should pay"? > > From a code maintenance p.o.v., it's easier to find and > replace 'he' with '[s]he' if really this becomes a priority > for Koha. > > Best -- Paul > > [1] I am aware of the so-called "singular third person epicene > 'they'", but academically object to it -- it often suggests > androgyny rather than gender neutrality. > > _______________________________________________ > Koha-devel mailing list > Koha-devel at lists.koha-community.org > > http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > website : http://www.koha-community.org/ > git : http://git.koha-community.org/ > bugs : http://bugs.koha-community.org/ > > > _______________________________________________ > Koha-devel mailing list > Koha-devel at lists.koha-community.org > > http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > website : http://www.koha-community.org/ > git : http://git.koha-community.org/ > bugs : http://bugs.koha-community.org/ > > > > _______________________________________________ > Koha-devel mailing list > Koha-devel at lists.koha-community.org > http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > website : http://www.koha-community.org/ > git : http://git.koha-community.org/ > bugs : http://bugs.koha-community.org/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From jonathan.druart at bugs.koha-community.org Wed Apr 19 20:18:02 2017 From: jonathan.druart at bugs.koha-community.org (Jonathan Druart) Date: Wed, 19 Apr 2017 18:18:02 +0000 Subject: [Koha-devel] Gender-neutral pronouns In-Reply-To: References: Message-ID: The patches only affect code comments so no translation needed. On Wed, 19 Apr 2017 at 15:12 Philippe Blouin wrote: > How many of "these" are there to change? Not that the work itself will be > massive, but putting a 'they' in the middle of a sentence does not make it > easy to translate intuitively, I would think. If it's a consideration (it > is for non-English users, at least). > > > Philippe Blouin, > Responsable du d?veloppement informatique > > T?l. : (888) 604-2627 > philippe.blouin at inLibro.com > inLibro | pour esprit libre | www.inLibro.com > On 04/19/2017 01:16 PM, Jonathan Druart wrote: > > The next step would be to provide a check to our QA tests to make sure we > will not introduce future occurrences. > I am pretty sure they will not be caught manually by QAers. > > On Wed, 19 Apr 2017 at 13:56 Eric Phetteplace > wrote: > >> Hi Paul, >> >> English has a singular "they". It doesn't suggest androgyny, either, from >> the definitions I've seen. For instance, Oxford English Dictionary: >> >> 2. In anaphoric reference to a singular noun or pronoun of undetermined >> gender: he or she. >> >> The first usage example OED provides is from 1375. I don't think >> replacing "he" with "she" addresses the problem, it's still assuming a >> default gender. It's not too much tricker to search code for he/him & >> replace with they/them but that's also just an implementation issue, not a >> policy one. >> >> >> It sounds like people are otherwise supportive but I'm not sure what the >> next step should be. >> >> Best, >> Eric Phetteplace >> Systems Librarian >> California College of the Arts >> libraries.cca.edu | vault.cca.edu >> 510.594.3660 >> 2>/dev/null >> >> On Wed, Apr 19, 2017 at 8:42 AM, Paul A >> wrote: >> >>> On 2017-04-18 08:25 PM, Eric Phetteplace wrote: >>> >>>> Hi list, >>>> >>>> I opened bug >>>> >>> [snip] >>> >>>> Before*:* >>>> >>> "Kid growing and become a juvenile, he should pay " >>> >>>> After: >>>> >>> "Kid growing and become a juvenile, they should pay " >>> >>> Political correctness has never been my strong point (although I try to >>> understand it), but I'm proficient in grammatical rigour. [1] >>> >>> "Kid" is a singular noun, "a" is a singular article -- "they" is a >>> plural pronoun. Perhaps replace "they" with "[s]he"? or "Kids growing and >>> becoming juveniles, they should pay"? >>> >>> From a code maintenance p.o.v., it's easier to find and replace 'he' >>> with '[s]he' if really this becomes a priority for Koha. >>> >>> Best -- Paul >>> >>> [1] I am aware of the so-called "singular third person epicene 'they'", >>> but academically object to it -- it often suggests androgyny rather than >>> gender neutrality. >>> >>> _______________________________________________ >>> Koha-devel mailing list >>> Koha-devel at lists.koha-community.org >>> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel >>> website : http://www.koha-community.org/ >>> git : http://git.koha-community.org/ >>> bugs : http://bugs.koha-community.org/ >>> >> >> _______________________________________________ >> Koha-devel mailing list >> Koha-devel at lists.koha-community.org >> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel >> website : http://www.koha-community.org/ >> git : http://git.koha-community.org/ >> bugs : http://bugs.koha-community.org/ > > > > _______________________________________________ > Koha-devel mailing listKoha-devel at lists.koha-community.orghttp://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > website : http://www.koha-community.org/ > git : http://git.koha-community.org/ > bugs : http://bugs.koha-community.org/ > > > _______________________________________________ > Koha-devel mailing list > Koha-devel at lists.koha-community.org > http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > website : http://www.koha-community.org/ > git : http://git.koha-community.org/ > bugs : http://bugs.koha-community.org/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From philippe.blouin at inlibro.com Wed Apr 19 21:16:22 2017 From: philippe.blouin at inlibro.com (Philippe Blouin) Date: Wed, 19 Apr 2017 15:16:22 -0400 Subject: [Koha-devel] Gender-neutral pronouns In-Reply-To: References: Message-ID: My mistake, I hadn't read the original bugzilla. :-( Well, can I -1 this or only +1 are politically acceptable? Since this is politic, really. Could you amend the ticket to also rewrite all the comments to some acceptable level of English, to start with? Syntax, grammar, conjugation... Call me obtuse, but 'they' can be quite offputting in the middle of a sentence. I've read some short novels with that usage (used as an androgynous pronoun). To someone whose first language is not English, that can be quite disconcerting on first and second read. The ticket also refers to someone having written "it" for a person in some comment. Well, that's the type of things that occurs in a software partly written by French (I'm not pointing), Indians and Finns... You want to set a rule forcing them to use proper English, you'll fail their patches because of it, in the name of inclusivity??? That's productive... Frankly, a much better "rule" should have been to write all comments using the _female_ form. Clear and concise. But I don't believe that was the aim of the ticket... Philippe Blouin, Responsable du d?veloppement informatique T?l. : (888) 604-2627 philippe.blouin at inLibro.com inLibro | pour esprit libre | www.inLibro.com On 04/19/2017 02:18 PM, Jonathan Druart wrote: > The patches only affect code comments so no translation needed. > > On Wed, 19 Apr 2017 at 15:12 Philippe Blouin > > wrote: > > How many of "these" are there to change? Not that the work itself > will be massive, but putting a 'they' in the middle of a sentence > does not make it easy to translate intuitively, I would think. If > it's a consideration (it is for non-English users, at least). > > > Philippe Blouin, > Responsable du d?veloppement informatique > > T?l. : (888) 604-2627 > philippe.blouin at inLibro.com > > inLibro | pour esprit libre | www.inLibro.com > > On 04/19/2017 01:16 PM, Jonathan Druart wrote: >> The next step would be to provide a check to our QA tests to make >> sure we will not introduce future occurrences. >> I am pretty sure they will not be caught manually by QAers. >> >> On Wed, 19 Apr 2017 at 13:56 Eric Phetteplace >> > wrote: >> >> Hi Paul, >> >> English has a singular "they". It doesn't suggest androgyny, >> either, from the definitions I've seen. For instance, Oxford >> English Dictionary: >> >> 2. In anaphoric reference to a singular noun or pronoun of >> undetermined gender: he or she. >> >> The first usage example OED provides is from 1375. I don't >> think replacing "he" with "she" addresses the problem, it's >> still assuming a default gender. It's not too much tricker to >> search code for he/him & replace with they/them but that's >> also just an implementation issue, not a policy one. >> >> >> It sounds like people are otherwise supportive but I'm not >> sure what the next step should be. >> >> Best, >> Eric Phetteplace >> Systems Librarian >> California College of the Arts >> libraries.cca.edu | vault.cca.edu >> >> 510.594.3660 >> 2>/dev/null >> >> On Wed, Apr 19, 2017 at 8:42 AM, Paul A >> > > wrote: >> >> On 2017-04-18 08:25 PM, Eric Phetteplace wrote: >> >> Hi list, >> >> I opened bug >> >> [snip] >> >> Before*:* >> >> "Kid growing and become a juvenile, he should pay " >> >> After: >> >> "Kid growing and become a juvenile, they should pay " >> >> Political correctness has never been my strong point >> (although I try to understand it), but I'm proficient in >> grammatical rigour. [1] >> >> "Kid" is a singular noun, "a" is a singular article -- >> "they" is a plural pronoun. Perhaps replace "they" with >> "[s]he"? or "Kids growing and becoming juveniles, they >> should pay"? >> >> From a code maintenance p.o.v., it's easier to find and >> replace 'he' with '[s]he' if really this becomes a >> priority for Koha. >> >> Best -- Paul >> >> [1] I am aware of the so-called "singular third person >> epicene 'they'", but academically object to it -- it >> often suggests androgyny rather than gender neutrality. >> >> _______________________________________________ >> Koha-devel mailing list >> Koha-devel at lists.koha-community.org >> >> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel >> website : http://www.koha-community.org/ >> git : http://git.koha-community.org/ >> bugs : http://bugs.koha-community.org/ >> >> >> _______________________________________________ >> Koha-devel mailing list >> Koha-devel at lists.koha-community.org >> >> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel >> website : http://www.koha-community.org/ >> git : http://git.koha-community.org/ >> bugs : http://bugs.koha-community.org/ >> >> >> >> _______________________________________________ >> Koha-devel mailing list >> Koha-devel at lists.koha-community.org >> >> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel >> website :http://www.koha-community.org/ >> git :http://git.koha-community.org/ >> bugs :http://bugs.koha-community.org/ > > _______________________________________________ > Koha-devel mailing list > Koha-devel at lists.koha-community.org > > http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > website : http://www.koha-community.org/ > git : http://git.koha-community.org/ > bugs : http://bugs.koha-community.org/ > > > > _______________________________________________ > Koha-devel mailing list > Koha-devel at lists.koha-community.org > http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > website : http://www.koha-community.org/ > git : http://git.koha-community.org/ > bugs : http://bugs.koha-community.org/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From chrisc at catalyst.net.nz Wed Apr 19 21:20:33 2017 From: chrisc at catalyst.net.nz (Chris Cormack) Date: Thu, 20 Apr 2017 07:20:33 +1200 Subject: [Koha-devel] Gender-neutral pronouns In-Reply-To: References: Message-ID: <8222506F-BB0D-4666-A47A-D8FD43E3593F@catalyst.net.nz> Of course we won't fail patches, thanks for the strawman. We can easily fix them instead. In fact I volunteer to do that. You're welcome to fix grammar too, send some patches. And of course you can vote -1 you just did. I certainly noticed it. Chris On 20 April 2017 7:16:22 AM NZST, Philippe Blouin wrote: >My mistake, I hadn't read the original bugzilla. :-( > >Well, can I -1 this or only +1 are politically acceptable? Since this >is politic, really. Could you amend the ticket to also rewrite all the > >comments to some acceptable level of English, to start with? Syntax, >grammar, conjugation... > >Call me obtuse, but 'they' can be quite offputting in the middle of a >sentence. I've read some short novels with that usage (used as an >androgynous pronoun). To someone whose first language is not English, >that can be quite disconcerting on first and second read. > >The ticket also refers to someone having written "it" for a person in >some comment. Well, that's the type of things that occurs in a >software >partly written by French (I'm not pointing), Indians and Finns... You >want to set a rule forcing them to use proper English, you'll fail >their >patches because of it, in the name of inclusivity??? That's >productive... > >Frankly, a much better "rule" should have been to write all comments >using the _female_ form. Clear and concise. But I don't believe that >was the aim of the ticket... > >Philippe Blouin, >Responsable du d?veloppement informatique > >T?l. : (888) 604-2627 >philippe.blouin at inLibro.com > >inLibro | pour esprit libre | www.inLibro.com >On 04/19/2017 02:18 PM, Jonathan Druart wrote: >> The patches only affect code comments so no translation needed. >> >> On Wed, 19 Apr 2017 at 15:12 Philippe Blouin >> > >wrote: >> >> How many of "these" are there to change? Not that the work >itself >> will be massive, but putting a 'they' in the middle of a sentence >> does not make it easy to translate intuitively, I would think. >If >> it's a consideration (it is for non-English users, at least). >> >> >> Philippe Blouin, >> Responsable du d?veloppement informatique >> >> T?l. : (888) 604-2627 >> philippe.blouin at inLibro.com >> >> inLibro | pour esprit libre | www.inLibro.com >> >> On 04/19/2017 01:16 PM, Jonathan Druart wrote: >>> The next step would be to provide a check to our QA tests to >make >>> sure we will not introduce future occurrences. >>> I am pretty sure they will not be caught manually by QAers. >>> >>> On Wed, 19 Apr 2017 at 13:56 Eric Phetteplace >>> > wrote: >>> >>> Hi Paul, >>> >>> English has a singular "they". It doesn't suggest androgyny, >>> either, from the definitions I've seen. For instance, Oxford >>> English Dictionary: >>> >>> 2. In anaphoric reference to a singular noun or pronoun of >>> undetermined gender: he or she. >>> >>> The first usage example OED provides is from 1375. I don't >>> think replacing "he" with "she" addresses the problem, it's >>> still assuming a default gender. It's not too much tricker >to >>> search code for he/him & replace with they/them but that's >>> also just an implementation issue, not a policy one. >>> >>> >>> It sounds like people are otherwise supportive but I'm not >>> sure what the next step should be. >>> >>> Best, >>> Eric Phetteplace >>> Systems Librarian >>> California College of the Arts >>> libraries.cca.edu | vault.cca.edu >>> >>> 510.594.3660 >>> 2>/dev/null >>> >>> On Wed, Apr 19, 2017 at 8:42 AM, Paul A >>> >> > wrote: >>> >>> On 2017-04-18 08:25 PM, Eric Phetteplace wrote: >>> >>> Hi list, >>> >>> I opened bug >>> >>> [snip] >>> >>> Before*:* >>> >>> "Kid growing and become a juvenile, he should pay " >>> >>> After: >>> >>> "Kid growing and become a juvenile, they should pay " >>> >>> Political correctness has never been my strong point >>> (although I try to understand it), but I'm proficient in >>> grammatical rigour. [1] >>> >>> "Kid" is a singular noun, "a" is a singular article -- >>> "they" is a plural pronoun. Perhaps replace "they" with >>> "[s]he"? or "Kids growing and becoming juveniles, they >>> should pay"? >>> >>> From a code maintenance p.o.v., it's easier to find and >>> replace 'he' with '[s]he' if really this becomes a >>> priority for Koha. >>> >>> Best -- Paul >>> >>> [1] I am aware of the so-called "singular third person >>> epicene 'they'", but academically object to it -- it >>> often suggests androgyny rather than gender neutrality. >>> >>> _______________________________________________ >>> Koha-devel mailing list >>> Koha-devel at lists.koha-community.org >>> >>> >http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel >>> website : http://www.koha-community.org/ >>> git : http://git.koha-community.org/ >>> bugs : http://bugs.koha-community.org/ >>> >>> >>> _______________________________________________ >>> Koha-devel mailing list >>> Koha-devel at lists.koha-community.org >>> >>> >http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel >>> website : http://www.koha-community.org/ >>> git : http://git.koha-community.org/ >>> bugs : http://bugs.koha-community.org/ >>> >>> >>> >>> _______________________________________________ >>> Koha-devel mailing list >>> Koha-devel at lists.koha-community.org >>> >>> >http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel >>> website :http://www.koha-community.org/ >>> git :http://git.koha-community.org/ >>> bugs :http://bugs.koha-community.org/ >> >> _______________________________________________ >> Koha-devel mailing list >> Koha-devel at lists.koha-community.org >> >> >http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel >> website : http://www.koha-community.org/ >> git : http://git.koha-community.org/ >> bugs : http://bugs.koha-community.org/ >> >> >> >> _______________________________________________ >> Koha-devel mailing list >> Koha-devel at lists.koha-community.org >> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel >> website : http://www.koha-community.org/ >> git : http://git.koha-community.org/ >> bugs : http://bugs.koha-community.org/ -- Sent from my Android device with K-9 Mail. Please excuse my brevity. -------------- next part -------------- An HTML attachment was scrubbed... URL: From katrin.fischer.83 at web.de Wed Apr 19 21:47:23 2017 From: katrin.fischer.83 at web.de (Katrin) Date: Wed, 19 Apr 2017 21:47:23 +0200 Subject: [Koha-devel] Gender-neutral pronouns In-Reply-To: References: Message-ID: Hi Eric, +1 Reading the discussion so far, I want to ask people to keep in mind that Koha is a very international project. I only learned about the use of they/them/their as singular neutral pronouns not so long ago and I think for a lot of other non-native speakers it might be similar. Our code comments are not perfect and we can always improve, but please let's be nice about it. I'd rather have a non-perfect code comment with imperfect grammar than people stop commenting :) Katrin On 19.04.2017 02:25, Eric Phetteplace wrote: > Hi list, > > I opened bug #18432 > https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18432 > because I saw several places in the Koha codebase where the pronoun > "he" was being used to refer to a generic third person who could be of > any gender. Jonathan Druart noted that this should be a coding > guideline, as otherwise new instances of gendered pronouns might > continue to be added. Perhaps it belongs on the "Terminology" page of > the wiki? > > So here's my proposal. I'm trying to be concise. > > ---- > > *Use gender neutral pronouns* > * > * > When referring to a person who could be of any gender, you should use > the words they/them/their. This goes for code comments, text in > templates, and strings in tests. For example, here's a string from a > patrons test updated to be gender neutral. > > Before*:* > * > * > is( $total, $enrolmentfee_K + $enrolmentfee_J, "Kid growing and become > a juvenile, he should pay " . ( $enrolmentfee_K + $enrolmentfee_J ) ); > > After: > > is( $total, $enrolmentfee_K + $enrolmentfee_J, "Kid growing and become > a juvenile, they should pay " . ( $enrolmentfee_K + $enrolmentfee_J ) ); > > Gender neutral terms are preferable for a few reasons. They're more > welcoming, showing that Koha expects users and contributors to be of > any gender. They're also more accurate. Inappropriately using a > particular gender can cause confusion, leading someone to believe that > code operates differently based on the value of borrowers.sex, for > instance. > > ---- > > I hope that's clear. I'm happy to reword it, and to attend the next > Koha developers meeting to explain further if need be. > > Best, > Eric Phetteplace > Systems Librarian > California College of the Arts > libraries.cca.edu | vault.cca.edu > > 510.594.3660 > 2>/dev/null > > > _______________________________________________ > Koha-devel mailing list > Koha-devel at lists.koha-community.org > http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > website : http://www.koha-community.org/ > git : http://git.koha-community.org/ > bugs : http://bugs.koha-community.org/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From philippe.blouin at inlibro.com Wed Apr 19 21:48:49 2017 From: philippe.blouin at inlibro.com (Philippe Blouin) Date: Wed, 19 Apr 2017 15:48:49 -0400 Subject: [Koha-devel] Gender-neutral pronouns In-Reply-To: <8222506F-BB0D-4666-A47A-D8FD43E3593F@catalyst.net.nz> References: <8222506F-BB0D-4666-A47A-D8FD43E3593F@catalyst.net.nz> Message-ID: <2f4654fd-f78f-a450-bce2-07b448aeda9a@inlibro.com> That's no strawman, that's a genuine questionning. You talk inclusivity, I'm all for it, but can we walk the talk now? 'They' is a bigger barrier to entry than 'he' for non-English readers/coders. But hey, what do I know, what is my perspective here? The stated initiative is good: the majority of users are female, the code is male-centric, can we be progressive, inclusive... But 'they' sucks. As I said, why not use "she" ? I don't send formating and commenting patches, the QA team having quite enough on its plate already. Philippe Blouin, Responsable du d?veloppement informatique T?l. : (888) 604-2627 philippe.blouin at inLibro.com inLibro | pour esprit libre | www.inLibro.com On 04/19/2017 03:20 PM, Chris Cormack wrote: > Of course we won't fail patches, thanks for the strawman. We can > easily fix them instead. In fact I volunteer to do that. > > You're welcome to fix grammar too, send some patches. > > And of course you can vote -1 you just did. I certainly noticed it. > > Chris > > On 20 April 2017 7:16:22 AM NZST, Philippe Blouin > wrote: > > My mistake, I hadn't read the original bugzilla. :-( > > Well, can I -1 this or only +1 are politically acceptable? Since > this is politic, really. Could you amend the ticket to also > rewrite all the comments to some acceptable level of English, to > start with? Syntax, grammar, conjugation... > > Call me obtuse, but 'they' can be quite offputting in the middle > of a sentence. I've read some short novels with that usage (used > as an androgynous pronoun). To someone whose first language is > not English, that can be quite disconcerting on first and second > read. > > The ticket also refers to someone having written "it" for a person > in some comment. Well, that's the type of things that occurs in a > software partly written by French (I'm not pointing), Indians and > Finns... You want to set a rule forcing them to use proper > English, you'll fail their patches because of it, in the name of > inclusivity??? That's productive... > > Frankly, a much better "rule" should have been to write all > comments using the _female_ form. Clear and concise. But I don't > believe that was the aim of the ticket... > > Philippe Blouin, > Responsable du d?veloppement informatique > > T?l. : (888) 604-2627 > philippe.blouin at inLibro.com > > inLibro | pour esprit libre | www.inLibro.com > > On 04/19/2017 02:18 PM, Jonathan Druart wrote: >> The patches only affect code comments so no translation needed. >> >> On Wed, 19 Apr 2017 at 15:12 Philippe Blouin >> > > wrote: >> >> How many of "these" are there to change? Not that the work >> itself will be massive, but putting a 'they' in the middle of >> a sentence does not make it easy to translate intuitively, I >> would think. If it's a consideration (it is for non-English >> users, at least). >> >> >> Philippe Blouin, >> Responsable du d?veloppement informatique >> >> T?l. : (888) 604-2627 >> philippe.blouin at inLibro.com >> >> inLibro | pour esprit libre | www.inLibro.com >> >> On 04/19/2017 01:16 PM, Jonathan Druart wrote: >>> The next step would be to provide a check to our QA tests to >>> make sure we will not introduce future occurrences. >>> I am pretty sure they will not be caught manually by QAers. >>> >>> On Wed, 19 Apr 2017 at 13:56 Eric Phetteplace >>> > wrote: >>> >>> Hi Paul, >>> >>> English has a singular "they". It doesn't suggest >>> androgyny, either, from the definitions I've seen. For >>> instance, Oxford English Dictionary: >>> >>> 2. In anaphoric reference to a singular noun or pronoun >>> of undetermined gender: he or she. >>> >>> The first usage example OED provides is from 1375. I >>> don't think replacing "he" with "she" addresses the >>> problem, it's still assuming a default gender. It's not >>> too much tricker to search code for he/him & replace >>> with they/them but that's also just an implementation >>> issue, not a policy one. >>> >>> >>> It sounds like people are otherwise supportive but I'm >>> not sure what the next step should be. >>> >>> Best, >>> Eric Phetteplace >>> Systems Librarian >>> California College of the Arts >>> libraries.cca.edu | >>> vault.cca.edu >>> 510.594.3660 >>> 2>/dev/null >>> >>> On Wed, Apr 19, 2017 at 8:42 AM, Paul A >>> >> > wrote: >>> >>> On 2017-04-18 08:25 PM, Eric Phetteplace wrote: >>> >>> Hi list, >>> >>> I opened bug >>> >>> [snip] >>> >>> Before*:* >>> >>> "Kid growing and become a juvenile, he should pay " >>> >>> After: >>> >>> "Kid growing and become a juvenile, they should pay " >>> >>> Political correctness has never been my strong point >>> (although I try to understand it), but I'm >>> proficient in grammatical rigour. [1] >>> >>> "Kid" is a singular noun, "a" is a singular article >>> -- "they" is a plural pronoun. Perhaps replace >>> "they" with "[s]he"? or "Kids growing and becoming >>> juveniles, they should pay"? >>> >>> From a code maintenance p.o.v., it's easier to find >>> and replace 'he' with '[s]he' if really this becomes >>> a priority for Koha. >>> >>> Best -- Paul >>> >>> [1] I am aware of the so-called "singular third >>> person epicene 'they'", but academically object to >>> it -- it often suggests androgyny rather than gender >>> neutrality. >>> >>> _______________________________________________ >>> Koha-devel mailing list >>> Koha-devel at lists.koha-community.org >>> >>> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel >>> website : http://www.koha-community.org/ >>> git : http://git.koha-community.org/ >>> bugs : http://bugs.koha-community.org/ >>> >>> >>> _______________________________________________ >>> Koha-devel mailing list >>> Koha-devel at lists.koha-community.org >>> >>> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel >>> website : http://www.koha-community.org/ >>> git : http://git.koha-community.org/ >>> bugs : http://bugs.koha-community.org/ >>> >>> >>> >>> _______________________________________________ >>> Koha-devel mailing list >>> Koha-devel at lists.koha-community.org >>> >>> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel >>> website :http://www.koha-community.org/ >>> git :http://git.koha-community.org/ >>> bugs :http://bugs.koha-community.org/ >> >> _______________________________________________ >> Koha-devel mailing list >> Koha-devel at lists.koha-community.org >> >> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel >> website : http://www.koha-community.org/ >> git : http://git.koha-community.org/ >> bugs : http://bugs.koha-community.org/ >> >> >> >> _______________________________________________ >> Koha-devel mailing list >> Koha-devel at lists.koha-community.org >> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel >> website :http://www.koha-community.org/ >> git :http://git.koha-community.org/ >> bugs :http://bugs.koha-community.org/ > > > -- > Sent from my Android device with K-9 Mail. Please excuse my brevity. -------------- next part -------------- An HTML attachment was scrubbed... URL: From chrisc at catalyst.net.nz Wed Apr 19 21:59:10 2017 From: chrisc at catalyst.net.nz (Chris Cormack) Date: Thu, 20 Apr 2017 07:59:10 +1200 Subject: [Koha-devel] Elasticsearch < 2.x support In-Reply-To: References: Message-ID: <20170419195910.u76jrgl4mv4mklg5@rorohiko.wgtn.cat-it.co.nz> Hi Tomas I think it is best to say 17.05 will support Elastic 5.0+ (Maybe 2.1 but I havent tested) Definitely not 1.7 Chris * Tomas Cohen Arazi (tomascohen at gmail.com) wrote: > Hi, I would like to ask what would the support status will be in 17.05 for > Elasticsearch 1.x (and maybe 2.x). > > According to the official docs [1], 1.x is already deprecated, and 2.x > will be supported until 2018-02-28. > I propose deprecating ES 1.x support officially, and also remove it from > kohadevbox. Maybe something to discuss next dev meeting, but I suppose > there's no point supporting unsupported versions. > Regards > [1]??https://www.elastic.co/support/eol > -- > Tom??s Cohen Arazi > Theke Solutions (https://theke.io) > ?** +54 9351 3513384 > GPG: B2F3C15F >_______________________________________________ >Koha-devel mailing list >Koha-devel at lists.koha-community.org >http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel >website : http://www.koha-community.org/ >git : http://git.koha-community.org/ >bugs : http://bugs.koha-community.org/ -- Chris Cormack Catalyst IT Ltd. +64 4 803 2238 PO Box 11-053, Manners St, Wellington 6142, New Zealand -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: not available URL: From mik at adminkuhn.ch Wed Apr 19 22:05:31 2017 From: mik at adminkuhn.ch (Michael Kuhn) Date: Wed, 19 Apr 2017 22:05:31 +0200 Subject: [Koha-devel] Gender-neutral pronouns In-Reply-To: <2f4654fd-f78f-a450-bce2-07b448aeda9a@inlibro.com> References: <8222506F-BB0D-4666-A47A-D8FD43E3593F@catalyst.net.nz> <2f4654fd-f78f-a450-bce2-07b448aeda9a@inlibro.com> Message-ID: <6c75215f-55dd-6de1-54f6-19d99b173b8a@adminkuhn.ch> Hi > You talk inclusivity, I'm all for it, but can we walk the talk now? > 'They' is a bigger barrier to entry than 'he' for non-English > readers/coders. But hey, what do I know, what is my perspective here? > The stated initiative is good: the majority of users are female, the > code is male-centric, can we be progressive, inclusive... But 'they' > sucks. As I said, why not use "she" ? In this case - why not introduce a new variable so everyone can choose the word that feels best for them and her and him? Best wishes: Michael From ephetteplace at cca.edu Wed Apr 19 22:16:26 2017 From: ephetteplace at cca.edu (Eric Phetteplace) Date: Wed, 19 Apr 2017 13:16:26 -0700 Subject: [Koha-devel] Gender-neutral pronouns In-Reply-To: <2f4654fd-f78f-a450-bce2-07b448aeda9a@inlibro.com> References: <8222506F-BB0D-4666-A47A-D8FD43E3593F@catalyst.net.nz> <2f4654fd-f78f-a450-bce2-07b448aeda9a@inlibro.com> Message-ID: Hi Philippe, "She" doesn't solve either of the problems I outlined in my original statement, however. It still excludes people who aren't of a particular gender and it's still inaccurate in places where it implies a particular value for borrowers.sex. I don't mean to make more work for anyone, cause trouble, or to make things more confusing. There are places where Chris' suggestion makes sense; we can avoid pronouns altogether, if possible. But I'm not sure that works in every comment. I just see so little harm in correcting the existing instances of gendered language and establishing a guideline for future writing. Most of this work has already been done. When you look at the current terminology guidelines , some choices have already been based upon locality. Thus the use of "patrons" over "borrowers" even though the database table was named borrowers, for instance. There will always be tradeoffs. I think "they" is the best option given the available choices, for reasons already articulated. > The ticket also refers to someone having written "it" for a person in some comment. If you're referring to my bug, you've misunderstood my comment; an object, not a person, was being referred to as "he" and I changed it to "it." Best, Eric Phetteplace Systems Librarian California College of the Arts libraries.cca.edu | vault.cca.edu 510.594.3660 2>/dev/null On Wed, Apr 19, 2017 at 12:48 PM, Philippe Blouin < philippe.blouin at inlibro.com> wrote: > That's no strawman, that's a genuine questionning. > > You talk inclusivity, I'm all for it, but can we walk the talk now? > 'They' is a bigger barrier to entry than 'he' for non-English > readers/coders. But hey, what do I know, what is my perspective here? The > stated initiative is good: the majority of users are female, the code is > male-centric, can we be progressive, inclusive... But 'they' sucks. As I > said, why not use "she" ? > > I don't send formating and commenting patches, the QA team having quite > enough on its plate already. > Philippe Blouin, > Responsable du d?veloppement informatique > > T?l. : (888) 604-2627 > philippe.blouin at inLibro.com > inLibro | pour esprit libre | www.inLibro.com > On 04/19/2017 03:20 PM, Chris Cormack wrote: > > Of course we won't fail patches, thanks for the strawman. We can easily > fix them instead. In fact I volunteer to do that. > > You're welcome to fix grammar too, send some patches. > > And of course you can vote -1 you just did. I certainly noticed it. > > Chris > > On 20 April 2017 7:16:22 AM NZST, Philippe Blouin > wrote: >> >> My mistake, I hadn't read the original bugzilla. :-( >> >> Well, can I -1 this or only +1 are politically acceptable? Since this is >> politic, really. Could you amend the ticket to also rewrite all the >> comments to some acceptable level of English, to start with? Syntax, >> grammar, conjugation... >> >> Call me obtuse, but 'they' can be quite offputting in the middle of a >> sentence. I've read some short novels with that usage (used as an >> androgynous pronoun). To someone whose first language is not English, that >> can be quite disconcerting on first and second read. >> >> The ticket also refers to someone having written "it" for a person in >> some comment. Well, that's the type of things that occurs in a software >> partly written by French (I'm not pointing), Indians and Finns... You want >> to set a rule forcing them to use proper English, you'll fail their patches >> because of it, in the name of inclusivity??? That's productive... >> >> Frankly, a much better "rule" should have been to write all comments >> using the *female* form. Clear and concise. But I don't believe that >> was the aim of the ticket... >> Philippe Blouin, >> Responsable du d?veloppement informatique >> >> T?l. : (888) 604-2627 >> philippe.blouin at inLibro.com >> inLibro | pour esprit libre | www.inLibro.com >> On 04/19/2017 02:18 PM, Jonathan Druart wrote: >> >> The patches only affect code comments so no translation needed. >> >> On Wed, 19 Apr 2017 at 15:12 Philippe Blouin >> wrote: >> >>> How many of "these" are there to change? Not that the work itself will >>> be massive, but putting a 'they' in the middle of a sentence does not make >>> it easy to translate intuitively, I would think. If it's a consideration >>> (it is for non-English users, at least). >>> >>> >>> Philippe Blouin, >>> Responsable du d?veloppement informatique >>> >>> T?l. : (888) 604-2627 >>> philippe.blouin at inLibro.com >>> inLibro | pour esprit libre | www.inLibro.com >>> On 04/19/2017 01:16 PM, Jonathan Druart wrote: >>> >>> The next step would be to provide a check to our QA tests to make sure >>> we will not introduce future occurrences. >>> I am pretty sure they will not be caught manually by QAers. >>> >>> On Wed, 19 Apr 2017 at 13:56 Eric Phetteplace >>> wrote: >>> >>>> Hi Paul, >>>> >>>> English has a singular "they". It doesn't suggest androgyny, either, >>>> from the definitions I've seen. For instance, Oxford English Dictionary: >>>> >>>> 2. In anaphoric reference to a singular noun or pronoun of undetermined >>>> gender: he or she. >>>> >>>> The first usage example OED provides is from 1375. I don't think >>>> replacing "he" with "she" addresses the problem, it's still assuming a >>>> default gender. It's not too much tricker to search code for he/him & >>>> replace with they/them but that's also just an implementation issue, not a >>>> policy one. >>>> >>>> >>>> It sounds like people are otherwise supportive but I'm not sure what >>>> the next step should be. >>>> >>>> Best, >>>> Eric Phetteplace >>>> Systems Librarian >>>> California College of the Arts >>>> libraries.cca.edu | vault.cca.edu >>>> 510.594.3660 <(510)%20594-3660> >>>> 2>/dev/null >>>> >>>> On Wed, Apr 19, 2017 at 8:42 AM, Paul A >>>> wrote: >>>> >>>>> On 2017-04-18 08:25 PM, Eric Phetteplace wrote: >>>>> >>>>>> Hi list, >>>>>> >>>>>> I opened bug >>>>>> >>>>> [snip] >>>>> >>>>>> Before*:* >>>>>> >>>>> "Kid growing and become a juvenile, he should pay " >>>>> >>>>>> After: >>>>>> >>>>> "Kid growing and become a juvenile, they should pay " >>>>> >>>>> Political correctness has never been my strong point (although I try >>>>> to understand it), but I'm proficient in grammatical rigour. [1] >>>>> >>>>> "Kid" is a singular noun, "a" is a singular article -- "they" is a >>>>> plural pronoun. Perhaps replace "they" with "[s]he"? or "Kids growing and >>>>> becoming juveniles, they should pay"? >>>>> >>>>> From a code maintenance p.o.v., it's easier to find and replace 'he' >>>>> with '[s]he' if really this becomes a priority for Koha. >>>>> >>>>> Best -- Paul >>>>> >>>>> [1] I am aware of the so-called "singular third person epicene >>>>> 'they'", but academically object to it -- it often suggests androgyny >>>>> rather than gender neutrality. >>>>> >>>>> _______________________________________________ >>>>> Koha-devel mailing list >>>>> Koha-devel at lists.koha-community.org >>>>> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel >>>>> website : http://www.koha-community.org/ >>>>> git : http://git.koha-community.org/ >>>>> bugs : http://bugs.koha-community.org/ >>>>> >>>> >>>> _______________________________________________ >>>> Koha-devel mailing list >>>> Koha-devel at lists.koha-community.org >>>> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel >>>> website : http://www.koha-community.org/ >>>> git : http://git.koha-community.org/ >>>> bugs : http://bugs.koha-community.org/ >>> >>> >>> >>> _______________________________________________ >>> Koha-devel mailing listKoha-devel at lists.koha-community.orghttp://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel >>> website : http://www.koha-community.org/ >>> git : http://git.koha-community.org/ >>> bugs : http://bugs.koha-community.org/ >>> >>> >>> _______________________________________________ >>> Koha-devel mailing list >>> Koha-devel at lists.koha-community.org >>> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel >>> website : http://www.koha-community.org/ >>> git : http://git.koha-community.org/ >>> bugs : http://bugs.koha-community.org/ >> >> >> >> _______________________________________________ >> Koha-devel mailing listKoha-devel at lists.koha-community.orghttp://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel >> website : http://www.koha-community.org/ >> git : http://git.koha-community.org/ >> bugs : http://bugs.koha-community.org/ >> >> >> > -- > Sent from my Android device with K-9 Mail. Please excuse my brevity. > > > > _______________________________________________ > Koha-devel mailing list > Koha-devel at lists.koha-community.org > http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > website : http://www.koha-community.org/ > git : http://git.koha-community.org/ > bugs : http://bugs.koha-community.org/ > -------------- next part -------------- An HTML attachment was scrubbed... URL: From veron at veron.ch Wed Apr 19 22:32:41 2017 From: veron at veron.ch (=?UTF-8?Q?Marc_V=c3=a9ron?=) Date: Wed, 19 Apr 2017 22:32:41 +0200 Subject: [Koha-devel] Gender-neutral pronouns In-Reply-To: References: Message-ID: <45de4dc2-d3d6-3275-a25f-a750b228cef5@veron.ch> +1 for trying to achieve gender neutrality Marc Am 19.04.2017 um 02:25 schrieb Eric Phetteplace: > Hi list, > > I opened bug #18432 > https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18432 > because I saw several places in the Koha codebase where the pronoun > "he" was being used to refer to a generic third person who could be of > any gender. Jonathan Druart noted that this should be a coding > guideline, as otherwise new instances of gendered pronouns might > continue to be added. Perhaps it belongs on the "Terminology" page of > the wiki? > > So here's my proposal. I'm trying to be concise. > > ---- > > *Use gender neutral pronouns* > * > * > When referring to a person who could be of any gender, you should use > the words they/them/their. This goes for code comments, text in > templates, and strings in tests. For example, here's a string from a > patrons test updated to be gender neutral. > > Before*:* > * > * > is( $total, $enrolmentfee_K + $enrolmentfee_J, "Kid growing and become > a juvenile, he should pay " . ( $enrolmentfee_K + $enrolmentfee_J ) ); > > After: > > is( $total, $enrolmentfee_K + $enrolmentfee_J, "Kid growing and become > a juvenile, they should pay " . ( $enrolmentfee_K + $enrolmentfee_J ) ); > > Gender neutral terms are preferable for a few reasons. They're more > welcoming, showing that Koha expects users and contributors to be of > any gender. They're also more accurate. Inappropriately using a > particular gender can cause confusion, leading someone to believe that > code operates differently based on the value of borrowers.sex, for > instance. > > ---- > > I hope that's clear. I'm happy to reword it, and to attend the next > Koha developers meeting to explain further if need be. > > Best, > Eric Phetteplace > Systems Librarian > California College of the Arts > libraries.cca.edu | vault.cca.edu > > 510.594.3660 > 2>/dev/null > > > _______________________________________________ > Koha-devel mailing list > Koha-devel at lists.koha-community.org > http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > website : http://www.koha-community.org/ > git : http://git.koha-community.org/ > bugs : http://bugs.koha-community.org/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From katrin.fischer.83 at web.de Wed Apr 19 22:50:51 2017 From: katrin.fischer.83 at web.de (Katrin) Date: Wed, 19 Apr 2017 22:50:51 +0200 Subject: [Koha-devel] Gender-neutral pronouns In-Reply-To: <2f4654fd-f78f-a450-bce2-07b448aeda9a@inlibro.com> References: <8222506F-BB0D-4666-A47A-D8FD43E3593F@catalyst.net.nz> <2f4654fd-f78f-a450-bce2-07b448aeda9a@inlibro.com> Message-ID: <06325ba4-e99c-53d3-1a3f-8ad97f6b9578@web.de> I have to admit that 'they' sounded unusual to me at first, but that doesn't mean it's not correct English and that we shouldn't use it. What's wrong about learning about gender neutral language in English? I definitely prefer gender neutral to 'she'. On 19.04.2017 21:48, Philippe Blouin wrote: > > That's no strawman, that's a genuine questionning. > > You talk inclusivity, I'm all for it, but can we walk the talk now? > 'They' is a bigger barrier to entry than 'he' for non-English > readers/coders. But hey, what do I know, what is my perspective > here? The stated initiative is good: the majority of users are > female, the code is male-centric, can we be progressive, inclusive... > But 'they' sucks. As I said, why not use "she" ? > > I don't send formating and commenting patches, the QA team having > quite enough on its plate already. > > Philippe Blouin, > Responsable du d?veloppement informatique > > T?l. : (888) 604-2627 > philippe.blouin at inLibro.com > > inLibro | pour esprit libre | www.inLibro.com > On 04/19/2017 03:20 PM, Chris Cormack wrote: >> Of course we won't fail patches, thanks for the strawman. We can >> easily fix them instead. In fact I volunteer to do that. >> >> You're welcome to fix grammar too, send some patches. >> >> And of course you can vote -1 you just did. I certainly noticed it. >> >> Chris >> -------------- next part -------------- An HTML attachment was scrubbed... URL: From chris at bigballofwax.co.nz Wed Apr 19 22:54:14 2017 From: chris at bigballofwax.co.nz (Chris Cormack) Date: Thu, 20 Apr 2017 08:54:14 +1200 Subject: [Koha-devel] Gender-neutral pronouns In-Reply-To: <2f4654fd-f78f-a450-bce2-07b448aeda9a@inlibro.com> References: <8222506F-BB0D-4666-A47A-D8FD43E3593F@catalyst.net.nz> <2f4654fd-f78f-a450-bce2-07b448aeda9a@inlibro.com> Message-ID: On 20 April 2017 at 07:48, Philippe Blouin wrote: > That's no strawman, that's a genuine questionning. > > You talk inclusivity, I'm all for it, but can we walk the talk now? 'They' > is a bigger barrier to entry than 'he' for non-English readers/coders. But > hey, what do I know, what is my perspective here? The stated initiative is > good: the majority of users are female, the code is male-centric, can we be > progressive, inclusive... But 'they' sucks. As I said, why not use "she" ? > Interestingly enough, my first language M?ori has no gendered pronouns at all. All of them are non gendered. So they is much easier to understand for me. Anei t?n? ngeru Here is their cat. There's your useless trivia for the day. Not all non english speakers have gendered pronouns either :) Chris From philippe.blouin at inlibro.com Wed Apr 19 23:19:48 2017 From: philippe.blouin at inlibro.com (Philippe Blouin) Date: Wed, 19 Apr 2017 17:19:48 -0400 Subject: [Koha-devel] Gender-neutral pronouns In-Reply-To: References: <8222506F-BB0D-4666-A47A-D8FD43E3593F@catalyst.net.nz> <2f4654fd-f78f-a450-bce2-07b448aeda9a@inlibro.com> Message-ID: <4dc97a1c-b5f9-6db1-71e4-15c3745a4031@inlibro.com> I appreciate the trivia, I was not aware of that possibility. I certainly envy the students of the language. But I'll presume you've since used English quite enough to be considered fluent in it, unlike most other Koha contributors. And if Kate is ready to learn genderless pronouns, as I'm sure are most of the well rounded and educated individuals that make up this community, _it is not intuitive nor easy, in fact it is very very confusing_ to the discrete contributor. An unwarranted confusion, in my opinion. Again, to be clear, we're not talking about the face of Koha we're presenting to the world, the Product. We're talking about coding guidelines for _code comments_ added genuinely by naive contributors. Lower the barrier to entry, do not raise them! Anyway... have a good day/night/evening/dusk/dawn/lunch Damn it! It's hard to be inclusive! Have a good they Philippe Blouin, Responsable du d?veloppement informatique T?l. : (888) 604-2627 philippe.blouin at inLibro.com inLibro | pour esprit libre | www.inLibro.com On 04/19/2017 04:54 PM, Chris Cormack wrote: > On 20 April 2017 at 07:48, Philippe Blouin wrote: >> That's no strawman, that's a genuine questionning. >> >> You talk inclusivity, I'm all for it, but can we walk the talk now? 'They' >> is a bigger barrier to entry than 'he' for non-English readers/coders. But >> hey, what do I know, what is my perspective here? The stated initiative is >> good: the majority of users are female, the code is male-centric, can we be >> progressive, inclusive... But 'they' sucks. As I said, why not use "she" ? >> > Interestingly enough, my first language M?ori has no gendered pronouns at all. > All of them are non gendered. So they is much easier to understand for me. > > Anei t?n? ngeru > Here is their cat. > > There's your useless trivia for the day. Not all non english speakers > have gendered pronouns either :) > > Chris > _______________________________________________ > Koha-devel mailing list > Koha-devel at lists.koha-community.org > http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > website : http://www.koha-community.org/ > git : http://git.koha-community.org/ > bugs : http://bugs.koha-community.org/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From chris at bigballofwax.co.nz Wed Apr 19 23:34:26 2017 From: chris at bigballofwax.co.nz (Chris Cormack) Date: Thu, 20 Apr 2017 09:34:26 +1200 Subject: [Koha-devel] Gender-neutral pronouns In-Reply-To: <4dc97a1c-b5f9-6db1-71e4-15c3745a4031@inlibro.com> References: <8222506F-BB0D-4666-A47A-D8FD43E3593F@catalyst.net.nz> <2f4654fd-f78f-a450-bce2-07b448aeda9a@inlibro.com> <4dc97a1c-b5f9-6db1-71e4-15c3745a4031@inlibro.com> Message-ID: On 20 April 2017 at 09:19, Philippe Blouin wrote: > I appreciate the trivia, I was not aware of that possibility. I certainly > envy the students of the language. > > But I'll presume you've since used English quite enough to be considered > fluent in it, unlike most other Koha contributors. And if Kate is ready to > learn genderless pronouns, as I'm sure are most of the well rounded and > educated individuals that make up this community, it is not intuitive nor > easy, in fact it is very very confusing to the discrete contributor. An > unwarranted confusion, in my opinion. > > Again, to be clear, we're not talking about the face of Koha we're > presenting to the world, the Product. We're talking about coding guidelines > for code comments added genuinely by naive contributors. Lower the barrier > to entry, do not raise them! I've already volunteered to fix any mistakes spotted, without making the person resubmit. So case closed eh? :) Bonne nuit, P? m?rie Chris > > Anyway... have a good day/night/evening/dusk/dawn/lunch > > Damn it! It's hard to be inclusive! > > Have a good they > > Philippe Blouin, > Responsable du d?veloppement informatique > > T?l. : (888) 604-2627 > philippe.blouin at inLibro.com > > inLibro | pour esprit libre | www.inLibro.com > On 04/19/2017 04:54 PM, Chris Cormack wrote: > > On 20 April 2017 at 07:48, Philippe Blouin > wrote: > > That's no strawman, that's a genuine questionning. > > You talk inclusivity, I'm all for it, but can we walk the talk now? 'They' > is a bigger barrier to entry than 'he' for non-English readers/coders. But > hey, what do I know, what is my perspective here? The stated initiative is > good: the majority of users are female, the code is male-centric, can we be > progressive, inclusive... But 'they' sucks. As I said, why not use "she" ? > > Interestingly enough, my first language M?ori has no gendered pronouns at > all. > All of them are non gendered. So they is much easier to understand for me. > > Anei t?n? ngeru > Here is their cat. > > There's your useless trivia for the day. Not all non english speakers > have gendered pronouns either :) > > Chris > _______________________________________________ > Koha-devel mailing list > Koha-devel at lists.koha-community.org > http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > website : http://www.koha-community.org/ > git : http://git.koha-community.org/ > bugs : http://bugs.koha-community.org/ > > > > _______________________________________________ > Koha-devel mailing list > Koha-devel at lists.koha-community.org > http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > website : http://www.koha-community.org/ > git : http://git.koha-community.org/ > bugs : http://bugs.koha-community.org/ From fridolin.somers at biblibre.com Thu Apr 20 12:31:34 2017 From: fridolin.somers at biblibre.com (Fridolin SOMERS) Date: Thu, 20 Apr 2017 12:31:34 +0200 Subject: [Koha-devel] Koha and xhtml2pdf Message-ID: <87ad6dc9-9c1e-2e9c-aed6-302eb54596e3@biblibre.com> Hie. We have some problems with xhtml2pdf on Ubuntu Xenial. This soft is used by misc/cronjobs/printoverdues.sh. First it is strange that the package containing this soft "python-pisa" is not in koha-deps. I see there is "html2pdf" but there is no CSS option. In jessie we have to use the jessie-backports repo and install several packages : python-pisa python3-reportlab python-html5lib python-pypdf python-imaging python-renderpm python-reportlab python-reportlab-accel On ubuntu Xenial, we install those same packages but we have a bug in python call. We found it can be corrected by installing xhtml2pdf from its GIT repo. We would prefere to avoid this. Any help is welcome. Best regards, -- Fridolin SOMERS Biblibre - P?les support et syst?me fridolin.somers at biblibre.com From nick at bywatersolutions.com Thu Apr 20 14:57:35 2017 From: nick at bywatersolutions.com (Nick Clemens) Date: Thu, 20 Apr 2017 12:57:35 +0000 Subject: [Koha-devel] Elasticsearch < 2.x support In-Reply-To: <20170419195910.u76jrgl4mv4mklg5@rorohiko.wgtn.cat-it.co.nz> References: <20170419195910.u76jrgl4mv4mklg5@rorohiko.wgtn.cat-it.co.nz> Message-ID: 1.x to 2.x I think has a fair amount of breaking changes and we shouldn't support it. 2.x to 5.x should be workable ( https://www.elastic.co/guide/en/elasticsearch/reference/current/breaking-changes-5.0.html) but I would say 5.x is what we are officially supporting On Wed, Apr 19, 2017 at 3:59 PM Chris Cormack wrote: > Hi Tomas > > I think it is best to say 17.05 will support Elastic 5.0+ > (Maybe 2.1 but I havent tested) > > Definitely not 1.7 > > Chris > > * Tomas Cohen Arazi (tomascohen at gmail.com) wrote: > > Hi, I would like to ask what would the support status will be in 17.05 > for > > Elasticsearch 1.x (and maybe 2.x). > > > > According to the official docs [1], 1.x is already deprecated, and 2.x > > will be supported until 2018-02-28. > > I propose deprecating ES 1.x support officially, and also remove it > from > > kohadevbox. Maybe something to discuss next dev meeting, but I suppose > > there's no point supporting unsupported versions. > > Regards > > [1]? https://www.elastic.co/support/eol > > -- > > Tom??s Cohen Arazi > > Theke Solutions (https://theke.io) > > ?** +54 9351 3513384 <+54%209%20351%20351-3384> > > GPG: B2F3C15F > > >_______________________________________________ > >Koha-devel mailing list > >Koha-devel at lists.koha-community.org > >http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > >website : http://www.koha-community.org/ > >git : http://git.koha-community.org/ > >bugs : http://bugs.koha-community.org/ > > > -- > Chris Cormack > Catalyst IT Ltd. > +64 4 803 2238 <+64%204-803%202238> > PO Box 11-053, Manners St, Wellington 6142, New Zealand > _______________________________________________ > Koha-devel mailing list > Koha-devel at lists.koha-community.org > http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > website : http://www.koha-community.org/ > git : http://git.koha-community.org/ > bugs : http://bugs.koha-community.org/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From jonathan.druart at bugs.koha-community.org Thu Apr 20 15:28:04 2017 From: jonathan.druart at bugs.koha-community.org (Jonathan Druart) Date: Thu, 20 Apr 2017 13:28:04 +0000 Subject: [Koha-devel] Koha and xhtml2pdf In-Reply-To: <87ad6dc9-9c1e-2e9c-aed6-302eb54596e3@biblibre.com> References: <87ad6dc9-9c1e-2e9c-aed6-302eb54596e3@biblibre.com> Message-ID: Hi Frido, The script is telling you to install it using easy_install. If you want an alternative, take a look at PDF::FromHTML, it's what we use to generate discharges. Cheers, Jonathan On Thu, 20 Apr 2017 at 07:31 Fridolin SOMERS wrote: > Hie. > > We have some problems with xhtml2pdf on Ubuntu Xenial. > > This soft is used by misc/cronjobs/printoverdues.sh. > First it is strange that the package containing this soft "python-pisa" > is not in koha-deps. > I see there is "html2pdf" but there is no CSS option. > > In jessie we have to use the jessie-backports repo and install several > packages : > python-pisa python3-reportlab python-html5lib python-pypdf > python-imaging python-renderpm python-reportlab python-reportlab-accel > > On ubuntu Xenial, we install those same packages but we have a bug in > python call. > We found it can be corrected by installing xhtml2pdf from its GIT repo. > We would prefere to avoid this. > > Any help is welcome. > > Best regards, > > -- > Fridolin SOMERS > Biblibre - P?les support et syst?me > fridolin.somers at biblibre.com > _______________________________________________ > Koha-devel mailing list > Koha-devel at lists.koha-community.org > http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > website : http://www.koha-community.org/ > git : http://git.koha-community.org/ > bugs : http://bugs.koha-community.org/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From paul.poulain at biblibre.com Thu Apr 20 16:59:06 2017 From: paul.poulain at biblibre.com (Paul Poulain) Date: Thu, 20 Apr 2017 16:59:06 +0200 Subject: [Koha-devel] Gender-neutral pronouns In-Reply-To: References: Message-ID: <6eefcca5-f248-7d75-d3ae-a7dcd1a88cad@biblibre.com> I'll probably be poorly ranked here, but in my opinion there are more important things to fix in Koha... (randomly chosen: clean the wiki from severely outdated pages, test one of the 205 patches waiting for sign-off, improve documentation, investigate why we have 10 blockers or critical bugs open -without a patch-, one of them BZ14731 being >1yr old) additional comment: note that changes not related to code comment will change translations & translators will have additional work to do to fix. Le 19/04/2017 ? 02:25, Eric Phetteplace a ?crit : > Hi list, > > I opened bug #18432 > https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18432 > because I saw several places in the Koha codebase where the pronoun > "he" was being used to refer to a generic third person who could be of > any gender. Jonathan Druart noted that this should be a coding > guideline, as otherwise new instances of gendered pronouns might > continue to be added. Perhaps it belongs on the "Terminology" page of > the wiki? > > So here's my proposal. I'm trying to be concise. > > ---- > > *Use gender neutral pronouns* > * > * > When referring to a person who could be of any gender, you should use > the words they/them/their. This goes for code comments, text in > templates, and strings in tests. For example, here's a string from a > patrons test updated to be gender neutral. > > Before*:* > * > * > is( $total, $enrolmentfee_K + $enrolmentfee_J, "Kid growing and become > a juvenile, he should pay " . ( $enrolmentfee_K + $enrolmentfee_J ) ); > > After: > > is( $total, $enrolmentfee_K + $enrolmentfee_J, "Kid growing and become > a juvenile, they should pay " . ( $enrolmentfee_K + $enrolmentfee_J ) ); > > Gender neutral terms are preferable for a few reasons. They're more > welcoming, showing that Koha expects users and contributors to be of > any gender. They're also more accurate. Inappropriately using a > particular gender can cause confusion, leading someone to believe that > code operates differently based on the value of borrowers.sex, for > instance. > > ---- > > I hope that's clear. I'm happy to reword it, and to attend the next > Koha developers meeting to explain further if need be. > > Best, > Eric Phetteplace > Systems Librarian > California College of the Arts > libraries.cca.edu | vault.cca.edu > > 510.594.3660 > 2>/dev/null > > > _______________________________________________ > Koha-devel mailing list > Koha-devel at lists.koha-community.org > http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > website : http://www.koha-community.org/ > git : http://git.koha-community.org/ > bugs : http://bugs.koha-community.org/ -- Paul Poulain, Associ?-g?rant / co-owner BibLibre, Services en logiciels libres pour les biblioth?ques BibLibre, Open Source software and services for libraries -------------- section suivante -------------- Une pi?ce jointe HTML a ?t? nettoy?e... URL: From gmc at equinoxinitiative.org Thu Apr 20 17:14:33 2017 From: gmc at equinoxinitiative.org (Galen Charlton) Date: Thu, 20 Apr 2017 11:14:33 -0400 Subject: [Koha-devel] Gender-neutral pronouns In-Reply-To: <6eefcca5-f248-7d75-d3ae-a7dcd1a88cad@biblibre.com> References: <6eefcca5-f248-7d75-d3ae-a7dcd1a88cad@biblibre.com> Message-ID: Hi, On Thu, Apr 20, 2017 at 10:59 AM, Paul Poulain wrote: > I'll probably be poorly ranked here, but in my opinion there are more > important things to fix in Koha... (randomly chosen: clean the wiki from > severely outdated pages, test one of the 205 patches waiting for sign-off, > improve documentation, investigate why we have 10 blockers or critical bugs > open -without a patch-, one of them BZ14731 being >1yr old) Well, folks remain free to set their personal priorities in how they choose to contribute to Koha. Trying to be more inclusive by measuring our words more carefully does not preclude working on bugs or updating the wiki... and may also result in more potential contributors deciding to stick around and pitch in. Regards, Galen -- Galen Charlton Infrastructure and Added Services Manager Equinox Open Library Initiative phone: 1-877-OPEN-ILS (673-6457) email: gmc at equinoxInitiative.org web: https://equinoxInitiative.org direct: +1 770-709-5581 cell: +1 404-984-4366 From egpetridis at gmail.com Thu Apr 20 18:09:51 2017 From: egpetridis at gmail.com (Manos PETRIDIS) Date: Thu, 20 Apr 2017 19:09:51 +0300 Subject: [Koha-devel] Gender-neutral pronouns In-Reply-To: References: <6eefcca5-f248-7d75-d3ae-a7dcd1a88cad@biblibre.com> Message-ID: Tossing P.C. aside, is the syntax in ?Kid growing and becoming a juvenile, that kid must pay"?" acceptable? Wouldn't "Should a kid start paying on becoming an adult?" (or something among these lines) be preferable? MP ???? 20 ??? 2017 18:14, ? ??????? "Galen Charlton" < gmc at equinoxinitiative.org> ??????: Hi, On Thu, Apr 20, 2017 at 10:59 AM, Paul Poulain wrote: > I'll probably be poorly ranked here, but in my opinion there are more > important things to fix in Koha... (randomly chosen: clean the wiki from > severely outdated pages, test one of the 205 patches waiting for sign-off, > improve documentation, investigate why we have 10 blockers or critical bugs > open -without a patch-, one of them BZ14731 being >1yr old) Well, folks remain free to set their personal priorities in how they choose to contribute to Koha. Trying to be more inclusive by measuring our words more carefully does not preclude working on bugs or updating the wiki... and may also result in more potential contributors deciding to stick around and pitch in. Regards, Galen -- Galen Charlton Infrastructure and Added Services Manager Equinox Open Library Initiative phone: 1-877-OPEN-ILS (673-6457) email: gmc at equinoxInitiative.org web: https://equinoxInitiative.org direct: +1 770-709-5581 cell: +1 404-984-4366 _______________________________________________ Koha-devel mailing list Koha-devel at lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From marka at pobox.com Fri Apr 21 00:57:28 2017 From: marka at pobox.com (Mark Alexander) Date: Thu, 20 Apr 2017 18:57:28 -0400 Subject: [Koha-devel] Koha and xhtml2pdf In-Reply-To: <87ad6dc9-9c1e-2e9c-aed6-302eb54596e3@biblibre.com> References: <87ad6dc9-9c1e-2e9c-aed6-302eb54596e3@biblibre.com> Message-ID: <1492728474-sup-6582@t60p> This may not be relevant to Ubuntu, but I was able to get a working xhtml2pdf on Debian Jessie using this: apt-get install python-pip python-dev pip install xhtml2pdf Before figuring this out, I tried using 'easy_install pisa', but xhtml2pdf complained about missing dependencies and I was too lazy to figure out how to install them. One thing I discovered during this head-scratching phase was that easy_install has been deprecated, and pip is used nowadays, which led me to the above solution. From fridolin.somers at biblibre.com Fri Apr 21 17:13:16 2017 From: fridolin.somers at biblibre.com (Fridolin SOMERS) Date: Fri, 21 Apr 2017 17:13:16 +0200 Subject: [Koha-devel] Koha and xhtml2pdf In-Reply-To: <1492728474-sup-6582@t60p> References: <87ad6dc9-9c1e-2e9c-aed6-302eb54596e3@biblibre.com> <1492728474-sup-6582@t60p> Message-ID: <1e77f5f4-e33b-a22d-3dad-b210d72f9c1e@biblibre.com> Okiii, thanks a lot Le 21/04/2017 ? 00:57, Mark Alexander a ?crit : > This may not be relevant to Ubuntu, but I was able to get a working > xhtml2pdf on Debian Jessie using this: > > apt-get install python-pip python-dev > pip install xhtml2pdf > > Before figuring this out, I tried using 'easy_install pisa', but > xhtml2pdf complained about missing dependencies and I was too lazy to > figure out how to install them. One thing I discovered during this > head-scratching phase was that easy_install has been deprecated, and > pip is used nowadays, which led me to the above solution. > -- Fridolin SOMERS Biblibre - P?les support et syst?me fridolin.somers at biblibre.com From katrin.fischer.83 at web.de Sat Apr 22 08:12:18 2017 From: katrin.fischer.83 at web.de (Katrin) Date: Sat, 22 Apr 2017 08:12:18 +0200 Subject: [Koha-devel] Koha 16.11.07 released Message-ID: <1523cfd4-a68c-0f13-a641-82aba72c3570@web.de> The Koha community is proud to announce the release of Koha 16.11.07. This is a maintenance release of 16.11 and includes 38 bugfixes. The full release notes are available at https://koha-community.org/koha-16-11-07-release/ Packages will be available soon. From dcook at prosentient.com.au Mon Apr 24 02:03:19 2017 From: dcook at prosentient.com.au (David Cook) Date: Mon, 24 Apr 2017 10:03:19 +1000 Subject: [Koha-devel] Gender-neutral pronouns In-Reply-To: References: <6eefcca5-f248-7d75-d3ae-a7dcd1a88cad@biblibre.com> Message-ID: <035f01d2bc8e$2e7a4a70$8b6edf50$@prosentient.com.au> +1 for gender neutral pronouns, and I agree with Galen; we all have our own priorities, as well as our own limitations and capabilities, when it comes to contributing to Koha. While I think it's the prerogative of the QA team and Release Manager to prioritize certain patches, I don't see any problems with people contributing patches regardless of their perceived importance. As for gender neutral pronouns, users of modern online English interfaces may notice that websites like Facebook are already doing this on their front-end. Instead of "X changed his status" or "X changed her status", it's now "X changed their status" - at least in cases where gender isn't specified. I graduated with a master's degree less than 5 years ago, and the norm was to use "they" instead of "him/her" or "him or her" in academic writing. As others have noted on Bugzilla, "him or her" or "him/her" is heavy to read and non-inclusive. The idea of using "her" instead of "him" (as Phillippe suggested) was used by some writers in the early 21st century, but it's mostly fallen out of fashion. While it was politically significant, it's not inclusive/accurate. While some people might think "they" is overly politically correct, it seems perfectly logical to me. It's more concise, inclusive, and accurate. Consider the following scenario. Your child goes to the doctor as they are feeling ill. They come home and you say, "you've been to the doctor? What was their medical opinion?". You wouldn't say "What was her medical opinion?" or "What was his medical opinion?" as you don't know the gender of the doctor. (Also you are being inclusive of trans and non-gender conforming people as well.) (Note also that I didn't specify the gender of your child either, as I don't know the gender of your child, so I used "they" there too.) I can understand that this might be difficult to understand for people whose primary languages are heavily gendered like French and Spanish. While those languages have engaged with the concept of gender neutrality (https://en.wikipedia.org/wiki/Gender_neutrality_in_languages_with_grammatic al_gender), I think pronouns haven't quite been worked out. I've seen proposals for new gender neutral pronouns in both languages, but I don't think they're widely recognized, while "they" is quite widely used in contemporary English. If I understand Bug 18432 correctly, the change is just to code comments, which are in English anyway, so I don't think there is the problem of gender neutrality in other languages. If we're using gender neutral pronouns in templates/code, I can see that becoming more difficult. David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Direct: 02 8005 0595 > -----Original Message----- > From: koha-devel-bounces at lists.koha-community.org [mailto:koha-devel- > bounces at lists.koha-community.org] On Behalf Of Galen Charlton > Sent: Friday, 21 April 2017 1:15 AM > To: Paul Poulain > Cc: koha-devel at lists.koha-community.org > Subject: Re: [Koha-devel] Gender-neutral pronouns > > Hi, > > On Thu, Apr 20, 2017 at 10:59 AM, Paul Poulain > wrote: > > I'll probably be poorly ranked here, but in my opinion there are more > > important things to fix in Koha... (randomly chosen: clean the wiki > > from severely outdated pages, test one of the 205 patches waiting for > > sign-off, improve documentation, investigate why we have 10 blockers > > or critical bugs open -without a patch-, one of them BZ14731 being > > >1yr old) > > Well, folks remain free to set their personal priorities in how they choose to > contribute to Koha. Trying to be more inclusive by measuring our words more > carefully does not preclude working on bugs or updating the wiki... and may > also result in more potential contributors deciding to stick around and pitch in. > > Regards, > > Galen > -- > Galen Charlton > Infrastructure and Added Services Manager Equinox Open Library Initiative > phone: 1-877-OPEN-ILS (673-6457) > email: gmc at equinoxInitiative.org > web: https://equinoxInitiative.org > direct: +1 770-709-5581 > cell: +1 404-984-4366 > _______________________________________________ > Koha-devel mailing list > Koha-devel at lists.koha-community.org > http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > website : http://www.koha-community.org/ git : http://git.koha-community.org/ > bugs : http://bugs.koha-community.org/ From dcook at prosentient.com.au Mon Apr 24 02:06:50 2017 From: dcook at prosentient.com.au (David Cook) Date: Mon, 24 Apr 2017 10:06:50 +1000 Subject: [Koha-devel] Gender-neutral pronouns In-Reply-To: References: <6eefcca5-f248-7d75-d3ae-a7dcd1a88cad@biblibre.com> Message-ID: <036001d2bc8e$ac503040$04f090c0$@prosentient.com.au> I imagine there are a number of ways we could re-word it. I don?t fully understand the test out of context, but I suspect maybe something like ?The borrower has changed category from kid to juvenile. They should pay X + Y.?. David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Direct: 02 8005 0595 From: koha-devel-bounces at lists.koha-community.org [mailto:koha-devel-bounces at lists.koha-community.org] On Behalf Of Manos PETRIDIS Sent: Friday, 21 April 2017 2:10 AM Cc: koha-devel at lists.koha-community.org Subject: Re: [Koha-devel] Gender-neutral pronouns Tossing P.C. aside, is the syntax in ?Kid growing and becoming a juvenile, that kid must pay"?" acceptable? Wouldn't "Should a kid start paying on becoming an adult?" (or something among these lines) be preferable? MP ???? 20 ??? 2017 18:14, ? ??????? "Galen Charlton" > ??????: Hi, On Thu, Apr 20, 2017 at 10:59 AM, Paul Poulain > wrote: > I'll probably be poorly ranked here, but in my opinion there are more > important things to fix in Koha... (randomly chosen: clean the wiki from > severely outdated pages, test one of the 205 patches waiting for sign-off, > improve documentation, investigate why we have 10 blockers or critical bugs > open -without a patch-, one of them BZ14731 being >1yr old) Well, folks remain free to set their personal priorities in how they choose to contribute to Koha. Trying to be more inclusive by measuring our words more carefully does not preclude working on bugs or updating the wiki... and may also result in more potential contributors deciding to stick around and pitch in. Regards, Galen -- Galen Charlton Infrastructure and Added Services Manager Equinox Open Library Initiative phone: 1-877-OPEN-ILS (673-6457) email: gmc at equinoxInitiative.org web: https://equinoxInitiative.org direct: +1 770-709-5581 cell: +1 404-984-4366 _______________________________________________ Koha-devel mailing list Koha-devel at lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From julian.maurice at biblibre.com Mon Apr 24 10:02:49 2017 From: julian.maurice at biblibre.com (Julian Maurice) Date: Mon, 24 Apr 2017 10:02:49 +0200 Subject: [Koha-devel] [Koha] Koha 3.22.20 security release Message-ID: <79f3cfaf-a822-3c5f-5d5e-6482ae88b1db@biblibre.com> The Koha community is proud to announce the release of Koha 3.22.20. This is a security release and contains several bugfixes. If you are running 3.22.x it is strongly recommended to upgrade. The full release notes are available at https://koha-community.org/koha-3-22-20-security-release/ From dcook at prosentient.com.au Mon Apr 24 10:08:34 2017 From: dcook at prosentient.com.au (David Cook) Date: Mon, 24 Apr 2017 18:08:34 +1000 Subject: [Koha-devel] Koha and xhtml2pdf In-Reply-To: <1492728474-sup-6582@t60p> References: <87ad6dc9-9c1e-2e9c-aed6-302eb54596e3@biblibre.com> <1492728474-sup-6582@t60p> Message-ID: <03b301d2bcd1$f8231080$e8693180$@prosentient.com.au> Yeah, no one uses easy_install anymore. It's all about pip. However, the community likes to have everything packaged, and using pip is like using cpan... so this seems like an issue to me. Does Koha have anyone of notifying that there's a dependency missing if it's not installed in this case? David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Direct: 02 8005 0595 > -----Original Message----- > From: koha-devel-bounces at lists.koha-community.org [mailto:koha-devel- > bounces at lists.koha-community.org] On Behalf Of Mark Alexander > Sent: Friday, 21 April 2017 8:57 AM > To: Fridolin SOMERS > Cc: koha-devel > Subject: Re: [Koha-devel] Koha and xhtml2pdf > > This may not be relevant to Ubuntu, but I was able to get a working xhtml2pdf > on Debian Jessie using this: > > apt-get install python-pip python-dev > pip install xhtml2pdf > > Before figuring this out, I tried using 'easy_install pisa', but xhtml2pdf > complained about missing dependencies and I was too lazy to figure out how to > install them. One thing I discovered during this head-scratching phase was that > easy_install has been deprecated, and pip is used nowadays, which led me to > the above solution. > _______________________________________________ > Koha-devel mailing list > Koha-devel at lists.koha-community.org > http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > website : http://www.koha-community.org/ git : http://git.koha-community.org/ > bugs : http://bugs.koha-community.org/ From jonathan.druart at bugs.koha-community.org Tue Apr 25 18:21:04 2017 From: jonathan.druart at bugs.koha-community.org (Jonathan Druart) Date: Tue, 25 Apr 2017 16:21:04 +0000 Subject: [Koha-devel] Task schedulers and message queues for Koha In-Reply-To: <0ce901d28d88$2470b300$6d521900$@prosentient.com.au> References: <0ad301d28b14$e55deb30$b019c190$@prosentient.com.au> <42a983a1-d2c7-b857-384d-a0fcf630ef6d@cineca.it> <0c2d01d28c91$f4b9f5a0$de2de0e0$@prosentient.com.au> <0e689b11-ebe7-107e-151e-0f7edfbeb981@cineca.it> <0cd801d28d6f$abc22780$03467680$@prosentient.com.au> <0ce901d28d88$2470b300$6d521900$@prosentient.com.au> Message-ID: On Thu, 23 Feb 2017 at 00:51 David Cook wrote: > I?m planning to post the code for what I have already in early March. > Any news here? We really need to remove the way our background jobs are implemented to make them work under Plack. I'd like to avoid duplication of work... > David Cook > > Systems Librarian > > Prosentient Systems > > 72/330 Wattle St > > Ultimo, NSW 2007 > > Australia > > > > Office: 02 9212 0899 <02%2092%2012%2008%2099> > > Direct: 02 8005 0595 <02%2080%2005%2005%2095> > > > > *From:* Tomas Cohen Arazi [mailto:tomascohen at gmail.com] > *Sent:* Thursday, 23 February 2017 2:16 PM > *To:* David Cook ; Tajoli Zeno < > z.tajoli at cineca.it>; koha-devel at lists.koha-community.org > > > *Subject:* Re: [Koha-devel] Task schedulers and message queues for Koha > > > > Share it :-) > > > > El mi?., 22 de feb. de 2017 9:57 PM, David Cook > escribi?: > > Hi Zeno, > > I have a number of concerns about Celery. One of those is that it would add > numerous external dependencies and complexity to Koha implementations. > > Your suggestion of Celery + RabbitMQ + AnyEvent::RabbitMQ sounds ok, > although it would involve work too. While Celery clients exist for PHP and > Node.js, we'd need to create a Perl implementation of the Celery protocol > using AnyEvent::RabbitMQ (or Net::RabbitFoot). Not that I'm necessarily > opposed to that. > > We'd also still need to write the tasks in Python (or use web hooks which > would have the overhead of HTTP plus you'd have to worry about your web > server being up). I'm not sure how keen the community at large is to > support > more server-side languages. I like writing Python, so I don't mind porting > over my OAI-PMH code from Perl to Python. I've abandoned the HTTP::OAI > module anyway for a few reasons. > > RabbitMQ is a pretty heavy duty product as well which comes with its own > requirements: https://www.rabbitmq.com/production-checklist.html. While we > currently help people with Apache, MySQL, Zebra, and ElasticSearch, we'd > also all need to become experts with RabbitMQ. > > I've already put together a Perl-based scheduler using POE which forks its > own workers. And I've already put together a basic Perl-based message queue > which sends events to pre-existing workers (like Celery). Celery with > RabbitMQ is more mature and complex, but my Perl programs do the trick. > > Looking at DSpace's OAI-PMH harvester, it works very much like my first > design. It's a Java scheduler which uses threads rather than child > processes > to do its work. > > Due to the lack of engagement overall, I think I'll probably just keep my > existing design, since it works and works quite well. > > David Cook > Systems Librarian > Prosentient Systems > 72/330 Wattle St > Ultimo, NSW 2007 > Australia > > Office: 02 9212 0899 <02%2092%2012%2008%2099> > Direct: 02 8005 0595 <02%2080%2005%2005%2095> > > > > -----Original Message----- > > From: Tajoli Zeno [mailto:z.tajoli at cineca.it] > > Sent: Wednesday, 22 February 2017 7:49 PM > > To: David Cook ; koha-devel at lists.koha- > > community.org > > Subject: Re: [Koha-devel] Task schedulers and message queues for Koha > > > > Hi David and all, > > > > Il 21/02/2017 23:29, David Cook ha scritto: > > >. Two, they wanted to > > > execute OAI-PMH requests every 2-3 seconds and cron has 1 minute as > > >its finest granularity. Three, even if you setup a cronjob to run > > >every minute, long running tasks could get duplicated (although you > > >could mitigate that with locks which would be a pain). Plus, you want > > >to run tasks in parallel, so you're going to want to use multiple > > >processes, which cron isn't really set up to achieve. > > > > Ok, if you need those features cron isn't enough. > > But why do you drop the option Celery + RabbitMQ + AnyEvent::RabbitMQ > > > > They have official debiano packages: > > https://packages.debian.org/jessie/python-celery > > https://packages.debian.org/jessie/rabbitmq-server > > https://packages.debian.org/jessie/libanyevent-rabbitmq-perl > > > > We still use one of their dpendencies for similar tasks (libanyevent-perl > "event > > loop framework with multiple implementations"). > > > > Python is already present in our Debian/Ubuntu system, it is a prereq of > the > > distributions. > > > > Redone a so complex stack in perl i think is very complex. > > > > Bye > > Zeno Tajoli > > > > > > > > -- > > Zeno Tajoli > > /SVILUPPO PRODOTTI CINECA/ - Automazione Biblioteche > > Email: z.tajoli at cineca.it Fax: 051/6132198 > > *CINECA* Consorzio Interuniversitario - Sede operativa di Segrate (MI) > > > _______________________________________________ > Koha-devel mailing list > Koha-devel at lists.koha-community.org > http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > website : http://www.koha-community.org/ > git : http://git.koha-community.org/ > bugs : http://bugs.koha-community.org/ > > -- > > Tom?s Cohen Arazi > > Theke Solutions (https://theke.io ) > ? +54 9351 3513384 <+54%209%20351%20351-3384> > GPG: B2F3C15F > _______________________________________________ > Koha-devel mailing list > Koha-devel at lists.koha-community.org > http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > website : http://www.koha-community.org/ > git : http://git.koha-community.org/ > bugs : http://bugs.koha-community.org/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From jonathan.druart at bugs.koha-community.org Tue Apr 25 19:19:12 2017 From: jonathan.druart at bugs.koha-community.org (Jonathan Druart) Date: Tue, 25 Apr 2017 17:19:12 +0000 Subject: [Koha-devel] What's on in koha-devel #12 Message-ID: Hello librarians and developers, My last email got a lot of interest and people do not stop contacting me to help us, it's fantastic! Heh, no, just kidding. But I am still willing to help you! Whenever you are ready, just let me/us know! The next release is on its way. We are in the final stretch, I will summarize in this email what needs to be done in the next month. = Release dates = Kyle published the different dates of the Koha 17.05 release: May 5 - Feature Slush May 12 - Feature Freeze, String Freeze, 1st Draft of Release Notes May 19 - Release Beta, 2nd Draft of Release Notes May 26 - Final Release May 27 - Champagne! What does it mean? * Feature slush - enhancements that have not been marked as Passed QA at this time will not be considered for the release * Feature freeze - no new enhancements will be pushed to master, only bug fixes! * String freeze - only bug fixes without string changes will be pushed to master If you want one of our awesome features waiting for testing to be present in this new release, you should warm the sandboxes up for the next 10 days! = New stuffs pushed (or almost) = == Hea v2 == The production server (https://hea.koha-community.org) has been updated last week. The Koha side code (bug 18066) has been pushed to master and should be backported into the next stable releases (16.11.07, 16.05.13 and 3.22.21). What's new? * Ability to share the information at library level instead of installation level. If you have more than one library defined in your Koha installation, you will be able to share the URL, country and geolocation of each library * Configuration page in the administration module to define what you want to share with the community (Home ? Administration ? Usage statistics - admin/usage_statistics.pl) * On the hea website your Koha installation will be linked to one public page where you will see all the public information we collect * The database of the website has been cleaned to remove the duplicate and test entries The screenshots I have done during the development: Koha side: New page to configure the info to share: https://pageshot.net/opGCLAZFt0s1HVzp/pro.kohadev.vm (with libraries info) https://pageshot.net/SKTFZgr40EKg6fge/pro.kohadev.vm (without libraries info) Hea side: New layout for the homepage: https://pageshot.net/GGKbBZlZwxpXuCoi/localhost View "see all libraries" (existing one): https://pageshot.net/2XplbZXFFr9rLNJS/localhost View "see libraries by country": https://pageshot.net/G5czRcqh47WFIfRD/localhost View "see libraries on a map": https://pageshot.net/Xa4qW3Vc4MclrEhO/localhost View "public view for a library" (to show libraries what is public): https://pageshot.net/7whCONhkPuJUUxDP/localhost I invite you all to take a look at the configuration page and share with us the information you want to be public. You can find the "Terms and Conditions" on github https://github.com/joubu/hea-app/blob/v2/Terms_and_Conditions.md (Todo: link it from the hea website and Koha!) == Onboarding tools == The onboarding tool (bug 17855) is not pushed yet to master but is Passed QA and should be part of the next release. It adds new steps at the end of the installation process, to create different kinds of data and ease the first contact. You will be able to create a first library, patron category, item type, circulation rule and a patron with superlibrarian permission. Note that another patch (bug 17942) will arrive soon to refresh the style of the web installer interface. = Patches waiting for love = == Automatically convert SQL reports (urgent) == Since we have bug 17196 (Move marcxml out of the biblioitems table) pushed into the next release, we absolutely need bug 17898 (Add a way to automatically convert SQL reports) too. It is waiting for testing and is really easy to test and QA. This patch will help librarians to update SQL reports after the move of the marcxml field out of the biblioitems table. == Permissions for lists (urgent) == The aim of bug 18228 is to make the permissions for list easier to use and understand. However as it will remove complexity, it may remove a feature you are using. If you are using complex permission system to manage the lists you should take a look at this bug from comment 19. As Marcel already asked on the mailing list twice, this is the LAST CALL. I am going to QA it before the feature slush if nobody disagrees. == Facet configurable for Elastic == If you want to get a new Elastic search enhancement in the next release, take a look at bug 18235. It adds a new configuration area to configure facets. = Technical discussions = I would like to rework our background jobs. They do not work under Plack and it is a pity (see bug 15032). If anybody already did that in the past or has a clear idea on how to implement a job queue using TheSchwartz, gearman or others, please let me know. Unfortunately I do not have much time at the moment to explore the different options and play with them. = Tools for devs = I have added a new commit to the apply_on_cascade branch of my git-bz github repo: https://github.com/joubu/git-bz/commit/7afcfdb8a55384e79405ae44a697c36fa5f583a7 It modifies the behaviour of `git bz attach -e` when there are several patches to attach. The edit will be effective on the first attachment only. Indeed most of the time I just want to change the status and obsolete the patches and not to edit the commit messages. Just revert it if you do not want this behaviour. If you want to help testing bugs before the release, take a look at this search: https://frama.link/Koha_Needs_Signoff_bugs It shows all the opened bugs with a patch attached. They are bugs and new enhancement, are sorted by severity. Pick them from the top :) The next general IRC meeting is on May 3rd, 20 UTC. https://wiki.koha-community.org/wiki/General_IRC_meeting_03_May_2017 The next dev IRC meeting is tomorrow, April 26th at 13UTC https://wiki.koha-community.org/wiki/Development_IRC_meeting_26_April_2017 Hope to see your there! Cheers, Jonathan -------------- next part -------------- An HTML attachment was scrubbed... URL: From nick at bywatersolutions.com Wed Apr 26 04:32:25 2017 From: nick at bywatersolutions.com (Nick Clemens) Date: Wed, 26 Apr 2017 02:32:25 +0000 Subject: [Koha-devel] Koha Developers IRC Meeting Tomorrow Message-ID: Hello Koha community! In case any of you didn't read to the end of Jonathan's email (and if you didn't you really should) tomorrow is the next developers meeting: The next dev IRC meeting is tomorrow, April 26th at 13UTC https://wiki.koha-community.org/wiki/Development_IRC_meeting_26_April_2017 Local time and date conversion here: https://www.timeanddate.com/worldclock/fixedtime.html?msg=Koha+Developers+IRC+Meeting&iso=20170426T13 This will be the last meeting before feature slush so come one and come all, tell us what you need, tell us how you want to help, or just come and lurk and watch the sausage get made :-) -Nick -------------- next part -------------- An HTML attachment was scrubbed... URL: From paul.poulain at biblibre.com Thu Apr 27 10:39:25 2017 From: paul.poulain at biblibre.com (Paul Poulain) Date: Thu, 27 Apr 2017 10:39:25 +0200 Subject: [Koha-devel] schema.koha-community.org not updated Message-ID: <648f3aeb-27bc-4e88-9e11-6d2dd7b509bc@biblibre.com> Hi, We just discovered that schema.koha-community.org has not been updated since december. Can it be fixed ? (it's really annoying for master) -- Paul Poulain, Associ?-g?rant / co-owner BibLibre, Services en logiciels libres pour les biblioth?ques BibLibre, Open Source software and services for libraries From fridolin.somers at biblibre.com Thu Apr 27 13:41:52 2017 From: fridolin.somers at biblibre.com (Fridolin SOMERS) Date: Thu, 27 Apr 2017 13:41:52 +0200 Subject: [Koha-devel] Elasticsearch < 2.x support In-Reply-To: References: Message-ID: <92fbd77c-d803-0fc9-66a9-f71ec789f22a@biblibre.com> Do not support ES 1.x in my opinion. Since it is a new feature there will be no migration issues. Best regards, Le 19/04/2017 ? 15:34, Tomas Cohen Arazi a ?crit : > Hi, I would like to ask what would the support status will be in 17.05 for > Elasticsearch 1.x (and maybe 2.x). > > According to the official docs [1], 1.x is already deprecated, and 2.x will > be supported until 2018-02-28. > > I propose deprecating ES 1.x support officially, and also remove it from > kohadevbox. Maybe something to discuss next dev meeting, but I suppose > there's no point supporting unsupported versions. > > Regards > > [1] https://www.elastic.co/support/eol > > > > _______________________________________________ > Koha-devel mailing list > Koha-devel at lists.koha-community.org > http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > website : http://www.koha-community.org/ > git : http://git.koha-community.org/ > bugs : http://bugs.koha-community.org/ > -- Fridolin SOMERS Biblibre - P?les support et syst?me fridolin.somers at biblibre.com From bargioni at pusc.it Thu Apr 27 17:02:24 2017 From: bargioni at pusc.it (Stefano Bargioni) Date: Thu, 27 Apr 2017 17:02:24 +0200 Subject: [Koha-devel] Elasticsearch < 2.x support In-Reply-To: <92fbd77c-d803-0fc9-66a9-f71ec789f22a@biblibre.com> References: <92fbd77c-d803-0fc9-66a9-f71ec789f22a@biblibre.com> Message-ID: Can we check the SearchEngine syspref through UsageStats? And maybe we could add some info about Elasticsearch in the "About Koha" screen. Stefano > On 27 Apr 2017, at 13:41, Fridolin SOMERS wrote: > > Do not support ES 1.x in my opinion. > > Since it is a new feature there will be no migration issues. > > Best regards, > > Le 19/04/2017 ? 15:34, Tomas Cohen Arazi a ?crit : >> Hi, I would like to ask what would the support status will be in 17.05 for >> Elasticsearch 1.x (and maybe 2.x). >> >> According to the official docs [1], 1.x is already deprecated, and 2.x will >> be supported until 2018-02-28. >> >> I propose deprecating ES 1.x support officially, and also remove it from >> kohadevbox. Maybe something to discuss next dev meeting, but I suppose >> there's no point supporting unsupported versions. >> >> Regards >> >> [1] https://www.elastic.co/support/eol >> >> >> >> _______________________________________________ >> Koha-devel mailing list >> Koha-devel at lists.koha-community.org >> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel >> website : http://www.koha-community.org/ >> git : http://git.koha-community.org/ >> bugs : http://bugs.koha-community.org/ >> > > -- > Fridolin SOMERS > Biblibre - P?les support et syst?me > fridolin.somers at biblibre.com > _______________________________________________ > Koha-devel mailing list > Koha-devel at lists.koha-community.org > http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > website : http://www.koha-community.org/ > git : http://git.koha-community.org/ > bugs : http://bugs.koha-community.org/ From francois.charbonnier at inlibro.com Thu Apr 27 20:58:52 2017 From: francois.charbonnier at inlibro.com (Francois Charbonnier) Date: Thu, 27 Apr 2017 14:58:52 -0400 Subject: [Koha-devel] The interface "winks" when I check out a book after upgrading firefox Message-ID: <19b5bdc1-9dd0-022f-6d72-6136f0e13d15@inlibro.com> Hi, I use Koha 16.05 and firefox 53. When I check out an item, the interface "winks". I tried this with firefox 52, the interface stays still. Have you noticed it as well ? Any advice to fix it ? Thanks! -- Fran?ois Charbonnier, Bibl. prof. / Chef de produits T?l. : (888) 604-2627 francois.charbonnier at inLibro.com inLibro | Sp?cialistes en technologies documentaires | www.inLibro.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From mirko at abunchofthings.net Fri Apr 28 08:12:01 2017 From: mirko at abunchofthings.net (Mirko Tietgen) Date: Fri, 28 Apr 2017 08:12:01 +0200 Subject: [Koha-devel] [Koha] Koha 16.11.07 released In-Reply-To: <1523cfd4-a68c-0f13-a641-82aba72c3570@web.de> References: <1523cfd4-a68c-0f13-a641-82aba72c3570@web.de> Message-ID: Koha 16.11.07 is now available from the Koha community repository. Katrin Fischer schrieb am 22.04.2017 > The Koha community is proud to announce the release of Koha > 16.11.07. > > This is a maintenance release of 16.11 and includes 38 > bugfixes. > > The full release notes are available at > https://koha-community.org/koha-16-11-07-release/ > > Packages will be available soon. > > _______________________________________________ Koha mailing > list http://koha-community.org Koha at lists.katipo.co.nz > https://lists.katipo.co.nz/mailman/listinfo/koha From mirko at abunchofthings.net Fri Apr 28 09:14:39 2017 From: mirko at abunchofthings.net (Mirko Tietgen) Date: Fri, 28 Apr 2017 09:14:39 +0200 Subject: [Koha-devel] Koha + Elasticsearch 5.x dependency packages In-Reply-To: <39063ece-d53a-e6fb-9259-59697f3d6bb8@abunchofthings.net> References: <39063ece-d53a-e6fb-9259-59697f3d6bb8@abunchofthings.net> Message-ID: Hi, please try the (non Kohadevbox) setup for master explained in the wiki and send some feedback if it works for you. https://wiki.koha-community.org/wiki/Elasticsearch#Manual_install_.28master.29 I would like to offer it for regular installations of 17.05, but it should be tested by a few people before that. Thank you in advance, Mirko From fridolin.somers at biblibre.com Fri Apr 28 09:47:18 2017 From: fridolin.somers at biblibre.com (Fridolin SOMERS) Date: Fri, 28 Apr 2017 09:47:18 +0200 Subject: [Koha-devel] Koha + Elasticsearch 5.x dependency packages In-Reply-To: <39063ece-d53a-e6fb-9259-59697f3d6bb8@abunchofthings.net> References: <39063ece-d53a-e6fb-9259-59697f3d6bb8@abunchofthings.net> Message-ID: <1b794cc0-a636-91e4-2b97-9efb112a5f87@biblibre.com> Awesome :) Thanks a lot Mirko Le 30/03/2017 ? 17:28, Mirko Tietgen a ?crit : > Hi, > > it looks like I am done submitting and backporting dependencies for > Koha and Elasticsearch 5.x. I ran it in a test repo and it works as > far as I can see. > > Adding them to the unstable repository may or may not break > Kohadevbox and other setups, so I thought I'd give you a warning > before I do that. > > I will add the following packages: > > libapp-cmd-perl_0.331-1~kohadev1 > libbusiness-isbn-perl_3.003-1~kohadev1 > libcatmandu-marc-perl_1.09-1~kohadev1 > libcatmandu-perl_1.0304-2~kohadev1 > libcatmandu-store-elasticsearch-perl_0.0507-1~kohadev1 > libcpanel-json-xs-perl_3.0225-1~kohadev1 > liblog-any-perl_1.045-1~kohadev1 > libmarc-lint-perl_1.50-1~kohadev1 > libmoox-aliases-perl_0.001006-1~kohadev1 > libmoox-role-logger-perl_0.005-1~kohadev1 > libnamespace-clean-perl_0.27-1~kohadev1 > libsearch-elasticsearch-perl_5.01-1~kohadev1 > libmarc-spec-perl_0.1.2-1~kohadev1 > libparser-mgc-perl_0.15-1~kohadev1 > libref-util-perl_0.113-1~kohadev1 > libtext-hogan-perl_1.04-1~kohadev1 > liburi-template-perl_0.22-0.1~kohadev1 > > Tomas (and other people with Kohadevbox knowledge), I suppose you > need to make changes to not CPAN stuff anymore? To pull in the new > packages, it should be enought to > > apt-get install libcatmandu-store-elasticsearch-perl > libcatmandu-marc-perl > > once they are in the repository. > > I plan to have the packages in the unstable repository next monday. > > Cheers, > > Mirko > > > -- > > Mirko Tietgen > mirko at abunchofthings.net > http://koha.abunchofthings.net > http://meinkoha.de > > _______________________________________________ > Koha-devel mailing list > Koha-devel at lists.koha-community.org > http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > website : http://www.koha-community.org/ > git : http://git.koha-community.org/ > bugs : http://bugs.koha-community.org/ > -- Fridolin SOMERS Biblibre - P?les support et syst?me fridolin.somers at biblibre.com From tomascohen at gmail.com Fri Apr 28 16:22:11 2017 From: tomascohen at gmail.com (Tomas Cohen Arazi) Date: Fri, 28 Apr 2017 14:22:11 +0000 Subject: [Koha-devel] Koha + Elasticsearch 5.x dependency packages In-Reply-To: References: <39063ece-d53a-e6fb-9259-59697f3d6bb8@abunchofthings.net> Message-ID: Mirko, Just a side note: kohadevbox follows exactly those steps. but I just noticed it is pointing to a different ES debian repo so ES is a bit outdated (5.0 vs 5.3). I'll fix that ASAP. Great work! This is what we are doing. The thing I like about Ansible is that the YAML notation is easy to read and self explanatory! (note we still pick Oracle's JRE, because I read it was recommended on the ES page, but might be worth moving back to openjdk): --- - name: Elasticsearch {{ elasticsearch_version }} | Add Oracle Java 8 repository (key) apt_key: keyserver: keyserver.ubuntu.com id: 7B2C3B0889BF5709A105D03AC2518248EEA14886 state: present - name: Elasticsearch {{ elasticsearch_version }} | Add Oracle Java 8 repository (repo) apt_repository: repo: 'deb http://ppa.launchpad.net/webupd8team/java/ubuntu xenial main' state: present update_cache: yes - name: Elasticsearch {{ elasticsearch_version }} | Accept Oracle license shell: echo oracle-java8-installer shared/accepted-oracle-license-v1-1 select true | /usr/bin/debconf-set-selections - name: Elasticsearch {{ elasticsearch_version }} | Install Oracle Java 8 apt: name: oracle-java8-installer state: latest - name: Elasticsearch {{ elasticsearch_version }} | Add Elasticsearch repository (key) apt_key: url: 'https://packages.elastic.co/GPG-KEY-elasticsearch' state: present - name: Elasticsearch {{ elasticsearch_version }} | Add Elasticsearch repository (repo) apt_repository: repo: "deb https://artifacts.elastic.co/packages/{{ elasticsearch_version }}/apt stable main" state: present - name: Elasticsearch {{ elasticsearch_version }} | Install Elasticsearch apt: name: elasticsearch state: latest force: yes - name: Elasticsearch {{ elasticsearch_version }} | Run Elasticsearch on startup service: name: elasticsearch enabled: yes state: started - name: Elasticsearch {{ elasticsearch_version }} | Install Koha's Elasticsearch deps apt: name: koha-elasticsearch state: latest -- Tom?s Cohen Arazi Theke Solutions (https://theke.io ) ? +54 9351 3513384 GPG: B2F3C15F -------------- next part -------------- An HTML attachment was scrubbed... URL: From veron at veron.ch Fri Apr 28 21:35:04 2017 From: veron at veron.ch (=?UTF-8?Q?Marc_V=c3=a9ron?=) Date: Fri, 28 Apr 2017 21:35:04 +0200 Subject: [Koha-devel] The interface "winks" when I check out a book after upgrading firefox In-Reply-To: <19b5bdc1-9dd0-022f-6d72-6136f0e13d15@inlibro.com> References: <19b5bdc1-9dd0-022f-6d72-6136f0e13d15@inlibro.com> Message-ID: Hi Fran?ois I have a strange 'blinking' or 'winking' on current master as well - not sure if we speak about the same thing: - On the staff client main page, click on 'Patrons' - While loading the page, I see very shortly a yellow message "Add patrons to" (I took a video and stepped through it to be able to read the text). - Then the page refreshes and displays as expected. - I get the same when I am on the page Home > Patrons and click 'Search'. I get it with Firefox 53.0 (Windows) I do not get it with Firefox ESR 45.3.0 (Debian) Is it that what you mean? Marc Am 27.04.2017 um 20:58 schrieb Francois Charbonnier: > > Hi, > > I use Koha 16.05 and firefox 53. When I check out an item, the > interface "winks". > > I tried this with firefox 52, the interface stays still. > > Have you noticed it as well ? Any advice to fix it ? > > Thanks! > > -- > Fran?ois Charbonnier, > Bibl. prof. / Chef de produits > > T?l. : (888) 604-2627 > francois.charbonnier at inLibro.com > > > inLibro | Sp?cialistes en technologies documentaires | www.inLibro.com > > > > _______________________________________________ > Koha-devel mailing list > Koha-devel at lists.koha-community.org > http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > website : http://www.koha-community.org/ > git : http://git.koha-community.org/ > bugs : http://bugs.koha-community.org/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From nick at bywatersolutions.com Fri Apr 28 22:35:33 2017 From: nick at bywatersolutions.com (Nick Clemens) Date: Fri, 28 Apr 2017 20:35:33 +0000 Subject: [Koha-devel] Global Bug Squashing Day (Bugs only edition) - GBSD, May 10th, 2017 Message-ID: Hi All, At the last Koha Developers Meeting it was proposed to hold a special 'Bugs Only' Squashing Day in order to clean up things before the 17.05 release. We are hoping to get some new sign-offers, librarians, and developers involved in the process and make 17.05 the new hotness. There is a developers meeting that day as well, so there should be plenty of us available to help. We want your questions, we want to help! If you have always wanted to get involved now is a good time, so spin up a devbox, try out a sandbox, or just visit us in IRC and ask everything you wanted to know about Koha and we will help as best as we can I will follow with more info next week but wanted to at least get the date out before the weekend. -Nick (kidclamp) -------------- next part -------------- An HTML attachment was scrubbed... URL: From katrin.fischer.83 at web.de Sun Apr 30 17:54:25 2017 From: katrin.fischer.83 at web.de (Katrin) Date: Sun, 30 Apr 2017 17:54:25 +0200 Subject: [Koha-devel] Gender-neutral pronouns In-Reply-To: References: Message-ID: <49d91b27-174f-34be-b024-8423a1eb2642@web.de> Hi Eric, thx for writing this up! I have added your draft to the agenda of the next dev meeting: https://wiki.koha-community.org/wiki/Development_IRC_meeting_10_May_2017 Katrin On 19.04.2017 02:25, Eric Phetteplace wrote: > Hi list, > > I opened bug #18432 > https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18432 > because I saw several places in the Koha codebase where the pronoun > "he" was being used to refer to a generic third person who could be of > any gender. Jonathan Druart noted that this should be a coding > guideline, as otherwise new instances of gendered pronouns might > continue to be added. Perhaps it belongs on the "Terminology" page of > the wiki? > > So here's my proposal. I'm trying to be concise. > > ---- > > *Use gender neutral pronouns* > * > * > When referring to a person who could be of any gender, you should use > the words they/them/their. This goes for code comments, text in > templates, and strings in tests. For example, here's a string from a > patrons test updated to be gender neutral. > > Before*:* > * > * > is( $total, $enrolmentfee_K + $enrolmentfee_J, "Kid growing and become > a juvenile, he should pay " . ( $enrolmentfee_K + $enrolmentfee_J ) ); > > After: > > is( $total, $enrolmentfee_K + $enrolmentfee_J, "Kid growing and become > a juvenile, they should pay " . ( $enrolmentfee_K + $enrolmentfee_J ) ); > > Gender neutral terms are preferable for a few reasons. They're more > welcoming, showing that Koha expects users and contributors to be of > any gender. They're also more accurate. Inappropriately using a > particular gender can cause confusion, leading someone to believe that > code operates differently based on the value of borrowers.sex, for > instance. > > ---- > > I hope that's clear. I'm happy to reword it, and to attend the next > Koha developers meeting to explain further if need be. > > Best, > Eric Phetteplace > Systems Librarian > California College of the Arts > libraries.cca.edu | vault.cca.edu > > 510.594.3660 > 2>/dev/null > > > _______________________________________________ > Koha-devel mailing list > Koha-devel at lists.koha-community.org > http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > website : http://www.koha-community.org/ > git : http://git.koha-community.org/ > bugs : http://bugs.koha-community.org/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From francois.charbonnier at inlibro.com Sun Apr 30 23:08:20 2017 From: francois.charbonnier at inlibro.com (Francois Charbonnier) Date: Sun, 30 Apr 2017 17:08:20 -0400 Subject: [Koha-devel] The interface "winks" when I check out a book after upgrading firefox In-Reply-To: References: <19b5bdc1-9dd0-022f-6d72-6136f0e13d15@inlibro.com> Message-ID: <1fd3e1eb-46df-f5ef-9cba-8ca7697f7828@inlibro.com> Thanks Marc! That's exactly what I mean. Do you think it's something that can be fixed ? Fran?ois Charbonnier, Bibl. prof. / Chef de produits T?l. : (888) 604-2627 francois.charbonnier at inLibro.com inLibro | Sp?cialistes en technologies documentaires | www.inLibro.com Le 2017-04-28 ? 15:35, Marc V?ron a ?crit : > > Hi Fran?ois > > I have a strange 'blinking' or 'winking' on current master as well - > not sure if we speak about the same thing: > > - On the staff client main page, click on 'Patrons' > - While loading the page, I see very shortly a yellow message "Add > patrons to" (I took a video and stepped through it to be able to read > the text). > - Then the page refreshes and displays as expected. > - I get the same when I am on the page Home > Patrons and click 'Search'. > > I get it with Firefox 53.0 (Windows) > I do not get it with Firefox ESR 45.3.0 (Debian) > > Is it that what you mean? > > Marc > > Am 27.04.2017 um 20:58 schrieb Francois Charbonnier: >> >> Hi, >> >> I use Koha 16.05 and firefox 53. When I check out an item, the >> interface "winks". >> >> I tried this with firefox 52, the interface stays still. >> >> Have you noticed it as well ? Any advice to fix it ? >> >> Thanks! >> >> -- >> Fran?ois Charbonnier, >> Bibl. prof. / Chef de produits >> >> T?l. : (888) 604-2627 >> francois.charbonnier at inLibro.com >> >> >> inLibro | Sp?cialistes en technologies documentaires | >> www.inLibro.com >> >> >> _______________________________________________ >> Koha-devel mailing list >> Koha-devel at lists.koha-community.org >> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel >> website :http://www.koha-community.org/ >> git :http://git.koha-community.org/ >> bugs :http://bugs.koha-community.org/ > > > > _______________________________________________ > Koha-devel mailing list > Koha-devel at lists.koha-community.org > http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > website : http://www.koha-community.org/ > git : http://git.koha-community.org/ > bugs : http://bugs.koha-community.org/ -------------- next part -------------- An HTML attachment was scrubbed... URL: