Board/Minutes/2022-06
Date and time: Thursday 30 June 2022, 13:00 UTC - Countdown
The topics of the agenda will get locked one week before the meeting, on 2022-06-23.
Location: Video room https://osmvideo.cloud68.co/user/ror-nt7-6tu
using BigBlueButton.
Participants
Board members
- Amanda McCann
- Eugene Alvin Villar
- Guillaume Rischard
- Jean-Marc Liotier
- Mikel Maron
- Tobias Knerr
Not Present
- Roland Olbricht (Apologies)
Officers and board
Biographies
Minutes by Dorothea Kazazi.
Guests
- 10 guests
Open to all OSMF members.
You are welcome to ask questions or to comment (via voice or on the chat) at the end of the meeting.
- Please mute your microphone when you join, and to preserve bandwidth, refrain from turning on your webcam.
- If you are in a low-bandwidth environment, you may benefit from using BigBlueButton's low-bandwidth settings. To assess them, click on the 3 dots on the top right of the black video-window.
Administrative
Previous minutes
- 2022-05-23 Approved
Circular Resolutions
2022/Res13 Renew BigBlueButton service from Cloud68
Our BigBlueButton server from Cloud68 is due for renewal, at €1089 per year (a Medium+ instance at €99 per month with 1 month free)
This circular resolution is to approve that renewal for the 1 May 2022 to 1 May 2023 period, and also to approve regular yearly renewals at this price (including reasonable price changes which Cloud68 may do), i.e. a circular resolution would not be needed to renew next year. |
Approved on 2022-05-25 with 5 votes in favour: Amanda McCann, Eugene Alvin Villar, Mikel Maron, Roland Olbricht, Tobias Knerr |
Circular by Amanda McCann. |
2022/Res14 Authorize board members to participate in board discussion on corporate membership rates
The Board authorizes all current Board members to participate in Board discussions in 2022 on what the price of OSMF corporate membership should be, even if they normally have a Conflict of Interest in this. Voting is not included in this motion. |
Approved on 2022-06-25 with 3 votes in favour: Tobias Knerr, Roland Olbricht, Jean-Marc Liotier (Corporate membership rates do not seem like a contentious issue to me, currently or potentially - nor are they an avenue of subversion.) |
Circular by Amanda McCann. |
Action item updates
See osm:Foundation/Board_action_items.
Reportage
Pro-bono lawyer
- OSMF's pro-bono lawyer, who has been mostly ill during the past year, is back.
- It might be legally possible for minors to become OSMF associate members - in progress.
Upgrading all Local Chapters to current Local Chapter agreement
Related to action item "Eugene Villar with help by Amanda McCann to upgrade all Local Chapters to current Local Chapter agreement".
Action item ownership: 2021-03 Amanda McCann, 2022-03 Eugene Villar with help by Amanda McCann, 2022-06 Dorothea Kazazi, after request by Amanda McCann.
- Eugene has created an email reply regarding the difference of the current Local Chapter agreement to the previous one.
- Amanda has asked Dorothea to take over the action item.
Suggestions:
- Eugene could reply to any emails received from Local Chapters about the update..
- Eugene could take over other action items from the action item list.
Windsor Hackforge Local Chapter application
Background |
---|
Windsor Hackforge has applied to be the Local Chapter for Windsor-Essex (Essex County of Ontario, Canada).
Previous board discussion:
|
Related to 2022-02-10 action item "Eugene Villar to to talk to the Windsor-Essex Hackerspace regarding their local chapter application".
- Eugene received a reply from Windsor-Essex Hackerspace and a message from a local mapper in Canada about the evaluation of the local chapter application.
- Some members of Hackforge started conversing with local community members from Canada via email - Eugene was copied on the emails.
- The board can proceed with the next step of the application.
Extracting usernames from CiviCRM
Related to action item: "Guillaume Rischard to find how to extract usernames from CiviCRM".
- Completed.
Copyright enforcement
Related to 2022-06-09 action item: "Guillaume Rischard to arrange a meeting with Robert Kaye of MusicBrainz and the board about their experience with copyright enforcement".
Meeting on 2022-06-16 of some OSMF board member with Robert Kaye of MusicBrainz, who shared about his experience with copyright enforcement.
Updating the local chapter template agreement with regards to commercial activities
Related to 2022-02-26 and 27 action item: "Jean-Marc Liotier to write up a proposal for the minimum local chapter criteria before the March 24 board meeting. Will be supported by Eugene Villar. From: Board 2022 screen-to-screen session "Local Chapter minimum criteria (including formalisation/clarification on commercial activities)".
Fédération des Pros d'OSM
Association of professionals/companies who operate in the French OSM services market.
- They are not represented at the board of the French Local Chapter (OSM France).
- Effort to isolate commercial activities from Local Chapter activities.
- Membership: not open to everyone - they reserve the right to admit members.
- Presentation of Fédération des Pros d'OSM during the April OSMF board meeting.
Fundraising workshop
Related to 2022-05-23 action item: "Mikel Maron to clarify whether the Aspiration tech workshop was offered for free to OSMF board members".
- The workshop will be offered for free to the OSMF board members.
Fastly blogpost
Related to 2020-10 action item: "Mikel Maron to write draft about Operations Working Group (OWG) and work with Paul Norman".
Post will be written by Grant Slater (Senior Site Reliability Engineer).
MapBuilder implementation proposal
Background |
---|
Related to previous discussions about contributions to OSM without individual OSM accounts, by external tools such as Microsoft MapBuilder.
Microsoft MapBuilder was presented to the board and to Advisory Board members during November 2021: Microsoft presentation - "MapBuilder, an experiment to build the best map" (during an Advisory Board meeting). Its initial implementation allowed some Microsoft users to submit changes to the OSM data via a single account, instead of having one account per individual contributor. This led to the single Map builder user OSM account getting a block by the Data Working Group (DWG) on February 2022. The Data Working Group (DWG), after a request by the board, sent a list of requirements for contributions to OSM via external services - such as the Microsoft MapBuilder - for the contributor to be a meaningful part of the community, including:
There has been communication between Microsoft and individual board members, and at least two online meetings in 2022 with some members of the OSMF board: 2022-03 and the latest on 2022-06-20, where Microsoft presented the latest implementation of MapBuilder they have been working on. Related board discussions:
|
Related to 2022-03-24 action item: "Tobias Knerr to ask Microsoft to share their new MapBuilder implementation proposal with the whole board".
- Completed. Also Mapbuilder is on the agenda.
Software dispute resolution panel for iD
Background |
---|
The board in January 2021 decided to evaluate the work of the Software dispute resolution panel after one year (January 2022). The panel reported that there had not been any cases of disputes brought forward. On 2022-02-10 the board decided to start the public consultation of the membership about the software dispute resolution panel.
The panel's initial mandate was to deal solely with disputes over changes to the iD editor. The current five members of the panel are: Richard Fairhurst, David Morais Ferreira, Wille Marcel, Minh Nguyen and Ilya Zverev. Related board discussions and other communications:
|
Related to 2022-02-10 action item: "Tobias Knerr to update the membership about the status of the software dispute resolution panel for iD".
Tobias asked for feedback from the board on whether to update the membership now or wait to receive the response of the software dispute resolution panel for iD to the board's suggestion for the panel to take on the OSM-Carto project.
Points mentioned during discussion:
- Waiting for the panel's response and sending a single email is fine.
- Tobias can update the membership that the panel had no issue raised for the iD editor yet and that the panel's status might change.
Treasurer's report
Previous reports during monthly board meetings |
---|
Please note that additional financial-related topics have been discussed during previous board meetings. |
Presented by Roland Olbricht (Treasurer). |
Deferred as the Treasurer was not present.
Updated membership prerequisites plan
Background |
---|
The board is seeking feedback from OSMF members* about their plan to introduce some requirements for people to become OSMF members.
The OSMF membership voted in 2020-12 and decided the following: "The board of directors shall, together with the OSMF Membership Working Group, work on a set of proposals to ensure that all successful applicants for membership or associate membership in the OpenStreetMap Foundation have made a reasonable amount of contributions to OpenStreetMap. The specific form of the contributions (e.g. mapping vs. non-mapping) does not make a difference for the fulfillment of these prerequisites. The board shall submit these proposals as possible resolutions at a general meeting in 2021." The rationale was presented here. The board some months before the 2021 annual general meeting (AGM) asked the volunteers of the Membership Working Group (MWG) to make proposals. The MWG did not have the humanpower to complete the work in time for the Annual General Meeting in December 2021 and the board decided to submit the proposals on a General Meeting in April 2022. The General Meeting in April was subsequently cancelled.
Related board discussions:
|
Suggested by Guillaume Rischard. |
The board was seeking feedback on osmf-talk* and on community.openstreetmap.org about their plan to limit new OSM Foundation memberships to people who have at least registered three months ago and mapped 15 days.
* Mailing list for OSMF members (join OSMF here. Past messages here).
Initial motion
"The board intends to accept new normal and associate memberships applications only from persons who have mapped over 15 days, and have registered at least three months ago.""
If you want to get involved with OSM, mapping is at the core at what we do - low requirement, you should have an idea about mapping.
On the board approving new members who have not fulfilled the mapping requirements
Suggestion during the membership consultation: to mention during the sign-up process for becoming an OSMF member that we have a fallback opportunity for people with disabilities who can't map to fulfill the minimum mapping requirement.
- Purpose: Clarify the purpose of the exceptions.
- Frequency: the board expects to rarely have to decide on such exceptions.
- Board workload: If voting on the exceptional cases proves to be a lot of workload for the board, the board can make later changes.
On implementation and requiring an OSM username during sign-up
Current status: During sign-up, new OSMF members are asked to provide their OSM username and they have the option to state "no OSM username".
Decision: The Membership Working Group (MWG) to update the sign-up form regarding the OSM username.
Vote on amended motion
Amended motion: The board to accept new normal and associate memberships applications only from persons who have mapped over 15 days, and have registered at least three months ago, or if approved by the Board for exceptional circumstances. |
Approved on 2022-06-30 with 5 votes in favour: Eugene Alvin Villar, Guillaume Rischard, Jean-Marc Liotier, Mikel Maron, Tobias Knerr. |
On membership feedback via a survey
The board has promised to the membership that they will be able to provide feedback via a survey on the introduction of the membership prerequisites.
Action item: Tobias to take steps on running the survey regarding the members' feedback, including contacting Allan Mustard and preparing an online collaborative document with the survey questions to share them with the board.
Consider directing the OWG to cut tile access off due to attribution or other legal policy reasons, if flagged by the LWG
Suggested by Guillaume Rischard.
Currently:
- The Operations Working Group (OWG) blocks websites from scraping osm.org tiles. They do not take action regarding websites with attribution issues, as they don't want to take legal decisions.
- The Licensing Working Group (LWG) gets complaints about websites without attribution, but can't block sites.
Points mentioned during discussion
- LWG is currently focused on attribution cases.
- Example of other reasons to block tile access: If someone has a Nazi website and we don't want them to use tiles from osm.org
- On workload: Could lead to increased workload for LWG/OWG if people see OSM-based tiles hosted by others without OSM attribution and contact OSMF asking us to block them.
- OWG meeting in a few hours.
OSM Carto
Background |
---|
Related to the open letter to OSMF board members on the talk mailing list (further discussion).
OSM Carto is a community project, and the OSM Carto stylesheet is used for the generation of the default tile layer on the OpenStreetMap homepage. Other recent OSM Carto related links:
|
Suggested by Mikel Maron. |
- Some conflicts in the OSM Carto project.
- Not under the jurisdiction of OSMF - but the board has been asked to get involved.
- The board should not have a strong position but should have a discussion with people involved and have a clear view on the issues and solutions.
Amanda has contacted the Software dispute resolution panel for iD (SDRP) and is waiting for their reply. Also emailed the OSM Carto maintainers just the day before the board meeting, to notify them about it.
Points mentioned during discussion
- When you are a large project, it is normal for some people to have issues.
- Maybe the board can help.
- We need more tile servers and map styles.
- Some OSMers are asking the board to kick-out OSM Carto maintainers.
- It is not the first time the board has been asked to facilitate solutions.
Suggestions
- Talk to OSM Carto maintainers to facilitate what seems to be a breakdown in communication.
- Wait for the reply of the Software dispute resolution panel for iD to the board's email.
OSM account creation API
Background |
---|
Related to previous discussions about contributions to OSM without individual OSM accounts, by external tools such as Microsoft MapBuilder.
Microsoft MapBuilder was presented to the board and to Advisory Board members during November 2021: Microsoft presentation - "MapBuilder, an experiment to build the best map" (during an Advisory Board meeting). Its initial implementation allowed some Microsoft users to submit changes to the OSM data via a single account, instead of having one account per individual contributor. This led to the single Map builder user OSM account getting a block by the Data Working Group (DWG) on February 2022. The Data Working Group (DWG), after a request by the board, sent a list of requirements for contributions to OSM via external services - such as the Microsoft MapBuilder - for the contributor to be a meaningful part of the community, including:
There has been communication between Microsoft and individual board members, and at least two online meetings in 2022 with some members of the OSMF board: 2022-03 and the latest on 2022-06-20, where Microsoft presented the latest implementation of MapBuilder they have been working on. Related board discussions:
|
Suggested by Tobias Knerr. |
- Larger policy issue than the MapBuilder discussion.
On board and Microsoft communications
- Tobias Knerr was engaged in the conversations with Microsoft on behalf of the board, to make sure that the Data Working Group (DWG) requirements forwarded to Microsoft will be fulfilled.
- There had been private conversations between Guillaume Rischard and Harsh Govind (Microsoft), and additional requirements were mentioned during the board meeting discussion.
On Microsoft's MapBuilder
- Goal: Encourage people who use BingMaps, an OSM-based product, to contribute to OSM.
- Issue: OSM account creation is a barrier to people who want to make a small change to the map.
On OSM account creation
- Allowing the anonymous creation of notes acknowledges that OSM account creation can be barrier.
- We don't allow anonymous edits.
On MapBuilder implementation attempts
First attempt:
- Collective account for MapBuilder - blocked by DWG.
Second attempt:
- Microsoft mediated OSM account creation:
- People with Microsoft accounts get shown the OSM contributor terms and get an OSM account, connected to their Microsoft account.
- Currently the account creation is done manually by Microsoft employees, as there is no official API for the creation of OSM accounts.
- OSM communications: forwarded by Microsoft to the user's Microsoft account.
Concerns:
- There is no contract between the contributor and the OSM Foundation if Microsoft created the account.
- Against the terms of service, which do not allow impersonation, as Microsoft users would be impersonating Microsoft.
Ideas for future:
- Their Microsoft mediated OSM account, to be possible to become a normal OSM account with no connection to MapBuilder.
On Mapbuilder implemetation slides: To be shared by Guillaume on board chat.
On API for creation of OSM accounts
- Development: Code might be written by Microsoft and used by other parties, if the board and Microsoft agree.
- Technical implementation: has not been discussed - would probably require an API key mechanism and people to accept terms by OSMF.
- Disagreement by some board members if that is the way forward.
- There will be questions about API management and granting access.
- Downsides: spam/legal aspects.
Logging-in to OSM account with third-party accounts
- Already possible, e.g. with Github, Maps.me.
Other points mentioned during discussion
- Some approaches give too much control to a company.
- Important: what are the requirements for people contributing to OSM. The specific mechanism (directly registering or proxy mechanism) is not important.
- The board has spent a lot of time on the issue.
- The board members that are interested can work on the topic.
Suggested next steps regarding MapBuilder
Guillaume has emailed the DWG enquiring about their feedback to the second suggested Mapbuilder implementation.
- Get feedback from Licensing Working Group (LWG) and Operations Working Group (OWG) on the suggestion of an API for creation of OSM accounts.
- Instead of creating an API, use the existing system and work on making it easy for Microsoft users to log-in.
- Would fulfill all Data Working Group (DWG), OWG requirements.
- Does not open the door to spam or abuse.
- The whole board to have visibility on the discussions with Microsoft.
- Guillaume to contact Tom Hughes (sysadmin/OWG) who is involved with blocking.
- Provide to Microsoft the feedback by DWG and Tom Hughes.
Action items
- Tobias Knerr and Guillaume Rischard to communicate with Microsoft (MS) that the board has received the proposal and is checking with Working Groups (WGs).
- Ask MS for input on ideas, such as the suggestion of using a plugin to add third party logins to the OSM website.
- ask MS to prepare a very brief document about technical proposal, where the board can comment on.
- Guillaume Rischard to ask the Licensing Working Group (LWG) for potential legal issues on the API creation during their next LWG meeting.
Advisory Board - monthly update
Background |
---|
The Advisory Board members are separate from the OSMF board of directors - individuals are either nominated by Local Chapters and Gold or higher Corporate Members of the OSMF or invited directly by the OSMF board of directors. The OSMF Board of Directors will publicly minute, in the board meeting minutes, any communication sent to, or received from, the AB members. This monthly section is reserved for this purpose. Overview of board communications with representatives on the Advisory Board. 2022 Jan, Feb, Mar, Apr, May |
Presented by Amanda McCann (Secretary). |
Presentation by Mapbox Workers Union
About this monthly section |
---|
In 2020 the board started hourly discussions with Corporate Member representatives on the Advisory Board and inviting Local Chapter representatives on the Advisory Board to give 10' presentations during public board meetings (this slot). A year later, during the 2021-04 board meeting, delegation of the Local Chapter presentation scheduling was suggested by the Secretary (Amanda McCann), who was previously solely responsible for that. Mikel Maron and Eugene Alvin Villar offered to help with organisation.
2022 presentations
2021 presentations |
Arranged by Amanda McCann. |
Presentation by Mapbox Workers Union. Cancelled.
Any other business
State of the Map 2022
- Tickets are available for the State of the Map 2022 conference. June 30 was the last day to buy the early bird (cheaper) tickets.
- There will be a board "ask us anything" session.
Guest comments or questions
Open to all OSMF members (join the OpenStreetMap Foundation). You are welcome to ask questions or to comment (via voice or on the chat) at the end of the meeting.
|
Responsibility for what is shown on openstreetmap.org
Question by Jeroen Hoek (guest) if the OSMF ultimately responsible for what is shown on openstreetmap.org and if not, who is? For many users this is the face of OpenStreetMap after all; our calling card.
Additionally, comment by Jeroen Hoekin (guest) in the chat:
"I would like to invite to OSMF board to reach out to stakeholders outside of the (remaining) Carto maintainers as well (i.e., mappers, other contributors to Carto, etc.) to gain a broader understanding of this issue and its effects on the community. Communication is one problem, but the main issue is that community and end-user needs are apparently not met and that the OpenStreetMap project is being harmed by the current situation. Getting the Software Dispute Resolution Panel involved might help, but I'm not sure if that can address the stagnation of Carto (and thus openstreetmap.org's standard layer)".
Comments by board members
- Yes, OSMF is responsible. However the way responsibilities are structured does not mean at this time the board can direct how the OSM Carto project runs or is organised.
- People think that vector tiles are around the corner, but probably are not, though there is work on vector tiles.
- Some board members had discussions with OSM Carto maintainers.
On files hosted on OSM wiki with unclear or invalid copyright status
Comments by Mateusz Konieczny (guest):
- ~30,000 files hosted on the OSM wiki with unclear or invalid copyright status. Examples:
- OSM map without attributing OSM contributors.
- files where it's unclear if the uploader was also the creator.
- 5,000 of these have already been processed.
On OSM logo
Mateusz Konieczny was unsure about the legal status of the OSM logo and who was the creator of the original logo (not the current one).
- Supposedly on CC licence, requiring attribution of the creator.
- People are not usually attributing the creator when using the logo.
- Concern in the case of people inheriting the copyright of the original logo.
Comments by board members:
- Creator of original logo was probably Matt Amos or Steve Coast.
- No urgency or concern about the copyright status of the logo.
- If it was easy, OSMF could try to get the rights for the original logo, but probably not need to expend much effort on the issue.
On OSM Carto issue
Comments by Mateusz Konieczny (guest), who is also one of the OSM Carto maintainers.
- Part of the problem is that while most complaints are demanding that something should be done by maintainers - if no-one is willing to work on it - including complainers - then OSMF has limited ability.
- OSM maintainers are not obligated to spend a lot of time on specific things.
- Some people expect that people will be hired specifically for OSM Carto.
Next meetings
- 2022-07-14 Mid month board chat, not open to observers.
- 2022-07-28 Public board meeting Thursday 28 July 2022 at 13:00 UTC.
Open board meetings take place online once a month, usually on the 3rd or 4th Thursday of the month, at 13:00 UTC.
See the Monthly Board meetings page to find out where board meetings are announced and for a subscription link to have future board meetings automatically added to your calendar.
Meeting adjourned 89' after start.