01
Where tasks live
GitHub Issues is the single queue for everything except per-address outreach, which has its own purpose-built tracker.
| Kind of work | Tracked in |
|---|---|
| Code features & bugs | GitHub Issues on this repo |
| Outreach (per address) | The outreach tracker at /admin/outreach — see the outreach guide. |
| Research & data cleanup | GitHub Issues with the research label |
| Translations | GitHub Issues with the i18n label |
02
Labels
Label every issue so people can filter by track.
| Label | Meaning |
|---|---|
| code · research · outreach · i18n · design | The track the task belongs to, so people can filter to their own. |
| good-first-task | Well scoped and low context — ideal for a new collaborator. |
| blocked | Waiting on data, access or a decision. Say which, in a comment. |
| question | Needs maintainer input before it can move. |
03
Claiming & working a task
Claim
Comment "taking this" on the issue, or assign yourself. One task at a time until you know the codebase.Work
Branch as<type>/<short-description>and follow the pre-commit checklist.Update
If a task takes more than a week, drop a one-line status comment so it does not look abandoned. Stale claims — two weeks or more of silence — are fair game for someone else to pick up.Close
Once the pull request is merged, close the issue with a link to it.
04
Workstreams
The standing buckets new tasks fall into.
- 01
Map & timeline
Performance, clustering, time-slider states.
- 02
Data integrity
Date verification, geocoding fixes, duplicate cleanup.
- 03
Plaque program
Plaque pages, the inquiry form, the production pipeline.
- 04
Outreach
Occupant research and contact, driven by the tracker.
- 05
Localisation
German, Yiddish and Hebrew translation, and RTL support.
- 06
Frankfurt expansion
Extending the platform beyond Berlin.
05
Proposing new work
Open an issue describing what and why before building anything.
- New to the project? Filter for
good-first-taskand read the onboarding guide first.