Add a LICENSE file (the package currently has none)

未关闭 适合新手
#24 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

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

调研方向

首先,将 CodeEditSourceEditor 和 CodeEditTextView 中的 MIT LICENSE 文件与 CodeEditSymbols 的仓库根目录进行比较。与 maintainer 确认是否计划使用 MIT,然后添加适当的根 LICENSE 文件;当该 package 以与所引用的兄弟 package 一致的方式声明其许可证时,此 issue 即完成。

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

描述

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!

主要语言
Swift
星标
25
派生
15
PR 合并指标
30 天内没有已合并 PR

贡献指南

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

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

CodeEditApp/CodeEditSymbols 的其他 Issue

查看 CodeEditApp/CodeEditSymbols 的全部 Issue

相似的 Issue

更多 Swift Issue

把新 issue 发到你的邮箱

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