You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The InnerSource License Questionnaire is required for the purpose of creating a convenient FinOS InnerSource License Chooser. This will help define a set of popular InnerSource licenses that can be used by Financial instutions that can better protect InnerSource assets and a conveniet tool (InnerSource license chooser) that will help identify the correct license for your requirement. For more background to this project see -> https://www.youtube.com/watch?v=bQz12Rwzzbk
1) What Industry classification does your organization belong to? *
Banking
Insurance
Information Technology
Retail
Healthcare
Manufacturing
Transport
Other:
2) Do you presently use a license for your Inner Source projects?
Yes
No
If not, how are you protecting copyright and rights of contributors presently?
3) What is the scope of inner source material that needs to be protected?
Application Code
Application/ DevOps configuration
Data
Documentation
SLDC artifacts
Other:
4) How do you define your Inner Source distribution boundary (multiple allowed based on project) ?
Within Organization but not subsidiaries or vendors
Within Organization and Subsidiaries but not vendors
Within Organization, Subsidiaries and Authorized Vendors
Other:
5) Do you also have restrictions on distribution by region for inner source projects presently (e.g. export laws - encryption)? Please explain
4) What is the approach towards attribution for your Inner Source projects?
No Attribution (right to be forgotten)
Internal Attribution to Copyright holder
Internal Attribution to Project
Internal Attribution to Contributors
Other:
How is attribution implemented in your org?
6) What mechanisms encourage Inner Source in your organization?
Internal Career Recognition
Internal Rewards
External Career Recognition
Copyleft use model
Other:
7) How are derivative works handled in your organization?
Permissive use of Inner Source code
Copyleft model for Inner Source code
All derivative works are registered centrally
No derivative works are allowed (all code need to be shared back to main project)
Other:
8) What warranty do you provide internally?
No Warranty
30 Day Warranty
Full supported internally
Commercially supported internally
Other:
###9) How are violations to Inner Source dealt with?
Termination of use of inner source
Termination / Penalties for violating user
Termination / Penalties for violating vendor
No penalties are defined
Other:
10) What body internally deals with violations and exceptions to the Inner Source policy?
OSPO
Inner Source Governance Committee
Other Internal Compliance or Security group
Human Resources
Other:
11) Are there any general comments you would like to share on the best practices or lessons learned on your inner source assets with respect to licensing or otherwise?
If you need any clarifications on the questions above please post general questions to #93
The text was updated successfully, but these errors were encountered:
Inner Source License Questionnaire
The InnerSource License Questionnaire is required for the purpose of creating a convenient FinOS InnerSource License Chooser. This will help define a set of popular InnerSource licenses that can be used by Financial instutions that can better protect InnerSource assets and a conveniet tool (InnerSource license chooser) that will help identify the correct license for your requirement. For more background to this project see -> https://www.youtube.com/watch?v=bQz12Rwzzbk
1) What Industry classification does your organization belong to? *
2) Do you presently use a license for your Inner Source projects?
If not, how are you protecting copyright and rights of contributors presently?
3) What is the scope of inner source material that needs to be protected?
4) How do you define your Inner Source distribution boundary (multiple allowed based on project) ?
5) Do you also have restrictions on distribution by region for inner source projects presently (e.g. export laws - encryption)? Please explain
4) What is the approach towards attribution for your Inner Source projects?
How is attribution implemented in your org?
6) What mechanisms encourage Inner Source in your organization?
7) How are derivative works handled in your organization?
8) What warranty do you provide internally?
###9) How are violations to Inner Source dealt with?
10) What body internally deals with violations and exceptions to the Inner Source policy?
11) Are there any general comments you would like to share on the best practices or lessons learned on your inner source assets with respect to licensing or otherwise?
If you need any clarifications on the questions above please post general questions to #93
The text was updated successfully, but these errors were encountered: