Add a LICENSE file (the package currently has none)

Open Beginner friendly
#24 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
74/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Active
Tech stack
swift
Domain
documentation

Research direction

Start by comparing the MIT LICENSE files in CodeEditSourceEditor and CodeEditTextView with the repository root of CodeEditSymbols. Confirm with a maintainer whether MIT is intended, then add the appropriate root LICENSE file; the issue is done when the package declares its license consistently with the referenced sibling packages.

Written by the indexing model from the issue text.

Description

Hi, and thanks for the package — the editor stack is a pleasure to build on.

This repository has no license file. There is none in the repository root, none
in the source tree, and GitHub's API reports "license": null for it. The same
is true of the sibling package (CodeEditLanguages), while
CodeEditSourceEditor and CodeEditTextView both carry MIT.

Why this matters downstream: without a license the default applies, and the
default is "all rights reserved" — no permission to redistribute. Both packages
are listed in the CodeEditSourceEditor target's own dependencies, so every
application that uses the editor redistributes them inside its binary. I ship a
macOS application built on CodeEditSourceEditor, and when I put together the
attribution notice for it I could only write "no license declared upstream" for
these two, which is not a comfortable line to publish and is presumably not what
you intended either.

If MIT was the intent — as it is for the rest of the project — adding the usual
LICENSE file would settle it. If a different license is intended, that would be
just as useful to know; the point is only that the file be there.

Happy to open a PR with an MIT LICENSE matching CodeEditSourceEditor's if that
helps.

Thanks!

Dominant language
Swift
Stars
25
Forks
15
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from CodeEditApp/CodeEditSymbols

All issues in CodeEditApp/CodeEditSymbols

Similar issues

More Swift issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.