Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add links to GitHub discussions in the project management plan #118

Merged
merged 1 commit into from
Dec 17, 2024
Merged

Add links to GitHub discussions in the project management plan #118

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 7 additions & 5 deletions docs/platform_management_plan/project_management.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -77,14 +77,14 @@ Technical committees
is to do a breakdown of platform sagas to the concrete tasks (see `Planning`_) .
Currently following *Communities* are defined in the *SCORE* project:

* *Tooling/Infrastructure*: *community* for all kind of infra topics:
compiler, IDE, build toolchain and etc.
* *Operational*: *community* for all kind of infra topics:
compiler, IDE, build toolchain and etc. See `GitHub Discussions/Operational Community <https://github.com/orgs/eclipse-score/discussions/categories/operational-community>`_ for more.
* *Testing*: *community* to clarify questions and define testing strategy
for the 'SCORE' project
for the 'SCORE' project. See `GitHub Discussions/Testing Community <https://github.com/orgs/eclipse-score/discussions/categories/testing-community>`_ for more.
* *Software Architecture*: *community* for clarification of software architecture topics,
e.g. discussion of new features or coding guidelines.
e.g. discussion of new features or coding guidelines. See `GitHub Discussions/Architecture Community <https://github.com/orgs/eclipse-score/discussions/categories/architecture-community>`_ for more.
* *Software Development Process*: *community* for definition and maintaining
of safety, security and quality software development process.
of safety, security and quality software development process. See `GitHub Discussions/SW Dev Process Community <https://github.com/orgs/eclipse-score/discussions/categories/sw-dev-process-community>`_ for more.

The planning of the activities is done by every *Community* independent of other
teams. Each *Community* has a *Community Lead*, who is nominated by the *Technical lead circle*. The prioritization of some topics can be requested by the *Technical lead circle*
Expand All @@ -101,6 +101,7 @@ Technical committees

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*.

The *GitHub Discussions* for cross-functional teams can be found in the `Cross-functional teams section <https://github.com/orgs/eclipse-score/discussions>`_ of the main *SCORE* project.

Meeting Structure
-----------------
Expand All @@ -115,6 +116,7 @@ Meeting Structure

The *Project Lead Circle meeting* takes place usually once a week.


* **Technical Lead Circle meeting**

Regular participants of the *Technical Lead Circle meeting* are the *Technical Leads* of the main *SCORE* project. The main purpose of the meeting is the exchange between technical leads for fulfilling their responsibilities.
Expand Down
12 changes: 12 additions & 0 deletions docs/score_releases/index.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -44,69 +44,81 @@ SW Module List
- Date
- Contribution Request
- Repo
- GitHub Discussions
* - IPC
- Holger Grandy, Gerd Schaeffer, Nico Hartmann, Sven Kappel, Thilo Schmitt
- v0.5
- Q4
- _
- `inc_mw_com <https://github.com/eclipse-score/inc_mw_com>`_
- `Communication CTF <https://github.com/orgs/eclipse-score/discussions/categories/communication-cft>`_
* - Fixed Execution Order Framework (incl. Orchestrator)
- Holger Grandy, Gerd Schaeffer, Nico Hartmann, Sven Kappel, Thilo Schmitt
- v0.5
- Q4
- _
- `inc_feo <https://github.com/eclipse-score/inc_feo>`_
- `FEO CTF <https://github.com/orgs/eclipse-score/discussions/categories/feo-cft>`_
* - Logging
- Holger Grandy, Gerd Schaeffer, Nico Hartmann
- v0.5
- Q4
- _
- `inc_mw_log <https://github.com/eclipse-score/inc_mw_log>`_
- `Logging CTF <https://github.com/orgs/eclipse-score/discussions/categories/logging-cft>`_
* - Persistency
- Gerd Schaeffer, Nico Hartmann, Sven Kappel
- v0.5
- Q4
- _
- `inc_mw_per <https://github.com/eclipse-score/inc_mw_per>`_
- `Persistency CTF <https://github.com/orgs/eclipse-score/discussions/categories/persistency-cft>`_
* - Integration Testing Framework
- Holger Grandy
- v0.5
- Q4
- _
- _
- _
* - SOME/IP
- _
- _
- _
- _
- _
- _
* - Lifecycle
- _
- _
- _
- _
- _
- _
* - Diagnosis
- _
- _
- _
- _
- _
- _
* - OS Abstraction Layer
- _
- _
- _
- _
- _
- _
* - Time Sync
- _
- _
- _
- _
- _
- _
* - Firewall
- _
- _
- _
- _
- _
- _
Loading