<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"><html><head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body>A new request with request id 8130 has been created by koha-devel-request@lists.koha-community.org. Short info on the request is : <br><br>Title : Koha-devel Digest, Vol 200, Issue 22<br>Category : <br>Description : <div>Send Koha-devel mailing list submissions to<br> koha-devel@lists.koha-community.org<br><br>To subscribe or unsubscribe via the World Wide Web, visit<br> https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel<br>or, via email, send a message with subject or body 'help' to<br> koha-devel-request@lists.koha-community.org<br><br>You can reach the person managing the list at<br> koha-devel-owner@lists.koha-community.org<br><br>When replying, please edit your Subject line so it is more specific<br>than "Re: Contents of Koha-devel digest..."<br><br><br>Today's Topics:<br><br> 1. Re: Updating SCSS lint process to use stylelint<br> (Tomas Cohen Arazi)<br> 2. Re: Updating SCSS lint process to use stylelint (Owen Leonard)<br> 3. Re: Long-term support version of Koha (bug 31008)<br> (Victor Grousset/tuxayo)<br><br><br>----------------------------------------------------------------------<br><br>Message: 1<br>Date: Thu, 21 Jul 2022 08:34:52 -0300<br>From: Tomas Cohen Arazi <tomascohen@gmail.com><br>To: "Renvoize, Martin" <martin.renvoize@ptfs-europe.com><br>Cc: Koha Devel <koha-devel@lists.koha-community.org><br>Subject: Re: [Koha-devel] Updating SCSS lint process to use stylelint<br>Message-ID:<br> <CABZfb=VbfFs3H-dFFpjGK0hETLhYPWiL6mHWFMy9fhh=6fFfpQ@mail.gmail.com><br>Content-Type: text/plain; charset="utf-8"<br><br>Hi Owen!<br><br>If the tool is deprecated, let's find another one. I'll follow your lead on<br>this matter.<br><br>El mié, 20 jul 2022 7:34, Renvoize, Martin <martin.renvoize@ptfs-europe.com><br>escribió:<br><br>> I'm in a similar camp to David, though I have touched it a few times here<br>> and there.. I wasn't aware of a linter, but would take your lead Owen, I<br>> like linters and tidies in general.. having consistent code is clearer code<br>> in my book.<br>><br>> On Tue, 19 Jul 2022, 4:36 pm BFL Catalog, <catalog@bfli.org> wrote:<br>><br>>> What exactly is stylelint? Is this what you get after washing clothes too<br>>> many times? You know the laundry lint builds up so much it cramps your<br>>> style!<br>>><br>>> Wendy Sharkey<br>>> Head of Circulation/ Cataloging and IT<br>>> Bennington Free Library<br>>> 101 Silver Street<br>>> Bennington, VT 05201<br>>> (802) 442-9051<br>>><br>>><br>>> On Tue, Jul 19, 2022 at 4:29 AM Paul Derscheid <<br>>> paul.derscheid@lmscloud.de> wrote:<br>>><br>>>> Hi Owen,<br>>>><br>>>> I recently played around with the SCSS to create a more minimalist<br>>>> version of the bootstrap OPAC for LMSCloud.<br>>>> I used the predefined rules and I think they’re reasonable choices<br>>>> (Although I didn’t cross every rule for sure).<br>>>><br>>>> Looking forward to stylint in Koha which I already use for some projects<br>>>> where I use stylus instead of SCSS. It’s a great tool.<br>>>><br>>>> Kind regards<br>>>><br>>>> Paul<br>>>><br>>>> --<br>>>> LMSCloud GmbH<br>>>> Paul Derscheid - Software Engineer<br>>>> Konrad-Zuse-Platz 8 - D-81829 München<br>>>> m +49 174 2436308<br>>>> e paul.derscheid@lmscloud.de<br>>>> w www.lmscloud.de<br>>>><br>>>> > On 18. Jul 2022, at 16:32, Owen Leonard <oleonard@myacpl.org> wrote:<br>>>> ><br>>>> > Hi all,<br>>>> ><br>>>> > Back when we switched from LESS to SCSS in the OPAC (Bug 20427) I<br>>>> > added a linting configuration, .scss-lint.yml. I've always configured<br>>>> > my editor to automatically lint SCSS using this configuration. I don't<br>>>> > know if anyone else does this too.<br>>>> ><br>>>> > In VS Code I was using scss-lint for this, but it's now deprecated.<br>>>> > They suggest stylelint instead: https://stylelint.io. I'd like to<br>>>> > propose replacing .scss-lint.yml with .stylelintrc.json, transferring<br>>>> > most of the same rules.<br>>>> ><br>>>> > It could be left up to the individual to install the dependencies, or<br>>>> > I could update package.json. One nice thing about stylelint is that it<br>>>> > has a "--fix" feature for some simple rules. This could be build into<br>>>> > our gulp tasks.<br>>>> ><br>>>> > Has anyone else been linting SCSS? If so, does anyone have opinions<br>>>> > about how our current rule set is working?<br>>>> ><br>>>> > -- Owen<br>>>> ><br>>>> > --<br>>>> > Web Developer<br>>>> > Athens County Public Libraries<br>>>> > (740) 737-6006<br>>>> > https://www.myacpl.org<br>>>> > _______________________________________________<br>>>> > Koha-devel mailing list<br>>>> > Koha-devel@lists.koha-community.org<br>>>> > https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel<br>>>> > website : https://www.koha-community.org/<br>>>> > git : https://git.koha-community.org/<br>>>> > bugs : https://bugs.koha-community.org/<br>>>><br>>>> _______________________________________________<br>>>> Koha-devel mailing list<br>>>> Koha-devel@lists.koha-community.org<br>>>> https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel<br>>>> website : https://www.koha-community.org/<br>>>> git : https://git.koha-community.org/<br>>>> bugs : https://bugs.koha-community.org/<br>>>><br>>> _______________________________________________<br>>> Koha-devel mailing list<br>>> Koha-devel@lists.koha-community.org<br>>> https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel<br>>> website : https://www.koha-community.org/<br>>> git : https://git.koha-community.org/<br>>> bugs : https://bugs.koha-community.org/<br>>><br>> _______________________________________________<br>> Koha-devel mailing list<br>> Koha-devel@lists.koha-community.org<br>> https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel<br>> website : https://www.koha-community.org/<br>> git : https://git.koha-community.org/<br>> bugs : https://bugs.koha-community.org/<br>><br>-------------- next part --------------<br>An HTML attachment was scrubbed...<br>URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20220721/107fcede/attachment-0001.htm><br><br>------------------------------<br><br>Message: 2<br>Date: Thu, 21 Jul 2022 07:53:59 -0400<br>From: Owen Leonard <oleonard@myacpl.org><br>To: Koha Devel <koha-devel@lists.koha-community.org><br>Subject: Re: [Koha-devel] Updating SCSS lint process to use stylelint<br>Message-ID:<br> <CAO4qe2Nd1xhd4MtxHgBK_vV058VwOukmMmCvkom=HLcT9ek06w@mail.gmail.com><br>Content-Type: text/plain; charset="UTF-8"<br><br>> I'd like to propose replacing .scss-lint.yml with .stylelintrc.json, transferring<br>> most of the same rules.<br><br>Thanks for the feedback everyone. I'll work on a patch for the lint<br>config and also one to add stylelint to the CSS build workflow.<br><br> -- Owen<br><br><br>------------------------------<br><br>Message: 3<br>Date: Thu, 21 Jul 2022 16:25:19 +0200<br>From: Victor Grousset/tuxayo <victor@tuxayo.net><br>To: Paul Poulain <paul.poulain@biblibre.com>,<br> koha-devel@lists.koha-community.org<br>Subject: Re: [Koha-devel] Long-term support version of Koha (bug<br> 31008)<br>Message-ID: <6cb05409-d5e3-a1de-1765-686d04d6a843@tuxayo.net><br>Content-Type: text/plain; charset=UTF-8; format=flowed<br><br>Hi :)<br><br>On 22-06-22 09:47, Paul Poulain wrote:<br>> Good thing to have a LTS, my main question is about the ecosystem around <br>> Koha. For example, how to manage Koha LTS regarding <br>> Debian/Ubuntu/<br><br>We already drop and gain support support for Debian/Ubuntu versions <br>during the lifetime of Koha releases.<br><br>> Elastic Search/MariaDB... upgrades ? <br><br>Same, we are getting patches for ElasticSearch 7 and OpenSearch support <br>backported to oldoldstable. And in the past, I recall we dropped ES 5 <br>support to fix a bug with ES 6.<br><br>> How can we be sure <br>> that, in 2 years, Koha LTS will become "unmaintainable" because it <br>> requires a Perl library that can't be upgraded and the underlying tool <br>> (OS, search engine...) isn't maintained anymore in the compatible version ?<br><br>So it should be ok. Unless there are scenarios not covered by what we <br>already do?<br><br>Cheers,<br><br>-- <br>Victor Grousset/tuxayo<br><br><br>------------------------------<br><br>Subject: Digest Footer<br><br>_______________________________________________<br>Koha-devel mailing list<br>Koha-devel@lists.koha-community.org<br>https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel<br>website : https://www.koha-community.org/<br>git : https://git.koha-community.org/<br>bugs : https://bugs.koha-community.org/<br><br><br>------------------------------<br><br>End of Koha-devel Digest, Vol 200, Issue 22<br>*******************************************<br></div><br><br>NOTE: You are receiving this mail because, the Requester/Technician wanted you to get notified on this request creation.<br></body></html>