Treat abandoned as basically dead and gone forever. As Grant indicates, there's no point in even forking it, just create a new project starting from that one. Though I wouldn't worry about searching, since I've honeslty never searched for a repo on a place like github. I've always found them through a search engine.
Attribution requirements don't change for a fork or copy. Whatever the original license said must be maintained.
As it so happened, I found this project by deep searching GitHub. I figured someone had to have attempted this already. But in general I know what you mean.
Treat abandoned as basically dead and gone forever. As Grant indicates, there's no point in even forking it, just create a new project starting from that one. Though I wouldn't worry about searching, since I've honeslty never searched for a repo on a place like github. I've always found them through a search engine.
Attribution requirements don't change for a fork or copy. Whatever the original license said must be maintained.
As it so happened, I found this project by deep searching GitHub. I figured someone had to have attempted this already. But in general I know what you mean.
If anyone's curious, this is the repo in question: github.com/patience-tema-baron/rub...
Hints at a feature I want to implement 🙂
Why not try to email the author? It seems like an active developer on github and might just be ignoring issue emails for a while for whatever reason.
If you then don't get a response, I would start a new repo with this repo as foundation (having read all the other responses on this thread).