Relicensing to Apache-2.0: agreement of the contributors before the change
维护者通常 1 天内回复
已经有一个关联 PR 被合并了。
- #182 来自 @SizzleUnrlsd —— 已合并
评估
- 难度
- 1/5
- 预计耗时
- 1 小时以内
- 新手友好度
- 15/100
- Issue 类型
- 文档
- 描述清晰度
- 描述清楚
- 活跃度
- 活跃
- 技术栈
- cpp
调研方向
The issue names docs/licensing.md as the place that will link to this record. Read the license history and requested contributor statements in the issue, then check whether both contributors have replied with agreement. Done when both agreements are recorded and this issue is linked from docs/licensing.md.
由索引模型根据 Issue 内容生成。
描述
CoreTrace moved to the Apache License 2.0 at the end of March 2026:
| Repository | Before | Since |
|---|---|---|
coretrace |
GPL-3.0 | Apache-2.0, 2026-03-29 (#33) |
coretrace-compiler |
GPL-3.0 | Apache-2.0, 2026-03-29 |
coretrace-stack-analyzer |
no license (all rights reserved) | Apache-2.0, 2026-03-30 |
A license change needs the agreement of every author whose code is in the work. Apart from @SizzleUnrlsd, two people authored commits on main before the change:
- @Arthurvroum: 7 commits in
coretrace, 10 incoretrace-compiler, 7 incoretrace-stack-analyzer; - @shookapic: 2 commits in
coretrace.
Contributions made since the change are already under Apache-2.0 (section 5 of the license).
@Arthurvroum, @shookapic: could you each reply with the sentence below? It records your agreement for those earlier contributions.
@Arthurvroum:
I, Arthur Mazeau, agree that my contributions to CoreTrace/coretrace, CoreTrace/coretrace-compiler and CoreTrace/coretrace-stack-analyzer made before their change to the Apache License 2.0 are licensed under the Apache License, Version 2.0.
@shookapic:
I, Cédric Roulof, agree that my contributions to CoreTrace/coretrace made before its change to the Apache License 2.0 are licensed under the Apache License, Version 2.0.
Once both have answered, this issue will be closed and linked from docs/licensing.md.
- 主要语言
- C++
- 星标
- 5
- 派生
- 4
- 平均合并
- 1 小时 57 分钟
- 30 天内合并 PR
- 88
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
CoreTrace/coretrace 的其他 Issue
-
chore good first issue severity/minor
难度 1/5 1 小时以内 新手友好度 90/100
维护者通常 1 天内回复
-
build severity/minor
难度 2/5 1-3 小时 新手友好度 84/100
CoreTrace/coretrace#176 · 1 条评论 ·
维护者通常 1 天内回复
-
build good first issue severity/minor
难度 2/5 1-3 小时 新手友好度 85/100
维护者通常 1 天内回复
-
Inputs: a file name starting with @ may be read as a response file by the compiler可能已有人在做 @SizzleUnrlsd 今天认领。 未关闭bug severity/minor
CoreTrace/coretrace#203 · 已指派 1 人 ·
维护者通常 1 天内回复
-
Builds without a build type are unoptimized: the README's commands and CI's main job可能已有人在做 @SizzleUnrlsd 于 2 天前认领。 未关闭build severity/minor
CoreTrace/coretrace#192 · 已指派 1 人 ·
维护者通常 1 天内回复
查看 CoreTrace/coretrace 的全部 Issue
相似的 Issue
-
bug
难度 2/5 1-3 小时 新手友好度 82/100
维护者通常 1 天内回复
-
Mac mini M6 (16 GB): Q2_0 streaming works - measured 11.7->27.2 tok/s + arena fix for sub-32 GB Macs未关闭
难度 2/5 1-3 小时 新手友好度 68/100
维护者通常 1 天内回复
-
champion good first issue remake source/qq
难度 2/5 1-3 小时 新手友好度 65/100
metasequoiaime/msime-windows#1025 ·
维护者通常 1 天内回复
-
backlog bug
难度 2/5 1-3 小时 新手友好度 75/100
EchoTools/nevr-runtime#653 ·
维护者通常 1 天内回复
-
`--fail-require-skip` never fires: run_tests.py searches stdout, but the unittest binary writes the skip summary to stderr可能已有人在做 关联的 PR 仍在进行中或已合并。 未关闭
难度 2/5 1-3 小时 新手友好度 72/100
维护者通常 1 天内回复