github / github/copilot-cli

LICENSE Clarification

未关闭
#1,962 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看
triage
主要语言
Shell
星标
11.2k
派生
1.9k
平均合并
14 小时 16 分钟
30 天内合并 PR
6

描述

As a user of `pixi` which is part of the `conda` ecosystem, I'd like to package `copilot-cli` for `conda-forge` so I can easily install it with `pixi global install copilot-cli`, or specify it as a dependency of an application.

The `conda` package would just include the `copilot-cli` binary, along with metadata such as the version and any dependency information (none for the `copilot-cli`). This would be redistributing on a standalone basis, as a `conda` package, but is necessary to specify it as a dependency of a `conda` application.

This would appear to contradict the license clauses below:
https://github.com/github/copilot-cli/blob/28d2487331bab53f92cc72bd703ebf2c2dca6d5c/LICENSE.md?plain=1#L9-L10

I have a couple of questions:
1. Am I correct and the license prohibits distributing as a `conda` package?
2. If so, is there any chance of removing that restriction, either completely, or specifically for distributing as a `conda` package?

贡献指南

打开贡献指南

调研方向

Read LICENSE.md, especially the clauses linked in the issue, and review how a standalone conda-forge package would redistribute the copilot-cli binary. The issue is done only when the licensing question has a maintainer-approved answer and, if a change is accepted, the license text reflects it.

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

评估

领域
documentation
Issue 类型
文档
难度
5/5
预计耗时
一周以上
活跃度
冷清
描述清晰度
需要澄清
新手友好度
25/100

把新 issue 发到你的邮箱

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