Contributing as government staff
If you work for the City of Raleigh, Wake County or another government we describe: thank you.
You know your services best, and corrections from you are the fastest way to keep this catalog
accurate.
The lightest way: tell us what’s wrong
Open a Report inaccurate info issue, or ask a colleague with a GitHub account to do it. Your
report doesn’t need to be formal. “This number changed to …, see " is perfect.
Under our [corrections policy](../CORRECTIONS.md), reports about your own services are
treated as high priority.
Before contributing changes yourself
- Your work may belong to your employer. Unlike federal employees, whose work is generally in
the public domain, state and local government employees’ work products usually belong to their
employer. If you contribute during work hours or as part of your job, check with your
supervisor (and, if needed, your legal or IT office) first.
- What you’d be agreeing to. Contributions are signed off under the
Developer Certificate of Origin, a one-line statement that you have the right to
submit the change. There is no contract to sign and no copyright assignment.
- The licenses are permissive. Code is MIT. Catalog data is CC0 (public domain), so your
government can reuse anything here, including your own corrections, in official materials
without attribution or permission.
- Representing your employer. Unless you’re authorized to, please contribute as an
individual, and don’t present a change as an official position.
What we will and won’t do
- We will describe services accurately, in our own words, with links to your official pages.
- We won’t use your logos or seals, or present this project as official.
- We will never submit test requests to your systems, and our software never contacts them. The
only automated access is a weekly link check that sends one request at a time.
- If you’d like us to describe something differently, or stop describing it, open an issue and
we’ll work with you.