Moving a large project, particularly one that uses lots of the SF.net infrastructure, is non-trivial. Github only provides replacements for some of that infrastructure. Even if you can trivially move all of your code into github, and don&#x27;t rely on mailing lists, ticket tracker, file downloads, etc. you&#x27;ve still got to update documentation, download links across sites you may not have control over, change code that relies on sf.net links (for automatic updates, etc.).<p>For the project I work on, we moved code hosting to github years ago, but still have our downloads hosted by SF.net, and haven&#x27;t even thought of what to do about mailing lists and tickets. We&#x27;ll get around to moving it all, eventually, but for small teams working on a project with so many users, so many files, so many mailing lists, so many tickets, and just a lot of pieces that make up the &quot;project&quot;, it&#x27;s a lot of work, and the gains may not be immediately felt.<p>I don&#x27;t know where the NetHack team is in their migration, but it is apparent they&#x27;re working on it. I&#x27;m not gonna criticize them for not having it done already.<p>And, of course, there is no guarantee that github won&#x27;t turn evil, someday, too.