Unlike most commercial software offerings, Open Source software is seldom backed by a corporate entity, paid support staff, and the like. Instead, it is developed and maintained by volunteers, in an open, cooperative manner.

This system works very well, on its own terms, but it can be confusing or even frustrating to new users, corporate lawyers, etc. So, we have prepared the following troubleshooting guide:

Y2K Compliance

In general, Y2K (Year 2000) problems are found in software for business applications (for example, COBOL programs for accounting, inventory, etc.) Because most Open Source software is not of this sort, it tends to be free of Y2K problems.

This is not, however, a guarantee of Y2K compliance. Leaving aside the question of whether it is possible to prove that a program is Y2K compliant (we don't think so :-), most Open Source packages do not have any corporate backer who would be willing to make such an assertion.

More to the point, Open ReSource is not interested in answering questions about whether a given package is compliant. We do not have the resources that would be needed to examine packages for Y2K compliance and we aren't interested in setting them up.

If you are required to obtain a guarantee of Y2K compliance, we suggest that you engage a suitable consulting firm. A detailed code walkthrough may find at least some problems and may also provide some legal accountability, in case a Y2K bug emerges and causes problems.