Maintenance Status

Open
#395 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Quiet
Tech stack
python

Research direction

Start by reading the README and PR #393 to understand the repository's current review path and pending contribution. Confirm who can enable tests, review, and merge pull requests, then determine whether a README note and CODEOWNERS file are appropriate. Done means the maintenance status and review contacts are clearly documented, if maintainers approve the change.

Written by the indexing model from the issue text.

Description

I'm opening this issue to ask about the current maintenance status of this repository, as it is not obvious to me who has the privileges to enable tests, review, and merge pull requests.

I'm asking because a small, CLA-signed, mergeable PR I opened (#393) has been waiting for review for three weeks, and since there is no CODEOWNERS file, I don't see a clear path to whom I should contact for a review.

Questions:

  • Is the repository still actively maintained, and who are the current maintainers contributors should tag for review?
  • Would maintainers be open to adding a short README note and a CODEOWNERS file clarifying the review process?
    Thanks for maintaining this useful repository!
Dominant language
Python
Stars
304
Forks
104
PR merge metrics
No merged PRs in 30d

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.

More from microsoft/python-type-stubs

All issues in microsoft/python-type-stubs

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.