Skip to content

feat: cookiecutter license prompt should include MIT as an option #1807

Open
@pnadolny13

Description

UPDATE: Edgar pointed out that we already have license as a prompt but its only Apache right now. I converted this issue to be for adding MIT as another option.

ORIGINAL DESCRIPTION:

We're finding that many open source SDK connector repos dont have a license. Many times the developer simply forgets to add one after using the cookiecutter to get started. Having a license be part of the getting started workflow should lead to more repos containing licenses.

Potential Solutions:

  • Add a few common permissive licenses to the cookiecutter template - MIT, Apache 2.0
  • Prompt the user to select a license while collecting info about the connector. If they want a custom license we can write a blank file to the repo as a placeholder
  • Alternatively we could add TODOs to the README, and docs to the guide to remind developers about the license, etc. This is less ideal though, maybe we could do it in addition to the cookiecutter options.

Metadata

Assignees

No one assigned

    Type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions