My team has been using ReactXP for 2.5 years -- but mostly on React-Native -- the time has finally come to extract some of our stuff into a Design System that we can share between multiple mobile-apps, and our Web experience -- and hopefully publicly down the line we might open source it. -- We're pretty sure we have a great scaffold, but one crucial question that came up is whether RX will be an internal implementation detail, or if we'll expose RX details in our API Surface area (it's much more work to build a facade that hides RX!).

I've noticed that you recently updated things Eric Traut (@erictraut) + Mike Hardy (@mikehardy) -- so I have faith that this project is still alive!
That said, there are 68 open issues.

I was wondering if you were open to more maintainers supporting this project?
In particular, in the past, I & my team filed the following still-open issues, but for reasons (we weren't using/testing RX on web), we weren't super comfortable opening external PRs to solve them

• React-Native AsyncStorage -- Deprecated, Moved to React-Native-Community #1053
• [Feature] font-variant-numeric Alignment for numbers in tables #1093
• React Legacy ContextTypes API Deprecation / Migration #1128
• React-Native 60, 61, 62 - Compatibility Issues with reactxp 2.0.0 #1187
• Picker not part of RN core any more #1199 (Team-member filed)
• Proposal: Migrate reactxp's trunk branch from master to main #1221 (Cultural question)
• RFC: react-native 0.63 -- Pressable #1222 (Freshly filed today)

Separate from the issues that we filed ourselves, we're also interested in a bunch of the other open issues.

We've also in general been interested in many of the open PRs over time including #1126 -- Our design system library has a mandate to be accessible from the get-go, and we're setting as high a bar as we can justify to make sure that that happens. #1126 is crucial there!

My ask(s)

Do you want more maintainers on this project? I'd be happy to both submit PRs and help review PRs submitted by others.

Additionally, I'd love to be able to help labeling tickets, responding to them promptly, and closing them out after a reasonable time of staleness -- (just general housekeeping).

I'm not sure of the process of preparing a release, and obviously there might be reasons we're not privy to that require you to be the one to do this. But once I demonstrate competence I'm also willing to participate there.

I maintain a few other active & healthy projects OSS including apollo-link-rest, react-native-zendesk-chat, react-native-parsed-text and tipsi-stripe (Political concerns mean master branch/stable-release is stuck / this one is only partially maintained, but I've been maintaining a Discord channel with a thousand members that have been using the 8.0.0-beta releases in production for a year).

We might have as many as 30 contributors (across 4 teams) to our in-house Design System toolkit, so it would make me feel much more comfortable if we can ensure that reactxp is a healthy and active project!

I'm happy to submit further credentials or discuss context publicly or in a private message conversation.

Eric Traut (@erictraut) -- I assume you're in charge here :P