All aboard the hype train. Seriously, tho. The code history is the important part and DVCS provides plenty of redundant offline backups. If people want issues

All aboard the hype train. Seriously, tho. The code history is the important part and DVCS provides plenty of redundant offline backups. If people want issues saved offline, GitHub provides an API that makes it relatively easy to pull down the issues. It wouldn't take a monumental effort to create an offline client. Maybe if GitHub added some metadata to their models/api, it would be possible to diff the changes, cache data offline, and reduce requests. Just don't version issues because recording all of the changes over time isn't worth saving.