The real issue is getting new authorized committers enrolled. With superman gone, Void needs 10 mortals in his place. That’s the big issue about “owning” the Github project.
Github is a business. View things from a corporate standpoint. Github must see self-interest in doing right.
Each Github account ties to a legal entity, person or corporation, that agreed to Github’s ToS. Remind Github its ToS say it can terminate anyone, anytime, for any reason or none. Propose that someone else assume Github billing responsibility for Void Linux. That’s key, even if there’s no charge (yet).
Ask Github to contact Void’s founder with legal notice that failure to respond in 30/60/90 days constitutes consent to project transfer and/or account termination. That notice lifts liability. As well, Void’s founder gets a last chance. ToS give Github permission to serve legal notice by e-mail, but requires any notice to it in writing. So Github can just try to e-mail the founder. By ToS that e-mail constitutes legal notice.
Simultaneously, tell Github of intent to publicize its actions. Corporations hop for publicity. It’s not in Github’s interest to mishandle the situation. It should be taken as a chance to fill a corporate policy hole. What does Github do with abandoned projects?
For Void I would prefer self-hosted git to any corporate setup, but in any case: if Github flops, just migrate and get it over with. Void has many people volunteering free time and equipment but no good way to adopt them. The key to future health is more committers.
Script for Gitlab Migration
RhodeCode for best security
Plan.io for German hosting