clearlydefined / clearlydefined/license-score
Blog post about scoring algorithm
Open
- Dominant language
- Python
- Stars
- 2
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
from https://github.com/clearlydefined/clearlydefined/issues/74 by @fossygirl
> Once the scoring algorithm has been decided and implemented we should talk publicly about the criteria and talk about some examples cases.
Contributor guide
No contributing guide indexed for this repository
Research direction
First review the scoring algorithm and its implemented criteria, then identify representative example cases for the public explanation. The work is done when a blog post clearly documents the scoring criteria and illustrates them with examples; the issue does not name a file, test, or entry point to begin from.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100