5,887
edits
Board/Minutes/2023-06: Difference between revisions
Added draft minutes, board members' presence, number of guests
m (Vector Tiles proposal: The description of the two votes were identical, updated the second one) |
(Added draft minutes, board members' presence, number of guests) |
||
|
<div style="margin:2px 0;border:1px solid #9B9;background:#EFE;color:#000;padding:2px .5em;text-align:center">
<font color="blue">
'''Meeting date and start time: [https://www.timeanddate.com/worldclock/fixedtime.html?msg=OSM+Foundation+board+meeting+-+Thursday+
''Please note that the individual points mentioned below usually reflect the opinion of one or more board members and not necessarily of the whole [[Officers_%26_Board|board]]. Official board decisions are taken during the meetings or by voting using [[Board_Rules_of_Order#7._Circular_Resolutions|circulars]], and votes are listed in the minutes.''
The topics of the agenda get locked one week before the meeting.
'''Location: Video room</font> https://osmvideo.cloud68.co/user/dor-2cd-qah-rim''' <br> using [https://en.wikipedia.org/wiki/BigBlueButton BigBlueButton]. <br>
== Participants ==
=== Board members ===
* [10'] Arnalie Vicario
* [06'] Craig Allan
* [36'] Guillaume Rischard ''(Chairing)
* [23'] Mikel Maron
* [12'] Mateusz Konieczny
* [
[https://wiki.osmfoundation.org/w/index.php?title=Officers_%26_Board&oldid=9091 Officers and board]<br>
[https://wiki.osmfoundation.org/w/index.php?title=Board_Member_Bios&oldid=9106 Biographies]
==== Not Present ====
* Roland Olbricht ''(apologies)''
''Minutes by [[osm:User:Dorothea|Do<nowiki>rothea Kaza</nowiki>zi]].''
=== Guests ===
* 5 guests
Open to all OSMF members.<br>
===Previous minutes===
* [[Board/Minutes/2022-
=== '''Circular Resolutions''' ===
* [[Board_Rules_of_Order#7._Circular_Resolutions| About circular resolutions]]
* Board [https://wiki.osmfoundation.org/w/index.php?title=Conflict_of_Interest_Policy&oldid=7369 conflict of interest policy]
==== 2023/Res15 Vector tile plan funding ====
{| class="wikitable"
|-
| Agree to a budget of 2k€ to pay Paul Norman to flesh out his vector tiles work plan and vector tiles proposal.
''link to Google document 1 accessible to board members only - Vector tiles work plan.''<br>
''link to Google document 2 accessible to board members only - Vector tiles proposal.''
Paul has already done a lot of work on vector tiles and on the proposal for free, and doesn't want to spend more time on the proposal in the face of past OSMF uncertainty.
|-
|style="text-align: left; background: white;" | <span style="color: black;">
'''Did not pass''' on 2023-07-02 with '''4 against''':<br>
<u>Mateusz Konieczny</u><br>
''(as replaced by voting on a board meeting)''<br>
<u>Craig Allan</u><br> ''(I like proper specifications for a big job like creating vector tiles. A work plan that exists in the absence of a specification kind of assumes an implied specification which is not written down anywhere and certainly not supported by Board and EWG and members. Big problems can happen in the future, the most disastrous of which is if Paul suddenly abandons the project and leaves with all of the specification in his head. We would have to start again from nothing. Can we talk about this.)''<br>
<u>Sarah Hoffmann</u><br> ''(The circular insufficiently defines the work outcome which is bound to lead to disagreements about when the proposal is finished. This does make uncertainty worse. On a technical note: this matter should not be decided via circular as it is not time-sensitive and board members have signaled a need for discussion.)''<br>
<u>Mikel Maron</u><br> ''(I am not against this idea in principle but need to see more detail on what the scope of the days work on the plan will produce. Just a few bullets / questions to address.)''><br>
'''2 in favour''':<br>
<u>Roland Olbricht</u><br>
<u>Guillaume Rischard</u><br>
'''1 did not vote''':
<u>Arnalie Vicario</u>
|-
| ''Circular by Guillaume Rischard''.
|}
'''''Note:''' This circular was running during the <u>June</u> board meeting. While the circular closed after the June board meeting, please note that '''the board considers the [[Board/Minutes/2023-06#Vote:_earmark_a_budget_of_EUR_2,000_for_a_Vector_Tile_rendering_stack_proposal_by_Paul_Norman|decision taken during the June meeting with a board vote]] to supercede the circular decision'''. An amendment to the board rules of order will be proposed during the [[Board/Minutes/2023-07|July board meeting]].''
==== 2023/
{| class="wikitable"
|-
|-
|style="text-align: left; background: white;" | <span style="color: black;">
'''Unanimously approved''' on 2023-07-22 with '''7 votes in favour''': <u>Mikel Maron</u>, <u>Guillaume Rischard</u>, <u>Roland Olbricht</u>, <u>Mateusz Konieczny</u>, <u>Sarah Hoffmann</u>,<u>Arnalie Vicario</u> ''([the candidate] is an example of a rockstar contributor who’s actively participating in working groups and indirect mapping volunteering that helps osm work!)'', <u>Craig Allan</u> ''([candidate]'s contribution has been enormous. This application is exactly why contributions other than mapping are accepted by this process for membership of the OSMF. I am honoured to vote Yes on this application)''.
|-
| ''Application initially processed by the [[Membership_Working_Group|Membership Working Group]]''.
|}
==== Comments on circulars ====
* 2023/Res10 Agreed to match inflation for Grant Slater's salary.
* 2023/Res11 The changes to Finance Committee structure have been discussed in a previous board meeting.
* 2023/Res12 The Working Group Conflict of Interest policy now applies to moderators and it was discussed with moderators before being put to a vote.
=== '''Action item updates''' ===
{| class="wikitable"
|-
|}
==== Arnalie Vicario ====
===== Local Chapter action items =====
Prioritising Local Chapter action items. More updates during the [[#Local_Chapters_and_Community_updates|related topic]].
==== Craig Allan ====
===== Strategic Plan - Gathering and editing amendments =====
GitLab: [https://gitlab.com/osmfoundation/board-action-items/-/issues/55 Strategic Plan: Gathering and editing amendments]
* Submitted a report to the board outlining the strategic plan's timeline and framework.
* <u>Current status</u>: gathering responses from the latest survey concerning the strategic plan.
* <u>Collection process</u>: there is approximately a 24 hours delay. Will send something to the board during the weekend.
===== Executive director - Establish what we'd want an executive director to do/not do =====
GitLab: [https://gitlab.com/osmfoundation/board-action-items/-/issues/9 Executive director - Establish what we'd want an executive director to do/not do]
* Pending.
* The topic was briefly discussed during the [[Board/Minutes/2023-06-S2S|June 2023 screen to screen board meeting]].
==== Guillaume Rischard ====
===== Vector Tiles action items =====
GitLab: [https://gitlab.com/osmfoundation/board-action-items/-/issues/37 Vector Tiles: To secure funding]<br>
GitLab: [https://gitlab.com/osmfoundation/board-action-items/-/issues/36 Vector Tiles: To set up Engineering Working Group/Operations Working Group/board meeting, agree on go/no go]
[[#Earmark_a_budget_of_EUR_33000_for_a_vector_tile_rendering_stack_such_that_tiles_can_be_re-rendered_minutely|Topic]] on today's agenda.
* <u>Current status</u>: specification stage.
* Guillaume had discussions with Grant on how to structure the work and finding ways of getting better communication about the work.
<u>Suggestion</u>: approve the whole budget of EUR 33,000 and then agree with what we have in the [[Board/Minutes/2023-07#2023/Res15_Vector_tile_plan_funding|circular]] ''("Agree to a budget of 2k€ to pay Paul Norman to flesh out his vector tiles work plan and vector tiles proposal")''.<br>
<u>Rationale</u>: to avoid coming multiple times back to the board for decisions.
==== Mikel Maron ====
===== FUNDRAISING: Secure resource to help with design assets =====
GitLab: https://gitlab.com/osmfoundation/board-action-items/-/issues/109
* It's very important that we have a representative visual language for the fundraising campaign.
* Several requests for help with design have been made.
* It would be appreciated if anyone else has leads on qualified visual designers who might be able to help.
* OSMF might need to allocate funds.
<u>Proposed work</u>: updating some colours and the logo and producing a banner for the OSM.org website and updating the [https://donate.openstreetmap.org/ donate site].
''Comment by Courtney Williamson (2023 fundraiser) that it's not a lot of work but graphic design and visual storytelling are highly skilled, and it's tough to task. It's also highly impactful in a way that we have to care about--even a color or logo change communicates a message about OSM.''
===== Take the work of the fundraising committee, formulate it and share with the board =====
GitLab: https://gitlab.com/osmfoundation/board-action-items/-/issues/108
* All board members should have access to the fundraising repository on GitLab.
* Everything has been shared - if board members want to see something in addition, they can notify Mikel.
===== Mikel Maron and Arnalie Vicario to have a meeting on communication strategy =====
GitLab: https://gitlab.com/osmfoundation/board-action-items/-/issues/107
There might be a meeting tomorrow.
===== Second 2023 quarterly post from the OSMF Board =====
GitLab: https://gitlab.com/osmfoundation/board-action-items/-/issues/100
Blog post on the June 2023 screen-to-screen meeting was [https://blog.openstreetmap.org/2023/06/26/checking-progress-planning-and-funding-the-june-2023-osmf-board-screen-to-screen/ published].
===== Draft something regarding the collection of sponsor funds for local chapter conferences =====
GitLab: https://gitlab.com/osmfoundation/board-action-items/-/issues/97
Agenda item.
===== 2023 Fundraising campaign launched =====
GitLab: https://gitlab.com/osmfoundation/board-action-items/-/issues/2
Aiming for mid-July.
==== Sarah Hoffmann ====
===== To have meeting with the Engineering Working Group to discuss possible communication venues =====
GitLab: https://gitlab.com/osmfoundation/board-action-items/-/issues/44
* Discussed during FOSSGIS 2023 conference.
* Action item to be closed.
===== To contact developers and set up an initial meeting =====
GitLab: https://gitlab.com/osmfoundation/board-action-items/-/issues/45
* Currently in the process of organising together with the [[Engineering_Working_Group|Engineering Working Group]] (EWG) the process for getting funds for website development from the German Sovereign Tech Fund.
===== EU registration - Find local points of contacts to clarify legal questions =====
GitLab: https://gitlab.com/osmfoundation/board-action-items/-/issues/6
Had a very informative call with the executive director of the Eclipse Foundation, who moved to Brussels.
* Brussels seems very well suited for the kind of association they have.
* Has bureaucracy.
* Lawyer: the director did not recommend his lawyer.
<u>On moving our assets</u>
* Contract terms: will not be a problem.
* Trademarks: might take 4-6 years to transfer, so we should keep OSMF UK.
===== EU transparency register - Re-register OSMF =====
GitLab: https://gitlab.com/osmfoundation/board-action-items/-/issues/28
* Can't give them a telephone number for OSMF.
* Last time we registered, Guillaume provided his number.
==== Mateusz Konieczny ====
===== Attribution: To finish reviewing https://wiki.openstreetmap.org/wiki/Lacking_proper_attribution, find the worst offenders that are still in active operation =====
GitLab: https://gitlab.com/osmfoundation/board-action-items/-/issues/63
* Underestimated the time need to review the entries for missing attribution, listed on [[osm:Lacking_proper_attribution|the OSM wiki]].
* https://openflights.org/ started attributing OSM this week.
* A lot of websites disappeared in the meantime
===== Visualisation of OSMF finances =====
* Trying to create a visualisation of OSMF finances, for fundraising and transparency reasons.
* Need to do own review and processing of Xero data to prepare for publication.
===== Discussion on focusing on attribution action item =====
Brief discussion centered around Mateusz' current action items, which are primarily focused on attribution. Mateusz would like to prioritise the attribution-related action items and take potential next steps with one or two of the candidates who lacked attribution. The importance of attribution was stated, as a tool for raising awareness about OpenStreetMap and attracting new mappers.
== '''Treasurer's report''' ==
{| role="presentation" class="wikitable"
! <b>Previous reports during monthly board meetings and general meetings</b>
|-
| See [[Finances#Treasurer's_Report|Treasurer's reports]] on the finances page.
|-
|}
Started to systematically chase down unpaid invoices, including:
* an organisation which had not paid an invoice for USD 10,000 - currently being processed.
* memberships in arrears.
== '''Secretary's report''' ==
{| role="presentation" class="wikitable mw-collapsible"
! <b>Background</b>
|-
|''During the 2023-02 board meeting it was decided to have a "Secretary's report" section during the monthly board meetings, in place of the "Advisory Board monthly updates", which were provided by the Secretary.''
''Previous reports:''<br>
''2023 [[Board/Minutes/2023-02#Secretary's_report|Feb]], [[Board/Minutes/2023-03#Secretary's_report|Mar]], [[Board/Minutes/2023-04#Secretary's_report|Apr]], [[Board/Minutes/2023-05#Secretary's_report|May]]''
|-
|}
=== External enquiry related to attribution ===
* Assigned to Mateusz.
* Mateusz wants to consult with the board on whether to send the email as a person or as an OSMF Director. In the later case, he was not sure whether we should request attribution on the poster, as it will most likely be used in private.
==== On handling cases of missing attribution ====
* If no prior communication with the entity lacking attribution was mentioned on the OSM wiki page, Mateusz sent a template email from his personal account.
* Mateusz has selected two cases of no attribution and he proposes communicating as an OSMF representative with the two companies.
<u>Suggestion</u>: The board to discuss how the communication with the entities missing attribution would like and under what circumstances it is going to be done.
''See also the later discussion and vote "[[Board/Minutes/2023-06#Review_of_entries_listed_at_%22insufficient_attribution%22_wiki_page,_taking_potential_next_steps|Review of entries listed at "insufficient attribution" wiki page, taking potential next steps]]".''
=== WikiMedia UK request to join a letter of supporting a position of online safety bill in UK ===
* Assigned to Guillaume.
* Paul from WikiMedia UK asked OSMF to join a letter supporting a position on the online safety bill in UK.
== '''EU Cyber Resiliency Act''' ==
{| role="presentation" class="wikitable"
! <b>Background</b>
|-
| ''The Apache Foundation reached out to us about OSMF holding a position and joining in actions by open source groups to shape the [https://digital-strategy.ec.europa.eu/en/policies/cyber-resilience-act EU Cyber Resiliency Act].''
|-
|}
Dirk from Apache Foundation reached out about OSMF holding a position and joining in actions by open source groups to shape the EU Cyber Resiliency Act.
https://digital-strategy.ec.europa.eu/en/policies/cyber-resilience-act
* The Act aims to bring more rigour and standards to software released as products.
* The process of software release may undergo standardisation or even require specific qualifications for participants, similar to manufacturing industries.
* The intent is to make companies reliable for their products.
<u>On current status of the Act</u>
* The commission has proposed the text for discussion to some people and the text might be changed.
The text will be sent to the parliament in September - it will be too late by then, because influencing within the parliament is really hard.
=== On open-source software ===
<u>Open-source in the Act</u>
From the beginning there was an exception for open source in the text, but it was very restrictive, as you must not make any money with the it. E.g. if you get sponsoring via GitHub sponsors (as OSMF has), you're out.
<u>Concerns</u>
* The proposed regulations significantly differ from the current practices of open-source software development.
* The Act could impose a substantial burden on both individual developers and larger commercial open-source projects.
<u>Current actions</u>
* A group of open source software organisations is collaborating to advocate and lobby for changes in this policy.
<u>Other points mentioned</u>
* The EU is unlikely to restrict the use of Linux as a server operating system.
* The Act should not apply when publishing open-source software but when creating a product for sale, allowing more flexibility for non-commercial open-source projects.
=== OSMF ===
Sarah talked to the person from NL.net who started to drive all this.
* Direct implications are probably minor for OSMF, since we're not releasing our software as part of products, but for maintaining our own services.
* We would want to support the things they are trying to do, as part of the open-source ecosystem.
* Too late for OSMF to make a public statement.
<u>Suggestions</u>
* Clearly communicate our financial model, which relies on memberships and recurring donations.
* Getting more involved in policy matters might be a good idea.
=== OSM software ===
* [[osm:JOSM|JOSM]] or [[osm:ID|iD]] probably won't have a problem because they're not financed at all.
* More difficult for software like GraphHopper.
* Our software is only in the not so important tier, which means you can self certify.
=== On signing collective letters ===
''In addition to the EU Cyber Resiliency Act, there was another initiative where the OSMF was asked to sign a collective letter, which included organisations such as the Eclipse Foundation and the Linux Foundation. The letter has been published - OSMF did not sign it.''
<u>For EU policies</u>
* Signing collective letters has become challenging since the foundation is no longer in the EU, which means our influence has diminished.
* Use of OSM data on the European Union websites gives us a standing to sign open letters addressed to European Union organisations.
<u>Suggestions</u>:
* work with the local chapters and local organisations in the EU.
* Send a similar letter just by us, as letters with many signatures are usually treated as one complaint.
** The board doesn't have the bandwidth.
''Mateusz offered to help with the EU Cyber Resiliency Act by drafting a letter, as he has some experience working with governments.''
=== '''Action item''' ===
* Mateusz Konieczny to draft a letter about the EU Cyber Resiliency Act and share it with the board.'''
== '''Engagement in policy committees''' ==
{| role="presentation" class="wikitable"
! <b>Background</b>
|-
| ''The OSMF has been asked by some open source organisations to join a coalition with a particular focus on policy initiatives.''
|-
| ''Topic suggested by Sarah Hoffmann.''
|}
We received two requests this week to engage in policies:
=== 1. Open Policy Alliance ===
* The Open Source Initiative (OSI) has initiated an effort to educate policymakers about how open-source functions.
* We received an invitation due to our affiliation with OSI.
* Workload: we have the option to have low involvement.
* OSI's focus is on policies within the United States.
They had mentioned they would like us to:
* Make an initial announcement about the new initiative, stating our membership in it.
* Provide our logo and name for inclusion, after which we will sign the letter.
by June 19th ''(the email was received eight days after it was said to be sent)''.
=== 2. Public Policy Council for Open Source Foundations ===
* Organised by Open Forum Europe (OFE).
* OFE is focused on EU based policy.
=== Points mentioned during discussion ===
* It would be beneficial to have a presence in both networks, as they would keep us updated on the broader policy landscape.
* Our obligation would primarily involve passive observation and listening.
* There are at least ten legislative efforts in the EU that impact software-related matters.
=== On joining both initiatives ===
* The Open Policy Alliance is a little more formalized at this point.
<u>Suggestion</u>: Say that we'd like to join.
<u>On documentation</u>:
* Documents from OSI are in Git.
* Mikel can forward the documents he received.
''Craig Allan was experiencing network connectivity problems and messaged that he anticipates power rationing within the next 15 minutes.''
=== '''Vote: Motion to join both initiatives 1) Open Policy Alliance and 2) Public Policy Council for Open Source Foundations''' ===
{| class="wikitable"
|-
| ''Motion to join both initiatives 1) Open Policy Alliance and 2) Public Policy Council for Open Source Foundations.''
|-
|style="text-align: left; background: white;" | <span style="color: black;">
'''Approved''' on 2023-06-29 with '''3 votes in favour''': <u>Sarah Hoffmann</u>, <u>Guillaume Rischard</u>, <u>Mikel Maron</u>.<br>
'''3 abstained''': <u>Arnalie Vicario</u>, <u>Craig Allan</u> ''(because he missed the discussion due to network issues)'', <u>Mateusz Konieczny</u>.<br>
'''1 did not vote''': <u>Roland Olbricht (absent)</u>
|-
|}
== '''Local Chapters and Community updates''' ==
{| role="presentation" class="wikitable"
! <b>Background</b>
* ''(tentative) OSM landing page''
* ''(tentative) Trails Engagement''
|-
| ''Topic suggested by Arnalie Vicario.''
|}
* During the June screen-to-screen board meeting, we have agreed that we will allow the [[Local_Chapters_and_Communities_Working_Group| Local Chapters and Communities Working Group]] (LCCWG) to put topics on the OSMF board agenda.
** There was no such agreement.
=== Local Chapter (LC) annual reports collection + write up ===
* We have collected 14 out of 18 [[Local_Chapters/Reports_and_chapter_changes|local chapter reports]] for 2021/2022.
* Arnalie will draft a blog post highlighting one activity or accomplishment from each [[Local_Chapters|Local Chapter]] (LC) to enhance their visibility.
* LC financial reports: will be left to be handled by the Secretary and Treasurer.
=== Sharing draft Local Chapter application redesign '(including criteria + evaluation/approval) for community consultation ===
* The [[Local_Chapters_and_Communities_Working_Group|Local Chapters and Communities Working Group]] (LCCWG) agreed to prioritise and significantly contribute to the review of LC applications.
* The LCCWG aims to address comments within the next two weeks to prepare the draft for community consultation.
* LCCWG meeting on the 5th of July 2023 - Craig Allan and Roland Olbricht were invited, other board members can also join.
=== Improving Affiliation Models (discuss at Local Chapter Congress or State of the Map regional) ===
* LCCWG is deprioritising the improvement of affiliation models for now.
* The topic will be addressed at this year's Local Chapters and Communities Congress.
On Local Chapters and Communities Congress: online event and we will be submitting proposals for in person attendance of board members at regional state of the Maps, such as Oceania, EU, Asia and Africa.
=== Microgrants (follow up on funds / from fundraising?) ===
The LCCWG:
* had requested funding for Microgrants.
* would like the board to consider if funding for Microgrants can be part of the fundraising campaign. The LCCWG is open to discussing this with the board.
<u>Suggestion</u>: the LCCWG to send a proposal to the board regarding Microgrants.
=== OSM landing page and website redesign ===
* The LCCWG would like to update the communities page and and is gathering the updates they wish to implement.
* <u>Suggestion</u>: Considering the board's plan to update pages like donate.osm.org, a special committee could be tasked with redesigning the website as a whole.
=== Trails Engagement ===
No updates.
=== SotM US community "Birds of a Feather" session ===
* A spontaneous session took place during State of the Map US 2023, attended by people from Africa, EU, US.
* Questions were raised about whether we are limiting local chapters' ability to generate funds and sustain themselves.
<u>Suggestions stated during that session</u>:
* Providing more context and more localized guidelines for the local chapters process and application.
* Supporting local chapters and communities with financial incentives, grants, and partnerships.
== '''Update to Corporate Membership tiers''' ==
{| role="presentation" class="wikitable"
! <b>Background</b>
|-
| ''Related to the [[Board/Minutes/2022-02-S2S|2022-02-26 and 27]] action item: The board to rework the[[Join_as_a_corporate_member#Membership_levels|Corporate Membership tiers]] [Session: Fundraising] - [[Board/Minutes/2022-02-S2S/Action_items_and_decisions#Action_items_from_2022-02_board_screen-to-screen_meeting|2022-02 screen-to-screen meeting]].''
''The current Corporate Membership tiers are [[Join_as_a_corporate_member|here]] ''([https://wiki.osmfoundation.org/w/index.php?title=Join_as_a_corporate_member&oldid=10875 hist. link]). The Corporate Membership tiers were previously changed in 2016.''
<u>''Related board discussions''</u>
* ''2023-03 [[Advisory_Board/Minutes/2023-03-14#Suggestion_related_to_reworking_the_OSMF_Corporate_Membership_tiers|Suggestion during Advisory Board meeting]].''
|}
Mikel submitted a proposal to the board, outlining the rationale and potential changes we can make to the [[Join_as_a_corporate_member|corporate membership tiers]] at a high level.
The corporate membership tiers:
* Were established 6 years ago.
* They no longer represent our financial needs or the level of support we should expect.
* Only recently we welcomed our first Corporate Member at the highest tier (Platinum - TomTom).
=== Issue ===
* The alignment of corporate membership tiers with their respective benefits has always been somewhat unclear.
=== Suggested changes ===
* Increase the financial contributions for all levels, making them more dependent on the size of the organisation (e.g., revenue, number of employees, or a different metric).
* Open up the Advisory Board optional membership to Silver and Bronze Corporate Members, as their insights would be valuable. ''(Note: currently only Gold and Platinum Corporate Members can have representatives on the Advisory Board)''
=== Other points mentioned ===
* The suggested changes have been discussed on the Advisory Board and other venues.
* As the proposed text was sent to the board yesterday, it would be premature to have a vote now.
=== Next steps ===
* Get feedback from the board over the next couple of weeks.
* Approve the changes through a circular resolution or during the upcoming board meeting.
''Comment by Courtney Williamson (2023 fundraiser) on the board chat that at the bottom of the document shared within the board there is a summary of her notes, which reflect previous conversations with the board and the fundraising committee.''
== '''Support as financial intermediary to regional State of the Map sponsorships''' ==
{| role="presentation" class="wikitable"
! <b>Background</b>
|-
| ''In contrast to the [https://stateofthemap.org/ international State of the Map conferences], [[osm:State_Of_The_Map#Regional.2Flocal_conferences|regional/local conferences]] are not organised by the OpenStreetMap Foundation. They are organised exclusively by local teams, which run their own sponsorship programs and have separate budgets from the Foundation.''
''Big companies usually have complicated procurement systems. For those companies which have OSMF already in their systems, it is easier to send the money to OSMF, which would then act as a financial intermediary.''
''This suggestion was made by a Corporate Member via the [[Advisory_Board|Advisory Board]] in 2018 and the OSMF board [[Board/Minutes/2018-12-20#2018.2FRes14_Decide_for_OSMF_to_administer_payments_to_regional_SotMs|decided at the time]] that "for 2019, OSMF will administer payments to sponsor regional SotM conferences. [[Corporate_Members|Corporate Members]] are eligible to ask OSMF to administer payments. The OSMF treasurer will set an administrative handling fee to manage this service. After 2019, only regional SotMs associated with a Local Chapter will be eligible for this service."''
<u>''Related discussions and circulars''</u>
* ''2019-06-19 [[Board/Minutes/2019-06-19#Supporting_regional_SotMs_through_the_OSMF_ticket_sales_system|Supporting regional SotMs through the OSMF ticket sales system]] (public board meeting discussion)''
|}
The suggestion for OSMF to act as financial intermediary to support regional State of the Map sponsorships was made in response to:
* local event organisers: face challenges in navigating the procurement systems of sponsors.
* sponsors: find it complex to facilitate the sponsorship process and handle payments.
* specific case: the board has an immediate request for this support for SotM EU 2023.
<u>Suggestion</u>: the OSMF to handle the receipt and distribution of funds from larger sponsors to a selection of local events.
This initiative will be integrated into the overall fundraising efforts of the foundation, involving both SotM sponsorships, Corporate Membership, and participation in donation campaigns.
There would be one distribution for all OSMF-related provision of funds, including Corporate Membership, international SotM sponsorship, and sponsorships for local SotMs. We'd have an agreement of what portion is going to local State of the Map events. Subsequently, event organisers would provide us with an invoice for the agreed sponsorship amount, which OSMF would then pay to them.
=== Set of criteria for evaluation of support requests ===
'''Local event organisers have to:'''
* Have approval of using our trademarks for a local SotM event, via a [[SOTM_Quick_Licence|SotM quick licence request]] or by being a Local Chapter.
* Be an entity with a bank account capable of receiving funds from OSMF - not an individual.
* Provide financial disclosure after the event.
* Additionally, the timelines for funding should align with our funders budgeting cycles, as well as with our request.
'''Regional sponsors have to:'''
* Be OSMF Corporate Members.
* Sponsor the international SotM, organised by OSMF.
* Already have OSMF listed in their procurement systems.
'''OSMF should'''
* Implement checks to ensure proper handling of funds.
=== Open questions ===
* Tax burden - getting mix responses even from the same people.
* Considering a small overhead fee to cover administrative burdens in processing transactions.
* Finalising the exact process.
=== Concern ===
* Tax implications for organisers of local SotMs.
** They may face issues if they don't have matching invoices for their sponsorships.
** That sounds like a contractual issue that can be solved.
** Need a proper system in place before negotiating contracts.
=== Suggestions ===
* Check whether the process would be ok tax-wise for the local SotM organisers.
* Prepare clear standard contracts for the sponsors and the event organisers.
<u>Other point mentioned during discussion</u>:
* In general the proposal is very constrained, so it's fine.
=== '''Action item''' ===
'''Mikel Maron to have draft standard contract ready by the next board meeting.'''
== '''Review of entries listed at "insufficient attribution" wiki page, taking potential next steps''' ==
{| role="presentation" class="wikitable"
! <b>Background</b>
|-
| ''Related to action item [https://gitlab.com/osmfoundation/board-action-items/-/issues/62 62]: "Attribution: Start reviewing [[osm:Lacking_proper_attribution|the OSM wiki page regarding lacking proper attribution]], find the worst offenders that are still in active operation"''.
''<u>Related post on community.osm.org</u>''
* ''[https://community.openstreetmap.org/t/lacking-proper-attribution-wiki-page-help-with-a-review-welcomed/100442/1 Lacking proper attribution wiki page - help with a review welcomed]''
|}
Two cases of missing attribution, selected by Mateusz:
* https://www.topozone.com/california (https://opencorpdata.com/us-wa/602975104) and
* https://www.squareyards.com/resale-3-bhk-1400-sq-ft-apartment-in-platinum-park-reach/4313471 (https://www.squareyards.com/contactus)
* They are [[osm:Lacking_proper_attribution|listed]] on the OSM wiki.
* They have
* They have been notified in the past about missing attribution.
* They have postal addresses.
* They are companies.
* Mateusz to draft and send to the entities above a paper letter on behalf of OSMF, asking them to start attributing OSM.
** The letter can be signed by Mateusz, or have no signature at all, or even be an email.
* Mateusz to check with the [[Licensing_Working_Group| Licensing Working Group]] (LWG) on the "love letters" they have prepared ''(template letter to be sent to entities with insufficient OSM attribution).''
* The [[Operations_Working_Group| Operations Working Group]] (OWG) to block their usage of www.osm.org tiles, after sending the letter.
** The companies have already been contacted that they're missing attribution.
=== '''Vote: ask OWG to block the tile usage for these two sites which lack OSM attribution''' ===
{| class="wikitable"
|-
| ''Motion to ask
* https://www.topozone.com/california (https://opencorpdata.com/us-wa/602975104) and
|}
=== '''Action items
* '''Guillaume Rischard to ask the
* '''Mateusz Konieczny to provide
== '''Earmark a budget of 33000 EUR for a vector tile rendering stack such that tiles can be re-rendered minutely''' ==
"Earmark a budget of 33000 EUR for a vector tile rendering stack such that tiles can be re-rendered minutely (the same fashion as now with Mapnik). The tiles shall allow for substantial flexibility for styles while still being performant."
Circular being open for voting during and after the meeting: [[Board/Minutes/2023-07#2023/Res15_Vector_tile_plan_funding|2023/Res15 Vector tile plan funding]]
=== Overview provided ===
* In the 2021 OSMF [[osm:Foundation/Surveys|survey]] the question of whether to implement vector tiles received mixed responses. Answers varied from leaving it to open source efforts to paying for it but avoiding competition with commercial producers.
* We have encouraged other open projects to create machines which create Vector Tiles.
* Nothing exists that can produce minutely-updated vector tiles, that we could use on www.osm.org
* Updating the map immediately on www.osm.org is a significant aspect of mapping, as it incentivises users to contribute more frequently due to the immediate "reward."
{| class="wikitable mw-collapsible"
! <b>Background</b>
|-
|-
|style="text-align: left; background: white;" | <span style="color: black;">
''Some OSM community members think the Board should fund change of the map displayed on openstreetmap.org from raster tiles to vector tiles. bearing in mind the potential cost of such an undertaking, and the possible impact on the OSM ecosystem, in your opinion the Board should:
*
*
*
*
*
|-
|}
=== On the 2021 survey ===
* The 2021 survey is not very representative.
** That was the widest outreach we ever did
** Not perfect, but best snapshot we have of the OSM community.
** It showed under-representation in many parts, but we can say with a lot of confidence that there is under-representation in the OSM community as a whole and not under-representation in the survey.
** The answer was mixed. There was partial support to do nothing and let others work on Vector Tiles, which is what has happened.
* The enthusiasm of SotM 2022 participants is not representative of the community.
=== On specific Vector Tiles project ===
* Paul Norman ''(OWG volunteer)'' wants to work on a Vector Tiles project and the board has not been great at responding to him.
*
* 30K is Paul's
*
'''Motion to earmark EUR
''- It would not mean that we would do the project completely. We would start with the spec, have a formal plan and decide whether to do it.''<br>
''- Would prefer not to come to the board every time the budget changes, so would like to earmark the whole EUR 33,000.''<br>
''- If we approve the whole budget, the circular becomes obsolete.''
=== Concerns ===
* What we have at the moment is insufficient for specification, as it doesn't describe what Vector Tiles are or how the work.
* '''Process:''' It is highly unusual to pay someone to write an application for funding. One usually puts the estimate for the money in the funding plan.
* '''Remit:''' This is in the remit of EWG, and we have a budget for the EWG.
** That was part of the discussion that Guillaume Rischard ''(OSMF chairperson)'' and Roland Olbricht ''(OSMF Treasurer)'' had separately and with Paul Norman. They were concerned this would be too large for the EWG budget (which is around EUR 50,000).
** Roland ''(speaking for EWG and as relayed by Guillaume)'' feels that the project does not belong there. The work that needs to happen is not the work EWG typically does.
** OWG has seen the project and seem to like it.
** It is not unusual for the board to fund projects directly.
* '''Not a time-sensitive issue.'''
** Not needs to happen this week, but we have been discussing this for a while and the board has known for a while.
* Approve
**
* Allocate EUR 2,000 for developing the plan. Once we have it, we can make decisions on the plan and its associated costs.
* It must be very clear that approved funds are intended for the specification and development of a product based on that specification.
* The [[Engineering_Working_Group|Engineering Working Group]] (EWG) to look at this - it is unnecessary to look at this as the board.
* Restrict the funds to the EUR 2,000 for the proposal.
* Communicate the
''Question by Imagico (guest)
> Both.
* It is not the most expensive rate we have paid.
==='''
{| class="wikitable"
|-
|style="text-align: left; background: white;" | <span style="color: black;">
'''Approved''' on 2023-06-29 with '''3 votes in favour''': <u>Craig Allan</u>, <u>Guillaume Rischard</u>, <u>Mikel Maron</u>
'''2 against''': <u>Arnalie Vicario</u>, <u>Sarah Hoffmann</u>.<br>
'''1 abstained''': <u>Mateusz Konieczny</u>.<br>
|}
=== '''Vote: earmark a budget of EUR 2,000 for a Vector Tile rendering stack proposal by Paul Norman''' ===
{| class="wikitable"
|-
| ''
|-
|style="text-align: left; background: white;" | <span style="color: black;">
'''Approved''' on 2023-06-29 with '''3 votes in favour''': <u>Craig Allan</u>, <u>Guillaume Rischard</u>, <u>Mikel Maron</u>
'''2 against''': <u>Arnalie Vicario</u>, <u>Sarah Hoffmann</u>.<br>
'''1 abstained''': <u>Mateusz Konieczny</u>.<br>
''There was a brief discussion during Mateusz' turn to vote on the main motion, on the votes so far and whether his vote would change the outcome.''
== '''Monthly presentation - OSM Cuba community''' ==
{| role="presentation" class="wikitable"
! <b>Previous presentations and about this section</b>
|-
| See [[Monthly_Board_Meetings/Presentations]].
|}
=== Questions and answers ===
''Question by Guillaume Rischard (board): Since the Internet is expensive in Cuba and limited if people get their maps as part of the [https://en.wikipedia.org/wiki/El_Paquete_Semanal El Paquete Semanal], and if other ways of distributing maps offline would be useful for the Cuba community.''
* Not so expensive but the value of the money is less due to inflation.
* Cubans use apps such as OsmAND and maps.me as there are offline maps.
* Paquete is a hard drive with TV series and movies.
* Maps are not in the Paquete.
''Question by Guillaume Rischard (board): Have you heard of Organic Maps, a newer fork of maps.me?''
> No
''Question by Arnalie Vicario (board): Which areas of support or collaboration would you like OSM Foundation to help/discuss with to further you activities in Cuba?''
> Best help to Cuba is to promote the OSM culture. Because people use OsmAND but they don't know where the maps come from or the organisation and people working behind everything.
== '''Any other business''' ==
=== Travel policy ===
Arnalie and Craig to take the topic forward.
== Guest comments or questions ==
''None.''
== Next meetings ==
* 2023-07-13, 1500 UTC ''(Mid-month board chat)''
* [[Board/Minutes/2023-06|2023-07-27]], 1500 UTC ''(Public board meeting)'' - [[Board/Minutes/2023-07|Agenda]]
Open board meetings take place online once a month.
''See the [[Monthly_Board_Meetings| 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.<br>
[[Acronyms]]
| |||