generated from operate-first/template
-
Notifications
You must be signed in to change notification settings - Fork 6
Open
Labels
area/communityIndicates an issue/PR is related to the overall community.Indicates an issue/PR is related to the overall community.area/contributorIndicates an issue/PR is related to a project platform contributor.Indicates an issue/PR is related to a project platform contributor.kind/governanceIndicates an issue/PR is related to governance.Indicates an issue/PR is related to governance.lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.Denotes an issue or PR has remained open with no activity and has become stale.
Description
There have been some untethered discussions and write-ups around having an "open source licensing approach" to how we collect and share operational data.
What I'd like to do is get a workstream going to look at what we are trying to do and what models, licenses, and approaches are out there already.
My concern is that without tethering this with SMEs in areas of open source licensing and data, we'll end up with people wanting to write a new license. While that may be where we end up as an approach, we want to be careful not to have our thinking start there.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
area/communityIndicates an issue/PR is related to the overall community.Indicates an issue/PR is related to the overall community.area/contributorIndicates an issue/PR is related to a project platform contributor.Indicates an issue/PR is related to a project platform contributor.kind/governanceIndicates an issue/PR is related to governance.Indicates an issue/PR is related to governance.lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.Denotes an issue or PR has remained open with no activity and has become stale.