All three of us attended. Other than administrivia we talked about formally documenting our supported platforms, and we intend to start a discussion on the mailing list about this soon. This is also a topic for the upcoming Perl Toolchain Summit.
Please find my learning experience in the post below:
https://theweeklychallenge.org/blog/terraform-docker
FOSDEM 2025 is just around the corner, and you know what that means—great talks, amazing people, and of course… fantastic food! 🥂
The Perl and Raku Foundation (TPRF) is once again bringing the community together for a special dinner during the FOSDEM weekend. If you’re an active member of the Perl and Raku ecosystem, this is your chance to relax, connect, and celebrate with fellow developers, contributors, and enthusiasts.
📅 When? Saturday Evening, during FOSDEM weekend
📍 Where? A great venue in Brussels (details will be shared with registered attendees)
💬 Who? Active community members, contributors, and Perl/Raku enthusiasts
We are very happy to announce that OTOBO supports the German Perl Workshop!
Die Rother OSS GmbH ist Source Code Owner und Maintainer der Service Management-Plattform OTOBO.
Gemeinsam mit der Community entwickeln wir OTOBO kontinuierlich weiter und sorgen dafür, dass das Tool zu 100 % Open Source bleibt.
Unsere Kunden unterstützen wir mit partnerschaftlicher Beratung, Training, Entwicklung, Support und Managed Services.
Back to the full roster, albeit with Philippe attending from on the road.
We mainly went over the list of PPCs, with an eye toward the fact that this release cycle is coming to a close.
As an aside regarding PPC0027, we reiterated that we would like use feature ':all' to go away if possible. It was never a good idea anyway, but has become untenable with the introduction of feature flags like indirect and bareword_filehandles, which we expect to have many more of in the future. Since their purpose is to be disabled rather than enabled by default, a simple toggling of all features (on or off) is a nonsensical request.
There are several competing philosophies for wrapping external C libraries. One is that the XS module should hide all the details of the library and provide a clean “Perlish interface”. The opposite extreme is that the external C functions should be exposed to Perl using an extremely minimal XS layer, or the Foreign Function Interface (FFI) and all the logic for working with the library should be written in Perl.
I advocate something in the middle. I think that a good interface should expose as much of the low-level as possible (to make the most usage of that library possible by other Perl modules) while “padding the sharp edges” so that it is difficult for Perl-side usage to crash the program. Higher level features can be provided in addition to the low level API via XS, Perl modules, or both.
Adding a SECURITY or SECURITY.md file to your Perl distributions will let people know:
The contact point is very important for modules that have been around for a long time and have had several authors over the years. When there is a long list of maintainers, it's not clear who to contact.
You don't want people reporting security vulnerabilities in public on the RT or GitHub issues for your project, nor do you want a post on IRC, Reddit or social media about it.
If your software is on GitHub, you can set up private vulnerability reporting. GitLab has a similar system.
Otherwise, a single email address is acceptable. An alias that forwards to all of the maintainers or at the very least, a single maintainer who has agreed to that role will work.
All three of us were present:
keyword_any and keyword_all. These can now be merged.I know, thinking about where to put what in a code file sounds lame to most artisan hero's that fly by intuition, but I find it actually helpful. Here my article about it on dev.to and you can tell its written with Perl in mind. I just wanted to publish outside to reach more people and maybe even bring some in.
Having reached a certain level of proficiency with Mojolicious and Vue.js, I made the decision to dedicate some of my free time every week to develop "cool and somewhat useful" (according to some) open-source web apps in Perl.
The goal is to practice and learn, and maybe also help make Perl a bit more popular.
My first such project is Gandalf Links, a link-aggregator website (inspired by pinboard.in) that's pretty much complete and can be installed and run very easily with Docker.
At the front page's footer you can find a link to the source code. A full list of current and future features can be found here.
If interested to contribute in ANY way (ideas, know-how, coding) please do get in touch with me via e-mail, through the form that's on gandalf.gr, or maybe use the project's issue tracker. I've done almost all I can on this project, now I'm looking for other people's expertise.
I'd also be looking for ideas on what other self-hosted web app to work on next (with you if you're interested).
Regards,
- Gandalf (first cousin of the copyrighted one)
Simplest is if you go to my homepage and follow the links to my Debian and Perl pages.
Note: The Debian and Mojolicious updates are minor, but a lot of changes are in the Perl wiki.
Only Philippe and Aristotle this time.
We spent most of our time on the PPC process, and started by merging Dave Cross’s PR for a static PPC web site. Many thanks to Dave once again.
We discussed revising the PPC process, and started by picking more specific names for the various statuses of a PPC, which we’ll soon apply to the existing PPCs.
Learning GitHub Actions for Map::Tube.
Please checkout the post for more information.
https://theweeklychallenge.org/blog/github-actions
We are delighted to announce the new release, which includes 57 significant bug fixes compared to the previous 2.1.8 version. This update addresses a range of important issues and enhances the overall stability and performance.
More details at https://blog.foswiki.org/Blog/Foswiki219IsReleased
Next PCC: July 3-4, 2025 in Austin, Texas USA
See entire the post to learn about our future plans, in perpetuity.
The very first Perl Community Conference was a tremendous success thanks to everyone of you authors and speakers. Many thanks to PCC Co-Organizer Will "The Chill" Braswell, our friends at the Diogenes Hackerspace (in Austin, Texas), and all the participants both online and in person! We'll be following up soon about posting the videos. The next stage will be editing and publishing Issue #2 of the Science Perl Journal. The schedule from the Winter'24 PCC should be a clue about some of its contents. We have discussed offering a "Letters to the Editor" section to address feedback from friends and foes alike. More on this will be announced in future posts.
Future Plans in Perpetuity
Let me start off by asking the folk on this platform one question. Imagine a scenario that you had lost something important with multiple potential negative consequences. For instance losing a bunch of keys including your car keys, your house keys, your changing room locker keys and a USB stick. What would be the greatest cause for alarm? I suspect that while there may be many possible answers aligned with each individual’s life priorities, the real men in this group know that the most feared is the reaction following the revelation to the wife. For while any calamitous occurrence may be approached objectively, with rationality, reflection and hopefully recovery, this particularly troublesome phase involves heightened emotions, reactivating Mrs Saif’s indelible memories of my many past failings. Objectivity, while desirable in principle, has to deal with such a tainted history.
A quick introduction to Docker Volume. Please check out the post for more information. https://theweeklychallenge.org/blog/docker-volume
Do you want LPW to happen again in 2025? Then you need to make it happen. You need to start thinking about this now. After Lee's closing talk, which detailed how organisation of the 2024 workshop worked and effectively put out a call for organisers for the future, a small number of attendees hinted they would be able to help out in one way or another. For that we are grateful.
However there is no core organising team yet for 2025. Someone, ideally two or three people, need to step up and explicitly say "we are going to organise LPW 2025". If you need help around any of this then we (the 2024 organisers) can guide you. The TPRF have also said they would like to explore how to support LPW 2025 and welcome potential organisers to join the monthly community meeting to discuss this.
Failing that LPW will be going on an indefinite hiatus again.
Happy birthday Perl!
The Perl Community Conference is a hybrid in-person-and-online event held on December 18th from 10:30a-4:00p CST, Perl's 37th birthday, featuring talks from the world's top Perl programmers and community members. Topics include artificial intelligence, bioinformatics, web applications, chemometrics, genetics, data science, high performance computing, ethics, and much more!
blogs.perl.org is a common blogging platform for the Perl community. Written in Perl with a graphic design donated by Six Apart, Ltd.
