Skip to content

Add a LICENSE file #1

Description

@mmsaki

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions