Is the tool status page here: Tools Status Board - DMS still maintained? Or is it better to just make a post asking if something is up?
I know there have been a lot of posts about the lasers recently but I was trying to get an idea of which ones are currently working.
And is the vinyl cutter still non-operational? I didn’t realize it had even been down tbh
It is not, despite some efforts…
This is probably the better option.
Cool, will do. I just didn’t want to be seen as ‘pestering’ or whatnot (I seem to recall some complaints about people constantly asking if something is fixed yet or asking for updates), but I don’t want to make the trek up if whatever I’m hoping to use is down. Sometimes it’s hard to keep track of all the various threads on OOS, IS, in progress, etc.
Now to find out if the fusion works yet 
Anyone can update the status of a tool using the “update this” link. We just got out of the habit of doing it.
I quickly wrote that tool as a “for now” placeholder many years ago (while we were still on Ladybird). At the time there was discussion of a grand scheme system (which still has never come to fruition). The tool status script was a placeholder - one which had been holding that place for a long time…
Lisa Selk maintained the tool list for a long time, but I don’t know who (if anyone) still has access.
I’m available to work with anyone who’d like to take over updating the list of tools, etc. I have no clue which server holds the code, nor how to access it. I believe I still have a copy of the code and the original tool list (which has been updated many times since the original).
It’s a dead-simple piece of code, written in Perl, with no odd permissions/dependencies. It uses a flat file setup for the “Database”: one file has a list of tools and a 2nd file gets updated with the tool number, time stamp, and status.
Tools are assumed to be running unless updated. Updates are just appended to the end of the status file (and thus should have the front of the file pruned off every once in a while but likely hasn’t). Without pruning, one could theoretically run some mean time between failure analysis, but that would only be as good as as the data.
Only a fixed set of status types are allowed (with bounds checking) to prevent/minimize shenanigans that free form text fields might instigate.