-
Notifications
You must be signed in to change notification settings - Fork 354
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Project still alive? #150
Comments
There's a release this year so yes? |
Hi, the project is alive and well. We (@quintschaf) took over the maintenance of the project and we've shipped quite a few releases since Siteline stopped working on it. We're trying to keep the project somewhat up-to-date and ship fixes to existing issues whenever possible. However, since the maintenance of Introspect is very time-consuming (thanks to numerous quirks in SwiftUI itself) and it's not our primary focus we're a bit behind on some things. We're pretty much maintaining the project in our very limited free time, but PRs are always welcome. |
Great :) Thanks for your answer and maintaining the project 👍 |
Adding on to what everyone else said here, it's probably just about maintainers not having enough time and effort. i totally relate to splittydev, as i maintain some open source libraries myself. i'm not even a full time worker, i'm still a student and i can't imagine how people with full time jobs can squeeze enough time to struggle on maintaining open source projects - i love software but it's really on the bottom of my priorities |
CTO of Siteline here. If you think we should expand the set of maintainers on the project, please let us know! Happy to accommodate. We've paused our mobile development efforts but recognize how widely adopted this project is and want to continue to support. Let me know! |
@joelpoloney I think this project might need some more maintainers in order to keep merging important changes such as #165 which seems to improve the reliability of this library across the board. |
Good push @davdroman @jevonmao @Urkman |
Is this project still maintained?
The text was updated successfully, but these errors were encountered: