Skip to content
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

Open
quaid opened this issue Aug 26, 2021 · 8 comments
Open
Assignees
Labels
area/community Indicates an issue/PR is related to the overall community. area/contributor Indicates an issue/PR is related to a project platform contributor. kind/governance Indicates an issue/PR is related to governance. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@quaid
Copy link
Member

quaid commented Aug 26, 2021

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.

@quaid quaid added area/community Indicates an issue/PR is related to the overall community. area/contributor Indicates an issue/PR is related to a project platform contributor. kind/governance Indicates an issue/PR is related to governance. labels Aug 26, 2021
@msdisme
Copy link
Contributor

msdisme commented Aug 26, 2021

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.

@sesheta
Copy link
Member

sesheta commented Nov 24, 2021

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@sesheta sesheta added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Nov 24, 2021
@quaid
Copy link
Member Author

quaid commented Dec 7, 2021

Ongoing work, not stale just not visible in this issue. We can look for an update to bring through.

/remove-lifecycle stale

@sesheta sesheta removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 7, 2021
@sesheta
Copy link
Member

sesheta commented Mar 7, 2022

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@sesheta sesheta added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Mar 7, 2022
@quaid quaid removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Mar 11, 2022
@sesheta
Copy link
Member

sesheta commented Jun 10, 2022

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@sesheta sesheta added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jun 10, 2022
@quaid quaid removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jun 25, 2022
@sesheta
Copy link
Member

sesheta commented Sep 24, 2022

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@sesheta sesheta added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Sep 24, 2022
@quaid quaid removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Oct 7, 2022
@sesheta
Copy link
Member

sesheta commented Jan 5, 2023

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@sesheta sesheta added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 5, 2023
@quaid quaid removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 26, 2023
@sesheta
Copy link
Member

sesheta commented Apr 27, 2023

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@sesheta sesheta added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/community Indicates an issue/PR is related to the overall community. area/contributor Indicates an issue/PR is related to a project platform contributor. kind/governance Indicates an issue/PR is related to governance. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Development

No branches or pull requests

5 participants