Skip to content

Issues live in the repository they concern #4

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
marcos-mendez wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Issues live in the repository they concern #4

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions BRIEF.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -152,6 +152,12 @@ Ordering rationale: the spec first because it is the least invasive change and u
- Git: never squash, never rewrite history; keep the upstream remote; cherry-pick with attribution.
- A change of technical direction requires written justification with three parts: (1) why the previous approach does not work, (2) whether it can be made to work, (3) why the new approach is better. No exceptions.
- Process over result: if the process fails, fix the process. Never bypass it.
- **Issues live in the repository they concern.** Work that lands in a repository
gets an issue there and is closed by a pull request there. `tracker` is only for
what is common to the whole organization: cross-repo ordering, org-wide decisions,
things that belong to no single repo. Cross-referencing between the two is
encouraged; filing repo work in `tracker` instead of the repo is not. Open the
repo issue before delegating the work, never a task that exists only in a prompt.
- Licensing: forked code stays GPL. Licensing of new components is a maintainer decision.
- Documentation typography: no em dashes; use commas, colons, parentheses or semicolons; plain hyphen in numeric ranges.

Expand Down