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
Ideally, existing maintainers would grant GitHub Collaborator status to one or more users with a proven track record of multiple previously accepted PRs. Pragmatically, that's unlikely to happen.
Are there valid alternatives to plyer with similar scope and feature set still in active development? I pray to Octocat for a saner dev cycle in competing projects. 🙏 🙏
The text was updated successfully, but these errors were encountered:
To be fair its an impossible support task, you have to be fluent and current on all platforms so other people don't have to be. Very appealing to everybody else, but the waves are continually washing your sand castle off the beach.
Noted @leycec . Although not entirely accurate, the point is valid. But it's not "abandoned", it's just lacks the manpower for it to get the love it deserves. And yes, we do look for regular contributors to try and give them approval power, but they often move on. Most often people just fix the issue that's relevant to them and move on. Nothing wrong there, at least they give back, but it does mean big efforts (like plyer) seldom get constant attention.
Either way, this is not an action-able issue report, so I'm going to close this ticket. But thanks, would be great if you could help out in any way here.....
plyer is functionally dead for all intents and purposes. Active development all but ground to a halt last November despite a ludicrous number of passing open pull requests (PRs) and growing laundry list of critical open issues. The core idea is sound; the development effort is not.
Ideally, existing maintainers would grant GitHub Collaborator status to one or more users with a proven track record of multiple previously accepted PRs. Pragmatically, that's unlikely to happen.
Are there valid alternatives to plyer with similar scope and feature set still in active development? I pray to Octocat for a saner dev cycle in competing projects. 🙏 🙏
The text was updated successfully, but these errors were encountered: