You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was building the project and I noticed a lot of outdated dependencies. So, I checked the issues and the PRs. There are 17 PRs dating back to 2023 many of them directly addressing broken dependencies (thank you dependabot).
While I do see sporadic commits, they all appear to be coming from a single source @2color although @dozyio was last seen in September.
I'm grateful for the efforts, and yes I'm volunteering to help, but I have concerns as to why so many PRs are just sitting there with no action taken.
If nothing else, it discourages people from helping.
Is it because this is a stable project now and all the excitement is going on somewhere else?
Thanks for any info and if you'd like some help I'm here for ya!
-- Update --
After digging deeper I can see that @2color is tirelessly working on many different branches at once. So it's not so much is this being actively maintained (yes it is), as what can we do to get the outstanding PRs closed?
The text was updated successfully, but these errors were encountered:
I was building the project and I noticed a lot of outdated dependencies. So, I checked the issues and the PRs. There are 17 PRs dating back to 2023 many of them directly addressing broken dependencies (thank you dependabot).
While I do see sporadic commits, they all appear to be coming from a single source @2color although @dozyio was last seen in September.
I'm grateful for the efforts, and yes I'm volunteering to help, but I have concerns as to why so many PRs are just sitting there with no action taken.
If nothing else, it discourages people from helping.
Is it because this is a stable project now and all the excitement is going on somewhere else?
Thanks for any info and if you'd like some help I'm here for ya!
-- Update --
After digging deeper I can see that @2color is tirelessly working on many different branches at once. So it's not so much is this being actively maintained (yes it is), as what can we do to get the outstanding PRs closed?
The text was updated successfully, but these errors were encountered: