Anything where the liability clause of the MIT license is meaningful beyond protection against litigation trolls, because if you need it, it means that you simply are a liability.
Exceptions to that:
Clearly marked experimental / immature software
Repos with good process or at the very least many eyes, independent audits help too
Novel primitives, but those should generally fall under (1)
For example, I like what @m0wer did with #1546237 the other day. I'm not nearly done with analyzing it (so this isn't a recommendation, yet) but what is good about it is the supporting framework: it is extensive and thoughtful and there is a lot of process around provisioning there. If half the ecosystem would do half the effort of what was done there, my days would be a lot less frustrating.
I think we need to find a better way to do collaborations
I really, really should go check out Block's Buzz thingy, because that feels like it provides a way to do on-topic collaboration without (premature) publication.
FOSS is important to preserve sovereignty.
It's important to make/keep sovereignty attainable, agreed.
Anything where the liability clause of the MIT license is meaningful beyond protection against litigation trolls, because if you need it, it means that you simply are a liability.
Exceptions to that:
For example, I like what @m0wer did with #1546237 the other day. I'm not nearly done with analyzing it (so this isn't a recommendation, yet) but what is good about it is the supporting framework: it is extensive and thoughtful and there is a lot of process around provisioning there. If half the ecosystem would do half the effort of what was done there, my days would be a lot less frustrating.
I really, really should go check out Block's Buzz thingy, because that feels like it provides a way to do on-topic collaboration without (premature) publication.
It's important to make/keep sovereignty attainable, agreed.