Official GitHub organization for the KTH Royal Institute of Technology

Since its founding in 1827, KTH Royal Institute of Technology in Stockholm has grown to become one of Europe’s leading technical and engineering universities, as well as a key centre of intellectual talent and innovation. We are Sweden’s largest technical research and learning institution and home to students, researchers and faculty from around the world dedicated to advancing knowledge.

Website: www.kth.se

Who can contribute to github.com/KTH?

Only employees of the KTH IT-Department can publish software or eqvivalent on github.com/KTH.

Adding feature or bug fixes via pull requests

We normally work with, and accept pull request, but we can not promise to accept or look at them. But we can promise to do our best with the time we have.

GitHub Repository Management and Security Guidelines

To ensure the efficient management and security of GitHub repositories within your organization, follow these guidelines:

Default Privacy Setting:

All new repositories should be created as private by default. This ensures that the content remains confidential unless explicitly decided otherwise.

Internal Visibility for Shared Repositories:

Repositories intended to be accessible by all users within the organization should be set to internal visibility. This setting allows everyone in the organization to view and contribute to the repository while keeping it inaccessible to outsiders.

Public Visibility Approval for IT Department:

Repositories that need to be made public and are owned by the IT Department require prior approval. The approval process should be clearly documented, including who has the authority to give such approvals and how they are granted.

Repository Ownership:

Repositories must be associated with a team rather than an individual. This promotes collaboration and ensures continuity of work, even if individual members leave the organization.

Tagging Repositories:

Repositories should be tagged with relevant information such as the responsible person, team, or department. This aids in the organization, identification, and accountability of repositories within the organization.

Enable Dependabot:

Dependabot should be enabled by default for all repositories. This tool automatically checks for dependencies in your project and raises pull requests to update them to the latest versions, helping to keep your code secure and up-to-date.

Enable Secret Scanning:

Secret scanning should also be enabled by default. This feature scans your repositories for known types of secrets, like digital keys and tokens, to prevent accidental exposure of sensitive information.

Teams and access management for GitHub

GitHub teams should be used to give access to repositories.
Access to repositories should be given to Teams and users directly. In some cases direct access to repositories are allowed.
A user can belong to a single team or multiple teams.
A team in GitHub should have a descriptive name for the team and the description should include the emailaddress of the responsible person.

External Users

External users can be invited to collaborate in a team or a specific repository.
The person responsible for the team or the specific repository must remove the invited users access as soon as they are no longer a part of a team or collaborating on the specific repository.

Open source license

The default license for open source distributed by KTH on github.com/KTH is the MIT license. Some repositories may have other licenses.

If you find a repository on github.com/KTH that do not have a LICENCE-file, is missing a attribution, or in some other way violate the open source community, please let us know so we can fix this.

Contact us

Github.com/KTH is maintained by the KTH IT-departmentat KTH. Contact us on it-support@kth.se.

Legacy repositories

Github.com/KTHse is an old Github organisation for KTH. No repositories will be published or maintained on github.com/KTHse.