Improve this page

To use the assets of the CloudBoost library you need to have access to one of the two GIT repositories CloudBoost is hosted. GitHub hosts to primary repository, all changes and contributions are added to this one first. Azure DevOps hosts the secondary remote. The CloudBoost maintainers will take care that they are always in sync. There is no difference in assets between the repositories, you even can make pull requests in Azure DevOps, but it is preferable to do that from GitHub (less work for the maintainers).

GitHub is the preferable Git repo to work from. In the next section you can read how to gain access.

GitHub onboarding

Step 1 create or update your GitHub profile conform the below requirements.

To create a GitHub account go to: https://github.com/, to update your GitHub profile go to: https://github.com/profilename

  1. GitHub profile needs either a Sogeti or Capgemini email address in the mail address or when not possible in the bio.
  2. The Profile should contain full name and optional a profile picture

Step 2 send your GitHub account name to the CloudBoost maintainers.

They will add you to the CloudBoost Contributers team in GitHub which has access to the CloudBoost Git repo and two others. These other two are in the same context as CloudBoost but contain other artifacts. One is the DevOps Adoption Framework, which contains practices for DevOps the other one is Cloud Automation, which contains automation scripts for cloud management. Feel free to browse around and contribute.

Expect some mails from the CloudBoost Contributers team, the GitHub repo is hosted on a free team instance which doesn’t have an identity store to validate against, this is why we validate via sending mails. When bounced you GitHub Id will be removed from the team. It is a temporary solution, together with Capgemini group delivery we are working on a GitHub enterprise instance.

General Information for contributor

When you have contributor rights to the CloudBoost Git Repository you must be aware that the library is Sogeti intellectual property, don’t share it outside Sogeti.

The -as code- paradigm is the big driver behind the library, reuse and recreate Cloud Infrastructures in an automated way. Read the main page introduction and the concept page for more understanding.

To use the CloudBoost library for your project you can clone the Git repo, make a Git Submodule, a branch or take the templates from the package manager. To start working with the templates we advice to setup a Development environment with Git.

The CloudBoost library is an Sogeti internal open-source project (InnerSource), contributing back is important. Contributing on the templates and on the documentation. Please go through the Contribute Guidelines page to understand how to start contributing to CloudBoost library. You would need to setup a Development environment for work with the documentation which would help you to contribute easily.

CloudBoost Maintainer activities for contributor access to GitHub

The CloudBoost library is Sogeti IP only given access to colleagues outside of Sogeti when there is a project connected with it.

  1. Identify the type of user from below categories- I) Sogeti Colleague II) Capgemini Colleague

    Identification of user can be done via outlook. Check their organization, company and email id. For example - US Sogeti Colleague has mail id with name@us.sogeti.com address.

  2. After identifying the user, follow the below steps for each category-

    I. Sogeti Colleague

    a) Ask the following question to the user- Can you share your GitHub ID and is it associated with your sogeti.com address? See our onboarding guide for GitHub account requirements. b) add the GitHub account to the CloudBoost contributors team in GitHub.

    II. Capgemini Colleague

    a) Send them the following message - The CloudBoost library is build and maintained by Sogeti with Sogeti resources, due to this it is required that a Sogeti colleague is connected to a project which uses the CloudBoost library. We only can give access to Capgemini project and colleagues when there is a scope in the project for Sogeti and a Sogeti colleague is involved in that project. Which area of the CloudBoost library are you most interested in, maybe I can help you.

  3. After providing them the access to the cloudboost library, send the below message and also keep it notified to the Cloudboost Guardians-

    You have been provided access to CloudBoost Git Repository as a contributor. Be aware that the library is Sogeti intellectual property, don’t share it outside Sogeti.

    The -as code- paradigm is the big driver behind the library, reuse and recreate Cloud Infrastructures in an automated way. Read the main page introduction and the concept page for more understanding.

    To use the CloudBoost library for your project you can clone the Git repo, make a Git Submodule, a branch or take the templates from the package manager. To start working with the templates, we advise to setup a Development environment with Git.

    The CloudBoost library is a Sogeti internal open-source project (InnerSource), contributing back is important. Contributing on the templates and on the documentation. Please go through the Contribute Guidelines page to understand how to start contributing to CloudBoost library. You would need to setup a Development environment for work with the documentation which would help you to contribute easily.

    To refer all the pages mentioned above, please visit https://cloudboost.cloud/. Please write to SogetiGitHubAdmins@capgemini.onmicrosoft.com for any assistance with the library.