Implement PEP-792 - Project status markers
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
Research direction
Start by reading PEP-792 to understand the proposed project status markers and how they are communicated. The issue names no files, tests, or entry points; done means implementing the standardized markers in the HTML and JSON simple indices described by the PEP.
Written by the indexing model from the issue text.
Description
This PEP proposes a standardized set of index-supplied project status markers, as well as a mechanism for communicating those markers in the HTML and JSON simple indices.
- Dominant language
- Python
- Stars
- 49
- Forks
- 88
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 31
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 pulp/pulp_python
-
Difficulty 3/5 1-2 days Newbie friendliness 68/100
pulp/pulp_python#1381 ·
-
Feature Triage-Needed
Difficulty 5/5 Over a week Newbie friendliness 45/100
pulp/pulp_python#1371 ·
-
Difficulty 5/5 Over a week Newbie friendliness 45/100
pulp/pulp_python#1360 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 52/100
pulp/pulp_python#1358 ·
-
Feature
pulp/pulp_python#1340 · 1 assignee ·
All issues in pulp/pulp_python
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
use-agent-os/agent-os#3314 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
BasedHardware/omi#15662 · 1 comment ·
-
documentation help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
AiursoftWeb/AnduinOS-2#19 ·