Feature team creation #1714

antonkri · 2025-09-10T09:46:34Z

No description provided.

github-actions · 2025-09-10T09:50:45Z

The created documentation from the pull request is available at: docu-html

antonkri · 2025-09-10T09:54:15Z

Follow-up of #1281 with fixed findings.

AlexanderLanin · 2025-09-10T11:07:12Z

docs/platform_management_plan/project_management.rst

+Merge rights & code ownership
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+As already stated, every *Feature Team* has normally a dedicated repository. Before the creation of the new repository,
+*Technical Leads* should initially nominate developers, whose review is mandatory for merging PRs to the repository


Suggested change

*Technical Leads* should initially nominate developers, whose review is mandatory for merging PRs to the repository

*Technical Leads* should nominate initial codeowners, whose review is mandatory for merging PRs to the repository

AlexanderLanin · 2025-09-10T11:09:00Z

docs/platform_management_plan/project_management.rst

+* GitHub Team for quality managers
+* GitHub Team for safety managers
+
+**ToDo**: can we have an 'AND relationship' for teams in CODEOWNERS file?


No. But we can create custom logic to enforce such rules. That's a custom CODEOWNER-like-solution.

@AlexanderLanin, did you have a look into the solution from Zephyr? https://github.com/zephyrproject-rtos/zephyr/blob/main/MAINTAINERS.yml

Yeah exactly something like that. I don't know whether zephyr has the best solution for that or not. But from a concept point of view, it looks like a match.

AlexanderLanin · 2025-09-10T11:13:53Z

docs/platform_management_plan/project_management.rst

+All other Technical Leads who are already committers in the S-CORE project are expected to support these
+elections by voting positively, provided there are no specific objections.


This violates eclipse handbook.

Becoming a Committer is a privilege that is earned by contributing and showing discipline and good judgment. It is a responsibility that should be neither given nor taken lightly, nor is it a right based on employment by an Eclipse member company or any company employing existing Committers.

This was discussed and agreed with Wayne Beaton

I think what was agreed is that if there are developer which are already in the historie because they did the job inhouse. For the rest I would agree that we need some kind of process which fits with the handbook

@FScholPer I think, we should apply here the same rules, that are applied when a new eclipse project is added and we add initial committers or project leads to it. I do not remember, that for s-core project we had to show any historie.....

FScholPer

Until the role of the TLs and PLs with respect to the handbook of Eclipse is clear we can not continue

docs/platform_management_plan/project_management.rst

FScholPer · 2025-09-10T11:26:14Z

docs/platform_management_plan/project_management.rst

+Afterwards a GitHub Issue is created in the `Technical Lead Cirle LOP project <https://github.com/orgs/eclipse-score/projects/3>`_
+using the special *Feature Team Creation* GitHub Issue template and is assigned to one of the Technical Leads.
+
+**ToDo**: create such a template.


Please add a issue that we need additional work here

docs/platform_management_plan/project_management.rst

FScholPer · 2025-09-10T11:34:25Z

docs/platform_management_plan/project_management.rst

+
+* **Developer GitHub Team**
+
+  Every *Feature Team* should have a corresponding software developer GitHub team, e.g. *ipc_ft_dev*, that contains all


Is there a process how we can get the Teams?

docs/platform_management_plan/project_management.rst

FScholPer · 2025-09-10T12:04:33Z

docs/platform_management_plan/project_management.rst

+All other Technical Leads who are already committers in the S-CORE project are expected to support these
+elections by voting positively, provided there are no specific objections.


I think what was agreed is that if there are developer which are already in the historie because they did the job inhouse. For the rest I would agree that we need some kind of process which fits with the handbook

antonkri · 2025-09-11T06:25:18Z

Until the role of the TLs and PLs with respect to the handbook of Eclipse is clear we can not continue

@FScholPer could you please take care of the clarification?

FScholPer · 2025-09-11T14:15:13Z

For me it would also be okay when we merge that version and if there is a change because of the discussion right now we do a change

FScholPer

For the moment and as first version its okay

johannes-esr · 2025-09-16T05:46:15Z

docs/platform_management_plan/project_management.rst

+  *Feature Teams* have end-to-end responsibility for specific functionalities. This includes all
+  aspects beginning with the architecture definition to the integration test. They are usually assigned
+  to the *S-CORE* main integration project or to one particular software module. *Feature Teams* work
+  independently of each other on *GitHub Issues* in the assigned software module.


Should we call it work packages instad of GitHub issues to be more general?

docs/platform_management_plan/project_management.rst

github-actions · 2025-10-08T09:12:57Z

⚠️ Docs-as-Code version mismatch detected
Please check the CI build logs for details and align the documentation version with the Bazel dependency.

aschemmel-tech

fine for me

docs: Add description for feature creation

95f4906

antonkri requested review from a team, FScholPer, johannes-esr, markert-r and qor-lb as code owners September 10, 2025 09:46

antonkri mentioned this pull request Sep 10, 2025

Feature team creation #1281

Closed

antonkri changed the title ~~Ankr feature team creation~~ Feature team creation Sep 10, 2025

AlexanderLanin reviewed Sep 10, 2025

View reviewed changes

antonkri force-pushed the ankr_feature_team_creation branch from cc9d3c6 to 80de758 Compare September 10, 2025 11:22

FScholPer requested changes Sep 11, 2025

View reviewed changes

FScholPer previously approved these changes Sep 11, 2025

View reviewed changes

johannes-esr mentioned this pull request Sep 15, 2025

PMP: Describe process of creation of new feature team #1200

Open

johannes-esr reviewed Sep 16, 2025

View reviewed changes

docs/platform_management_plan/project_management.rst Show resolved Hide resolved

docs: Improve description for feature team creation

90e2538

antonkri dismissed FScholPer’s stale review via 90e2538 October 8, 2025 09:12

antonkri force-pushed the ankr_feature_team_creation branch from 80de758 to 90e2538 Compare October 8, 2025 09:12

antonkri requested review from PhilipPartsch, aschemmel-tech, masc2023 and pahmann as code owners October 8, 2025 09:12

aschemmel-tech approved these changes Oct 8, 2025

View reviewed changes

antonkri merged commit b6c8f75 into main Oct 8, 2025
8 checks passed

antonkri deleted the ankr_feature_team_creation branch October 8, 2025 11:45

	Technical Leads should initially nominate developers, whose review is mandatory for merging PRs to the repository
	Technical Leads should nominate initial codeowners, whose review is mandatory for merging PRs to the repository

		All other Technical Leads who are already committers in the S-CORE project are expected to support these
		elections by voting positively, provided there are no specific objections.


		* Developer GitHub Team

		Every Feature Team should have a corresponding software developer GitHub team, e.g. ipc_ft_dev, that contains all

Feature team creation #1714

Feature team creation #1714

Uh oh!

Conversation

antonkri commented Sep 10, 2025

Uh oh!

github-actions bot commented Sep 10, 2025

Uh oh!

antonkri commented Sep 10, 2025

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

AlexanderLanin Sep 10, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

FScholPer left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

antonkri commented Sep 11, 2025

Uh oh!

FScholPer commented Sep 11, 2025

Uh oh!

FScholPer left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

github-actions bot commented Oct 8, 2025

Uh oh!

aschemmel-tech left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

6 participants

AlexanderLanin Sep 10, 2025 •

edited

Loading