Update README.md

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,24 @@
+---
+name: Bug report
+about: Create a report to help us improve
+title: ''
+labels: bug
+assignees: ''
+
+---
+
+## Game and version
+*name of game, version of game*
+
+## Version of spice2x
+*version of spice, this can be seen in the About tab, and in log.txt*
+
+## Laptop
+*Are you running this on a laptop? Does it have a hybrid iGPU+ dGPU configuration?*
+
+## Attached log.txt file, if available
+> [!WARNING]
+> Please make sure you remove any personally identifiable information from the log file.
+
+## Describe the issue
+*what's the issue?*

.github/ISSUE_TEMPLATE/documentation-update.md

@@ -0,0 +1,10 @@
+---
+name: Documentation update
+about: For suggesting edits to the wiki page.
+title: ''
+labels: documentation
+assignees: ''
+
+---
+
+

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,10 @@
+---
+name: Feature request
+about: Suggest an idea for this project
+title: ''
+labels: enhancement
+assignees: ''
+
+---
+
+

.github/ISSUE_TEMPLATE/patch-submission.md

@@ -0,0 +1,28 @@
+---
+name: Patch submission
+about: Submit code changes for review
+title: ''
+labels: patch
+assignees: ''
+
+---
+
+> [!NOTE]
+> Before submitting code changes... 
+> * Please do note that this is a GPL v3.0 open source project.
+> * Maintainers reserve the right to reject or modify your submission without reason.
+> * If accepted, your github user name will be credited on the main web page, and then archived in the [past versions wiki page](https://github.com/spice2x/spice2x.github.io/wiki/Past-versions-and-change-log)
+> 
+> Feel free to remove this section after you have read it.
+
+## Description of change
+*what does this code do?*
+
+## Compiling
+*you must be able to compile with the included Docker script with zero compiler warnings*
+
+## Testing
+*how was the code tested?*
+
+## Patch file
+*what patch format are you using? Unix Patch format? Git Patch?*

CONTRIBUTING.md

@@ -0,0 +1,23 @@
+## Contributing
+Baseline rules for patch submissions are as follows. Any patches violating the rules below will not be accepted.
+
+### Adding support for games
+
+* No BomberGirl, as long as the Free To Play service is still alive.
+* No support for that one touch screen game that dispenses plushies of mouse character (`O26`).
+* No support for eaCloud ("Konasute") games.
+* For a new game that was never supported (not a new version of a game, but rather a new series): please wait 1 year after official AC release in Japan.
+* For new version of an already supported game: proceed with caution and use generally-accepted community guidelines.
+
+### Code quality requirements
+
+* Test for regressions, at least in and around the component you are modifying:
+  * All currently supported games / versions must continue to work.
+  * Backwards compatibility must be preserved, unless there is a really good reason to break it. This includes (but not limited to): global/local config files, command line parameters, game patches, device interop (e.g., card readers), and SpiceAPI / Companion interop.
+  * Reasonable level of compatibility with the last release of original spicetools is expected. The stated goal of spice2x is to be a drop-in replacement for spicetools.
+  * Simply put, if someone has an existing install of spicetools/spice2x, copying over new version of spice2x should not result in different behavior or loss of functionality.
+* Make sure you compile with the included Docker script and ensure you do not introduce **any** new compiler warnings or build breaks. The Docker script is the standard build environment, your custom Linux build environment or MSVC can be used during development, but you must validate the final build using Docker.
+* Do not submit snippets of code as a "patch". Exceptions can be made for trivial changes (correct a typo, fix a single line of code...), but otherwise, a successfully compiled & fully tested patch file is required when submitting for review.
+* Do not make code changes in unrelated areas; i.e., do not run code linters and auto-formatters for parts of the code that you didn't modify.
+  * Note: there are no strict rules for code formatting, but please attempt to emulate the style around the code you are modifying.
+* Try to submit smaller chunks of code, instead one gigantic patch. For example, don't submit a patch for "Improve feature XYZ"; instead, submit "Change how A works to prepare for feature XYZ" "Refactor B for feature XYZ" "Add feature B to enable feature XYZ".

README.md

@@ -1,18 +1,47 @@
-spice2x is a fork of SpiceTools, focused on addressing bugs, usability, and quality-of-life improvements
+<br/><br/><br/><br/><br/><br/><br/><br/>
 
-Please visit the homepage: **[https://spice2x.github.io/](https://spice2x.github.io/)**
+# This is the GitHub page for code development. If you just want to download the latest spice2x EXE, visit the homepage instead:
+
+# 🌶️🌶️ [https://spice2x.github.io/](https://spice2x.github.io/) 🌶️🌶️
+
+<br/><br/><br/><br/><br/><br/><br/><br/>
+
+# spice2x
+
+## Overview
+
+spice2x is a fork of SpiceTools, focused on addressing bugs, usability, and quality-of-life improvements.
 
 We do not use GitHub for source control, but we do use the [issue tracker](https://github.com/spice2x/spice2x.github.io/issues) and [the wiki](https://github.com/spice2x/spice2x.github.io/wiki). Source is distributed in the release package.
 
-Before you file a new issue in the issue tracker:
+spice2x team does not provide any tools to circumvent software copy protection, nor distribute any copyright-protected game data.
 
-* Check the [known issues](https://github.com/spice2x/spice2x.github.io/wiki/Known-issues) page first.
+[Features](https://github.com/spice2x/spice2x.github.io/wiki/spice2x-features)
-* Make sure you are on the latest version.
+
-* In SpiceCfg, if you hover over (?) icon next to each option, a helpful mouseover text will appear that will most likely answer your questions.
+[List of supported games](https://github.com/spice2x/spice2x.github.io/wiki/List-of-supported-games)
+
+## How do I set up game data & start playing?
+
+By policy,
+
+* we do **NOT** provide links on where to acquire game data
+* we do **NOT** provide guides on setting up & basic troubleshooting
+
+please do not ask for these, as it will never happen here.
+
+## Submitting to the Issue Tracker
+Rules for filing a new issue or adding comments to existing issues in the tracker:
+
+* Check the [known issues](https://github.com/spice2x/spice2x.github.io/wiki/Known-issues) page first before reporting a new issue.
 * Use the search function and see if there is an existing issue. 
-* Make sure to post the log file (log.txt) as an attachment, and remove any personally identifiable information.
+* This is not the place to obtain a guide or receive basic troubleshooting.
-* This is not the place to ask about other projects, especially EA servers. Bad servers can (and will) crash your game.
+* **Do not link to external websites that distribute game data!**
+* **Do not link to external websites that provide guides on how to run games!**
 
-New GitHub accounts are prevented from creating new issues to prevent spam.
+New GitHub accounts are prevented from creating new issues to prevent spam. Maintainers of this project reserve the right to close or delete any issues that violate the rules above, or low effort issues.
+
+## Contributing
+**We encourage the community to submit patches via the issue tracker for any bug fixes or feature enhancements.** If you want to resolve any reported (or not reported) bugs, implement features, add support for new games, or fix a [known issue](https://github.com/spice2x/spice2x.github.io/wiki/Known-issues) - feel free to reach out via the Issue tracker. All submitted code patches are assumed to be GPLv3 compliant.
+
+Please see [CONTRIBUTING page](https://github.com/spice2x/spice2x.github.io/blob/main/CONTRIBUTING.md) for a full list of guidelines when submitting code.
 
-Maintainers of this project reserve the right to close or delete any low effort issues.

src/SOURCE_FILES.md

@@ -0,0 +1,3 @@
+As always, this project is **distributed with source per GPLv3 license**. Check the [Releases](https://github.com/spice2x/spice2x.github.io/releases) page.
+
+spice2x team does not use GitHub for source control.