CodeEditApp / CodeEditApp/CodeEditLanguages

Add a LICENSE file (the package currently has none)

未关闭 适合新手
#96 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看
主要语言
Swift
星标
133
派生
55
PR 合并指标
30 天内没有已合并 PR

描述

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 (CodeEditSymbols), 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!

贡献指南

这个仓库没有索引到贡献指南

调研方向

Check the repository root and compare the existing license treatment in CodeEditSourceEditor and CodeEditTextView. Add the intended license as a root LICENSE file, or document the chosen alternative clearly; done means the package no longer reports a missing license and downstream attribution has a definitive license to reference.

由索引模型根据 Issue 内容生成。

评估

技术栈
swift
领域
documentation
Issue 类型
文档
难度
1/5
预计耗时
1 小时以内
活跃度
活跃
描述清晰度
基本清楚
新手友好度
78/100

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。