comaps/Governance
21
42
Fork
You've already forked Governance
5

Expanded mission description #139

Closed
gedankenstuecke wants to merge 4 commits from 20260116-mission into main
pull from: 20260116-mission
merge into: comaps:main
comaps:main
comaps:hbond-access
comaps:pastk-AI
comaps:ai_usage
comaps:patepelo-spending
comaps:yannikbloscheck-structure
comaps:oleg-rswll-update-contributors-doc
comaps:oleg-rswll-governance-structure
comaps:zyphlar-patch-1
comaps:github_owner
comaps:oleg-rswll-word-update
comaps:oleg-rswll-patch-1

This PR builds on discussions we had on Zulip and that got started as we tried to define what our plans for 2026 are: comaps/communication#59

I just took the plain text and formatted a bit more, to make the key points stand out.

This current draft has benefited substantially from input & co-writing by @jeanbaptisteC, @zyphlar, @vikiawv, and @patepelo
(sorry if I missed anyone: I think I got everyone who chimed in on Zulip, but if I missed you, e.g. as you edited the initial drafting pad without leaving a name/named feedback, chime in!)

Signed-off-by: gedankenstuecke gedankenstuecke@noreply.codeberg.org

This PR builds on discussions we had on Zulip and that got started as we tried to define what our plans for 2026 are: https://codeberg.org/comaps/communication/issues/59 I just took the plain text and formatted a bit more, to make the key points stand out. This current draft has benefited substantially from input & co-writing by @jeanbaptisteC, @zyphlar, @vikiawv, and @patepelo (sorry if I missed anyone: I think I got everyone who chimed in on Zulip, but if I missed you, e.g. as you edited the initial drafting pad without leaving a name/named feedback, chime in!) Signed-off-by: gedankenstuecke <gedankenstuecke@noreply.codeberg.org>
Signed-off-by: gedankenstuecke <gedankenstuecke@noreply.codeberg.org>
patepelo left a comment
Copy link

+1

+1

This section expands on our mission. It is designed to help with understanding the goals we have for the CoMaps applications and to offer guidance on which things are considered in or out of scope for development.
Other than that, LGTM. Thank you.

*This section expands on our mission. It is designed to help with understanding the goals we have for the CoMaps applications and to offer guidance on which things are considered in or out of scope for development.* Other than that, LGTM. Thank you.
Signed-off-by: gedankenstuecke <gedankenstuecke@noreply.codeberg.org>

I would replace the "shall"s with "should" as that makes it seem less intimidating ("shall" makes it sound like some legal code). Also I would lay off on the bold for the same reason.

Other than that, looks good!

I would replace the "shall"s with "should" as that makes it seem less intimidating ("shall" makes it sound like some legal code). Also I would lay off on the bold for the same reason. Other than that, looks good!
Author
Member
Copy link

I replaced the shall with should!

For the bold: My reasoning was that it helps identifying the key aspects to navigate the text more easily, especially when sharing it with people as feedback to PRs etc :)

I replaced the shall with should! For the bold: My reasoning was that it helps identifying the key aspects to navigate the text more easily, especially when sharing it with people as feedback to PRs etc :)
thesupertechie left a comment
Copy link

Looks good! A +1 from me.

Looks good! A +1 from me.
map-per left a comment
Copy link

👍

👍
hbond left a comment
Copy link

looks great :)

looks great :)
Contributor
Copy link

Maybe we can re-write mission sentence at the beginning of the document?

Maybe we can re-write mission sentence at the beginning of the document?
Author
Member
Copy link

Should we just use this, which is now also below: "Our goal is to create a free and open map and navigation application that respects people's privacy and can be an alternative to commercial solutions for people around the world. "?

Should we just use this, which is now also below: "Our goal is to create a free and open map and navigation application that respects people's privacy and can be an alternative to commercial solutions for people around the world. "?
Author
Member
Copy link

@jeanbaptisteC made the change!

@jeanbaptisteC made the change!
@ -22,0 +30,4 @@
**We want to keep CoMaps easy to use, for everyone and most general map use cases.**
For that reason, we aim to create a "general-purpose" application, by focusing on features that help the experience of many users and their common use cases.
This, in turn, means that CoMaps is not designed to, and will not, support more specialist use cases, such as rare modes of transport).
Owner
Copy link

What do we define as rare modes of transport?
Helicopter? Boat?

What do we define as rare modes of transport? Helicopter? Boat?
Author
Member
Copy link

@zyphlar's example was snowmobiles, but I'm not sure if we need to enumerate that here, as there'll always be individual cases that are neither here nor there.

(Generally, I think these points are for having a shared "big idea" and then help us discuss concrete cases by if they fit with that or not, and not so much for having a "rulebook" if that makes sense 🙂)

@zyphlar's example was snowmobiles, but I'm not sure if we need to enumerate that here, as there'll always be individual cases that are neither here nor there. (Generally, I think these points are for having a shared "big idea" and then help us discuss concrete cases by if they fit with that or not, and not so much for having a "rulebook" if that makes sense 🙂)
Owner
Copy link

Indeed, it might raise unnecessary questions (is a moped or a caravan is considered rare and won't be ever supported?). IMO just drop the such as rare modes of transport.

Indeed, it might raise unnecessary questions (is a moped or a caravan is considered rare and won't be ever supported?). IMO just drop the `such as rare modes of transport`.
pastk left a comment
Copy link

Basically the following important app qualities had been covered, which is great!

  • easy to use and simple
  • offline-first
  • open data and two-way integration with these ecosystems

IMO need to add and expand on:

  • privacy focus (only remote connections are mentioned so far, add no tracking and no collection of personal info and we make a reasonable effort to protect it from third parties)
  • free and no ads and no nagging (respectful)
  • fast and light on resources and battery
  • fully FOSS (auditable, distributable, no vendor lock-in, etc.)
  • interoperable via open formats/standards (combine with open data?)
Basically the following important app qualities had been covered, which is great! - easy to use and simple - offline-first - open data and two-way integration with these ecosystems IMO need to add and expand on: - privacy focus (only remote connections are mentioned so far, add no tracking and no collection of personal info and we make a reasonable effort to protect it from third parties) - free and no ads and no nagging (respectful) - fast and light on resources and battery - fully FOSS (auditable, distributable, no vendor lock-in, etc.) - interoperable via open formats/standards (combine with open data?)
@ -5,3 +5,3 @@
**Mission** (provisional)
Provide easy navigating offline for drivers, hikers, and cyclists, with privacy-focus and open-source, made by and for the community.
Our goal is to create a free and open map and navigation application that respects people's privacy and can be an alternative to commercial solutions for people around the world.
Owner
Copy link

I like that too detailed and limiting for drivers, hikers, and cyclists had been generalized!
I think that made by and for the community should stay in some form.

I suggest
Provide an open map and navigation software for people around the world that respects privacy and is a free community-based alternative to commercial solutions.

I like that too detailed and limiting `for drivers, hikers, and cyclists` had been generalized! I think that `made by and for the community` should stay in some form. I suggest `Provide an open map and navigation software for people around the world that respects privacy and is a free community-based alternative to commercial solutions.`
Author
Member
Copy link

Good idea, I'd prefer community-created over based if you're okay with that?

Good idea, I'd prefer `community-created` over `based` if you're okay with that?
Owner
Copy link

Its better indeed!

Its better indeed!
Owner
Copy link

I think it'd be better to have a separate PR for this and perhaps address feedback from #70 and #94.
I'll give it a go

I think it'd be better to have a separate PR for this and perhaps address feedback from #70 and #94. I'll give it a go
Owner
Copy link

#149

https://codeberg.org/comaps/Governance/pulls/149
@ -19,6 +19,32 @@ A world in which the top choice for navigation software is free and developed th
6. **Community Funding**: the primary method of funding is donations from the community. This doesn't exclude grants, or potential B2B-level products in the future, as long as they adhere to the principles, are approved by the community and don't diminish the free and open nature of the project.
7. **Assets for Public Interest**: any assets created or acquired are owned by the community and for its benefit. Core assets that constitute project's identity can't be sold, this includes, but is not limited to domains, trademarks, app stores accounts, social media accounts, etc.
## Our software's mission
Owner
Copy link

Actually the text below focuses on "why" not on "what".
So its not a mission, but an explanation / rationale why the mission is such and not something else and how to keep it such :)

So its better to come up with a more fitting title..
Core qualities of user-facing CoMaps apps?
Principles of CoMaps apps development?

Actually the text below focuses on "why" not on "what". So its not a mission, but an explanation / rationale why the mission is such and not something else and how to keep it such :) So its better to come up with a more fitting title.. `Core qualities of user-facing CoMaps apps`? `Principles of CoMaps apps development`?
Author
Member
Copy link

Maybe "Putting our mission into practice"? In reality the text tries to operationalize that very high-level summary of the mission into concrete(r) decisions we agree on for the development/ways we work.

Maybe "Putting our mission into practice"? In reality the text tries to operationalize that very high-level summary of the mission into concrete(r) decisions we agree on for the development/ways we work.
Owner
Copy link

"Putting our mission into practice" is good, but misses on point that this section is about user-facing app things, while there is an organisational aspect of "Putting our mission into practice" too

"Putting our mission into practice" is good, but misses on point that this section is about user-facing app things, while there is an organisational aspect of "Putting our mission into practice" too
@ -22,0 +24,4 @@
> [!Note]
> This section expands on our mission. It is designed to help with understanding the goals we have for the CoMaps applications and to offer guidance on which things are considered in or out of scope for development.
Our goal is to create a free and open map and navigation application that respects people's privacy and can be an alternative to commercial solutions for people around the world.
Owner
Copy link

Why duplicate the mission statement from above?

Why duplicate the mission statement from above?
Author
Member
Copy link

As @jeanbaptisteC suggested to keep a one-sentence summary that reflects the "updated" longer version.

As @jeanbaptisteC suggested to keep a one-sentence summary that reflects the "updated" longer version.
Owner
Copy link

If we follow the bullet points structure then we'd have a good enumerated overview already. Just like the "core principles" section doesn't really need a one-sentence summary, it just follows and expands on prior mission and vision.

If we follow the bullet points structure then we'd have a good enumerated overview already. Just like the "core principles" section doesn't really need a one-sentence summary, it just follows and expands on prior mission and vision.
@ -22,0 +28,4 @@
To achieve this, we focus on these aspects when developing and implementing features in CoMaps:
**We want to keep CoMaps easy to use, for everyone and most general map use cases.**
Owner
Copy link

IMO making it a bullet or numbered list (like core principles above) will make it easier to skim through and also more consistent with project's principles.

IMO making it a bullet or numbered list (like core principles above) will make it easier to skim through and also more consistent with project's principles.
@ -22,0 +43,4 @@
To ensure its long-term maintainability and sustainability, CoMaps **prioritizes open data for all of its current and future data sources**, as not-openly-licensed data sources, even if "free" to use right now, are always at risk of disappearing (either due to licensing changes or outright closure).
For this reason, CoMaps should also **be a good "open source citizen"** that allows its users to contribute to the commons-based data sets we rely on.
As part of our commitment to working in a way that is sustainable with respect to our volunteer time, we are also prioritising platform and distribution channels, **focusing on widely-used and value-aligned platforms**.
Owner
Copy link

I'm not sure I understand this one. E.g. do we consider GPlay and AppStore to be value-aligned?

I'm not sure I understand this one. E.g. do we consider GPlay and AppStore to be value-aligned?
Author
Member
Copy link

No, the subtle difference is that we don't prioritize or focus on those, but also support them to reach more people.

E.g.

  • the first/prioritized distribution channel (at least for Android, for iOS there's lamentably no alternative in most places) via Codeberg before pushing it to non-aligned distribution channels.
  • Similarly, our development happens here, though we do maintain a mirror on GitHub.
  • And we do post our communications to non-aligned platforms like Telegram, Reddit or Bluesky, but put priority on open/aligned alternatives like Matrix or Mastodon.
No, the subtle difference is that we don't prioritize or focus on those, but _also_ support them to reach more people. E.g. * the first/prioritized distribution channel (at least for Android, for iOS there's lamentably no alternative in most places) via Codeberg before pushing it to non-aligned distribution channels. * Similarly, our development happens here, though we do maintain a mirror on GitHub. * And we do post our communications to non-aligned platforms like Telegram, Reddit or Bluesky, but put priority on open/aligned alternatives like Matrix or Mastodon.
Owner
Copy link

Then perhaps it should be focusing on value-aligned or widely-used platforms?
Also it'd be nice to somehow make more clear that "platforms" mentioned are not about app stores (covered by "distribution channels" already), but about cross-platform apps availability.

Not sure we want to mention SM and software forge here, as the idea was to limit it to user-facing stuff? (what not how)

Then perhaps it should be `focusing on value-aligned or widely-used platforms`? Also it'd be nice to somehow make more clear that "platforms" mentioned are not about app stores (covered by "distribution channels" already), but about cross-platform apps availability. Not sure we want to mention SM and software forge here, as the idea was to limit it to user-facing stuff? (what not how)
Author
Member
Copy link

closed in favor of letting @pastk make his changes

closed in favor of letting @pastk make his changes

Pull request closed

Please reopen this pull request to perform a merge.
Sign in to join this conversation.
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
11 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
comaps/Governance!139
Reference in a new issue
comaps/Governance
No description provided.
Delete branch "20260116-mission"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?