OpenStreetMap Foundation, Licensing Working Group

Agenda & Minutes

  Tuesday 25th February 2014, 19:00 - 19:46 UTC

draft

Present: Simon Poole, Dermot McNally, Michael Collinson

Apologies:

Minutes by: Michael

1. Adoption of Minutes of last meeting

Nov 26 Note: This editable minute link is for LWG members only. A public version is normally available at http://www.osmfoundation.org

Proposed: Simon

Seconded: Dermot

Accepted

  • 2013-08- 27 Mike/Paul DMCA procedure doc:
  • Finalise for for board by 2013-10-29
  • - Generate templates for various stages
  • 2013-08- 27 Mike - Facebook logins: Ask legal counsel whether there is any general risk to the project and its data if Facebook feel we do not match their policies.
  • 2013-10-22 Mike - Legal counsel ... under DMCA we really *must* restore data if a contributor files a counter notice? No discretion despite CTs saying that we do?
  • 2013-11-05 Mike Respond to Wikimapia and update complainants of what has happened.
  • 2013-11-26 Simon Respond to group importing Finish NLS.fi data. (Done)

3. Finalise today’s agenda

4. CC 4.0

Not discussed in detail. Paul not present.

5. Imagery Blacklist

Getting JOSM’s blacklist update is important for the DWG, be it by modifying the API to return a blacklist or not. The question is, should this be delivered by the OpenStreetMap API? The positive is that it actively helps prevent well meaning map data and editor software contributors from contaminating the OSM database with data from non-allowed sources. The potential negative to this is that it may imply that other source not on the blacklist are OK. After discussion, it was felt that the right balance could be struck by additionally adding a whitelist, which may also be of use in its own right. Therefore:

LWG recommends and supports an API-delivered blacklist AND whitelist. We urge that it be made clear in supporting documentation that if a source is not on the blacklist, that does not imply that it OK and research should be done before adding it.

Potential whitelist https://github.com/osmlab/editor-imagery-index

6.  Community Guidelines

Mike has been working on the wiki pages. LWG members are asked to review so that we get proper consensus before actively soliciting wider community feedback.

7. Use by SAAS or PAAS Providers

Clarification sought wrt private use of OSM derived data by customers of a service as mentioned above (that this is not publicly conveyed by the customer). Example: travel logs of a truck tracking service (owned by the customer, service provider has no access).

Our conclusion after discussion: This is a clear example of private data that is not publicly conveyed, therefore there is no share alike requirement.

9. Attribution

The board has asked the LWG to follow up on the issue of insufficient attribution by larger OSM based service providers.

10. FB and MS Logins

Kai Krüger would like a minuted “OK” that he can proceed.

The LWG has no objection to adding Facebook and MS login support and considers the risk for legal issues minimal.

11. AOB

Next Meeting:

Tuesday 25th March at 1x:00 GMT/UTC unless urgent business