Build Type

Official Mac Source Ports Build

Mac Source Ports handles the official build for this project, often posted directly to the project's repo itself

Mac Source Ports Build

Mac Source Ports does the build based off of project’s repo

Mac Source Ports Fork

Mac Source Ports does the build based off of our own fork

Third Party Build

Mac Source Ports links to a third party build

---

Port Type

Official Source Code

Project's code is from the original game's official source (i.e., Selaco)

Original Source Code

Project's code is from an official release of the game/engine's original source code (i.e., GZDoom)

Derived Source Code

Project's code is derived from the original engine's source code and reverse engineered differences (i.e., Strife support in GZDoom)

Recreated Source Code

Project's code is from recreated/reflected source code (i.e., DevilutionX)

Reverse Engineered Source Code

Project's code is from reverse engineered code, intended to act like original without recreating it (i.e., OpenMW)

Leaked Source Code

Project's code is based on leaked source code. With the exception of later blessed releases MSP does not work with these

Source Code Unknown

Project does not release source, so nature of source is unknown

---

Project Build Strategy

Project doesn’t do Mac builds

Project does not do their own Mac builds, MSP does the build

Project doesn't do App Bundles

Project does their own Mac builds, but does not do App Bundles, MSP does the build

Project doesn’t sign/notarize their App Bundles

Project does their own Mac builds into App Bundles but does not sign and/or notarize, MSP does a signed/notarized build

Project doesn't do Universal 2 App Bundles

Project does their own Mac builds into App Bundles but doesn't do Universal 2 builds, MSP does a signed/notarized build

Project does Ad Hoc signed App Bundles

Project does their own Mac builds into App Bundles but does not sign and/or notarize, however MSP links to a third party build for pre-existing reasons

Project does signed/notarized App Bundles

Project does their own Mac builds into App Bundles and signs and notarizes them, MSP links to their third party builds

---

Source Code Strategy

Source available

Source is available, project is "open source" in some form or fashion

Source unavailable

Source is unavailable, potentially despite being a source port project

Source confidential

Source is unavailable, but MSP has access to it that we can't share (i.e. Daikatana)

---

Release Strategy

Official project releases only

Closed source, atomic/versioned releases from the project

Versioned releases

Versioned releases based off of a GitHub tag

Versioned but outdated releases

Versioned releases, but the last official version is old, despite the project continuing to receive activity

Versioned releases from inactive project

Versioned releases, but the project has not had activity or releases in a while

Releases based off latest code

No release strategy, builds are based off of the latest code at build time

No releases

No releases, project is source only

---

Mac Support Status

Official Mac support and builds

Project officially supports Mac, does Mac builds

Official Mac support, no builds

Project officially supports Mac, does not do Mac builds

Unofficial Mac support

Project unofficially supports Mac, does not go out of their way to ensure Mac compatibility

No official Mac support

Project does not officially support Mac

No Mac support provided

Project explicitly does not support Mac

Unspecified platform support

Project is ambiguous as to platform support in general

---

Project Status

Active

Project is currently active (commits within the past year)

Inactive

Project is currently inactive (last commit over a year ago)

Abandoned

Project is currently inactive and likely abandoned (last commit several years ago)

Archived

Project has been explicitly labeled archived or otherwise inactive