Project Summary
Chocolate Doom is a Doom source port which aims to behave as closely as possible to the original DOS Doom executables.
There are a number of reasons for having a port which behaves like the DOS version:
* Just Doom. No more. No less. With all the flashy features that have been added to modern ports, it's easy to forget the original.
* DOS is dead. DOS Doom does not run properly under modern operating systems (Windows XP/Vista, Linux, MacOS X, etc). With hardware and software support for DOS fading away, it's hard to see a future where it's possible to play the original.
* Demo compatibility. The majority of demos are recorded for the original DOS Doom. Few ports maintain demo compatibility.
* Testing. Releasing a WAD "for Vanilla Doom" means that it will work on all ports.
In a Nutshell, Chocolate Doom...
- ...
- ...
-
...
has a well established, mature codebase
maintained by a large development team
with decreasing Y-O-Y commits -
...
took an estimated 60 years of effort (COCOMO model)
starting with its first commit in July, 2005
ending with its most recent commit about 1 month ago
Quick Reference
GNU General Public License v2.0 or later
Permitted
Commercial Use
Modify
Distribute
Place Warranty
Forbidden
Sub-License
Hold Liable
Required
Distribute Original
Disclose Source
Include Copyright
State Changes
Include License
These details are provided for information only. No information here is legal advice and should not be used as such.
Project Security
Vulnerabilities per Version ( last 10 releases )
There are no reported vulnerabilities
Project Vulnerability Report
Security Confidence Index
Vulnerability Exposure Index
Did You Know...
-
...
in 2016, 47% of companies did not have formal process in place to track OS code
-
...
check out hot projects on the Open Hub
-
...
55% of companies leverage OSS for production infrastructure
-
...
data presented on the Open Hub is available through our API
30 Day SummaryApr 23 2024 — May 23 2024
|
12 Month SummaryMay 23 2023 — May 23 2024
|
