Mikel Maron
    • Create new note
    • Create a note from template
      • Sharing URL Link copied
      • /edit
      • View mode
        • Edit mode
        • View mode
        • Book mode
        • Slide mode
        Edit mode View mode Book mode Slide mode
      • Customize slides
      • Note Permission
      • Read
        • Only me
        • Signed-in users
        • Everyone
        Only me Signed-in users Everyone
      • Write
        • Only me
        • Signed-in users
        • Everyone
        Only me Signed-in users Everyone
      • Engagement control Commenting, Suggest edit, Emoji Reply
      • Invitee
    • Publish Note

      Share your work with the world Congratulations! 🎉 Your note is out in the world Publish Note

      Your note will be visible on your profile and discoverable by anyone.
      Your note is now live.
      This note is visible on your profile and discoverable online.
      Everyone on the web can find and read all notes of this public team.
      See published notes
      Unpublish note
      Please check the box to agree to the Community Guidelines.
      View profile
    • Commenting
      Permission
      Disabled Forbidden Owners Signed-in users Everyone
    • Enable
    • Permission
      • Forbidden
      • Owners
      • Signed-in users
      • Everyone
    • Suggest edit
      Permission
      Disabled Forbidden Owners Signed-in users Everyone
    • Enable
    • Permission
      • Forbidden
      • Owners
      • Signed-in users
    • Emoji Reply
    • Enable
    • Versions and GitHub Sync
    • Note settings
    • Engagement control
    • Transfer ownership
    • Delete this note
    • Save as template
    • Insert from template
    • Import from
      • Dropbox
      • Google Drive
      • Gist
      • Clipboard
    • Export to
      • Dropbox
      • Google Drive
      • Gist
    • Download
      • Markdown
      • HTML
      • Raw HTML
Menu Note settings Sharing URL Create Help
Create Create new note Create a note from template
Menu
Options
Versions and GitHub Sync Engagement control Transfer ownership Delete this note
Import from
Dropbox Google Drive Gist Clipboard
Export to
Dropbox Google Drive Gist
Download
Markdown HTML Raw HTML
Back
Sharing URL Link copied
/edit
View mode
  • Edit mode
  • View mode
  • Book mode
  • Slide mode
Edit mode View mode Book mode Slide mode
Customize slides
Note Permission
Read
Only me
  • Only me
  • Signed-in users
  • Everyone
Only me Signed-in users Everyone
Write
Only me
  • Only me
  • Signed-in users
  • Everyone
Only me Signed-in users Everyone
Engagement control Commenting, Suggest edit, Emoji Reply
Invitee
Publish Note

Share your work with the world Congratulations! 🎉 Your note is out in the world Publish Note

Your note will be visible on your profile and discoverable by anyone.
Your note is now live.
This note is visible on your profile and discoverable online.
Everyone on the web can find and read all notes of this public team.
See published notes
Unpublish note
Please check the box to agree to the Community Guidelines.
View profile
Engagement control
Commenting
Permission
Disabled Forbidden Owners Signed-in users Everyone
Enable
Permission
  • Forbidden
  • Owners
  • Signed-in users
  • Everyone
Suggest edit
Permission
Disabled Forbidden Owners Signed-in users Everyone
Enable
Permission
  • Forbidden
  • Owners
  • Signed-in users
Emoji Reply
Enable
Import from Dropbox Google Drive Gist Clipboard
   owned this note    owned this note      
Published Linked with GitHub
Subscribed
  • Any changes
    Be notified of any changes
  • Mention me
    Be notified of mention me
  • Unsubscribe
Subscribe
1. --- tags: osmf --- # Corporate Membership Revision The OpenStreetMap Foundation will revise the corporate membership levels to align more with scale of corporate operation than strictly with benefits, and update amounts of tiers to reflect updated financial picture. ## Rationale Corporate Membership tiers were set 6 years ago, and no longer reflect financial needs of the OSMF nor expectations of level of support from companies. The benefits have not been a clear fit for the levels of support. The level at which members join should be more aligned with the size of their operation. We only recently signed on our first top tier member, yet the top tier should be the default for the other large company members. One of the key benefits has been advisory board membership, but by limiting this to the higher tiers we miss out on advice from small and medium enterprises which are an important consituency. Overall, membership should be framed as a valuable way to support OSM, and be highlighted alongside adjacent ways to support like donations and pro bono volunteers ## Changes * Increase all levels by 50% * The levels are associated with the size of operation and product footprint that benefits from OSM. * Rather than hard numbers (X revenue, Y employees), use descriptive terms that reflect expectations ("mapping applications is core to your substantial business with a global footprint -- choose platinum"; you are a small business with an established used of OSM, choose silver; you are just getting started with OSM, choose bronze" ) * Present Supporter level in a somewhat different light than other tiers (you can also show your support..) * Simplify and somewhat decouple benefits. * Presence on OSMF website for all levels, scaled to level of support. * Link to members should be at most 2 clicks away from osm.org default banner and about page * All levels get Advisory Board except Supporter * Drop "First access to SotM sponsor opportunities" * Make press-release gold level * Change platinum level "Invite a board member for an in-house presentation" to "Consultations with board-designated facilitator to share direction on how to engage with OSM/OSMF on specific topics" * With more groups in the advisory board, create three different sub lists (advisory-localchapter, advisory-silverbronze, advisory-platinumgold), all of which receive email to existing general advisory board list. Gives us the option to address the groups distinctly if needed. * Give an optional grace period for current members for their next renewal to be at the previous cost. But strongly encourage them to go to new rates, or a higher level (while acknowledging companies that have already gone above and beyond). * When ready, offer bundled State of the Map and regional State of the Map, as well as donation campaign or "add ons" to a complete funding package aligned with membership. ## Questions * What is the right metric for assessment of tier? Revenue, number of employees? A strict rubric or guidelines? * Rather than hard numbers (X revenue, Y employees), use descriptive terms that reflect expectations ("mapping applications is core to your substantial business with a global footprint -- choose platinum"; you are a small business with an established used of OSM, choose silver; you are just getting started with OSM, choose bronze" ) * What is the right level of increase? * 50% is substantial and reasonable * How do we handle corporate memberships that are in arrears? * On a monthly basis, corporate membership invoices that are overdue by 3 months are reviewed. * Supporter and bronze level are informed they will lose status unless paid within 1 month. * Silver and above are kindly reminded on a monthly basis until 6 months have elapsed without payment or pathway to resolution, then they are informed of loss of status. * If a member is responsive but there are difficulties with administering payment (ie procurement system difficulties, budget delay), the Board may choose to allow for a longer grace period. * Any members that lose status are also informed they are welcome to join again in the future if their circumstances change. ## Steps from Here * [x] Present to Board for discussion at June 2023 Board meeting. * [x] Incorporate feedback and present this plan for approval at July 2023 Board meeting or in circular. * [ ] Following approval, make changes to corporate membership page, blog post and communicate new tiers # Previous Notes (from Courtney) Here is a summary of thinking re: the recommendation to change the corporate membership levels: I proposed some changes to the corporate membership text. I got feedback from you, the board, and Mikel put out some questions to advisory committee members. I then did a revised version of the proposed text that is reflective of the board's feedback and some of the corporate feedback. The revision was approved, but not the tiers, pending further consideration. Here are some comments on the proposal, tiers, and the advisory committee feedback: We could "carve out" those who got advisory seats for the Gold level in 2023. Then, in 2024, the companies who want to keep their seat will need to give at the Platinum level. They will get more than a year of notice, which is plenty, and we should encourage them to upgrade early. It was suggested that access to Working Groups would be appreciated. This doesn't have to create a burden of time, because such access may even reduce errors made by corporations. The process for this can be made very transparent: For example: "send an email with your precise questions and a member of the Working Group will contact you within XX days of your request to discuss." The board can be clear that a seat on the advisory committee is a privilege that comes with the expectation of collaboration. The committee should help the board, not be a burden on it, and vice versa. The committee could even nominate a coordinator who can set meetings and agendas and report meeting minutes. Angelina proposed deemphasizing benefits. This has a lot of merit. You could simply say "membership in the OSMF is encouraged for all companies who use OSM. We recommend a membership fee based on the size of your company." Tiers could then simply be tied to the company's size or revenue, or some other objective measure. It would be simple and transparent. Regarding people who want more outreach from the board/wanting less antagonism from the board. I might suggest that 'less antagonism' is equal to or more important than "more outreach." It's all in *how* things are said, not *what* is said. For example, it is not antagonistic to point out that the attribution is being done incorrectly or that a company is editing improperly, but it is antagonistic to imply that the company was intentionally obtuse and/or is the definition of evil. Members of the CWG can help the board when it needs to say something tough, but fair, to a company, especially in public forums. People like the idea of a press release or blog post as part of their membership. This is not a hard thing for the CWG to deliver. A "clear line of site" to the impact of the donation is important. I think we agree on this and I think clearing up the language on the pages and in the renewal letters will help a lot. Related: a stable, annual membership fee over a multi-year cycle is easier to support than 'ad hoc' requests. "It would be much easier for us to pay for a membership, a SOTM sponsorship and possibly an additional donation (for example to support infra) at one time rather than having to do three separate transactions." We heard this a couple of times from the advisory committee. It's hard to get a purchase order and it's easier to have one line item in a budget than several. --Courtney .... Hi, again, Having had time to think about it, I think that changing to a recommendation based on the company's size is a strong idea for a couple of reasons. 1. It can be more closely tied to the obligation for attribution so that the message becomes something like: "If you use OSM data, you must attribute it, and our strong suggestion is that you also support the project commensurate with your organization's annual revenue." 2. It's confident. It says "look, you're benefiting, you need to support." Instead of "if you support us, we will do nice things for you." It's a better approach for an organization that isn't ever going to have major gifts officers who can continuously cultivate each year's gift. 3. We can easily put this out to the many small orgs that use OSM with a request to identify the appropriate level and join as members. We should still tweak the language about "what is the advisory board" and who gets to be on it. C

Import from clipboard

Paste your markdown or webpage here...

Advanced permission required

Your current role can only read. Ask the system administrator to acquire write and comment permission.

This team is disabled

Sorry, this team is disabled. You can't edit this note.

This note is locked

Sorry, only owner can edit this note.

Reach the limit

Sorry, you've reached the max length this note can be.
Please reduce the content or divide it to more notes, thank you!

Import from Gist

Import from Snippet

or

Export to Snippet

Are you sure?

Do you really want to delete this note?
All users will lose their connection.

Create a note from template

Create a note from template

Oops...
This template has been removed or transferred.
Upgrade
All
  • All
  • Team
No template.

Create a template

Upgrade

Delete template

Do you really want to delete this template?
Turn this template into a regular note and keep its content, versions, and comments.

This page need refresh

You have an incompatible client version.
Refresh to update.
New version available!
See releases notes here
Refresh to enjoy new features.
Your user state has changed.
Refresh to load new user state.

Sign in

Forgot password

or

By clicking below, you agree to our terms of service.

Sign in via Facebook Sign in via Twitter Sign in via GitHub Sign in via Dropbox Sign in with Wallet
Wallet ( )
Connect another wallet

New to HackMD? Sign up

Help

  • English
  • 中文
  • Français
  • Deutsch
  • 日本語
  • Español
  • Català
  • Ελληνικά
  • Português
  • italiano
  • Türkçe
  • Русский
  • Nederlands
  • hrvatski jezik
  • język polski
  • Українська
  • हिन्दी
  • svenska
  • Esperanto
  • dansk

Documents

Help & Tutorial

How to use Book mode

Slide Example

API Docs

Edit in VSCode

Install browser extension

Contacts

Feedback

Discord

Send us email

Resources

Releases

Pricing

Blog

Policy

Terms

Privacy

Cheatsheet

Syntax Example Reference
# Header Header 基本排版
- Unordered List
  • Unordered List
1. Ordered List
  1. Ordered List
- [ ] Todo List
  • Todo List
> Blockquote
Blockquote
**Bold font** Bold font
*Italics font* Italics font
~~Strikethrough~~ Strikethrough
19^th^ 19th
H~2~O H2O
++Inserted text++ Inserted text
==Marked text== Marked text
[link text](https:// "title") Link
![image alt](https:// "title") Image
`Code` Code 在筆記中貼入程式碼
```javascript
var i = 0;
```
var i = 0;
:smile: :smile: Emoji list
{%youtube youtube_id %} Externals
$L^aT_eX$ LaTeX
:::info
This is a alert area.
:::

This is a alert area.

Versions and GitHub Sync
Get Full History Access

  • Edit version name
  • Delete

revision author avatar     named on  

More Less

Note content is identical to the latest version.
Compare
    Choose a version
    No search result
    Version not found
Sign in to link this note to GitHub
Learn more
This note is not linked with GitHub
 

Feedback

Submission failed, please try again

Thanks for your support.

On a scale of 0-10, how likely is it that you would recommend HackMD to your friends, family or business associates?

Please give us some advice and help us improve HackMD.

 

Thanks for your feedback

Remove version name

Do you want to remove this version name and description?

Transfer ownership

Transfer to
    Warning: is a public team. If you transfer note to this team, everyone on the web can find and read this note.

      Link with GitHub

      Please authorize HackMD on GitHub
      • Please sign in to GitHub and install the HackMD app on your GitHub repo.
      • HackMD links with GitHub through a GitHub App. You can choose which repo to install our App.
      Learn more  Sign in to GitHub

      Push the note to GitHub Push to GitHub Pull a file from GitHub

        Authorize again
       

      Choose which file to push to

      Select repo
      Refresh Authorize more repos
      Select branch
      Select file
      Select branch
      Choose version(s) to push
      • Save a new version and push
      • Choose from existing versions
      Include title and tags
      Available push count

      Pull from GitHub

       
      File from GitHub
      File from HackMD

      GitHub Link Settings

      File linked

      Linked by
      File path
      Last synced branch
      Available push count

      Danger Zone

      Unlink
      You will no longer receive notification when GitHub file changes after unlink.

      Syncing

      Push failed

      Push successfully