fix: update Corp v1 skill references
Build and publish Corp v1 Board portal / build (push) Successful in 39s
Build and publish Corp v1 Board portal / build (push) Successful in 39s
This commit is contained in:
@@ -15,14 +15,14 @@ slug: /decisions/corp-v1-board-migration/
|
||||
## Decision
|
||||
|
||||
1. Replace the steering committee channel with the Corp v1 Board channel. Discord canonicalized the requested `corp-v1--board` text-channel name to `corp-v1-board`; the immutable channel ID remains `1537070875503886356`.
|
||||
2. Rename the global governance skill and repository to `corp-v1--main`.
|
||||
2. Rename the global governance skill and repository to `corp-v1-main`.
|
||||
3. Rename `corp-v1/sterring-commitee` to `corp-v1/portal` and deploy it at `https://pages.apps.lego-cloud.eu/corp-v1/portal/`.
|
||||
4. Establish exactly these Board members:
|
||||
- RootAtSkic (`<@1518725627845283888>`)
|
||||
- Panther Skeleton (`<@476287310627864587>`)
|
||||
- MartynasP (`<@773109855497093191>`)
|
||||
5. Only these Board members may approve a project kickoff, project closure, or a change to `corp-v1--main`.
|
||||
6. Central `corp-v1-channel-*` reference-skill changes require Board approval. After publication, every affected project channel must be asked to review and synchronize its project-adopted `corp-v1-channel-*--<code>` skill; synchronization must preserve project-specific decisions.
|
||||
5. Only these Board members may approve a project kickoff, project closure, or a change to `corp-v1-main`.
|
||||
6. Central `corp-v1-channel-*` reference-skill changes require Board approval. After publication, every affected project channel must be asked to review and synchronize its project-adopted `corp-v1-channel-*-<code>` skill; synchronization must preserve project-specific decisions.
|
||||
|
||||
## Consequences
|
||||
|
||||
|
||||
Reference in New Issue
Block a user