Clarify the license for pantry manifests and build recipes

未关闭
#14,756 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
2/5
预计耗时
1-3 小时
新手友好度
50/100
Issue 类型
文档
描述清晰度
基本清楚
活跃度
活跃
领域
documentation

调研方向

The issue asks maintainers to clarify the license for pantry metadata and build recipes, and offers a license-file PR if Apache 2.0 is confirmed. First read the repository license history and linked issue #10021, then check whether a maintainer has established the intended terms. Done means the policy is confirmed and documented; the issue alone cannot determine the license choice.

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

描述

I’m evaluating pantry for use in a project and would like to clarify the terms for reuse/mirroring of manifests and build recipes.

I couldn’t find a license file in this repository. I found #10021, where @jhheider reassured another project about using pantry, which was encouraging but not binding.

Is Apache 2.0, as used by the pkgx client, also the intended license for the existing pantry content? Or is there another license or policy that applies?

If Apache 2.0 is the intended choice, I’m happy to submit a small PR adding the license.

The clarification I’m looking for is for pantry’s own metadata and build recipes - I understand that the packaged software has its own license terms.

Thanks!

主要语言
C
星标
199
派生
140
平均合并
4 小时 48 分钟
30 天内合并 PR
123

环境准备

在 Codespaces 中打开

在浏览器里用你自己的 GitHub 账号启动这个项目的开发容器。

  • 没有 Dockerfile 或 Docker Compose 文件
  • 有 Pull Request 模板
  • 没有贡献指南

从这里开始

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

pkgxdev/pantry 的其他 Issue

查看 pkgxdev/pantry 的全部 Issue

相似的 Issue

更多 C Issue

把新 issue 发到你的邮箱

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