public/librenotes
1
0
Fork 0
Code Issues 37 Pull Requests Actions Packages Projects Releases Wiki Activity

Set up community infrastructure: issue templates, PR template, and code of conduct #31

New Issue
Open
opened 2026-03-03 22:24:06 +01:00 by libretech · 0 comments
libretech commented 2026-03-03 22:24:06 +01:00
Owner
Copy Link

Parent

#28 — Epic: Prepare public launch, community infrastructure, and initial user onboarding

Summary

Create the community infrastructure files needed for open source collaboration. This includes Gitea issue templates (bug report, feature request), a pull request template, a CODE_OF_CONDUCT.md (Contributor Covenant), and a standalone CONTRIBUTING.md guide that covers development setup, coding standards, commit conventions, and how to submit PRs.

Acceptance Criteria

  • Bug report issue template exists and renders correctly when creating a new issue
  • Feature request issue template exists and renders correctly
  • Pull request template exists with checklist (tests, docs, changelog)
  • CODE_OF_CONDUCT.md is present in the repository root (Contributor Covenant v2.1)
  • CONTRIBUTING.md covers: dev environment setup, coding standards, branch naming, commit message format, and PR process
  • All templates and docs are linked from README.md

Dependencies

  • #29 (documentation) should be completed or in progress first, since CONTRIBUTING.md references the dev setup docs

Scope Notes

  • This issue covers only the template files and community docs, not the actual documentation content (that is #29)
  • Does not include setting up external community channels (Discord, Matrix, forum)
  • Does not include Gitea Actions automation for issue triage
## Parent #28 — Epic: Prepare public launch, community infrastructure, and initial user onboarding ## Summary Create the community infrastructure files needed for open source collaboration. This includes Gitea issue templates (bug report, feature request), a pull request template, a CODE_OF_CONDUCT.md (Contributor Covenant), and a standalone CONTRIBUTING.md guide that covers development setup, coding standards, commit conventions, and how to submit PRs. ## Acceptance Criteria - [ ] Bug report issue template exists and renders correctly when creating a new issue - [ ] Feature request issue template exists and renders correctly - [ ] Pull request template exists with checklist (tests, docs, changelog) - [ ] CODE_OF_CONDUCT.md is present in the repository root (Contributor Covenant v2.1) - [ ] CONTRIBUTING.md covers: dev environment setup, coding standards, branch naming, commit message format, and PR process - [ ] All templates and docs are linked from README.md ## Dependencies - #29 (documentation) should be completed or in progress first, since CONTRIBUTING.md references the dev setup docs ## Scope Notes - This issue covers only the template files and community docs, not the actual documentation content (that is #29) - Does not include setting up external community channels (Discord, Matrix, forum) - Does not include Gitea Actions automation for issue triage
libretech added the
phase-6
documentation
task
 labels 2026-03-03 22:24:06 +01:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
backend
Backend changes
database
Database changes
documentation
Documentation improvements
epic
frontend
Frontend changes
infrastructure
Infrastructure and deployment
launch
Launch and release tasks
phase-0
phase-1
phase-2
phase-3
phase-4
phase-5
phase-6
security
Security-related
task
Actionable task
No Label
documentation
phase-6
task
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
libretech
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: public/librenotes#31
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?