Week 7: Presentation proposal #2614
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Recreating the pull request because my partner dropped out: #2591 (comment) |
|
Merging, good luck :) |
|
@Jonas-Liley could you please share the presentation with me? I really liked and I would like to reflect on the category of licenses slide that you have. My email: [email protected]. |
|
@algomaster99 yes sure! I’ll send it later today |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Assignment Proposal
Title
Software licencing overview and compliance automation
Names and KTH ID
Deadline
Category
Description
In this presentation we will introduce the different licencing types and cover some of the most common licences including their implications. We will also propose (a) solution(s) to automate licence compliance checks using code/tools in a CI/CD pippeline.
Relevance
Licenses are an important topic for legal compliance and risk mitigation, especially if the produced software product is supposed to be re-licensed and sold. As one can see with the license change of elasticsearch from an open-source Apache 2.0 license to a more restrictive Server Side Public License (SSPL), software licensing can have a massive impact on companies and software products.