inner.py carries an ASF header over MIT third-party code and is missing from LICENSE
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 84/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- python
- Domain
- documentation, release
Research direction
Start by comparing the existing kjetland/formly pattern and the ASF third-party policy. Update amber/src/main/python/core/util/customized_queue/inner.py, LICENSE, licenses-3rd-party-code/, and .licenserc.yaml; it is done when the MIT notice and bundled license text are present and the file is exempted.
Written by the indexing model from the issue text.
Description
Task Summary
amber/src/main/python/core/util/customized_queue/inner.py is vendored from
https://github.com/sebkeim/inner-class (MIT, Copyright (c) 2019 sebkeim) — the
file says so itself — but it carries the standard ASF header instead of the
MIT notice, and LICENSE does not list it. ASF policy forbids adding the ASF
header to third-party files and requires the third-party license to ship with
the work (https://www.apache.org/legal/src-headers.html#3party).
Found by the podling release-checker during the 1.2.1-incubating RC1 review;
the file is identical on main, release/v1.2 and release/v1.3 (in tree since
2022), so it affects the upcoming 1.3.0-incubating RC as well.
Fix, mirroring the existing kjetland/formly pattern: swap the header for the
MIT notice, add the LICENSE entry, bundle the license text under
licenses-3rd-party-code/, and exempt the file in .licenserc.yaml.
Task Type
- Refactor / Cleanup
- DevOps / Deployment / CI
- Testing / QA
- Documentation
- Performance
- Other
- Dominant language
- Scala
- Stars
- 316
- Forks
- 192
- Avg merge
- 4d 17h
- Merged PRs (30d)
- 141
Getting set up
- No Dockerfile or Docker Compose file
- Has a 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 apache/texera
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
apache/texera#8756 · 4 comments ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
apache/texera#8700 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
apache/texera#8682 · 5 comments ·
Maintainers usually reply within 1 day
-
JSONL File Scan reads a JSON null as the text "null"Possibly taken @CaroFernando claimed this 4 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
apache/texera#8674 · 1 comment · 1 assignee ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
[Rust][Flaky Test] multiple_deadlines_fire_in_order asserts a wall-clock gap instead of firing orderOpenCI/CD ⚒️ Flaky-tests 🐦
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
valkey-io/valkey-glide#7255 ·
Maintainers usually reply within 3 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
lichess-org/lila#21905 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day