Too many people are confusing the two. Whenever lemmy.ml or its devs do something stupid, people go “Lemmy is getting worse and worse,” or “I’m leaving Lemmy,” or worse, “I’m leaving for Beehaw.”
If you’re using Beehaw, then you’re using Lemmy. Lemmy is the software these instances run on. If you don’t like lemmy.ml, join another instances that have rules that match your philosophy. Some instance hosts authoritarian or fascist shit? Turn to another Lemmy instance. Lemmy.ml is not even the biggest instance. People who just joined and are unfamiliar with the platform will just think the entire Lemmyverse is run by autocratic admins if we don’t get our terminology right.
Just a remark: “Whenever lemmy.ml or its devs do something stupid” admins or lemmy.ml ARE the devs of lemmy software. Moreover, they developed lemmy because they where thrown out of reddit for did something “stupid”.
I just had a look at Lemmy’s GitHub. Of the web interface alone, the second biggest contributor only joined two weeks ago. And there are many others. Those are new developers. So in essence: lemmy.ml admins are some of the software developers and are actually now in the minority, unless I missed something very obvious.
This might be a stupid question, so forgive me. Who controls what happens to the actual software? Like, if a hundred great ideas get added to the GitHub, who controls which ones make it into the next version of Lemmy?
Lemmy.ml devs own the repo, it’s just licensed as open source software under the GNU AFFERO GENERAL PUBLIC LICENSE. You can read the license in the repo files. So you can fork off it and run your own instance. If you go to GitHub.com/LemmyNet you see the two people who are members of the project, with the accounts, both have Fidel Castro avatars.
Personally I think having a bunch of socialists run the software, is by definition the best way to have it avoid corporate interests.
If the main project start doing something stupid, other devs can just fork the project as a new lemmy project with a new kind of government of how codes are merged into the project.