KerrickStaley
Joined 14 years ago
Joined 14 years ago
The primary reason for putting this process in place was to allow more transparency. There was a sense that the DseWiki incident should have been disclosed, before outside researchers had to disclose it for us.
There was no meta gaming about regulation that I was aware of. I would personally be excited if there were regulation mandating this disclosure process, which allows anyone at the company to raise an issue and shepherd it through the reporting process.
So in practice the oxygen level can never drift meaningfully far from the atmospheric pressure, whereas carbon dioxide easily can because the pressures involved are so low.
[1] https://fund-docs.vanguard.com/F0958.pdf
[2] https://www.msci.com/indexes/documents/methodology/2_MSCI_25...
[3] https://www.msci.com/documents/10199/6bafd9e3-0474-f03b-16bd...
[4] https://investor.vanguard.com/investment-products/etfs/profi...
[5] https://www.invesco.com/qqq-etf/en/about.html
The Vibe Kanban developers unfortunately decided that they didn't see a path to profitability and have stopped investing in the project. It's open source and so you can run it locally / fork it, but it has stopped improving and there are still annoying bugs that need to be fixed (and I don't have time to maintain it personally). This makes me sad because I would be willing to pay for Vibe Kanban, but I didn't need the features their paid plan offered (in retrospect maybe I should have paid anyway).
I'll give Kanbots a go :) I'd recommend liberally copying features from Vibe Kanban. In particular the remote support and "Open in VS Code" button (which in my case opens a local VSCode client pointing to a remote VSCode server) are critical for me.
[1] https://github.com/UKGovernmentBEIS/inspect_ai/pull/3145