Merge pull request #16 from Piras314/dev

better maintainer policy and mention prebuilt binaries in server hosting tutorial

src/en/general-development/setup/server-hosting-tutorial.md

@@ -4,11 +4,11 @@ Hosting a local sandbox server for playing around is easy, but setting up a larg
 
 ## Level 0: Local Sandbox Server
 
-1. Download and install the [.NET 8 Runtime](https://dotnet.microsoft.com/download). You only need "x64" under "run console apps" not "hosting bundle" from the downloads page.
+1. Download the latest build from https://cdn.networkgamez.com/fork/goobstation/, Windows x64 if you're on Windows, macOS x64 if you're on macOS, Linux x64 if you're on Linux, and Linux ARM64 if you're on an ARM linux machine like a Raspberry Pi (server builds are headless).
 2. Extract that to a directory somewhere.
 3. Run `run_server.bat` (Windows) or `Robust.Server` [via terminal on macOS/Linux](#running-the-server-on-macos-or-linux))
 4. Open your Space Station 14 Launcher and click on ``Direct Connect To Server`` and type in ``localhost`` and click connect. You can also add it as a favorite if you click the ``Add Favorite`` button.
-5. When there is a new update. Go back to the second step and just overwrite the files to update your server.
+5. When there is a new update, re-do the first and second step and just overwrite the files to update your server.
 
 ```admonish info
 If you ever wish to develop for the game. You will need a [proper development environment](./setting-up-a-development-environment.md). You cannot use the premade server for this use case.

src/en/staff/maintainer-policy.md

@@ -13,18 +13,19 @@ Every PR must have at least one **Head Maintainer** approving it before being me
 
 For content PRs, at least 24 hours must have passed since the creation of the PR before being merged. This can be bypassed by Head Maintainers if reasonable to do so.
 
-If a PR may affect game admins (rules, rule clarifications, admin tooling etc) **ensure a post has been made in #admin-reviews on discord.**
+If a PR may affect game admins (rules, rule clarifications, admin tooling, big balance changes, antags, etc) **ensure a post has been made in #admin-reviews on discord.**
   - **If you are not sure, do it anyway.**
-  - **If this is a very important or large PR, Game Admins must be pinged in the post.**
+  - **If this is a very important or large PR, all Game Admins must be pinged in the post. (@Game Admins)**
+  - **The scope of what affects admins is very broad currently because the Maintainer team is small.**
 
 - After a minimum of two days:
   - If no one dissents, the PR can be merged (with Head Maintainer approval, as usual).
   - If there is dissent, the PR author must be notified on GitHub of people's requests for changes and/or arguments against it. You do not need to put a ton of effort in summarizing people's points, simply list opinions as "Maintainer opinion" and "Game Admin opinion".
     - **These opinions must be communicated in a neutral manner, even if you disagree with them.**
   - This is the case even if only one person dissents.
   - Once addressed by the PR author, the process may be started again.
-  - If a deadlock is reached where one or more people's dissents cannot be resolved, **a 24-hour-long poll** must be made in the channel with **an @Head Game Admin ping**.
+  - If a deadlock is reached where one or more people's dissents cannot be resolved, **a 24-hour-long poll** must be made in the channel along with **an @Head Game Admin ping**.
   - At least **75% or more of voters** must agree to it being merged before it does.
     - There is no veto power from any role in the project.
   - If less than 75% of people vote to merge the PR, it must be discussed again and the PR author must be notified.
-  - If after another 48 hours no poll reaches 75% or more approvals, the PR may be closed.
+  - If after another 48 hours no poll reaches 75% or more approvals, the PR *may* be closed.