New gh copilot policy, and more info about the onboarding. (#227)

* New gh copilot policy, and more info about the onboarding.

* Fixed typo

* Specified the Gitlab token permissions.

content/guides/local-development-environment-configuration.md

@@ -187,6 +187,16 @@ Get the credentials for the cluster:
 gcloud container clusters get-credentials spark-op-services --zone europe-west1-b --project spark-int-cloud-services
 ```
 
+### Configure FireStarter Builds
+
+To build FireStarter-based Drupal projects, a user must access specific properties and modules. To such extent, this procedure must be put in place:
+
+* The user must be added to the `Service Group - DTU members` GitLab group (ask HR or Platform team)
+* The user must generate a personal access token on GitLab with `read_api` and `read_repository` scopes (`Settings > Access Tokens`)
+* The user must [authenticate as described in the team's documentation](https://docs.firestarter.sparkfabrik.cloud/packages/firestarter-cli/docs/install_and_update/#shell-setup)
+
+Information on how to build the project is out of the scope of this guide, but these steps are a requirement for Drupal properties.
+
 ### Test and enjoy
 
 To test that everything is working as expected, we'll try to run a service in a container, exposing it through a local URL.

content/procedures/employee-onboarding.md

@@ -54,6 +54,8 @@ The employee must, with the help of an HR representative:
 
 * Duly sign in and check their ability to access every service
 * If they are a developer, log into GCP using [this procedure](/guides/local-development-environment-configuration#log-into-gcloud)
+* If they are a Drupal developer, make sure [they can build FireStarter-based projects](/guides/local-development-environment-configuration#configure-firestarter-builds)
+* If they are a developer, add the user to the `Copilot members` team on GitHub and ask them to activate relevant IDE's plugins
 * Activate two-factor authentication on Gitlab
 * Generate an SSH key and add it among the available keys for their Gitlab account
 * If applicable, [install GH Copilot in the CLI](/tools-and-policies/github-copilot#github-copilot-in-the-cli) and [review how to require company access to Copilot](/tools-and-policies/github-copilot)

content/tools-and-policies/github-copilot.md

@@ -45,7 +45,7 @@ Purpose: This policy aims to establish guidelines for using GitHub Copilot withi
 
 ## How to request a subscription
 
-Github Copilot subscriptions must be requested through the internal slack account `#copilot-program-2023`, you will be requested to confirm to have read and understood the usage policy.
+You should have been granted a GitHub Copilot subscription during your onboarding. If that's not the case, you can ask an HR representative for a subscription. You will be requested to confirm that you have read and understood this usage policy
 
 As the subscription will be made through our Github Organization, your already existing Copilot subscriptions (if any on the same account) will be automatically cancelled and reimbursed from Github, you’ll be informed in any case of the new activated subscription.