Would you consider adding a LICENSE file?
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 68/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- swift
- Domain
- documentation
Research direction
Review the repository's current README and compare the licensing in the sibling CodeEdit and CodeEditSourceEditor repositories. Confirm that the org's standard MIT license applies here, then add the LICENSE file and a README license statement; done means downstream users can identify the redistribution and attribution terms.
Written by the indexing model from the issue text.
Description
Hi! We depend on CodeEditSymbols in a small macOS app and want to ship it
with correct attribution for the packages we bundle.
This repository doesn't currently have a LICENSE file, and there's no license
statement in the README — so there's no explicit grant covering redistribution
of the package inside a distributed application. The sibling repos in the org
(CodeEdit, CodeEditSourceEditor) are MIT, so we suspect that's the intended
license here too and the LICENSE file just hasn't been added yet.
Would the team be open to adding the org's standard MIT LICENSE? It would let
downstream apps like ours reproduce the required attribution correctly.
We're also contributing fixes upstream — see #22 — so we're invested in the
package's health.
Thanks so much!
- Dominant language
- Swift
- Stars
- 25
- Forks
- 15
- 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 CodeEditApp/CodeEditSymbols
-
Difficulty 1/5 Under an hour Newbie friendliness 74/100
-
Difficulty 3/5 1-2 days Newbie friendliness 72/100
-
enhancement
Difficulty 1/5 Under an hour Newbie friendliness 45/100
-
✨ Add C++ Symbol Openenhancement
Difficulty 3/5 1-2 days Newbie friendliness 30/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 25/100
All issues in CodeEditApp/CodeEditSymbols
Similar issues
-
area:dictation documentation P2
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
uttrflow/uttrflow-swift#1180 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
OneBusAway/onebusaway-ios#1451 ·
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100