[OSM-talk] [OSM-legal-talk] Putting simple scripts in the Wiki without violating CC BY-SA 2.0

Devon Fyson devonfyson at gmail.com
Wed Sep 20 01:09:42 UTC 2017


I like the idea of putting it in a software specific version control system
but we need to preserve all the tools used to help curate the database
along with the database. I don't like the idea of relying on 3rd party
hosts with user accounts. We then we have to trust that both the users and
hosts will keep it available in perpetuity. If hosted on a service like
GitHub, unless someone else backs up that repository, that code could
disappear out of error, malicious intent, change of mind on open source,
etc. I also think keeping code available after becoming obsolete is
important in the event that some contribution it made needs to be examined.

However on the other hand GitHub is very popular and there would likely be
poor buy-in if contributors were asked to use a different system. Therefore
I propose that a new template be made on the wiki which is specifically for
referring tools in any repository used on the OSM database. Those
repositories would then be automatically and periodically cloned (backed
up) to say git.openstreetmaps.org.


On Tue, Sep 19, 2017 at 1:09 PM, Kathleen Lu <kathleen.lu at mapbox.com> wrote:

> If I were you, I would put the code into GitHub. It may seem like
> overkill, but it will make it much easier for others to find your scripts.
> It's free and there is a setting to generate a license file.
>
> The wiki is under a CC-SA license, which is not a good match for code. You
> could explicitly state another license next to the code (copy and paste the
> license text onto the wiki page). MIT is compatible but I do not think GPL
> is. I think Apache is probably compatible but seems like overkill for
> scripts (it includes a patent license).
>
> (disclaimer: not legal advice, just my 2 cents)
>
> Best,
> Kathleen
>
>
> On Mon, Sep 18, 2017 at 10:15 PM SwiftFast <swiftfast at gmx.com> wrote:
>
>> I have a bot[1]. I'd like to publish its scripts. A versioning  system
>> like GIT would be overkill, because the scripts are short and rarely
>> changing.
>>
>> I'm not a lawyer, and I have some questions:
>>
>> 1. Suppose I don't state any license, would that implicitly the same
>> license of the wiki itself?[2]
>>
>> 2. Can I explicitly state a license such as MIT/Apache/GPL? Would any
>> of those licenses conflict with the license of the Wiki itself?
>>
>> Thanks!
>>
>> [1] https://wiki.openstreetmap.org/wiki/User:SwiftFast#SwiftFast_bot
>> [2] https://wiki.openstreetmap.org/wiki/Wiki_content_license
>>
>> _______________________________________________
>> legal-talk mailing list
>> legal-talk at openstreetmap.org
>> https://lists.openstreetmap.org/listinfo/legal-talk
>>
>
> _______________________________________________
> talk mailing list
> talk at openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/talk/attachments/20170919/95621e83/attachment.html>


More information about the talk mailing list