@specter lol, good target audience. And yeah - this is why I think it's good to have a healthy variety of licenses in open source... for people to choose the one that applies to them the best.
Of course now I'm stepping on the toes of people that have experienced "license incompatibility" (a.k.a. needing to release a program that combines several different works for which the licenses have contradictory terms) for whom this idea seems like an absolute atrocity, and I can't blame them.
Copyright is silly
The vision: A git CLI utility for writing conventional commits used to derive semantically versioned tags, that plays nicely with monorepos.
put your code in the public domain! copyright is silly
which was a really effective way to radicalize me towards unlicense.org:
"How many precious hours of your life have you spent deliberating how to license your software or worrying about licensing compatibility with other software? You will never get those hours back, but here's your chance to start cutting your losses. Life's too short, let's get back to coding."
if not an odd way to discover this
spent wayyy too long trying to figure out how/if to add my name to an MIT copyrighted file to which I added Windows support
then I realized EVERY OTHER file in that repo is under unlicense.org, like specifically as a comment header on each
New essay: Seven theses on the Fediverse and the becoming of FLOSS
Recently, @rra and I have been working on an essay highlighting questions about the #Fediverse and how these are getting entangled with #FLOSS practices. From software production to structure and governance within alternative social media, online communities and politics.
The text follows a multi theses model, to map the different things we've been looking at and publish the current state of our research.
It is the closing chapter of a new publication from INC/Transmediale (https://networkcultures.org/blog/publication/the-eternal-network)
Feedback welcome. We're planning to publish an online version with more references!
a personally historic event
Feels good! 😊
I'm gonna try it and it is gonna depend on Node but only because that's the fastest way for me to make a cross-OS bin rn but it's gonna be generic to git still probably just wrap `git commit` and also add `git release` for the tagging
it should be generic to just git I think and have built in support for versioning the repo or folders within. Enforced conventional commits + a semver tool that tags the repo up like <folder>@<version>
other tools can grab the version info from git tags and do things like update the package.json, tag a docker image or publish a new version to a registry
currently I only see tools that are node/lerna specific and this seems to be all able to be baked into vanilla git