Align README with GitHub Issues policy #4

New issue

Open

opened 2026-08-15 11:08:27 +02:00 by michael · 0 comments

michael commented

2026-08-15 11:08:27 +02:00

Owner

Goal

Align this public repository's README with the accepted Dragons@Work policy for GitHub Issues.

Session rationale

GitHub Issues on public mirrors are now an accepted external communication channel for bug reports, questions, suggestions, and contributor feedback. Forgejo remains the primary development environment. lazy-admin-tools is already mirrored on GitHub, so its README must reflect this policy.

Scope

Review README.md for issue and contribution-channel wording.
Remove or replace wording that conflicts with the accepted GitHub Issues policy.
Keep Forgejo identified as the primary development environment.
Make clear that reports opened through GitHub Issues are accepted and handled there.
Do not include unrelated README changes.

Acceptance criteria

README.md has been checked against the current public README standard and documentation landscape.
README.md does not reject GitHub Issues as an external reporting or feedback channel.
Forgejo remains identified as the primary development environment.
Changed wording is consistent with the updated PUBLIC_README_STANDARD.
No unrelated README content is changed as part of this issue.

Coordination

Cross-repository documentation update coordinated with DAW/daw-docs. The same policy must remain consistent across all public Dragons@Work repositories.

## Goal Align this public repository's README with the accepted Dragons@Work policy for GitHub Issues. ## Session rationale GitHub Issues on public mirrors are now an accepted external communication channel for bug reports, questions, suggestions, and contributor feedback. Forgejo remains the primary development environment. `lazy-admin-tools` is already mirrored on GitHub, so its README must reflect this policy. ## Scope - Review README.md for issue and contribution-channel wording. - Remove or replace wording that conflicts with the accepted GitHub Issues policy. - Keep Forgejo identified as the primary development environment. - Make clear that reports opened through GitHub Issues are accepted and handled there. - Do not include unrelated README changes. ## Acceptance criteria - [ ] README.md has been checked against the current public README standard and documentation landscape. - [ ] README.md does not reject GitHub Issues as an external reporting or feedback channel. - [ ] Forgejo remains identified as the primary development environment. - [ ] Changed wording is consistent with the updated PUBLIC_README_STANDARD. - [ ] No unrelated README content is changed as part of this issue. ## Coordination Cross-repository documentation update coordinated with DAW/daw-docs. The same policy must remain consistent across all public Dragons@Work repositories.

michael added the

coordination/cross-repo

labels

2026-08-15 11:08:27 +02:00