For Studierende, Forschende und Lehrende an der BFH
who want to publish a project as Open Source
the OS License compatibility outline
is a guideline
that gives an overview, which OS Licenses can be used under which circumstances in the context of the BFH
unlike general overviews over OS Licenses, that do not consider the BFH environment
our solution is tailored towards BFH members
Business Outcomes
BFH members now have a decision guideline to quickly choose the OS License that is suited for their BFH-project.
Leading Indicators
<The early measures that will help predict the business outcome hypothesis.>
Nonfunctional Requirements (NFRs) e.g. via ISO-25010
<Nonfunctional requirements (NFRs) associated with the idea.>
is it possible at all to make such a guideline/list?
are there any restrictions at all given by BFH membership statutes?
Funnel Entry Date
2023-01
Idea Owner
@Hannes-Ole
Idea Description
For
Studierende, Forschende und Lehrende an der BFH
whowant to publish a project as Open Source
theOS License compatibility outline
is aguideline
thatgives an overview, which OS Licenses can be used under which circumstances in the context of the BFH
unlikegeneral overviews over OS Licenses, that do not consider the BFH environment
our solutionis tailored towards BFH members
Business Outcomes
BFH members now have a decision guideline to quickly choose the OS License that is suited for their BFH-project.
Leading Indicators
<The early measures that will help predict the business outcome hypothesis.>
Nonfunctional Requirements (NFRs) e.g. via ISO-25010
<Nonfunctional requirements (NFRs) associated with the idea.>
-- derived from SAFe Epic Hypothesis Statement Template