Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Licensing

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

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Active
Domain
documentation

Research direction

Review the current LICENSE.md file in the repository root and the docs/LICENSE.md. Understand the implications of MIT vs. non-commercial licenses and the legal process for changing license holders. Research how other projects like kelp handle licensing. Determine the steps to propose a new license, including updating files and obtaining consent from stakeholders.

Written by the indexing model from the issue text.

Description

Currently MIT licensed to Encode OSS Ltd.

Could consider a free-for-non-commercial-use type license. Eg... see kelp.

Also could consider opening out the license holders. Perhaps staying under "Encode OSS Ltd" is a reasonable balance? Keeps my name out of the spotlight, without getting too airy. Seems like a reasonable starting point at least. Could feasibly be changed with consent at a later date.

Also interesting that GitHub treats LICENSE.md as special (shows in UI) though not docs/LICENSE.md.
In contrast both README.md and docs/README.md are treated as special.

Dominant language
Python
Stars
32
Forks
2
Avg merge
8h 51m
Merged PRs (30d)
15

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.

More from encode/mkdocs

All issues in encode/mkdocs

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.