Call for maintainers

[jchitel]

I'm currently twiddling my thumbs while waiting for #56 to be merged, so I decided to take a look at the insights.

The last commit was some README updates in July, and the last actual code change was back in May, before the first iOS 14 beta.

I was tempted to copy this project's code into my project so that I can fix the problems I was having, but upon reading some of the code, I'm realizing that this is a pretty solid project. It's well-documented, the code is clean, it's written in a safe way, and it's tested. It's just currently suffering from a lack of love.

I would be happy to fork this repo and take ownership of the library, but I work full-time so I wouldn't always have much time to maintain it.

Is there someone else who has the availability to take proper ownership of this project? Or is there anyone on the current contributors list who would like to chime in?

[ldiqual]

@jchitel thanks a lot for opening an issue. For some context: we created this library when we were working on the Siteline iOS app. Priorities have shifted and we're now focusing efforts on Siteline web, which means we haven't developed for iOS in a while, nor used the Introspect library. It makes it pretty hard for us to maintain it at the moment.

We do plan on focusing back on iOS in the upcoming months, but not quite yet. However, we do acknowledge that this library has become essential for a lot of projects, and we'll be happy to welcome new maintainers. If this is something you're interested in, please reply to this thread and we'll add you to the project. We're also happy to go through the release process anytime a maintainer asks to.

I'm also going to allocate some of my time every week to keep up with issues and pull requests. Thanks for your patience while I get all this started again.

[SergeiMeza]

I want to help

[ldiqual]

@SergeiMeza Awesome! What's your email address? I'll followup with you directly

[dsa28s]

Hello @ldiqual! This project is a big contribution to developing my project. I'm very interested in this project. I'd like to help with this project.

[SplittyDev]

I'm interested too, my company (@Quintschaf) is using Introspect a lot. We're interested in keeping the SwiftUI ecosystem going and we're building OSS around SwiftUI ourselves.

We'd happily help maintaining PRs and doing QA. Please contact me at marco@quintschaf.com :)

[ldiqual]

We've now added @SplittyDev and @JannThomas to the Introspect maintainers, and they've revived this project quite a bit! I don't think there's a pressing need for maintainers anymore, so I'm closing this issue

[ldiqual]

We're now looking for more maintainers to keep the project going, as requested in https://github.com/siteline/SwiftUI-Introspect/issues/150. Please respond in this thread if you're interested!

[davdroman]

@ldiqual I'm interesting in being a maintainer. I actually maintain a moderately well-received library that leverages Introspect as a key component, so I'm very much reliant on it.

[ldiqual]

@davdroman neat! Would you mind shooting me an email at lois@siteline.com? Thank you!

[davdroman]

Due to personal reasons I'm no longer able to dedicate time to maintaining this project. I'm going to reopen this issue and pin it to hopefully find some new maintainers who might be keen on it.

cc/ @ldiqual — thank you for the opportunity, it's been an honor.

[Alex293]

I’d love to help as this project saved me from the corners of SwiftUI a couple times. I’ll have a look at open issues I the mean time.

[GeorgeElsham]

This project truly is essential to bridging the gap that Apple hasn't quite done yet. I do try use this package minimally in my own projects but I often do fallback to it. I'm in the top 10 on Stack Overflow for the swiftui tag (albeit I haven't actively answered in years now) and have referenced people to this project countless times and probably brought a decent chunk of people to use SwiftUIIntrospect. I've also occasionally replied to issues and made some issues recently on this project.

I've not developed on this project directly but I'm reasonably familiar with the codebase as a whole. Since I currently rely on this project and will likely do so for the foreseeable future, I'd be happy to nominate myself as a maintainer. This would be in my free time but I'd be happy to help and give back. Let me know if you'd be interested, thank you.

[davdroman]

@ldiqual would be great for @Alex293 and/or @GeorgeElsham to get added so they can take over. I'm available for basic infra maintenance and PR merging but have no time for active development of new features or fixes.