@smallcircles @abekonge
At which point the wood-craving masses are free to start chopping wood for themselves.
If you set clear expectations of a communal software project then you are remiss if you don't. You effectively promised a form of shared governance, and reneged on that promise after people already invested time and effort.
But if you did not - and especially if you make it clear it's a personal hobby - then they can fork if they want, but they have little cause for complaints.
I think nobody (except my daugthers) is entitled to my work.
Not even managers at work can force me to do something I don't want to do, so much that "It cannot be done" and "I don't know how to do it" and "give me a five years and a team of five very skilled engineers, and I'll do it" are well known show-stopper at work.
When I share my high-skilled work, I set up whatever license I see fit (sometime debating with #OSI board gatekeepers, cause I like #copylefts they hate) and usually set an explicit POLITICS.txt to explicitly explain the socio-technical goals of the project.
Usually it does NOT cover governance because forks are welcome (within the rules of the license, obviously)
I started adding a POLITICS.txt to my projects 5 years ago, after writing my essay "What is Informatics?": https://encrypted.tesio.it/2019/06/03/what-is-informatics.html#be-political
Writing the POLITICS.txt for a project is always pretty difficult: it means to be explicit with your hopes and ambitions while finding the right words to express them is hard and often lead other developers to mock you even if they use and appreciate the code you wrote.
You can see a recent example here: https://code.tesio.it/p/self-hosting/doh.cgi/file?name=POLITICS.txt&ci=tip
@Shamar @jannem @abekonge
Oh, I was not aware of an existing practice around POLITICS.txt .. is there one, and a resource to share?
I just thought of something similar at: https://social.coop/@smallcircles/113508224930993093