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

Clarify licensing

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

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
35/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
documentation

Research direction

Review the LICENSE file and README, then compare the project’s stated licensing with the referenced python-sourcemap repository. Document the requested copyright, Apache license copy, and attribution for the borrowed portions, while preserving the project’s existing licensing information.

Written by the indexing model from the issue text.

Description

Hi! Nice library, thank you for making it and packaging it up.

You mention that it's based on code from https://github.com/martine/python-sourcemap. I'm not a lawyer, but I am pretty sure that this makes your library a derivative work, which means you must include @martine's copyright, a copy of the Apache license, and make a note of which parts of the code are by @martine (which would be covered by the Apache license instead of the BSD license). You'd probably be best off mentioning all of this in the LICENSE file and/or readme.

Dominant language
Python
Stars
43
Forks
15
No merged PRs in 30d

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.

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.