[FEATURE] Coordinate Phase 6 through issues and WIP pull requests #2

Open
opened 2026-09-12 07:56:21 +02:00 by erikinkinen · 0 comments
Owner

Problem and motivation

Phase 6 spans several repositories. Its issues and pull requests need to show who owns each change, what it depends on, and what remains before completion.

Proposed behavior and scope

Track each change in the repository responsible for it. Link its issue and pull request to dependent work and the Phase 6 tracker. Use phase-6 and relevant topic labels to make the work easy to find.

New repositories inherit the shared policies and templates from Meta. The full scope is defined by Phase 6 and AC1–AC24, including two complete EriX builds inside EriX and rebuilding Rust/LLVM there.

Authority, security and reliability

Use the existing account and only the permissions needed for each change. Keep credentials, signing keys, private evidence and vulnerability details out of public records; follow SECURITY.md for security reports. Preserve other contributors' edits and describe review and approval accurately. Prioritize security, then reliability, then performance.

Acceptance criteria

  • Check the Forgejo version, account and repository permissions before making changes, without expanding access or exposing credentials.
  • Create implementation and audit issues in the relevant repositories, with clear scope, dependencies, acceptance criteria and security implications.
  • Check for existing issues and pull requests before creating new ones. Maintain their index and preserve other contributors' edits.
  • Open a feature/posix-compat pull request after the first signed, reviewable commit. Keep the WIP: title prefix until its full scope and dependent checks are complete.
  • Keep pull request descriptions accurate about their scope, security decisions and relevant source revisions. Put routine progress in comments; include validation details when they concern a linked issue.
  • Publish changes through the authorized account, and claim review or approval only when it has occurred.
  • Keep secrets and sensitive vulnerability details out of issues, pull requests and artifacts. Use the reporting channel in SECURITY.md when needed.
  • Create new repositories from Meta, check the inherited shared files, then clone and branch before specializing them. Add audit, CI, documentation, manual and catalog coverage before other repositories depend on them.
  • Close issues and remove WIP: only when all their acceptance criteria are met. Merging and releasing need separate approval.
  • Keep repository changes, issues, pull requests, dependency revisions and CI evidence consistent at each checkpoint and handoff.

Alternatives and tradeoffs

Linked issues allow work to stay with its owning repository while exposing dependencies across repositories. Completion still depends on the agreed deliverables and working software; labels and closed issues alone do not demonstrate self-hosting.

Tracking and rollout

Use the feature_request.md template for planned features, designs and audits, with its six sections, [FEATURE] title prefix and enhancement label. Use bug_report.md for significant defects and regressions, including reproduction steps, expected and actual behavior, constraints and evidence. Add phase-6 and appropriate security, ci, docs, performance or refactor labels to issues and pull requests.

Work on feature/posix-compat and commit regularly with signed commits, tagged titles and explanatory bodies. Pin Cargo dependencies, component catalogs and CI helpers to full 40-character lowercase commit hashes. Keep existing main images until promotion is approved. Required formatting, strict Clippy, unit tests, doctests, warning-free builds, relevant VM checks and current-source CI run alongside implementation.

Write public documentation, issues, pull requests and comments in clear, natural prose. Focus status comments and commit messages on the change; include validation details when they concern a linked issue.

Related pull requests
Repository Pull request
lib-aes #2
lib-cli #2
lib-console #2
lib-constant-time #2
lib-deflate #2
lib-device #2
lib-elf #2
lib-fs-name #2
lib-handoff #2
lib-sha2 #2
docs #4
integration #12
meta #4
## Problem and motivation Phase 6 spans several repositories. Its issues and pull requests need to show who owns each change, what it depends on, and what remains before completion. ## Proposed behavior and scope Track each change in the repository responsible for it. Link its issue and pull request to dependent work and the [Phase 6 tracker](https://git.erikinkinen.fi/erix/integration/issues/65). Use `phase-6` and relevant topic labels to make the work easy to find. New repositories inherit the shared policies and templates from Meta. The full scope is defined by [Phase 6 and AC1–AC24](https://git.erikinkinen.fi/erix/docs/src/branch/main/phases/6.md), including two complete EriX builds inside EriX and rebuilding Rust/LLVM there. ## Authority, security and reliability Use the existing account and only the permissions needed for each change. Keep credentials, signing keys, private evidence and vulnerability details out of public records; follow `SECURITY.md` for security reports. Preserve other contributors' edits and describe review and approval accurately. Prioritize security, then reliability, then performance. ## Acceptance criteria - [ ] Check the Forgejo version, account and repository permissions before making changes, without expanding access or exposing credentials. - [ ] Create implementation and audit issues in the relevant repositories, with clear scope, dependencies, acceptance criteria and security implications. - [ ] Check for existing issues and pull requests before creating new ones. Maintain their index and preserve other contributors' edits. - [ ] Open a `feature/posix-compat` pull request after the first signed, reviewable commit. Keep the `WIP: ` title prefix until its full scope and dependent checks are complete. - [ ] Keep pull request descriptions accurate about their scope, security decisions and relevant source revisions. Put routine progress in comments; include validation details when they concern a linked issue. - [ ] Publish changes through the authorized account, and claim review or approval only when it has occurred. - [ ] Keep secrets and sensitive vulnerability details out of issues, pull requests and artifacts. Use the reporting channel in `SECURITY.md` when needed. - [ ] Create new repositories from Meta, check the inherited shared files, then clone and branch before specializing them. Add audit, CI, documentation, manual and catalog coverage before other repositories depend on them. - [ ] Close issues and remove `WIP: ` only when all their acceptance criteria are met. Merging and releasing need separate approval. - [ ] Keep repository changes, issues, pull requests, dependency revisions and CI evidence consistent at each checkpoint and handoff. ## Alternatives and tradeoffs Linked issues allow work to stay with its owning repository while exposing dependencies across repositories. Completion still depends on the agreed deliverables and working software; labels and closed issues alone do not demonstrate self-hosting. ## Tracking and rollout Use the `feature_request.md` template for planned features, designs and audits, with its six sections, `[FEATURE]` title prefix and `enhancement` label. Use `bug_report.md` for significant defects and regressions, including reproduction steps, expected and actual behavior, constraints and evidence. Add `phase-6` and appropriate `security`, `ci`, `docs`, `performance` or `refactor` labels to issues and pull requests. Work on `feature/posix-compat` and commit regularly with signed commits, tagged titles and explanatory bodies. Pin Cargo dependencies, component catalogs and CI helpers to full 40-character lowercase commit hashes. Keep existing main images until promotion is approved. Required formatting, strict Clippy, unit tests, doctests, warning-free builds, relevant VM checks and current-source CI run alongside implementation. Write public documentation, issues, pull requests and comments in clear, natural prose. Focus status comments and commit messages on the change; include validation details when they concern a linked issue. <details> <summary>Related pull requests</summary> | Repository | Pull request | | --- | --- | | lib-aes | [#2](https://git.erikinkinen.fi/erix/lib-aes/pulls/2) | | lib-cli | [#2](https://git.erikinkinen.fi/erix/lib-cli/pulls/2) | | lib-console | [#2](https://git.erikinkinen.fi/erix/lib-console/pulls/2) | | lib-constant-time | [#2](https://git.erikinkinen.fi/erix/lib-constant-time/pulls/2) | | lib-deflate | [#2](https://git.erikinkinen.fi/erix/lib-deflate/pulls/2) | | lib-device | [#2](https://git.erikinkinen.fi/erix/lib-device/pulls/2) | | lib-elf | [#2](https://git.erikinkinen.fi/erix/lib-elf/pulls/2) | | lib-fs-name | [#2](https://git.erikinkinen.fi/erix/lib-fs-name/pulls/2) | | lib-handoff | [#2](https://git.erikinkinen.fi/erix/lib-handoff/pulls/2) | | lib-sha2 | [#2](https://git.erikinkinen.fi/erix/lib-sha2/pulls/2) | | docs | [#4](https://git.erikinkinen.fi/erix/docs/pulls/4) | | integration | [#12](https://git.erikinkinen.fi/erix/integration/pulls/12) | | meta | [#4](https://git.erikinkinen.fi/erix/meta/pulls/4) | </details>
erikinkinen changed title from [FEATURE] [P18] Coordinate Phase 6 through public issues, WIP PRs and one organization project to [FEATURE] Coordinate Phase 6 through public issues, WIP PRs and one organization project 2026-09-12 08:01:58 +02:00
erikinkinen changed title from [FEATURE] Coordinate Phase 6 through public issues, WIP PRs and one organization project to [FEATURE] Coordinate Phase 6 through issues and WIP pull requests 2026-09-12 08:17:43 +02:00
erikinkinen added this to the Alpha 1 milestone 2026-10-30 09:35:02 +01:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
erix/meta#2
No description provided.