Add license for all files in the ArduinoCore-API repo
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- cpp
- Domain
- documentation
Research direction
Start by reviewing the repository files identified in the issue, including Interrupts.h, and compare their license information with the Arduino FAQ. Determine the appropriate license wording with maintainer or legal guidance, then add a repository-level LICENSE file and consistent license information to the applicable files. Done means the licensing status of all included files is explicit.
Written by the indexing model from the issue text.
Description
Some files (e.g. Interrupts.h) do not contain any license information. This makes them proprietary, so noone can copy / fork this repository without your explicit allowance. This contradicts the information "the C/C++ microcontroller libraries are under the LGPL" (see Arduino FAQ). If you want to make them useable, please add license information to those files.
Additionally, please add a LICENSE file to the ArduinoCore-API repository. This would make it easier to be sure about the license status of the included files. Currently users have to check the license information in each individual file before e.g. copying / modifying / redistributing.
You could start by checking whith your lawyer if LGPL 2.1 or newer would be the best choice for the LICENSE file or if the LICENSE file has to specify the license for each file individually.
- Dominant language
- C++
- Stars
- 306
- Forks
- 150
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
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 arduino/ArduinoCore-API
-
Difficulty 3/5 1-2 days Newbie friendliness 25/100
arduino/ArduinoCore-API#261 ·
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 30/100
arduino/ArduinoCore-API#256 ·
-
enhancement
Difficulty 3/5 1-2 days Newbie friendliness 48/100
arduino/ArduinoCore-API#251 · 1 comment ·
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 35/100
arduino/ArduinoCore-API#250 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
arduino/ArduinoCore-API#249 ·
All issues in arduino/ArduinoCore-API
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
duckdb/duckdb-wasm#2258 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
objectionary/eo-graphs#75 ·
-
Coarray integration tests carry no LABELS, so run_tests.py silently skips them under every backend Opencoarray
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
FISCO-BCOS/FISCO-BCOS#5642 ·