Relicensing to Apache-2.0: agreement of the contributors before the change
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 15/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- cpp
- Domain
- documentation
Research direction
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.
Written by the indexing model from the issue text.
Description
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.
- Dominant language
- C++
- Stars
- 5
- Forks
- 4
- Avg merge
- 1h 4m
- Merged PRs (30d)
- 71
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from CoreTrace/coretrace
-
documentation severity/minor
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
chore good first issue severity/minor
Difficulty 1/5 Under an hour Newbie friendliness 90/100
Maintainers usually reply within 1 day
-
build severity/minor
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
build good first issue severity/minor
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
test: add unit tests for ctrace::RunDirectoryPossibly taken @tecnolgd claimed this today. Opengood first issue test
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
All issues in CoreTrace/coretrace
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
1 type: problem 2 scope: firmware 3 good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
SpaceTeam/STS1_COBC_SW#511 ·
-
documentation good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
imaaiagent/fumi#3 ·
-
General perf
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
NVIDIA/TensorRT-LLM#20236 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 88/100
E3SM-Project/mam4xx#603 ·
Maintainers usually reply within 1 day