Repository_Access: remove superseded CONTRIBUTING section

diff --git a/Repository_Access.md b/Repository_Access.md
index c6232da2877fa1e2eb4a3d9a188127f40642278a..501b4cf6828b2746244c06099b208d190e1e05a8 100644 (file)
--- a/Repository_Access.md
+++ b/Repository_Access.md
@@ -98,24 +98,8 @@ To update your Git clone:
 \r
 If you run into issues with the latest version you can easily revert to an older one. Since most bugs are caused by the game code rather that the engine, you just need to downgrade that repository. Inside the main xonotic repository, use `cd data/xonotic-data.pk3dir` and then `git checkout <some older commit>`. After that go back `cd -` and `./all compile`.\r
 \r
-Contributing and Getting Write Access\r
--------------------------------------\r
 \r
-It's recommended to [request access](https://docs.gitlab.com/ee/user/group/index.html#request-access-to-a-group) to the [Xonotic project group](https://gitlab.com/xonotic).  Cloning our repositories and submitting merge requests from there will work but you won't be able to use our CI setup for the xonotic-data.pk3dir repo (which seems to need a custom runner).\r
-\r
-A condition for write (push) access and submission of merge requests is that **you agree that any code or data you push will be licensed under the [GNU General Public License, version 2](https://www.gnu.org/licenses/old-licenses/gpl-2.0.html), with and/or without the “or any later version” clause.**\r
-\r
-If the directory or repository your changes apply to contains a LICENSE or COPYING file indicating another license or a dual license, then **you agree that your pushed code will be licensed as specified in that file.**  Subdirectories and repositories with a dual license or a different license:\r
-* [xonotic-data.pk3dir/qcsrc/lib/warpzone](https://gitlab.com/xonotic/xonotic-data.pk3dir/-/tree/master/qcsrc/lib/warpzone) - dual licensed with GNU GPLv2 (or any later version), or MIT license.\r
-* [xonstat-go](https://gitlab.com/xonotic/xonstat-go/) - licensed with [GNU AGPLv3](https://www.gnu.org/licenses/agpl-3.0.html)\r
-\r
-In case the code you pushed was not written by you, it is your responsibility to ensure proper licensing.\r
-\r
-To apply for write access, please add your SSH key to your GitLab account and [request access](https://docs.gitlab.com/ce/user/group/index.html#request-access-to-a-group) to the [Xonotic project group](https://gitlab.com/xonotic) using the GitLab interface.  You can also request access on Matrix chat in [#dev:xonotic.org](https://matrix.to/#/#dev:xonotic.org) (remember to tell us your GitLab username!) but the admins might not see your request amongst the other messages.\r
-\r
-Please read [General Contributor Guidelines](https://gitlab.com/xonotic/xonotic/-/wikis/Repository_Access#general-contributor-guidelines) before pushing.\r
-\r
-### Windows/Linux/macOS\r
+# ./all script commands (Windows/Linux/macOS)\r
 \r
 Get a checkout (see above), and do:\r
 \r
@@ -162,19 +146,13 @@ Starts the Xonotic client
 \r
 Starts a Xonotic dedicated server\r
 \r
-General Contributor Guidelines\r
-------------------------------\r
-\r
-1.  Before creating your local branch and committing to it, make sure you’ve configured your user settings such as your name which will display in the logs (in TortoiseGit: Settings > Git > Config).\r
-2.  **You should name your branch myname/mychange for each patch.** For instance, if your name is Alex and the change you are committing is a menu fix, use something like alex/menufix.\r
 \r
-Git guides\r
------------------------\r
+# Git guides\r
 \r
-Git basics on [this wiki page](Git).\r
+Git howto on [this wiki page](Git).\r
 \r
 About tracking remote branches:\r
-http://git-scm.com/book/en/v2/Git-Branching-Remote-Branches\r
+https://git-scm.com/book/en/v2/Git-Branching-Remote-Branches\r
 \r
 A tutorial to Git for SVN users:\r
 https://git.wiki.kernel.org/index.php/GitSvnCrashCourse\r