clearlydefined / clearlydefined/license-score
Full texts scoring element
- Dominant language
- Python
- Stars
- 2
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
We may need an extra "definition" data element for full license texts to flag if a file contain a given full license text used in the [License Text](https://github.com/clearlydefined/license-score/blob/b6f7ad16c51a2fb25320093e33152ff2481b0a72/ClearlyLicensedMetrics.md#license-texts) scoring elements : And may be we could only consider a full text as relevant only if they are also a top, key file?
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the License Text scoring-elements section in ClearlyLicensedMetrics.md. Clarify whether a separate definition element is needed and whether full texts count only in top or key files; done means the scoring rules and this decision are documented unambiguously.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100