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

[Devon Fyson]

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  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  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-t...@openstreetmap.org
>> https://lists.openstreetmap.org/listinfo/legal-talk
>>
>
> ___
> talk mailing list
> talk@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk
>
>
___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk

Re: [OSM-talk] How to Create an Android App Using OSM

[Devon Fyson]

Is there a reason you wouldn't want to modify or contribute to an existing
open source app?

On Tue, Mar 28, 2017 at 12:29 PM, Jerome DeBartho  wrote:

> I want to create a voice navigation app for Android phones, using OSM
> data.  Such that the app is confined to a small area say,  a campus with
> the data offline.
> I need help on how to go about it.
>
> Jerome
>
> ___
> talk mailing list
> talk@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk
>
>
___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk

Re: [Talk-ca] Wikidata in OpenStreetMap

[Devon Fyson]

With respect to linking wikidata and OSM, all those properties should be
added to wikidata if they don't already exist. Then link to it by simply
adding the wikidata ID in OSM. Then if OSM ever wants to merge wikidata in,
it can all be done automatically via the wikidata ID. Most of what is in
that Ottawa example is already in wikidata and so it doesn't make sense to
duplicate it. See this discussion

on wikidata.
As for cross referencing existing OSM nodes with existing wikidata IDs, the
fastest way would be to use a script to search between the two databases
with a best fit algorithm then have user intervention to ensure quality.
(eg node 18886011 at 45, -75 is a capital with name 'Ottawa' and looks to
match Q1930 with a 90% fit, next match of ___ is a 50% fit). Even lower
hanging fruit would be to start with cross-referencing via the wikipedia
tags which could probably be fully automated. eg OSM → wikipedia → wikidata
to generate OSM → wikidata.
Devon

On Thu, Nov 10, 2016 at 8:19 PM, John Marshall  wrote:

> Great work James. I'm in.
>
> John
>
> John Marshall
>
> On Nov 10, 2016 20:17, "James"  wrote:
>
>> Seeing as ID[1] and Mapbox[2] are pushing to incorporate wikidata into
>> OSM, I thought it would be a perfect little project when mappers have
>> nothing better to do or in their downtime.
>>
>> The wikidata link can help developers get vital information like the
>> current population, current mayor, flags, coat of arms,etc. The list goes
>> on. This is a lot of data that can't necessarily be encoded into OSM. This
>> would help simplify the use of OSM data for small developers.
>>
>> I've started a project on the OSMCanada Tasking Manager here:
>> http://tasks.osmcanada.ca/project/40
>>
>> Join in for a more data rich Canada :)
>>
>>
>> [1] https://www.mapbox.com/blog/id-wikidata/
>> [2] https://www.mapbox.com/blog/geocoding-wikidata/
>>
>> ___
>> Talk-ca mailing list
>> Talk-ca@openstreetmap.org
>> https://lists.openstreetmap.org/listinfo/talk-ca
>>
>>
> ___
> Talk-ca mailing list
> Talk-ca@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk-ca
>
>
___
Talk-ca mailing list
Talk-ca@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-ca