Skip to content

Add a LICENSE file to clarify usage & redistribution terms #1621

Description

@norse75

Hi, and thanks for putting this collection together — it's a genuinely useful haul.

One small thing that's blocking us (and probably others) from adopting it with
confidence: the repo doesn't have a LICENSE file. Without one, the default is
"all rights reserved," which makes teams hesitant to use or build on the skills
even when that clearly isn't the intent of an "awesome-*" list.

Would you consider adding a license — MIT or Apache-2.0 are the usual choices for
this kind of collection? If some skills are aggregated from other sources, a quick
note on their provenance/terms would help too.

Really appreciate the work. A license file would let a lot more people actually use it.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions