[OSM-talk] FYI: Board now requires imports list (in)compatibility with OSM CT (& will work on a template)

[Tobias Knerr]

On 29.11.22 08:14 Simon Poole wrote:
> The main question is what "expect it to survive a hypothetical license 
> change" implies. My expectation is that because of practical 
> considerations any future licence would require downstream attribution 
> of OSM so that the OSMF can continue to offer third party sources 
> indirect attribution.

You have a point that it seems practical to look just at the more narrow 
scenario of another license that requires attribution of OSM. After all, 
a license change is not a high-probability event in the first place, and 
a change to a license that doesn't require some form of attribution 
seems even more unlikely. So it would be useful to be able to record 
something like "as long as attribution is ensured" for an import's 
license change compatibility.