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
--- tags: osmf --- # 2023 on the OSMF Board: Our individual views The new Board met together earlier this month for our informal mid month chat. The first item we discussed was the work each of us wanted to drive forward in 2023. What emerged was a quick and rough edge work in progress agenda for the year, with good distribution of focus areas. We're going to keep developing and refining our ideas, including we hope in a short half day screen to screen soon. Here is a few rough sentences from each of us about where our heads are at and where we want to contribute in 2023. We welcome your input and participation: [contact us](https://wiki.osmfoundation.org/wiki/Officers_%26_Board) or if you are an OSMF Member, join our [monthly Board meeting](https://wiki.osmfoundation.org/wiki/Monthly_Board_Meetings). ### _Mikel_: Fundraising is my top priority, to support our core staff and infrastructure in a sustainable way. We will have a dedicated fundraising campaign across diversified sources including community small donor campaign, public and private grants, and with the corporate sector. Second, I will focus on making OSMF a great place to work, continuing to implement the necessary process and structure, and supporting them to be successful. Finally, as secretary give OSMF a professional, responsive communication tone. The more I think about it, excellent communication is the key to so much -- from our fundraising, reputation, and community growth. ### _Sarah_: I'd like to focus this year on making the daily operations of OSMF run more smoothly, so that the board has more time in the future to focus on strategic matters. This includes yearly planning and budget, smoothly running communications to and from the board and a financial plan where the majority of our operational cost is covered through regular income. I also hope to get some wisdom from our working groups to understand how we can help each other to spread the work more efficiently on more shoulders. ### _Guillaume_: * moving to EU * better communication * liquid democracy process for tagging * financial planning and budgeting * fundraising diversity * with Grant, increase infrastructure reliability ### _Arnalie_: For my first year at OSMF Board, I would like to focus on: * Building more local chapters * Diversifying OSMF membership including membership at OSMF Working Groups * Ensure financial sustainability and fundraising (an aspect I need to learn more/develop personally) ### _Roland_: Fundraising is the most important thing to do right now. We need money both for long-awaited improvements and daily operations, and our traditional sources of income from individual and corporate members do not even cover daily operations. At the same time, the Overture announcement has made clear that some data consumers are willing to spend money on reliable map data. So one building block is to adjust the corporate membership levels. The other is to raise money for improvement projects or even completely new projects. The past has shown that it is more viable to get money for concrete ideas than for an abstract fund. As the board works on behalf of the community, I will bring project ideas into discussion and listen for existing project ideas in the community that are concrete enough for a cost estimation such that we have a list of project ideas to excite potential donors for. I do not expect that every project gets funding, but I do want that every potential funding finds an impactful project to be spent on. ### _Craig_: Now, a month in, I'm getting some traction on my [election promises](https://wiki.openstreetmap.org/wiki/Foundation/AGM2022/Election_to_Board/Answers_and_manifestos/Q03_What_would_you_personally_like_to_achieve_when_on_the_board). I want to help OSMF build up the mapping community and support and encourage existing community leaders. My special effort will be in Africa. I'm keen to prioritise the OSMF diversity and inclusion programme. I have some ideas, but it must be done as a collective effort. For tech I'd like to support OSMF documenting its computer operations, updating and improving the software, look at data structures, promote vector map tiles and keep the hardware up to date and reliable. I'm making an effort to support the administration in a professional way. I'll work on Strategic Planning, Budgeting, Fundraising, Communication. ### _Mateusz_: For start, it is necessary to keep basic things running - applies to OSM as community, servers and critical software. Hopefully only routine activities will be needed here. I am working on human-readable budget summary - needed for both OSMF board, transparency reasons and people interested in what OSMF is actually doing. Especially ones that would potentially donate. GDPR handling is stuck in limbo - and it is responsibility of OSMF board to organise handling of this annoying task. I also want to take action on enforcing attribution requirements. # 2023 board programme (draft!! -- for future communication) ##### Objective: To ensure the sustainable growth and success of the OpenStreetMap project by focusing on fundraising, improving operations, and fostering a positive work environment while increasing staffing, setting up predictable frameworks and improving communication with the community. ##### Actions: * Fundraising: Implement a dedicated fundraising campaign across diversified sources including community small donor campaign, public and private grants, and corporate sector to support the staff, projects and infrastructure of OSMF. * Work Environment: Make OSMF a great place to work by implementing necessary process and structure, and supporting staff to be successful. * Communication: Adopt a professional and responsive communication tone as secretary to give OSMF a professional, responsive communication tone. * Operations: Improve daily operations of OSMF to run more smoothly, including yearly planning, budgeting, and efficient communication to and from the board. * Financial Plan: Develop a budget and financial plan based on to cover majority of operational cost through regular income. * Wisdom from Working Groups: Gain wisdom from working groups to understand how to spread work more efficiently among more people. * Staffing: Increase staffing to cover day-to-day work, to increase operations reliability, allow the board to focus on strategic planning, and let working group volunteers concentrate on community work. The new staff will include an executive director. * Project Frameworks: Set up predictable frameworks to support and fund both internal and external projects. * Data Model: Discuss what the next steps of modernising our data model should be. * Community Communication: Communicate better and more often with the community, allowing it better input in the strategic planning process. Add (?): strategic plan, overture, visual budget, what else did I miss? No unanimity: attribution, what else?

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