WIP: Add TEAMS structure to GOVERNANCE #9914

pastk · 2024-12-22T20:31:16Z

pastk commented

2024-12-22 20:31:16 +00:00

Add visibility and structure to teams of people working together to further OM.

Helps to answer following questions:

who is responsible for what?
who has which permissions and why?
who is an expert in ...?
how to get permissions to ...?
what are processes and docs specific to a certain area?
whom to ask for a review / merge?
etc.

This is a draft so far.
Lists of people given in the Android team is an example (I've put just the ones who came to the top of my head; and I could be wrong about their permissions).

Add visibility and structure to teams of people working together to further OM. Helps to answer following questions: - who is responsible for what? - who has which permissions and why? - who is an expert in ...? - how to get permissions to ...? - what are processes and docs specific to a certain area? - whom to ask for a review / merge? etc. This is a draft so far. Lists of people given in the Android team is an example (I've put just the ones who came to the top of my head; and I could be wrong about their permissions).

👍 4 🎉 2

Ferenc- (Migrated from github.com) reviewed 2024-12-22 23:00:26 +00:00

docs/GOVERNANCE/ANDROID_TEAM.md

					
				@ -0,0 +22,4 @@

				- @andrewshkrob (repo write)

				- @strump (repo write)

				- @map-per

Ferenc- (Migrated from github.com) commented

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

I have push permission in case that has any relevance.

rtsisyk reviewed 2024-12-23 13:28:20 +00:00

docs/GOVERNANCE.md

					
				@ -1,36 +1,20 @@

				# Governance

rtsisyk commented

2024-12-23 11:55:29 +00:00

Hey, could we focus on TEAMS.md in this PR so we can move forward with it quickly without getting sidetracked by other topics for now?

docs/GOVERNANCE/EXPERTS.md

rtsisyk commented

2024-12-23 11:52:49 +00:00

Probably legal should be enough.

Probably `legal` should be enough.

rtsisyk commented

2024-12-23 11:53:34 +00:00

The purpose of this one isn't clear.

rtsisyk commented

2024-12-23 12:33:37 +00:00

Let's add web experts too:

Web Experts

HTML, CSS, and JavaScript development of web pages
UI/UX design implementation of web pages
Browser compatibility testing
Responsive design implementation
Performance optimization
Accessibility implementation

Let's add web experts too: ### Web Experts - HTML, CSS, and JavaScript development of web pages - UI/UX design implementation of web pages - Browser compatibility testing - Responsive design implementation - Performance optimization - Accessibility implementation

docs/GOVERNANCE/TEAMS.md

rtsisyk commented

2024-12-23 11:58:18 +00:00

What about Documentation? Should we include this domain here?

docs/GOVERNANCE/TEAMS.md

					
				@ -0,0 +7,4 @@

				People listed there are the most active contributors and "go to" persons, so that its clear whom to ask questions, request reviews, etc.

				They could be trusted with extra permissions and accesses necessary for their work (e.g. merge rights).

				If you've been contributing actively then feel free to open a PR/issue to add yourself to relevant teams and/or request permissions needed to facilitate your work.

rtsisyk commented

2024-12-23 11:50:13 +00:00

Quick formatting suggestion: how about putting each team under a second-level header (##) so there’s more room for details?

docs/GOVERNANCE/TEAMS.md

					
				@ -0,0 +12,4 @@

				- RELEASE

				<br>stores accs, maps generation, alphas/betas

				- COMMS

rtsisyk commented

2024-12-23 11:43:10 +00:00

Communication?

docs/GOVERNANCE/TEAMS.md

					
				@ -0,0 +31,4 @@

				<br>subject matter experts and talent in different fields, willing to share their knowledge

				- [ANDROID](ANDROID_TEAM.md)

rtsisyk commented

2024-12-23 11:50:54 +00:00

Do we need a separate file? Why don't incorporate the description right here?

docs/GOVERNANCE/TEAMS.md

					
				@ -0,0 +43,4 @@

				- DEVOPS

				<br>servers / cdn, CI/CD, tooling

				- ADMINS

rtsisyk commented

2024-12-23 11:51:09 +00:00

What is the difference with DEVOPS?

pastk reviewed 2024-12-23 17:39:03 +00:00

docs/GOVERNANCE/TEAMS.md

pastk commented

2024-12-23 17:39:02 +00:00

user-facing docs like FAQs

pastk reviewed 2024-12-23 17:51:07 +00:00

docs/GOVERNANCE/EXPERTS.md

pastk commented

2024-12-23 17:51:07 +00:00

many of expert pools here are just ideas for now, they would become a reality if there are people willing to share their expertise and there are people who need it :)

my particular idea for the "brainstorm" is that its for people who like to suggest and discuss novel and bold ideas, maybe do some basic research on them; and in general people who like brainstorming :)

i.e. if we got stuck with a UX problem and we need fresh ideas then we could just tag @organicmaps/brainstorm and ask for input :)

many of expert pools here are just ideas for now, they would become a reality if there are people willing to share their expertise and there are people who need it :) my particular idea for the "brainstorm" is that its for people who like to suggest and discuss novel and bold ideas, maybe do some basic research on them; and in general people who like brainstorming :) i.e. if we got stuck with a UX problem and we need fresh ideas then we could just tag @organicmaps/brainstorm and ask for input :)

pastk reviewed 2024-12-23 17:59:03 +00:00

docs/GOVERNANCE/TEAMS.md

					
				@ -0,0 +43,4 @@

				- DEVOPS

				<br>servers / cdn, CI/CD, tooling

				- ADMINS

pastk commented

2024-12-23 17:59:03 +00:00

DEVOPS work on servers, ci, etc and they need relevant permissions and accesses

ADMINS assign those permissions to them (as well as to other teams) by following a defined permission request policy/procedure (TBD), if permissions are time-limited (e.g. for a year) then they oversee renewals, etc.

if there won't be any permissions policies (like it is now) then there won't be any need in this team :)

DEVOPS work on servers, ci, etc and they need relevant permissions and accesses ADMINS assign those permissions to them (as well as to other teams) by following a defined permission request policy/procedure (TBD), if permissions are time-limited (e.g. for a year) then they oversee renewals, etc. if there won't be any permissions policies (like it is now) then there won't be any need in this team :)

pastk reviewed 2024-12-23 17:59:37 +00:00

docs/GOVERNANCE/TEAMS.md

					
				@ -0,0 +31,4 @@

				<br>subject matter experts and talent in different fields, willing to share their knowledge

				- [ANDROID](ANDROID_TEAM.md)

pastk commented

2024-12-23 17:59:37 +00:00

The file will get very big and harder to navigate and manage.

pastk reviewed 2024-12-23 18:02:17 +00:00

docs/GOVERNANCE/TEAMS.md

					
				@ -0,0 +7,4 @@

				People listed there are the most active contributors and "go to" persons, so that its clear whom to ask questions, request reviews, etc.

				They could be trusted with extra permissions and accesses necessary for their work (e.g. merge rights).

				If you've been contributing actively then feel free to open a PR/issue to add yourself to relevant teams and/or request permissions needed to facilitate your work.

pastk commented

2024-12-23 18:02:17 +00:00

The most of the teams will be just links to relevant team pages with all the details.
Maybe there could be a short sub-title (like it is now) so that its more clear what the team is about.

For now I've added short responsibility lists so that its easier to see if we missed some important bits or not.

The most of the teams will be just links to relevant team pages with all the details. Maybe there could be a short sub-title (like it is now) so that its more clear what the team is about. For now I've added short responsibility lists so that its easier to see if we missed some important bits or not.

pastk reviewed 2024-12-23 18:03:14 +00:00

docs/GOVERNANCE/TEAMS.md

					
				@ -0,0 +12,4 @@

				- RELEASE

				<br>stores accs, maps generation, alphas/betas

				- COMMS

pastk commented

2024-12-23 18:03:14 +00:00

yeap
I thought a short name sounds more cool :)

Just like DEVOPS and not DEVELOPER OPERATIONS

yeap I thought a short name sounds more cool :) Just like DEVOPS and not DEVELOPER OPERATIONS

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

No reviewers

No labels

Android Automotive (AAOS)

API

AppGallery

AppStore

Battery and Performance

External Map Datasets

F-Droid

Fonts

Frequently User Reported

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#9914

				`@ -1,36 +1,20 @@`
				`# Governance`

Rows
Columns