Skip to content

Would you consider adding a LICENSE file? #23

Description

@sohei56

Hi! We depend on CodeEditSymbols in a small macOS app and want to ship it
with correct attribution for the packages we bundle.

This repository doesn't currently have a LICENSE file, and there's no license
statement in the README — so there's no explicit grant covering redistribution
of the package inside a distributed application. The sibling repos in the org
(CodeEdit, CodeEditSourceEditor) are MIT, so we suspect that's the intended
license here too and the LICENSE file just hasn't been added yet.

Would the team be open to adding the org's standard MIT LICENSE? It would let
downstream apps like ours reproduce the required attribution correctly.

We're also contributing fixes upstream — see #22 — so we're invested in the
package's health.

Thanks so much!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions