<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"> <head> <meta http-equiv="Content-Type" content="text/html; charset=Windows-1252"> <meta name="Generator" content="Microsoft Word 15 (filtered medium)"> <style></style> </head> <body lang="en-BE" link="#0563C1" vlink="#954F72" style="word-wrap:break-word"> <div class="WordSection1"> Hello all,<o:p></o:p> <o:p> </o:p> Best wishes for all of you in 2023. I see we have this year our 10 year anniversary of publishing open source code for libraries together. Doing all our ELAG and SWIB meeting we managed to publish 131 repositories at <a href="https://github.com/LibreCat">https://github.com/LibreCat</a>. There are few library projects that can repeat that feat. I hope we will meet each other soon again in live conferences. I’ve very much enjoyed SWIB and ELAG the last 2 years, but it is still much better with a discussion and a beer and some unhealthy food.<o:p></o:p> <o:p> </o:p> I’ve talked with the group in Bielefeld and Ghent and we would like to have a fresh start of the year by making some things clearer on the website and keep it focused on the cooperation we had over the last year: enjoying to share code and keeping away from selling products and marketing the tools we provided as-is.<o:p></o:p> <o:p> </o:p> The first plan is to make a slimmed down version of the current website <a href="https://librecat.org">https://librecat.org</a> and focus more on the github project <a href="https://github.com/LibreCat">https://github.com/LibreCat</a> we already have. This would make it much easier to maintain this website and focus on the tooling we all have a shared interest in (mainly Catmandu I assume).<o:p></o:p> <o:p> </o:p> Here is a proposal for a smaller website: <a href="https://github.com/LibreCat/librecat.github.io/tree/pr/smaller">https://github.com/LibreCat/librecat.github.io/tree/pr/smaller</a> <o:p></o:p> <o:p> </o:p> It is just the old homepage without the LibreCat catalog, and listing of dozens of modules (of which many are quite old).<o:p></o:p> <o:p> </o:p> TODO: could some of you check if this new website is okay for you?<o:p></o:p> <o:p> </o:p> About all these Perl modules ..I really see a wide variety of activity level:<o:p></o:p> <o:p> </o:p> <ul style="margin-top:0cm" type="disc"> <li style="color:black;margin-top:0cm;margin-bottom:0cm;mso-list:l1 level1 lfo1;vertical-align:baseline"> 17 modules have had a release since 2020<o:p></o:p></li><li style="color:black;margin-top:0cm;margin-bottom:0cm;mso-list:l1 level1 lfo1;vertical-align:baseline"> More than 70 modules have not been touched in the last 3 years<o:p></o:p></li><li style="color:black;margin-top:0cm;margin-bottom:0cm;mso-list:l1 level1 lfo1;vertical-align:baseline"> 9 core developers for all these tools<o:p></o:p></li></ul> <o:p> </o:p> I think we need to provide some hints maybe in those modules which are deprecated or even not working anymore. To give an idea which of those can better be moved into the CPAN archive (backpan that is?).<o:p></o:p> <o:p> </o:p> Also for Catmandu itself we were contemplating to focus more on the command line capabilities of the code than in the Perl API (this latter one is hard to maintain). Catmandu is moving in our institute more into this command line processing direction. For library specific modules Catmandu is and will be very effective. But maintaining Perl APIs to talk to Solr, Mongo, Elastic, Couch etc etc is very time consuming and probably other tools exist that can better be used for these not-library specific tasks. What are your thoughts about this:<o:p></o:p> <o:p> </o:p> <ul style="margin-top:0cm" type="disc"> <li style="color:black;margin-top:0cm;margin-bottom:0cm;mso-list:l0 level1 lfo2;vertical-align:baseline"> Do you use the command line interface?<o:p></o:p></li><li style="color:black;margin-top:0cm;margin-bottom:0cm;mso-list:l0 level1 lfo2;vertical-align:baseline"> Do you use the Catmandu.pm Perl libraries inside your code? Do you write Perl code that requires Catmandu?<o:p></o:p></li><li style="color:black;margin-top:0cm;margin-bottom:0cm;mso-list:l0 level1 lfo2;vertical-align:baseline"> What are the main Catmandu extension modules you use (Catmandu::MARC, Catmandu::DBI, Catmandu::RDF, …)<o:p></o:p></li><li style="color:black;margin-top:0cm;margin-bottom:0cm;mso-list:l0 level1 lfo2;vertical-align:baseline"> Do you use Catmandu to store or query data in databases or search engines?<o:p></o:p></li></ul> <o:p> </o:p> Feedback is very welcome!<o:p></o:p> <o:p> </o:p> Hopefully, we meet each other again soon. <o:p></o:p> <o:p> </o:p> Patrick<o:p></o:p> <o:p> </o:p> </div> </body> </html>