libgit2 / libgit2/pygit2

Sustainability and progress

Open
#1,357 0 comments 5 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
1.7k
Forks
408
Avg merge
2d 57m
Merged PRs (30d)
7

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

Contributor guide

Open the contributing guide

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.

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.

Assessment

Tech stack
git, python
Domain
developer-experience
Issue type
Documentation
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
15/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.