linebender / linebender/linebender.github.io
Be more specific with licensing
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 10
- Forks
- 12
- Avg merge
- 5d 6h
- Merged PRs (30d)
- 1
Description
This feels slightly off to me; in particular, what counts as code? Like, is it content in code blocks - what happens if someone moves some content between code blocks and not in a code block?
I think the simplest solution might be to just dual-license everything as both/either CC-BY and Apache, unless anyone else has a better suggestion. Whatever the final scheme is, we should probably describe it in a README of this repo.
-- @DJMcNab (Copied from comment in #10)
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.
Research direction
Review the licensing discussion copied from issue #10 and determine the final licensing scheme, including what counts as code and content. Document the agreed scheme in a README for this repository; the issue is complete when the policy is specific and recorded.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100