From 6563ce9525b7956a976521f4ea2410bccdb93541 Mon Sep 17 00:00:00 2001 From: Brusk Hamarash Date: Sun, 3 Oct 2021 02:47:10 +0300 Subject: [PATCH] GitHub --- Software-Development/README.md | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/Software-Development/README.md b/Software-Development/README.md index ec8ca88..9f32b1a 100644 --- a/Software-Development/README.md +++ b/Software-Development/README.md @@ -219,6 +219,17 @@ Below is an overview of the policies: #### GitHub +All repositories must be hosted on the [KRG's main GitHub organization](https://github.com/ditkrg). All members of the Digital Development Team and the DevOps Team are eligible to receive a free seat on the organization. Contractors' collaborators must be added as external collaborators. + +All members of the organization are required to use: + +1. SSH Keys for authentication. +2. GPG to sign their commits. + +Unverified/unsigned commits are not going to be allowed. + +Please refer to [this guide](https://docs.github.com/en/authentication/managing-commit-signature-verification) to setup GPG keys. + ## Distributed Computing Specifications The guides below aim to clarify principles and design decisions when creating distributed systems. Whether the software you are building is distributed or centralized, it is important to follow the points mentioned in this sections. This will make sure that any centralized software can later be transformed into a distributed system without much headache.