organicmaps/organicmaps-tmp

Archived

[docs] Add Core Values doc #9905

Open

pastk wants to merge 1 commit from pastk-docs-values into master

pastk commented

2024-12-19 20:15:06 +00:00

Member

These Core Values should be agreed upon by most of OM contributors and users.
They unite us and set the main direction of the project.

Hence they need a wide discussion - if some point faces a strong opposition and an agreement couldn't be reached then likely it should be excluded from the values.

These Core Values should be agreed upon by most of OM contributors and users. They unite us and set the main direction of the project. Hence they need a wide discussion - if some point faces a strong opposition and an agreement couldn't be reached then likely it should be excluded from the values.

pastk reviewed 2024-12-19 20:16:37 +00:00

pastk commented

2024-12-19 20:16:37 +00:00

Author

Member

Personally I'd like it to be
"All communication channels and documents are public. Private data (names, bank account number, etc.) and credentials (passwords, etc.) are the only data stored in a private space and redacted from documents."
but at the moment we're far from being there..

Personally I'd like it to be "All communication channels and documents are public. Private data (names, bank account number, etc.) and credentials (passwords, etc.) are the only data stored in a private space and redacted from documents." but at the moment we're far from being there..

pastk reviewed 2024-12-19 20:17:43 +00:00

pastk commented

2024-12-19 20:17:43 +00:00

Author

Member

I'm planning to link to a detailed privacy disclosure document from here.
Its WIP.

I'm planning to link to a detailed privacy disclosure document from here. Its WIP.

rtsisyk reviewed 2024-12-19 22:48:51 +00:00

rtsisyk commented

2024-12-19 22:48:51 +00:00

Owner

Thanks for creating this. Please allow me to share the initial founding document back from Jan 2021 that definitely covered this section.

Thanks for creating this. Please allow me to share the initial founding document back from Jan 2021 that definitely covered this section.

rtsisyk reviewed 2024-12-19 23:03:50 +00:00

rtsisyk commented

2024-12-19 23:03:50 +00:00

Owner

Hey, here is an entire section from the original project charter, drafted in the early Jan and shared with all newcomers via Google Drive as early as on Jan 18, 2021. The "No MIT yet" folks probably missed it. The lingua franca in that initial group wasn't English, so below is ChatGPT translated version (can be slightly wrong). I will share the original doc later.

Principles

We want to continue developing the project as an open-source initiative under the Apache 2.0 license. In the context of the fork, we are removing the requirement for transferring all rights to the code to the "owners" (i.e., Mail.Ru Group -> Daegu Limited). Instead, we will retain all rights to the code with the developers and require licensing under Apache 2.0. This change is intended to simplify community involvement in the project and make it practically impossible to re-license and/or "close" the project without the authors' consent.
The open development approach does not exclude the possibility that we will monetize the app in the future in various ways while maintaining honor, dignity, and respect for users.

Allowed:

Donations.
Expanding user capabilities for a fee.
Selling various tours and guides.
Subscriptions for something useful to the user.
Partner integrations in relevant areas—booking, taxis, tours, guides, etc.
Highlighting objects on the map.

Not Allowed:

Intrusive advertising for the sake of advertising—full-screen banners, overlaying the map with banners, irrelevant AdWords.
Disabling existing features to move them to a paid version.
Any deliberate degradation of UX and user experience.
Blatant scams.

Everything else falls into a gray area—discussed jointly with the team and decided upon based on how it aligns with our moral and ethical principles.

Please don't scream about Kayak again - it wasn't seen as an issue at that time, but we can adjust based on the current vision, four years later.

Hey, here is an entire section from the original project charter, drafted in the early Jan and shared with all newcomers via Google Drive as early as on Jan 18, 2021. The "No MIT yet" folks probably missed it. The lingua franca in that initial group wasn't English, so below is ChatGPT translated version (can be slightly wrong). I will share the original doc later. # Principles We want to continue developing the project as an open-source initiative under the Apache 2.0 license. In the context of the fork, we are removing the requirement for transferring all rights to the code to the "owners" (i.e., Mail.Ru Group -> Daegu Limited). Instead, we will retain all rights to the code with the developers and require licensing under Apache 2.0. This change is intended to simplify community involvement in the project and make it practically impossible to re-license and/or "close" the project without the authors' consent. The open development approach does not exclude the possibility that we will monetize the app in the future in various ways while maintaining honor, dignity, and respect for users. ## Allowed: - Donations. - Expanding user capabilities for a fee. - Selling various tours and guides. - Subscriptions for something useful to the user. - Partner integrations in relevant areas—booking, taxis, tours, guides, etc. - Highlighting objects on the map. ## Not Allowed: - Intrusive advertising for the sake of advertising—full-screen banners, overlaying the map with banners, irrelevant AdWords. - Disabling existing features to move them to a paid version. - Any deliberate degradation of UX and user experience. - Blatant scams. Everything else falls into a gray area—discussed jointly with the team and decided upon based on how it aligns with our moral and ethical principles. ----------------------- Please don't scream about Kayak again - it wasn't seen as an issue at that time, but we can adjust based on the current vision, four years later.

rtsisyk reviewed 2024-12-19 23:10:38 +00:00

rtsisyk commented

2024-12-19 23:10:38 +00:00

Owner

. Private data (names, bank account number, etc.) and credentials (passwords, etc.) are the only data stored in a private space and redacted from documents." but at the moment we're far from being there..

Please don't stretch it too far. The data management requires more comprehensive policy, where the TOC alone will be on 5 pages. Let's focus on the values and leave the security compliance for another document.

> . Private data (names, bank account number, etc.) and credentials (passwords, etc.) are the only data stored in a private space and redacted from documents." but at the moment we're far from being there.. Please don't stretch it too far. The data management requires more comprehensive policy, where the TOC alone will be on 5 pages. Let's focus on the values and leave the security compliance for another document.

rtsisyk reviewed 2024-12-19 23:11:48 +00:00

rtsisyk commented

2024-12-19 23:11:48 +00:00

Owner

I'm planning to link to a detailed privacy disclosure document from here.
Its WIP.

I would start with the actual legally right privacy policy first. The current one is a joke, even if it is right.

> I'm planning to link to a detailed privacy disclosure document from here. > Its WIP. I would start with the actual legally right privacy policy first. The current one is a joke, even if it is right.

rtsisyk reviewed 2024-12-19 23:31:43 +00:00

rtsisyk commented

2024-12-19 23:31:43 +00:00

Owner

I, personally, want to highlight that the development activities should be performed using public channels, just to kill this endless Telegram DM story. We have GitHub and it works well. There was Slack and it also worked well. Yes, I know that we don't like Salesforce today, but Zulip is probably a viable alternative too.

I, personally, want to highlight that the development activities should be performed using public channels, just to kill this endless Telegram DM story. We have GitHub and it works well. There was Slack and it also worked well. Yes, I know that we don't like Salesforce today, but Zulip is probably a viable alternative too.

pastk reviewed 2024-12-20 11:28:26 +00:00

pastk commented

2024-12-20 11:28:26 +00:00

Author

Member

Yeap this is about development-related discussions, not compliance etc.

The current version "The project endeavours to have little hierarchy in its governance and to conduct as much discussion in public as possible." is short and good enough?

Yeap this is about development-related discussions, not compliance etc. The current version "The project endeavours to have little hierarchy in its governance and **to conduct as much discussion in public as possible.**" is short and good enough?

pastk reviewed 2024-12-20 11:34:02 +00:00

pastk commented

2024-12-20 11:34:02 +00:00

Author

Member

I would start with the actual legally right privacy policy first.

Sure! But its likely to be two related but different documents: a legal privacy policy and a detailed technical disclosure.

> I would start with the actual legally right privacy policy first. Sure! But its likely to be two related but different documents: a legal privacy policy and a detailed technical disclosure.

pastk reviewed 2024-12-20 11:39:37 +00:00

pastk commented

2024-12-20 11:39:37 +00:00

Author

Member

Hey, here is an entire section from the original project charter

Thanks for sharing this!
I'll think how to best integrate points from there into the Core Values and other docs!

> Hey, here is an entire section from the original project charter Thanks for sharing this! I'll think how to best integrate points from there into the Core Values and other docs!

rtsisyk reviewed 2024-12-20 13:32:14 +00:00

rtsisyk commented

2024-12-20 13:32:14 +00:00

Owner

Hey, here is an entire section from the original project charter

Thanks for sharing this! I'll think how to best integrate points from there into the Core Values and other docs!

Yeah, the original doc wasn't bad. Let's try to cover one issue in one document. Values here.

> > Hey, here is an entire section from the original project charter > > Thanks for sharing this! I'll think how to best integrate points from there into the Core Values and other docs! Yeah, the original doc wasn't bad. Let's try to cover one issue in one document. Values here.

oleg-rswll reviewed 2024-12-21 05:01:54 +00:00

oleg-rswll commented

2024-12-21 05:01:54 +00:00

Member

By doing this process here, this limits contribution to primarily developers, and excludes non-developers.

By doing this process here, this limits contribution to primarily developers, and excludes non-developers.

pastk reviewed 2024-12-21 10:38:19 +00:00

pastk commented

2024-12-21 10:38:19 +00:00

Author

Member

@oleg-rswll do you have a suggestion how to make it better?

I thought first it would be better to make a draft based mostly on input from contributors. Once its shaped I planned to make wider announcements in user chats.

@oleg-rswll do you have a suggestion how to make it better? I thought first it would be better to make a draft based mostly on input from contributors. Once its shaped I planned to make wider announcements in user chats.

oleg-rswll reviewed 2024-12-23 01:30:19 +00:00

oleg-rswll commented

2024-12-23 01:30:19 +00:00

Member

A document on a platform where more people can contribute - where more people have accounts, or where an account may not be required, and easier to engage for a non-technical user base, would help include more people. An example can be Google Docs as an option for this purpose (although I do not endorse Google in general).

A document on a platform where more people can contribute - where more people have accounts, or where an account may not be required, and easier to engage for a non-technical user base, would help include more people. An example can be Google Docs as an option for this purpose (although I do not endorse Google in general).

pastk reviewed 2024-12-23 22:10:22 +00:00

pastk commented

2024-12-23 22:10:22 +00:00

Author

Member

Ok let's try it :) https://board.net/p/Organic_Maps_Values

Ok let's try it :) https://board.net/p/Organic_Maps_Values

pastk reviewed 2024-12-25 16:03:09 +00:00

pastk commented

2024-12-25 16:03:08 +00:00

Author

Member

Are all our resource files under FOSS licenses indeed? E.g. all icons?
@rtsisyk

Are all our resource files under FOSS licenses indeed? E.g. all icons? @rtsisyk

pastk reviewed 2024-12-30 18:52:20 +00:00

pastk commented

2024-12-30 18:52:20 +00:00

Author

Member

Does it conflict with a possibility to have paid features?
Maybe it should be rephrased?
@rtsisyk WDYT?

Does it conflict with a possibility to have paid features? Maybe it should be rephrased? @rtsisyk WDYT?

rtsisyk reviewed 2024-12-31 10:58:44 +00:00

rtsisyk commented

2024-12-31 10:58:44 +00:00

Owner

Free as in beer is a bit too aggressive to be sustainable

Free as in beer is a bit too aggressive to be sustainable

pastk reviewed 2025-01-01 15:45:13 +00:00

pastk commented

2025-01-01 15:45:13 +00:00

Author

Member

Ok, I've removed it for now.

Ok, I've removed it for now.

This repo is archived. You cannot comment on pull requests.

No reviewers

No labels

Android Automotive (AAOS)

Android Automotive (AAOS)

Battery and Performance

Battery and Performance

Bookmarks and Tracks

Bookmarks and Tracks

External Map Datasets

External Map Datasets

Frequently User Reported

Frequently User Reported

Good first issue

Good first issue

Linux packaging

Linux packaging

NLnet 2024-06-281

NLnet 2024-06-281

No Feature Parity

No Feature Parity

Public Transport

Public Transport

Track Recording

Track Recording

Walk Navigation

Walk Navigation

No milestone

No project

No assignees

3 participants

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: organicmaps/organicmaps-tmp#9905

No description provided.