Add CONTRIBUTING.md (contribution & review guidelines) #350
Labels
No labels
breaking change
bug
documentation
enhancement
needs discussion
needs implementation
new nut
ready
wallet-only
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
forgejo-admin/nuts#350
Loading…
Add table
Add a link
Reference in a new issue
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?
We currently don’t have a CONTRIBUTING.md in this repo. That makes it harder for new contributors to know how to propose NUT changes, open PRs, and get reviews.
Proposal
Add a top-level CONTRIBUTING.md that covers:
• How to propose changes to existing NUTs vs propose a new NUT
• Expected structure for PRs (what to include, links, rationale, backwards-compat notes)
• Review process expectations (who to ping, when a PR is “ready”)
• Style conventions (markdown conventions, naming, formatting)
• How to handle controversial changes (when to open discussion first)