CodeEditApp / CodeEditApp/CodeEditSymbols
Add a LICENSE file (the package currently has none)
還沒有人認領這個 Issue。
- 主要語言
- Swift
- 星號
- 25
- 分支
- 15
- 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 (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!
貢獻指南
這個儲存庫沒有索引到貢獻指南
從這裡開始
- 先讀完整個 Issue,再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫,在一個分支上完成修改。
- 送出 Pull Request,並在描述裡引用這個 Issue 編號。
研究方向
首先,將 CodeEditSourceEditor 和 CodeEditTextView 中的 MIT LICENSE 檔案與 CodeEditSymbols 的儲存庫根目錄進行比較。與 maintainer 確認是否預計使用 MIT,然後新增適當的根 LICENSE 檔案;當該 package 以與所參照的兄弟 package 一致的方式宣告其授權條款時,此 issue 即完成。
由索引模型根據 Issue 內容生成。
評估
- 技術堆疊
- swift
- 領域
- documentation
- Issue 類型
- 文件
- 難度
- 1/5
- 預估耗時
- 1 小時以內
- 活躍度
- 活躍
- 描述清晰度
- 基本清楚
- 新手友好度
- 74/100