Sustainability and progress
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 15/100
- Issue type
- Documentation
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- git, python
- Domain
- developer-experience
Research direction
The issue names no files, tests, or entry points; start by reading the issue and the repository's open issue list. It does not define a code or documentation change or a completion condition, so there is no concrete definition of done.
Written by the indexing model from the issue text.
Description
With this issue I want to catch your attention to the fact that the development of pygit2 depends very much on your contributions.
As maintainer I do the following things:
- Review and merge pull requests. Occasionally there is a follow-up to a pull request where I do some further changes.
- Upgrade to new versions of libgit2 or Python.
- Releasing new versions of pygit2.
- Keep the build system and CI working.
- On rare occasions I pick up an issue or do some improvements by my own initiative.
This is the baseline, and it means that:
- New features are implemented by contributors through pull requests.
- The list of issues keeps piling up.
There are 2 important ways you can help the project with your time:
- Keep sending pull requests.
- Help with issues, specially helpful is to create a pull request that fixes an issue. But sometimes it's just to answer a question or help reproducing a bug.
If not with time, the other way to help is with money, so I've more time to spend in the project.
I've reviewed my sponsor page, hopefully you will find a tier that fits you.
I'm as well available for contract, since I'm a freelancer, to topics related to pygit2 (and others not related to pygit2). Just drop me an email at jdavid.ibp@gmail.com
- Dominant language
- Python
- Stars
- 1.7k
- Forks
- 408
- Avg merge
- 2d 57m
- Merged PRs (30d)
- 7
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 libgit2/pygit2
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
-
Difficulty 3/5 1-2 days Newbie friendliness 48/100
-
Difficulty 3/5 1-2 days Newbie friendliness 55/100
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 ·