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

まず、リポジトリに残っている80件のプルリクエストを確認し、このissueで言及されているコメントのないaiobleの10件のPRに特に注意を払います。古い変更、マージコンフリクト、初歩的なテスト結果、動作する貢献を確認します。完了とは、関連するPRがレビュー後にクローズまたはマージされている状態を指します。

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! 🎆