Change Working Groups into Sub Projects

camaraproject / Governance

Telco network capabilities exposed through APIs provide a large benefit for customers. By simplifying telco network complexity with APIs and making the APIs available across telco networks and countries, CAMARA enables easy and seamless access.

55 stars 44 forks source link

Change Working Groups into Sub Projects #84

Closed MarkusKuemmerle closed 3 weeks ago

MarkusKuemmerle commented 1 year ago

API Backlog WG --> SP Commonalties WG --> SP (already started) Marketing --> Outreach Committee below Governing Board Release Management SP

Adapt process description in ProjectStructuresAndRoles.md

MarkusKuemmerle commented 6 months ago

To proceed with this change I would suggest the following tasks:

Create separate repositories for all Working Groups (Commonalities and Release Management already available, API Backlog and Marketing todo)
The new repositories follow the same procedures as the repositories for Sub Projects. That means it will have maintainers and code owners, but no WG_participant.md files
To distinguish repos for Working Groups from repos for API familiy Sub Projects we use a new badge
Example:
The existing Working Groups repository is set to read only at an announced date and then archived after 1 month

MarkusKuemmerle commented 6 months ago

@hdamker : Would you please put it on the agenda of the next TSC to get a decision? Changing it requires TSC decision accoring our project charter...

hdamker commented 6 months ago

@MarkusKuemmerle thanks for the proposals above - looking good do me. And yes, good idea to bring it into the TSC. cc: @eric-murray @bigludo7 any further points which should be considered?

bigludo7 commented 6 months ago

any further points which should be considered?

For me discussion/approval at TSC is the right way to handle this.

hdamker commented 6 months ago

Approach approved within TSC on April 4th, 2024 (see minutes):

Resulting todos:

[x] Create a PR with the necessary changes to ProjectCharter.md and ProjectStructureAndRoles.md Herbert Damker
[x] Ask potential Maintainer to commit to the role Ricardo Serrano Gutierrez Markus Kümmerle
[x] Create two new repositories "APIBacklog" and "Marketing" (CAMARA Admin team)
- [x] Create Maintainer and Codeowner files (CAMARA Admin team)
[ ] Add existing content into the new repositories, transfer issues Ricardo Serrano Gutierrez Markus Kümmerle
[ ] Check that all content is already moved for Commonalities (@rartych )
[ ] Set repository https://github.com/camaraproject/WorkingGroups to read-only (remove write access)(CAMARA Admin team)
[ ] Update links within GitHub, Wiki and website, especially within https://github.com/camaraproject/WorkingGroups

MarkusKuemmerle commented 5 months ago

Open tasks at 22.04.2024:

Commonalities
- Confirmation that content is moved (Rafal - done)
- Delete old mailing list (end of May - done)
API Backlog
- Step 1: o Create new (empty) repository incl. Working Group badge (Markus - done) o Add people esp. maintainers and codeowners (Markus - done)
- Step 2: o Move content (Ricardo) o Move PRs (Ricardo) o Move issues (Ricardo) o Adjust https://github.com/camaraproject/Governance/blob/main/documentation/API-onboarding.md and Readme.md (Ricardo)
- Step 3: o Adjust Website links and pinning at CAMARA org github page (Markus) o Remove writing access to Working Group repository for all people (Markus)
- Step 4: o Archive Working Group repository after 1 month of inactiveness (Markus)

TEF-RicardoSerr commented 1 month ago

PRs are migrated to the new repo. API Backlog Step 2 is completed

hdamker commented 1 month ago

Removed writing access to Working Group repository for all people. Updated README of repository and APIBacklog directory. Archived repository.

@MarkusKuemmerle: issue ready to be closed, I suppose.