-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create workstream to study and recommend an open data sharing approach #79
Comments
An update on the telemetry discussion going on with BU - we set up a separate workgroup within BU to accelerate the work on the EULA - peoples vacation is affecting that a bit, but we expect to begin meeting regularly after labor day to work on an initial draft focused on making the gathering and use by researchers and the open source community clear. Having BU focus on the initial versions will allow other universities and partners to be editors which we believe will accelerate the process. I believe that work is a necessary first step towards something more broad for the Open Source Community through some combination of ORCI, Operate First and/or the Open Infrastructure foundation and that the workstream you speak of will be very helpful as we move forward. |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with /lifecycle stale |
Ongoing work, not stale just not visible in this issue. We can look for an update to bring through. /remove-lifecycle stale |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with /lifecycle stale |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with /lifecycle stale |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with /lifecycle stale |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with /lifecycle stale |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with /lifecycle stale |
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.
The text was updated successfully, but these errors were encountered: