I think we need higher-level documentation describing all of the software that we are working on (including all Glazy repositories), and maybe even a long-term vision of what we’d like to accomplish. To kick-start the discussion (please add to this!):
We need a place where we can discuss and share knowledge. Not Facebook groups. Our data needs to be searchable, archivable, accessible. I have tried numerous open-source alternatives, including Flarum, but Discourse still seems to be the best. If we go with Discourse, we need someone to take over moderation, updates to the system, backups, etc. of the server. And we need people to actually use Discourse, so that when people log in it feels like a living, inhabited system. NEEDS: Moderator/Administrator of Discourse.
We’ve had a number of discussions in this group about software standards. For example, standardizing EXACTLY how analyses are calculated using the same molar masses. (See Glaze Calculation in Software) Ideally if multiple people are writing different calculation tools, we can all use the same underlying core library.
The two core libraries underlying all the calculation are here:
[Added by Pieter] Lipgloss is written in Python, and currently only exists as a desktop app. I’ve tried to separate the computational core from the rest of the app; this can be found here:
I still intend to develop the desktop version of Lipgloss, since it’s likely that the version implemented on Glazy won’t be as customizable.
Immediate needs for Software Development
There are immediate needs for help with these libraries.
The code should be FULLY tested. Running the tests should show that the calculations are correct and verifiable.
There should be developer documentation as well as comments throughout the code explaining EXACTLY how glaze calculation works. Anyone should be able to read this documentation and understand glaze calculation.
We need to fully implement blends:
Once the above issues have been addressed, we will urgently need a pure Typescript implementation of ceramicscalc. See this issue: https://github.com/derekphilipau/ceramicscalc-js/issues/3