Debian Package: licenscing question
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 45/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- python
- Domain
- documentation
Research direction
Start by locating the payload binaries in the repository and checking any accompanying license or source information. Determine their origin and whether corresponding source code exists; the issue does not name specific files or establish those facts. Done means clarifying the payload licensing and, if possible, adding distribution licensing information that addresses Debian packaging concerns.
Written by the indexing model from the issue text.
Description
Hello,
I am currently working on trying to get mtkclient into an official debian package. however there are concerns about whether the payload binaries will be allowed to be packaged under the DFSG, and i was hoping you could provide some clarification:
- Where did the payload binaries come from? are they sourced from someone else? or did you make them?
- Is there corresponding source code for the binaries?
- Would it be possible to add a distribution licensing information for these binary payloads?
Thanks. hopefully if we can get this sorted out it will make installing & using mtkclient a lot easier for people on debian based systems.
- Dominant language
- Python
- Stars
- 1.5k
- Forks
- 309
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 2
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from bkerler/mtkclient
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
bkerler/mtkclient#378 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100
bkerler/mtkclient#351 · 1 comment ·
Maintainers usually reply within 1 day
All issues in bkerler/mtkclient
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
ida-arbeitszeit/workers-control#1578 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
aws-samples/sample-per-model-bedrock#898 ·
Maintainers usually reply within 1 day
-
intake mcp-intake needs-human-review priority:high
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Ikalus1988/MisakaNet#5041 · 3 comments ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 86/100