micropython / micropython/micropython-lib

The number of open PRs is... kinda concerning.

Open
#474 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
2.9k
Forks
1.1k
Avg merge
7d 6h
Merged PRs (30d)
3

Description

On the one hand, I reluctantly get it. This is open-source volunteerism. We're all eternally thankful for the continual oversight by @jimmo and @dpgeorge. They deserve all our thunderous applause for their many years of die-hard service to the cause of a usable MicroPython stack.

On the other hand... the last repository commit was over a month-and-a-half ago and there are 80 outstanding PRs (as of this writing) – most of which haven't even received a single comment. I'm concerned about the health of this repository and the subprojects housed under it – especially aioble, @jimmo's blessed API that makes Bluetooth viable under MicroPython.

aioble has a plethora of open issues, many with known resolutions and working open PRs. Moreover, aioble alone has 10 open uncommented PRs by community stalwart @andrewleech. Like, I feel for this guy! That's enthusiastic commitment right there. And... we're squandering all of that enthusiastic commitment and community goodwill. You know?

Merging PRs in a (reasonably) timely manner is absolutely the most critical facet of open-source project management. We can drop everything else – even testing. But when we drop PR merging, that's really the final death knell.

If we don't have even the spare manpower to review and accept work that others are freely submitting of their own accord and scarce time, the road ahead to 2022 and beyond is clouded with uncertainty. Let's part by the clouds by either:

  • Closing obsolete and broken PRs with merge conflicts.
  • Merging recent and working PRs with no merge conflicts that pass rudimentary scrutinity. Bonus points for PRs with one or more working tests.

Thanks again for all the h0t libs, @jimmo and @dpgeorge. Happy New Year! 🎆

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

Start by reviewing the repository's 80 outstanding pull requests, with particular attention to the 10 uncommented aioble PRs mentioned in this issue. Check for obsolete changes, merge conflicts, rudimentary test results, and working contributions; done would mean the relevant PRs are either closed or merged after review.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
developer-experience
Issue type
Refactor
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.