rename cft to ft #1078
Merged
rename cft to ft #1078
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The created documentation from the pull request is available at: docu-html |
antonkri
force-pushed
the
ankr_rename_cft_ft
branch
from
71e5c80 to
51517a7
Compare
FScholPer
previously approved these changes
May 13, 2025
markert-r
reviewed
May 13, 2025
docs/contribute/index.rst
Outdated
| Eclipse S-CORE is an open source project, so everyone is welcome to contribute. Since we are organized within the Eclipse Foundation, you must have an Eclipse Foundation account to participate - please see :ref:`contribution_attribution` for details. | ||
|
|
||
| The project is structured into various :ref:`technical committees <pmp_pm_technical_committees>`, which include communities focused on specific domains and cross-functional teams responsible for defined work areas. Their meetings are public; feel free to join or review the minutes via our `GitHub Discussions <https://github.com/orgs/eclipse-score/discussions>`_. | ||
| The project is structured into various :ref:`technical committees <pmp_pm_technical_committees>`, which include communities focused on specific domains and feature teams responsible for defined work areas. Their meetings are public; feel free to join or review the minutes via our `GitHub Discussions <https://github.com/orgs/eclipse-score/discussions>`_. |
Member
There was a problem hiding this comment.
communities which focus on cross-cutting topics and feature teams responsible for the implementation of specific functionalities
Contributor
Author
There was a problem hiding this comment.
- generally, this PR was only concerning renaming the CFTs to FTs. I am sure, there are a lot of not so perfect formulations in our documentation. You currently see only files I've touched, but there is so much more... I can also not comment on everything as not everything was originally written by me, I've just renamed it.
- regarding this finding, I've fixed it
markert-r
reviewed
May 13, 2025
| :need:`[[title]] <gd_req__problem__attr_stakeholder>` is defined in the description part of the | ||
| ISSUE using the Problem Template :ref:`prm_templates`. For S-CORE stakeholder use pre-defined labels | ||
| for Communities or Cross Functional Teams (Feature Owner) (under discussion, compare | ||
| for Communities or Feature Teams (Feature Owner) (under discussion, compare |
Member
There was a problem hiding this comment.
What is the reason to have (Feature Owner) in this sentence?
Contributor
Author
There was a problem hiding this comment.
I do not know, this document was not written by me. I just renamed CFT to FT.
markert-r
reviewed
May 13, 2025
| * **Feature Teams** | ||
|
|
||
| *Cross functional teams* are responsible for some piece | ||
| *Feature Teams* are responsible for some piece |
Member
There was a problem hiding this comment.
... have end-to-end responsibility for specific functionalities. This includes all aspects beginning with the architecture definition to the integration test. They are usually ...
markert-r
reviewed
May 13, 2025
| *Feature Teams* are responsible for some piece | ||
| of work from the beginning (e.g. definition of the architecture) till the end | ||
| (e.g. integration tests) and are usually assigned to the *S-CORE* main integration project or to one particular software module. *Cross-functional teams* work independently from each other on *GitHub Issues* in the assigned software module. *Cross-functional teams* consist of the contributors, who can specify requirements, define architecture, develop source code and implement tests afterwards. *Project Leads* and *Committers* are also *Contributors* and effectively work on processing of *GitHub Issues*. | ||
| (e.g. integration tests) and are usually assigned to the *S-CORE* main integration project or to one particular software module. *Feature Teams* work independently from each other on *GitHub Issues* in the assigned software module. *Feature Teams* consist of the contributors, who can specify requirements, define architecture, develop source code and implement tests afterwards. *Project Leads* and *Committers* are also *Contributors* and effectively work on processing of *GitHub Issues*. |
Member
There was a problem hiding this comment.
... work independently of each other ...
markert-r
reviewed
May 13, 2025
| (e.g. integration tests) and are usually assigned to the *S-CORE* main integration project or to one particular software module. *Feature Teams* work independently from each other on *GitHub Issues* in the assigned software module. *Feature Teams* consist of the contributors, who can specify requirements, define architecture, develop source code and implement tests afterwards. *Project Leads* and *Committers* are also *Contributors* and effectively work on processing of *GitHub Issues*. | ||
|
|
||
| *Cross-functional team* usually consists of the following roles: Project Lead, Safety Manager, Quality Manager, Security Manager, Committers and Contributors. Every *cross-functional* team has at least one committer who can approve and merge the Pull Requests of the Contributors. | ||
| *Feature Team* usually consists of the following roles: Project Lead, Safety Manager, Quality Manager, Security Manager, Committers and Contributors. Every *Feature Team* has at least one committer who can approve and merge the Pull Requests of the Contributors. |
Member
There was a problem hiding this comment.
A Feature Team usually ...
role: Feature Team Lead, Safety Manager, ... -> The name "Project Lead" is already used for the Eclipse role "Project Lead".
Contributor
Author
There was a problem hiding this comment.
We need to rework project_management plan, but this is not the idea of this PR.
markert-r
reviewed
May 13, 2025
| *Feature Team* usually consists of the following roles: Project Lead, Safety Manager, Quality Manager, Security Manager, Committers and Contributors. Every *Feature Team* has at least one committer who can approve and merge the Pull Requests of the Contributors. | ||
|
|
||
| In case *Cross-functional team* needs to request a new repository, this can be done be extending the `otterdog configuration file <https://github.com/eclipse-score/.eclipsefdn/blob/main/otterdog/eclipse-score.jsonnet>`_ and creating a new PR, that should be approved by the *Eclipse Project Security Team*. | ||
| In case *Feature Team* needs to request a new repository, this can be done be extending the `otterdog configuration file <https://github.com/eclipse-score/.eclipsefdn/blob/main/otterdog/eclipse-score.jsonnet>`_ and creating a new PR, that should be approved by the *Eclipse Project Security Team*. |
Member
There was a problem hiding this comment.
In case a Feature Team needs ...
... has to be approved by the ...
markert-r
reviewed
May 13, 2025
| :align: center | ||
|
|
||
| The members of the *Responsible Community* define or refine feature, process or tool requirements. They may also create feature architecture and high level component requirements for every involved software component. Depending on the feature scope, one of the cross-functional team can be requested to make a POC in the `incubation repository <https://eclipse-score.github.io/score/features/integration/index.html#incubation-repositories>`_. Finally, *Responsible Community* does the break down of the corresponding *saga* to the tickets that can be assigned to the individual software modules or *communities*. | ||
| The members of the *Responsible Community* define or refine feature, process or tool requirements. They may also create feature architecture and high level component requirements for every involved software component. Depending on the feature scope, one of the feature team can be requested to make a POC in the `incubation repository <https://eclipse-score.github.io/score/features/integration/index.html#incubation-repositories>`_. Finally, *Responsible Community* does the break down of the corresponding *saga* to the tickets that can be assigned to the individual software modules or *communities*. |
Member
There was a problem hiding this comment.
- What does "Responsible Community" refer to? Does it refer to S-CORE communities or to feature teams or both?
- one of the feature team: some member of the feature team or one of the feature teams ?
- Do we still have sagas?
Contributor
Author
There was a problem hiding this comment.
We need to rework project_management plan, but this is not the idea of this PR.
markert-r
reviewed
May 13, 2025
| The members of the *Responsible Community* define or refine feature, process or tool requirements. They may also create feature architecture and high level component requirements for every involved software component. Depending on the feature scope, one of the feature team can be requested to make a POC in the `incubation repository <https://eclipse-score.github.io/score/features/integration/index.html#incubation-repositories>`_. Finally, *Responsible Community* does the break down of the corresponding *saga* to the tickets that can be assigned to the individual software modules or *communities*. | ||
| As most of the software modules will have their own separate repository, | ||
| then the detailed tracking of their work will also happen inside of that repository. | ||
| However, the corresponding saga of the S-CORE repository will still have a sub-issue of type epic, |
Contributor
Author
There was a problem hiding this comment.
We need to rework project_management plan, but this is not the idea of this PR.
markert-r
reviewed
May 13, 2025
| * According process, cross functional teams implement and test. | ||
| * According process, feature teams implement and test. | ||
| * Check the :need:`wp__verification__module_ver_report` to ensure that all tests pass before proceeding to the release. | ||
| * In case of failed test, evaluate and possibly justify their failure. |
Member
There was a problem hiding this comment.
In case of failed test, evaluate and possibly justify their failure. -> Is here the subject missing?
Contributor
Author
There was a problem hiding this comment.
This document was not written by me, I do not know.
markert-r
requested changes
May 13, 2025
Member
markert-r
left a comment
markert-r
left a comment
There was a problem hiding this comment.
Changes from cross-function team to feature team is ok.
For other remarks please refer to my comments.
Rename cross-functional teams to feature teams and update the links.
antonkri
force-pushed
the
ankr_rename_cft_ft
branch
from
51517a7 to
afe59c7
Compare
markert-r
approved these changes
May 16, 2025
Member
markert-r
left a comment
markert-r
left a comment
There was a problem hiding this comment.
Comments not addressed in this PR should be addressed later.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Rename cross-functional teams to feature teams and update the links.