What it boils down to is having assigned yourself an ownership of the task way forward, resulting in a figurative cookie being licked. Of course, now nobody wants to touch this task/cookie with a 10 m foot pole, because any more collaboration from other parties is essentially obstructed.
I am guilty of trapping myself in a few such situations: job, making and stopping on 90% for a new logo for #Mbin, etc. I wanna learn from these mistakes and give as less cues of ownership as possible. There really isn't much to do to be excellent to each other, unlike to be some hotshot contributor. But as sayings go: the genius is in simple, and one should find beauty in simple.
I already was practicing "non-licking" with licenses on my works: mark all that I want others to move on without hesitation public domain. For logos, I still prefer CC-BY, but I might review some of my reservations (e.g. in lieu of trademark) one day.
Documentation? Absolutely CC0! Why would I need any provenance aside from git logs for some impartial or technical writing?
Overall, just avoiding CC-BY-SA for reusable assets. Saying NO to NoDerivatives, NonCommercial and other shenanigans - they are simply distastefull licenses.
Add comment