jldbc / jldbc/pybaseball

Add more maintainers

Open
#454 2 comments 6 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
1.7k
Forks
427
PR merge metrics
No merged PRs in 30d

Description

There hasn't been a pull request merged since July 2024. No new release since September 2023. Downloading Lahman data is broken. B-R queries are returning 503 errors. There are 33 active pull requests, four of which were created within the last week. There are two new issues in the last 24 hours. This code is still being used, and I'm not aware of anything (at least in the Python world) that would be a viable replacement.

This isn't to disparage anyone who is a current maintainer on this project. Maintaining any codebase is difficult work, let alone when you aren't being paid for it. But if the current maintainers no longer have the time or energy, then please pass it on to those who are able to be more active.

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 reviewing the project's current maintainer situation and the open pull requests and issues mentioned here. Done would require an agreed maintainer handoff and the necessary access changes, but this issue does not define that process.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
release
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.