What have we done in the last month or so?

Well, it has been another busy few weeks in LibrePlan land — and once again, progress is happening in all directions at once.

Expanding Help Texts: 4 → 18 Languages (!)

The biggest milestone — and one that is almost complete — is the expansion of our help texts from 4 languages to 18 (!).

Yes, you read that right.

This resulted in the addition of 387 new files to the repository. A significant increase, and a meaningful step toward making LibrePlan accessible to a much broader audience.

A large part of this effort has been powered by Claude AI. And while the results are impressive, the process itself has been… let’s say… paced. Due to the usage limits on my modest Anthropic account, I often find myself waiting up to four hours before continuing the next batch of translations.

Progress, however, is progress.

The updated help texts will also include a gentle call for donations. Because let’s be honest: maintaining and improving a project like LibrePlan takes a considerable amount of time and energy.

If all goes well, I expect to complete this entire help text overhaul later this week.

GitLab → Forgejo Migration (and Beyond)

In parallel, I’ve spent quite some time on a GitLab to Forgejo migration for a client.

As often happens, one thing led to another — and I took the opportunity to migrate my own internal repositories using the same approach. Always good to eat your own dog food.

The added benefit is that I now have local runners available for builds, which opens the door to improving and streamlining the build process. This is something that has been on the wishlist for quite some time.

SBOM Support on the Horizon

Another small but important improvement that is coming up is the generation of a Software Bill of Materials (SBOM).

With increasing expectations around software transparency and security, this is no longer a “nice to have” but quickly becoming a requirement. Integrating SBOM generation into the build process will help LibrePlan stay aligned with modern standards.

A Nexus Security Incident

Of course, it wouldn’t be a proper month without a bit of unexpected excitement.

There was a fairly serious security incident in Nexus, which requires a rather time-consuming migration of the entire Nexus database to fully resolve.

Fortunately, there is also a temporary mitigation available. That allows me to stay focused on the current development work for now, instead of dropping everything for an urgent migration.

Still, this is something that will need proper attention soon.

Team Update

My trusted teammate Santiago is currently in the middle of a house move — never the most relaxing of activities.

Even so, he already managed to fix a number of bugs. One particularly welcome improvement: we can now run the full test suite again during builds.

That alone is a big step forward in terms of reliability.

What’s Next?

Over the coming days, my focus will be on:

  • Finishing the help text expansion
  • Preparing a container image
  • Publishing a short announcement around these updates

As always, there is more to do than time allows — but we are steadily moving forward.

Stay tuned.

This entry was posted in Uncategorized. Bookmark the permalink.