[sorry_i_lisp]

Finally someone is speaking truth to power. These registered non-profits that release their code for free and their leisure time for support need to be knocked down a notch.

We all know they are evil. But you know the most evil thing? That code that was previously released under a free license? Still sneakily on display in the git history like the crown jewels in the Tower of London. Except of armed guard defending the code that wants to be free once more it's hidden behind arcane git commands. Name me a single person that knows how to navigate the git history. I'm waiting. Spoiler alert: I asked Claude and they don't exist.

[tclancy]

Sure, but this person is a doctor (or similar) who took time to learn to code this form up to better serve their patients. They are most likely blessedly ignorant of software licenses and version control.

[KirinDave]

As I read it the op said, "I don't like how they changed this license, this is a bad direction and I didn't think there was adequate transparency."

And your rebuttal is, "Well you can always recover the code from the git history?"

I mean, this is true, but do you think this really addresses the spirit of the post's complaint? Does mentioning they're a non-profit change anything about the complaint?

The leadership and future of a software project is an important component in its use professionally. If someone believes that the project's leadership is acting in an unfair or unpredictable way then it's rational and prudent for them to first express displeasure, then disassociate with the project if they continue this course. But you've decided to write a post that suggests the poster is being irrational, unfair, and that they want the project to fail when clearly they don't.

If you'd like to critique the post's points, I suggest you do so rather than straw manning and well-poisoning. This post may look good to friends of the project, but to me as someone with only a passing familiarity with what's going on? It looks awful.

[notpushkin]

1. Open LICENSE on GitHub

2. Click on the commit ID

3. You’ll see something like “1 parent: fdsfgsd” – click through to that commit

4. Browse

I mean, it’s a shitty move for sure, but eh.

[sritchie]

(Parent was being sarcastic)

[notpushkin]

Huh! I’m getting rusty.

[sudodevnull]

Yes, much power! Datastar is the worst, how dare they?