Is this repo abandoned?
Closed this issue · 5 comments
Documentation Is:
- Missing
- Needed
- Confusing
- Not Sure?
Please Explain in Detail...
Users of this library need to know if this repository is going to be maintained or not going forward.
If it is, great -- we can wait till you have some free time.
If not, we need to know so one of us can create a fork (or be added as a maintainer of this repo), to keep the project maintained. (there are several issues that affect its functionality currently, with solutions posted in the issue comments and merge requests, but they have so far not been added)
Your Proposal for Changes
Okay, I'll take that as a no. ^_^
Anyone willing to take up the project's maintenance?
If someone comes along who's willing to do so, we'd then need to get in contact with @richtr to ask him to add that person as a maintainer of the repo.
If we're unable to contact him... well that would be unfortunate since this is the most widely used library/repo for this functionality. I suppose someone would need to fork it, and we'd redirect people to that fork in the answers/comments mentioning this library. (on StackOverflow and such)
EDIT
==========
Some forks I've found (with some improvements made):
https://github.com/ViRPo/NoSleep.js
https://github.com/shinyshoe/mosleep
Perhaps I'll contact them and ask if one is willing to have their fork become the "new pseudo-official fork".
For what it's worth, there is a webcomponent WakeLock repo here. Disclaimer: I am the author.
Chrome 79 adds the Wake Lock API as Origin Trials 🎉
read more:
https://developers.google.com/web/updates/2019/12/nic79#wake-lock