Licensing Working Group/Minutes/2019-02-14

From OpenStreetMap Foundation
< Licensing Working Group
Revision as of 23:11, 22 March 2019 by Dorothea (talk | contribs) (→‎3rd party data licence guidance: fixed link)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

OpenStreetMap Foundation, Licensing Working Group - Agenda & Minutes
Thursday February 14th 2019, 20:00 - 21:00 UTC

Participants

Present:

  • Simon Poole
  • Kathleen Lu
  • Jim Vidano

Apologies:

  • Nuno Caldeira

Guests:

Minutes by: Dorothea

Administrative

Adoption of Minutes of last meeting

2019-01-10: Accepted

Previous Action Items

  • 2016-05-06 Dermot licence question wrt Ordnance Survey Northern Ireland Open Data
  • 2017-03-02 Simon determine existing obligations towards sources listed on the copyright page
  • 2017-05-04 All/Simon review import guidelines wrt licence “approval”
  • 2017-09-05 Simon ask Lawdit for quotes for registering for the additional class suggested
  • 2018-03-08 All look at the Working Groups collecting personal information
  • 2018-04-12 LWG to follow-up on the iD editor, as the number of changesets is now included on the changeset comments thread
  • 2018-04-12 Simon to contact openstreetmap.cymru. The LWG will allow use of domain name on the condition that if there's local group in the future, they will have to concede control to them and get agreement in writing, so that if domain expires it doesn't get squatted on
  • 2018-04-12 Canadian licences reminder - no Canadian Licences are currently in review by the LWG, as some members of the community seem to think
  • 2018-04-12 Simon to write short step by step guide of how to approach licencing considerations and add things to look out in the licences.
  • 2018-05-10 Jim to sign the LWG NDA
  • 2018-09-14 Simon to email OpenStreetCab
  • 2018-09-14 Open Data License - India (GODL) -Make statement, in line with other licences, to not use datasets with personal data which might be subject to privacy laws
  • 2018-09-14 Simon to create section on OSMF website for license compatibility
  • 2018-09-14 Simon to contact German lawyer involved with OSM about joining the LWG, touch base with Dermot, email the OSMF mailing list and contact Mapillary
  • 2018-10-11 Simon to ask the board to contact the Working Groups about the NDA and ask people to sign up.
  • 2018-10-11 Simon to investigate about whether Wikimedia Germany has an in-house lawyer (related to the 2018-09-14 action item).
  • 2018-10-11 Jim and Kathleen to follow up on the “OSM contributor” app issue.
  • 2018-11-08 LWG to update the OSMF address on US DMCA website - should match OSMF website listing.
  • 2018-11-08 Kathleen to process the input from the meeting regarding the DMCA policy and add section to top, describing formal versus informal policy.
  • 2018-11-08 Simon to get guidance regarding information requests in UK from law enforcement.
  • 2018-11-08 Simon to ask William to provide information about the Canadian OGL variants he is interested in, in a systematic format.
  • 2018-12-13 GDPR: We need to disclose the details about our hosted bookkeeping solution, Xero (they host in NZ and US), in the privacy policy.
  • 2019-01-10 Simon to draft text to developers of apps related to geo/mapping, having OSM in their names or using variations of our logo.
  • 2019-01-19 Simon to e-mail OpenStreetCab wrt disclaimer.
  • 2019-02-14 Simon to change the label for licences requiring special consideration. Suggestion: “Licences that LWG has specifically commented on”.
  • 2019-02-14 Simon to notify osmf-talk and talk mailing lists about the [[Licence_Compatibility|Licence compatibility page].
  • 2019-02-14 Simon to summarise the advice regarding information requests from law enforcement and send it around.
  • 2019-02-14 Simon to ask Frederik if he has contacted the Belgium Local Chapter regarding the recent blurring request request.

Reportage

3rd party data licence guidance

Licence Compatibility page is now live.

It is not an exclusive list.

Action items:

  • Simon to change the label for licences requiring special consideration. Suggestion: “Licences that LWG has specifically commented on”.
  • Simon to notify osmf-talk and talk mailing lists about the Licence compatibility page.

Information requests from law enforcement

We got input from legal counsel regarding information requests from law enforcement.

Main point: Need to verify that the request is actually coming from law enforcement.

Suggestion: Write down points and distribute to board and Working Groups as a rough guideline if they receive such requests.

Action item: Simon to summarise the advice and send it around.

  • Information requests from EU law enforcement entities are expected to come from UK organisation, because of related agreements. Discussion about UK-EU agreements affected by Brexit.

Blurring request BE

Received request from the Belgium Ministry of Defense about blurring aerial imagery with military installations.

  • Seems like standard letter sent to any provider of aerial imagery.
  • Not mentioned in letter:
    • Deadline.
    • Pre-made list of locations.
    • Having detailed map data.
  • We do provide access to such imagery, but we don’t control it and it is publically available.
  • Their interpretation of Belgian law might be questionable.

Decision: not do something proactively.
We could write a letter saying that we do not store aerial imagery, after checking whether we have any vulnerable points.

Action item: Simon to ask Frederik if he has contacted the Belgium Local Chapter.

Any Other Business

Brexit - GDPR related issues?

  • European Data Protection Board: in No-deal Brexit they will enforce GDPR related restrictions to data transfers to 3rd party countries (link).
  • This could cause issues for us, as we now have internal data transfers between Netherlands (our new data centre) and the UK (our two older data centres).
  • The UK would have to apply for equivalence determination and this could take a long time.
  • Most of our people with access to data are based in UK, so even if we host outside of the UK, we will still have certain issues.

Next Meeting

March 14th 2019 20:00 UTC on Mumble


Acronyms