Include an Autograph client
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 20/100
Research direction
The issue only proposes including an Autograph client and does not name any files, tests, entry points, or expected behavior. Start by reviewing the repository structure and existing Autograph usage, then clarify the client’s scope and acceptance criteria before implementation. Done should mean the agreed client behavior is implemented and covered by tests.
Written by the indexing model from the issue text.
Description
Thanks @mozbhearsum for the idea.
- Dominant language
- Python
- Stars
- 5
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Contributor guide
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 mozilla-services/python-autograph-utils
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
mozilla-services/python-autograph-utils#3 · 1 comment ·
All issues in mozilla-services/python-autograph-utils
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
learningequality/ricecooker#747 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
BSData/horus-heresy-3rd-edition#3171 ·
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
run-llama/llama_index#23199 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
KhronosGroup/glTF-Blender-IO#2769 ·