Unnecesary licence files
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 42/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Stale
- Domain
- documentation
Research direction
Start by reviewing the licence files under data/ and the relevant files that note the sources of the colours. Check whether any repository references depend on those files and confirm the project’s preferred attribution policy. Done means the unnecessary files are removed while required source acknowledgements remain intact.
Written by the indexing model from the issue text.
Description
IANAL, but I noticed the licence files under data/ and to the best of my understanding neither particular colours nor colour schemes can be copyrighted (particular shades can be trademarked, but that's another matter). In the source repositories, the code surrounding the colours themselves may be covered by copyright, but not the colours themselves.
References:
- Compendium of U.S. Copyright Office Practices § 906.3 "Mere coloration or mere variations in coloring alone are not eligible for copyright protection"
- In some recently outdated EUIPO guidelines I see "A single colour may of course be an element of a design, but on its own it does not comply with the definition of a design because it does not constitute the ‘appearance of a product’.", in the newer guidelines the only mention of colour I see is under the grounds for refusal.
- Given the Berne Convention and the TRIPS Agreement, it seems wholly reasonable to presume that US copyright guidelines on colour extend internationally.
As such, while it's polite to note the source of the colours in the relevant files, I think actually copying the licences is a bit excessive and would advocate for their removal.
- Dominant language
- Julia
- Stars
- 268
- Forks
- 44
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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 JuliaGraphics/ColorSchemes.jl
-
Colorcet NamingOpen
Difficulty 3/5 1-2 days Newbie friendliness 45/100
JuliaGraphics/ColorSchemes.jl#143 · 1 comment ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
JuliaGraphics/ColorSchemes.jl#132 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
JuliaGraphics/ColorSchemes.jl#121 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 40/100
JuliaGraphics/ColorSchemes.jl#115 ·
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
JuliaGraphics/ColorSchemes.jl#84 · 2 comments ·
All issues in JuliaGraphics/ColorSchemes.jl
Similar issues
-
`AMSGrad` state starts at `epsilon` instead of zero, so zero gradients move parameters and small gradients are dampedPossibly taken @parth-patel010 claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
FluxML/Optimisers.jl#247 · 1 comment ·
-
Difficulty 1/5 Under an hour Newbie friendliness 82/100
OpenFUSIONToolkit/GPEC#644 ·
Maintainers usually reply within 3 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 62/100
SciML/DataDrivenDiffEq.jl#694 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
JuliaLang/LinearAlgebra.jl#1834 ·
Maintainers usually reply within 1 day