violentmonkey / violentmonkey/violentmonkey.github.io

License

Open
#29 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
MDX
Stars
55
Forks
35
PR merge metrics
No merged PRs in 30d

Description

I understand that there may be issues with copying and modification (#16). However (assuming you don't want external contributors or have a CLA process), would it be possible to release non-JS components under, e.g., CC BY-ND 4.0? It's still a socially useful function to reproduce verbatim copies.

I'm unsure if CC BY 4.0 § 3(a)(1)(A)(ii) would require a copyright notice on every webpage from which the work is derived, but that might be worth looking into with a lawyer, if you want that sort of protection on a free license.

Also, if you do somehow want to accept contributions for the website, the Fiduciary License Agreement might be worth looking into with a lawyer.

(And a lawyer I am not. None of this post is legal advice.)

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files, tests, or entry points are named. Start by reviewing the project's current licensing and contribution terms, then determine whether the proposed licensing options are legally suitable with qualified counsel; done means a decided policy and corresponding documentation or license changes.

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
15/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.