Development report for 3 November 2025:
Done since last time
GLF #28: Make gallery images reorderable
GLF #4: Upload gallery images.
Next up
GLS #3: Add new users to users table.
GLF #7 Add project creation link on library front page.
Near-term forecast
I aim to move on to working on V4 tech demos after completing the above.
It may be several months before I return to any module library issues after these. If there are other module library issues you want addressed sooner, please consider volunteering to help with them or with the issues I have have planned for work.
Issues may be found in the issue trackers (GLF, GLS, UMS). Most of them are underdescribed at the moment, so the first step would be asking for a better description. Especially for the frontend issues, we could use pointers to examples of good design.
What skills are needed to help with library development and support?
e.g. is the library a web site hosted on AWS and developed in Java using Spring Boot? I’m an experienced software engineer but there is only a limited list of programming languages that I will work with.
As of yesterday, I’ve merged together the three repos for the library into one. The three services (UMS, GLS, GLF) run on our server hosted at Linode. The UMS and GLS are written in Rust using the axum framework for handling HTTP requests. The GLF is JavaScript and Svelte, with a small amount of Rust.
I haven’t gotten as far as moving GitHub issues from the three old repos to the new one. That will happen sometime in the next few days. All issues from the three old repos are moved to the new combined repo now.
The open issues are varied. Some involve adjustments to the project database and queries on it; some involve frontend modifications; some involve design and making mock-ups. The level of difficulty, amount of work, and urgency aren’t uniform. There’s likely something to suit anyone keen to help.