Sustainability and progress
Dieses Issue hat noch niemand übernommen.
- Vorherrschende Sprache
- Python
- Sterne
- 1.7k
- Forks
- 408
- Ø Merge
- 2 T. 57 Min.
- Gemergte PRs (30 T.)
- 7
Beschreibung
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
Beitragsleitfaden
Erste Schritte
- Lies das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreib ins Issue, dass du es übernimmst — das erspart doppelte Arbeit.
- Forke das Repository und arbeite in einem Branch.
- Öffne einen Pull Request, der die Issue-Nummer nennt.
Rechercherichtung
Das Issue nennt keine Dateien, Tests oder Einstiegspunkte; beginne damit, das Issue und die Liste der offenen Issues des Repositorys zu lesen. Es definiert weder eine Code- oder Dokumentationsänderung noch eine Abschlussbedingung, daher gibt es keine konkrete Definition of Done.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Bewertung
- Tech-Stack
- git, python
- Bereich
- developer-experience
- Issue-Typ
- Dokumentation
- Schwierigkeit
- 5/5
- Geschätzter Aufwand
- Über eine Woche
- Aktivitätsstatus
- Veraltet
- Klarheit
- Muss geklärt werden
- Anfängerfreundlichkeit
- 15/100