Skip to content

Welcome!

This is a hub for all relevant information on everything related to using GitHub for product and service development for Sopra Steria Norway, Sweden, and Denmark. On this website we want to help you decide if these suite of tools are the right for your project, or if you want to use the group assets. Using GitHub as the base for your project is a decision made with your project lead and stakeholders, approved by your business unit.

graph TD
    start[I got a project!] --> isWork{Is the project related to work?}
    isWork -->|No| workNo[Please use your own repositories.]
    
    isWork -->|Yes| isClient{Is the project a client project?} -->|Yes| clientHosted[Maybe the project should be hosted on the clients platform of choice?]
    isClient -->|No| isClosedorOpen{Is the project meant to be open source?} 
    isClosedorOpen -->|Yes| haveLicense{Do you already have access to our public organization?} -->|Yes| haveLicenseYes[Check guidence on open source projects.]
    haveLicense -->|No| haveLicenseNo[See section on creating a project and getting added as an external contributor.]

    isClosedorOpen -->|No| closedBudget{Do you have a budget and BU clearance?}
    closedBudget -->|Yes| closedBudgetYes[Then follow the project onboarding guide.]
    closedBudget -->|No| closedBudgetNo[Contact a BU stakeholder.]

Client, internal, product, or open source?

Section titled “Client, internal, product, or open source?”

If your project is for a client, the most logical thing would be to develop it based on their standards and practices. Our GitHub organizations are not a place to experiment and create prototypes for our clients but a common place for us to collaborate on projects across clients and business units.

If the project is developed and maintained for internal use only, consider if it is better to host it on our internal GitLab instance. While we in Scandinavia have a big focus on GitHub, our official internal platform is that which is hosted by the group. However, if you clear it with someone in the leadership team, you can still host your internal tools and projects on GitHub, but we have to have a proper cost center established for it.

If the project is a product or service that you want to create, you need to have a budget to spend. Billing is done through Azure subscriptions, both for licenses and metered usage. This is subject to change, but for now the cost would be $21 USD per user and metered billing after the shared pool of resources is spent. In reality, it’s only the cost per user and potentially a small sum for everything else.

If you want to create an open source project, we have an entire process for that outlined in our open source section of this website.

Hosting a non-public project on GitHub comes with a license and usage cost, and for that reason you need to get the approval and the budget for it. There is not necessarily a lot of red tape required from our end; we just need an Azure subscription. But it would be in your best interest to have a chat with your project owner or someone that can be a project sponsor in terms of cost.

We go into more details about this in this section of our onboarding guide.

Our company consists of people that are passionate about technology, and one thing passionate people do is to be involved. We would love for more people to be involved in the open source community, but we also know that it can be daunting to find out where to start. That is why we have created this page to help you find a place to start your open source journey.