state of monday library

[stevensting]

Hi,

thank you for your work. We are using your library in https://codeberg.org/Klasse-Methode/lauti up until now relatively sporadically. But now we want to localize all dates and times with it. Therefore I wanted to know about the state of the lib:

will you accept PRs for such things:

• adding new languages, e.g. someone is in the process of translating LAUTI into Arabic
• adding some more default localizations, e.g. DefaultFormatEnUSMonthDay = "Jan 02"
• functionality regarding start of the week
• will you do go package releases for new changes?

Thank you for your feedback!

[goodsign]

Hi @stevensting,

Thanks for using the library, and cool to see it being used in Lauti!

To be upfront: I'm not actively maintaining / developing this on any regular schedule, but I do usually find time to review and accept straightforward PRs. As well as once-in-a-while releases as needed.

When I started this thing 13 (Thirteen! Oh my god) years ago, I wrote in the README:

Monday is not an alternative to standard time package. It is a temporary solution to use while the internationalization features are not ready.

So this is a bit of a classic situation of "nothing being more permanent than a temporary thing" 😆

There was absolutely never a plan that this thing might live so long, while being a temporary quality of life package 😆 Since then a lot changed and I don't have a lot of time to invest into this anymore — but at the same time, I certainly plan to keep this thing working and doing what it already does to maintain backward compatibility and such.

So in terms of what PRs I'd be happy to merge:

• Adding new resource files like new languages that follow the existing API is totally fine
• Maintenance / routine updates, to be up-to-date with the ecosystem

For more significant API changes or any new functionality, I'd generally recommend building that as a wrapper around the library rather than expanding the core package API itself. I wouldn't be able to find resources right now to do active development of new features for the library or accept PRs that would require significant resource investment into reviewing or which might have bug introducing potential.