[docs] Add collaboration principles #9975

Open
rtsisyk wants to merge 1 commit from rt-docs-collaboration into master
Owner
No description provided.
oleg-rswll reviewed 2024-12-30 13:19:52 +00:00
vng (Migrated from github.com) reviewed 2024-12-30 13:19:52 +00:00
pastk reviewed 2024-12-30 19:01:34 +00:00
@ -0,0 +8,4 @@
### Funded Work
Organic Maps obtains donations and grant funding from public institutions to support new feature development. Please expect such work to be structured as projects with clear scope, deadlines, assigned teams, and a person in charge.

I think Funded Work could have its own doc with more detailed explanations and conditions/accountability, list of open positions, current paid stuff, etc.

I think Funded Work could have its own doc with more detailed explanations and conditions/accountability, list of open positions, current paid stuff, etc.
@ -0,0 +12,4 @@
### Interactivity
The objective is to merge all contributions as soon as they are ready and meet the merge criteria. However, certain changes may require expertise from individuals who are unavailable or busy with other tasks that have deadlines. Please be patient and collaborate on the provided comments to ensure all required criteria are met.

This should be a part of CONTRIBUTING.md (reviews are mentioned there a bit already).

This should be a part of CONTRIBUTING.md (reviews are mentioned there a bit already).
@ -0,0 +16,4 @@
### Priorities
The roadmap is more of a collection of funded or expected-to-be-funded projects. Voluntary work is difficult to plan, and features and bug fixes may arise out of order. The team will make every effort to organize work in key areas, completing all preliminary product and UI/UX tasks to ensure they are ready for execution by volunteers.

This could go to ROADMAP.md

This could go to ROADMAP.md
@ -0,0 +20,4 @@
### Publicity
All development communication should occur through public channels, avoiding direct messages and private chats whenever possible. Any decision made must be documented in writing within the ticket, ensuring that the motivation and reasoning are clear and understandable to all.

This could go to the FOSS values/principles organicmaps/organicmaps#9905

This could go to the FOSS values/principles https://git.omaps.dev/organicmaps/organicmaps/pulls/9905
@ -0,0 +24,4 @@
### Artifacts
Collaboration should be conducted in a way that produces tangible artifacts, such as tickets, design mockups, pull requests, and other relevant documentation. Chatting in messaging platforms (e.g., Telegram) often leads to time wastage and does not generate artifacts. Please respect your time and the time of others by prioritizing the creation of artifacts over generating chat logs.

Probably should be a part of CONTRIBUTING.md

Probably should be a part of CONTRIBUTING.md
@ -0,0 +28,4 @@
### Tools
Contributors and teams are free to choose the tools that best suit their needs. However, priority should be given to open-source tools that align with the project's philosophy. Using proprietary tools is fully acceptable as long as they help achieve the desired results more efficiently. This project is primarily focused on developing a mobile maps app. Any gaps in open-source tooling in other areas should be addressed outside the scope of this project.

This could go to the FOSS values/principles organicmaps/organicmaps#9905

This could go to the FOSS values/principles https://git.omaps.dev/organicmaps/organicmaps/pulls/9905
rtsisyk reviewed 2024-12-30 19:17:00 +00:00
@ -0,0 +8,4 @@
### Funded Work
Organic Maps obtains donations and grant funding from public institutions to support new feature development. Please expect such work to be structured as projects with clear scope, deadlines, assigned teams, and a person in charge.
Author
Owner

OK

OK
rtsisyk reviewed 2024-12-31 11:18:38 +00:00
@ -0,0 +24,4 @@
### Artifacts
Collaboration should be conducted in a way that produces tangible artifacts, such as tickets, design mockups, pull requests, and other relevant documentation. Chatting in messaging platforms (e.g., Telegram) often leads to time wastage and does not generate artifacts. Please respect your time and the time of others by prioritizing the creation of artifacts over generating chat logs.
Author
Owner

CONTRIBUTING.md looks solid already... This paragraph is more like a guideline. What kind of guideline we can create for such documentation?

CONTRIBUTING.md looks solid already... This paragraph is more like a guideline. What kind of guideline we can create for such documentation?
pastk reviewed 2024-12-31 14:09:35 +00:00
@ -0,0 +24,4 @@
### Artifacts
Collaboration should be conducted in a way that produces tangible artifacts, such as tickets, design mockups, pull requests, and other relevant documentation. Chatting in messaging platforms (e.g., Telegram) often leads to time wastage and does not generate artifacts. Please respect your time and the time of others by prioritizing the creation of artifacts over generating chat logs.

Yeap its quite big already so ideas are welcome how to decompose it :))

Maybe separate bug reporting / feature requests into another doc.

Move legal stuff (DCO) also...

One of the (raw) ideas is also to move some team-specific docs into the TEAMS.md, so that e.g. people who'd like to contribute to the Android app could find everything in one place (including an Android-specific INSTALL doc)..

Yeap its quite big already so ideas are welcome how to decompose it :)) Maybe separate bug reporting / feature requests into another doc. Move legal stuff (DCO) also... One of the (raw) ideas is also to move some team-specific docs into the TEAMS.md, so that e.g. people who'd like to contribute to the Android app could find everything in one place (including an Android-specific INSTALL doc)..
This repo is archived. You cannot comment on pull requests.
No reviewers
No labels
Accessibility
Accessibility
Address
Address
Android
Android
Android Auto
Android Auto
Android Automotive (AAOS)
Android Automotive (AAOS)
API
API
AppGallery
AppGallery
AppStore
AppStore
Battery and Performance
Battery and Performance
Blocker
Blocker
Bookmarks and Tracks
Bookmarks and Tracks
Borders
Borders
Bug
Bug
Build
Build
CarPlay
CarPlay
Classificator
Classificator
Community
Community
Core
Core
CrashReports
CrashReports
Cycling
Cycling
Desktop
Desktop
DevEx
DevEx
DevOps
DevOps
dev_sandbox
dev_sandbox
Directions
Directions
Documentation
Documentation
Downloader
Downloader
Drape
Drape
Driving
Driving
Duplicate
Duplicate
Editor
Editor
Elevation
Elevation
Enhancement
Enhancement
Epic
Epic
External Map Datasets
External Map Datasets
F-Droid
F-Droid
Fonts
Fonts
Frequently User Reported
Frequently User Reported
Fund
Fund
Generator
Generator
Good first issue
Good first issue
Google Play
Google Play
GPS
GPS
GSoC
GSoC
iCloud
iCloud
Icons
Icons
iOS
iOS
Legal
Legal
Linux Desktop
Linux Desktop
Linux packaging
Linux packaging
Linux Phone
Linux Phone
Mac OS
Mac OS
Map Data
Map Data
Metro
Metro
Navigation
Navigation
Need Feedback
Need Feedback
Night Mode
Night Mode
NLnet 2024-06-281
NLnet 2024-06-281
No Feature Parity
No Feature Parity
Opening Hours
Opening Hours
Outdoors
Outdoors
POI Info
POI Info
Privacy
Privacy
Public Transport
Public Transport
Raw Idea
Raw Idea
Refactoring
Refactoring
Regional
Regional
Regression
Regression
Releases
Releases
RoboTest
RoboTest
Route Planning
Route Planning
Routing
Routing
Ruler
Ruler
Search
Search
Security
Security
Styles
Styles
Tests
Tests
Track Recording
Track Recording
Translations
Translations
TTS
TTS
UI
UI
UX
UX
Walk Navigation
Walk Navigation
Watches
Watches
Web
Web
Wikipedia
Wikipedia
Windows
Windows
Won't fix
Won't fix
World Map
World Map
No milestone
No project
No assignees
4 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#9975
No description provided.