Closed pnorman closed 6 years ago
I'm not ruling out share-alike, but am currently inclined against it for cartography.
openstreetmap-carto is CC0, and I haven't seen any negative side effects of that. I'm not aware of any non-free redistributions of openstreetmap-carto, and most people working with openstreetmap-carto just clone git including its history, which (roughly) satisfies the attribution requirement of CC BY.
We shouldn't make things harder than necessary for people wanting to use our code, so I'd propose CC0.
I'm fine with CC0. What CC BY would get us is credit where the map is used, e.g. like "Tiles courtesy of Andy Allan" on osm.org
Reopening. CC0 is good for the cartography, but I'm going with MIT to allow the vector part to reuse code from https://github.com/tilezen/vector-datasource if needed
I would really prefer to stay with CC0, so our code can be re-used by other CC0-projects.
I suppose Tilezen is not willing/able to re-license?
CC0 is a bad license for code, and vector-datasource is primarily code.
CC0 is a bad license for code
Are you sure about that? As far as I'm aware, CC-0 is fine for code, unlike the other CC licenses. See for example here.
Are you sure about that? As far as I'm aware, CC-0 is fine for code, unlike the other CC licenses. See for example here.
Quoting from them,
However, CC licenses are not intended to be used to release software, as our FAQ has always said.
How good/bad it is can be a matter of discussion, but I know people who reject it.
However, this has been rendered moot by #12, and the remaining pure code (e.g. SQL functions) is trivial. Licensing SQL statements that define a style is an interesting question from a legal perspective, but from a practical perspective, licensing the style + definitions that implements the style as CC0 works.
Options for cartography are
Options for code are