Fun fact: when I was a freshman in college I thought my most useful contribution to free software (I was not a programmer at the time) would be to make a webcomic about two people mod'ing their house and it turning it into what we would now call a "hackerspace" (that term didn't exist then) where the whole house was slowly automated (IoT didn't exist then either). I never finished it or even got what we would call "far" at all.
But you can still find it... not that it's good...
The one thing I'm proud of about it was the level of experimentation I was doing at the time in each page. It did influence a lot of my future artwork and experiments.
Part of the reason I never finished it was "imposter syndrome" though I didn't know the term at the time. I was afraid I didn't understand the tech I was describing enough. The upside is I started learning more...
The problem with the NC is that it's counter-productive and does not achieve what artists want it to achieve.
It does nothing to stop people who do not care about licensing from "stealing" your work.
OTOH it stops people who feel strongly about licensing from using your work, making derivatives, making it popular.
It's terribly vague -- what does it even mean? If I use this CC By-NC picture in a presentation funded by a grant, is that "commercial"?
CC By-SA is way better.
@rysiek @Shamar Nobody agrees on what "noncommercial" means, and you will either block uses you want or be surprised to hear that others consider uses you feel should be prohibited they believe are allowed. Worse yet: noncommercial licenses don't compose. What happens when 100 entities later contribute to a noncommercial license, if they hope to enforce it as a revenue stream?
"noncommercial" licenses always fail.
I'm gearing up to release what I've written thus far on the web under a CC license, and I'm going with BY-SA-NC because I don't expect people to write fanfic based on my setting or adapt my work for other media, and if they do I sure as hell don't want them making money off it without coming to me first and offering me a piece of the action.
1. "I can't imagine people doing anything with X" is something I've seen in debates about Open Data (government officials saying "who would do anything with X kind of data?"), copyright, art, etc. Each time it turned out that indeed there would be people doing something.
This exists, because everyone from Linux kernel devs, through webserver devs, through OSM devs, up to OSM editors released stuff on open licenses. Nobody had this outcome in mind, and yet here we are.
I feel it makes sense to not limit the potential, not limit the possibilities, with an NC license.
This is something I have to reflect upon.
I'm under the impression that commercial exploitation destroys anything good that comes from hacking.
At times, I'd like a license stricter then AGPL for my code, just to protect it from "the market".
And I refuse to accept that being commercial is the only way to be useful to people. That's the ethics of Capitalism, and I don't like it.
CC's interpretation of NC is purposefully vague to be flexible: https://wiki.creativecommons.org/wiki/NonCommercial_interpretation
In my opinion, that doesn't make it very useful; NC is mostly a barrier to combining with other FOSS licenses, especially the big copyleft licenses.
In some cases, artists and musicians feel more comfortable with CC licensing... 1/2
But, back to your example - I think a reasonable interpretation would allow use of those emojis as "not primarily intended for or directed towards commercial advantage or monetary compensation.", which is the CC interpretation (though not actual legal advice, precedent, or ruling). 2/2
@ebel @rysiek @cwebber @Shamar @starbreaker interesting... attribution can be difficult for artistic works too, e.g. combining CC graphics from multiple sources for print works or merchandise (where do you put attribution on a one inch button?).
OSM should probably also ask the contributor to license any of their original work under ODbL when they submit; dual licenses would probably make life easier in the long run, but also new versions of CC licenses can address this compatibility directly.
@diggity @rysiek @cwebber @Shamar @starbreaker
"Where do you put the attribution?" Sec 3(a) of the CC-BY-SA licence covers this.
Copyright holder gets to define a "reasonable manner" (3.a.1.i)
#OSM has a form letter ( https://drive.google.com/file/d/0B3PN5zfbzThqeTdWR1l3SzJVcTg/view ) which asks the holder to agree that a mention on the osm.org/copyright page suffices.
Also CC licence forbids use with DRM (2.a.5.c), OSM licence allows it if you offer parallel download.