Default community health files for nxm-rs organization. Because even chaos needs structure.
- Issue Templates: Bug reports and feature requests that get to the point
- PR Template: What changed and why it won't break everything (hopefully)
- Contributing Guidelines: How to contribute without wasting everyone's time
These templates automatically apply to all repositories in the nxm-rs organization that don't have their own .github folder.
If you need different templates for your specific repository:
- Create your own
.github/folder in your repo - Add your custom templates
- They'll override these defaults
We use a pragmatic labeling system across all repos:
p0-fire: Production is burningp1-broken: Actually broken, fix this weekp2-annoying: Not broken but annoyingp3-maybe: Nice to have, probably never happens
blocked: Can't proceedinvestigating: Someone's looking at itpr-welcome: We want this but won't do it
bug: Code does the wrong thingfeature: New capabilitydx: Developer experience issuesperf: Performance problemsdebt: Technical debtdocs: Documentation issues
effort/minutes: Quick fixeffort/hours: Few hours workeffort/days: Few days workeffort/weeks: Week+ of work
We write code that works. We fix bugs that matter. We build features that solve real problems.
No corporate theater. No process for process's sake. Just pragmatic engineering.