2038 is still a long way off, and many factors could obviously impact our future plans. The current plan is to evolve Y2038.com (after 2038) into a software services and consulting company (with a different name to be determined) that will exist long after 2038. The new company will continue to support Y2038.com customers and the y2038.com website, and will also help with any latent Y2038 issues.
We at Y2038.com strive to be the most accurate, relevant, and useful Y2038-related site, but of course, you can always Google for Y2038. We also maintain a page with external links here.
Yes. There are a surprising number of other time-related computer issues, although none are expected to be as critical as Y2038. For example, Apple Mac computers running versions of the Apple MacOS prior to OSX will have a time rollover similar to Y2038 on February 6, 2040. The date is different than Y2038 because the MacOS uses a different epoch (Jan 1, 1904) and 32-bit unsigned value for time, rather than a signed value. There is also an issue with the Network Time Protocol (NTP) which will have a rollover event in 2036. While there is a way to deal with the rollover in NTPv4, this could still affect operation of the Internet and serve as a last-chance call to action for Y2038.
For future date testing purposes, there are some tools available for DTS (Date/Time Simulation) for platforms including Windows, Linux, and z/OS.
There are presently no known code scanning tools specifically for Y2038, but based on the sheer magnitude of Y2038, such tools will undoubtedly become available. We plan to review as many Y2038-related products as possible and keep an up to date list with reviews here.