Hi, and thanks for maintaining this — the per-make trouble-code data is genuinely hard to find anywhere else in a usable form.
The repository doesn't currently declare a licence, and GitHub reports it as NOASSERTION. Without one, the default position in most jurisdictions is all rights reserved, which makes the data risky to depend on even where you'd clearly be happy for people to use it.
Would you consider adding a LICENSE file? Two that fit this kind of dataset well:
- CC0 1.0 or ODbL if you think of it primarily as data
- MIT if you'd rather it match the tooling around it
Happy to open a PR adding whichever you prefer.
For context: I ship an iOS diagnostics app that reads OBD-II trouble codes, and obdb is the source I'd like to credit for the definitions. Right now I can credit the project but can't state the terms, which is the part I'd like to get right.
Hi, and thanks for maintaining this — the per-make trouble-code data is genuinely hard to find anywhere else in a usable form.
The repository doesn't currently declare a licence, and GitHub reports it as
NOASSERTION. Without one, the default position in most jurisdictions is all rights reserved, which makes the data risky to depend on even where you'd clearly be happy for people to use it.Would you consider adding a
LICENSEfile? Two that fit this kind of dataset well:Happy to open a PR adding whichever you prefer.
For context: I ship an iOS diagnostics app that reads OBD-II trouble codes, and obdb is the source I'd like to credit for the definitions. Right now I can credit the project but can't state the terms, which is the part I'd like to get right.