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.

Sign up for GitHub

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

Provide a charter for SIG Big Data #2988

Closed
wants to merge 6 commits into from
+64 −12
Closed

Provide a charter for SIG Big Data #2988

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
a504569
charter.md
erikerlandson Nov 28, 2018
528fdf6
update custom content to charter link
erikerlandson Nov 28, 2018
9bb4d82
add 'project promotion' to out of scope
erikerlandson Nov 28, 2018
b3e6eee
update SIG big data mission
erikerlandson Nov 28, 2018
78675c3
regenerate SIG big data readme
erikerlandson Nov 28, 2018
facf925
fix typo
erikerlandson Nov 28, 2018
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 4 additions & 9 deletions sig-big-data/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@ To understand how this file is generated, see https://git.k8s.io/community/gener
--->
# Big Data Special Interest Group

Covers deploying and operating big data applications (Spark, Kafka, Hadoop, Flink, Storm, etc) on Kubernetes. We focus on integrations with big data applications and architecting the best ways to run them on Kubernetes.
Serve as a community resource for advising big data and data science related software projects on techniques and best practices for integrating with Kubernetes. Represents the concerns of users from big data communities to Kubernetes for the purposes of driving new features and other enhancements, based on big data use cases.

## Meetings
* Regular SIG Meeting: [Wednesdays at 17:00 UTC](https://docs.google.com/document/d/1FQx0BPlkkl1Bn0c9ocVBxYIKojpmrS1CFP5h0DI68AE/edit) (weekly). [Convert to your timezone](http://www.thetimezoneconverter.com/?t=17:00&tz=UTC).
Expand Down Expand Up @@ -45,12 +45,7 @@ Note that the links to display team membership will only work if you are a membe
| @kubernetes/sig-big-data-test-failures | [link](https://github.com/orgs/kubernetes/teams/sig-big-data-test-failures) | Test Failures and Triage |

<!-- BEGIN CUSTOM CONTENT -->
## Goals
* Design and architect ways to run big data applications effectively on Kubernetes
* Discuss ongoing implementation efforts
* Discuss resource sharing and multi-tenancy (in the context of big data applications)
* Suggest Kubernetes features where we see a need

## Non-goals
* Endorsing any particular tool/framework

SIG Big Data [Charter](charter.md)

<!-- END CUSTOM CONTENT -->
56 changes: 56 additions & 0 deletions sig-big-data/charter.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,56 @@
# SIG Big Data Charter

This charter adheres to the conventions described in the [Kubernetes Charter README] and uses
the Roles and Organization Management outlined in [sig-governance].

## Scope

The Big Data SIG serves as a community resource for advising big data and data science related software projects on techniques and best practices for integrating with Kubernetes. This SIG also represents the concerns of users from big data communities to Kubernetes for the purposes of driving new features and other enhancements, based on big data use cases.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is isn't really a definition of a SIG, b/c there isn't code ownership in k/k. Instead, it's more of a working group.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's obviously not my prerogative to define them, but FWIW that seems inverted to me. A working group is what I'd convene to own some code-related projects, and an Interest Group is a community forum for people with Interest in some topic, such as big data integrations for k8s, to participate in.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Agree with @timothysc this doesn't sound much like a SIG, at least as far as we define them within this project: https://github.com/kubernetes/community/blob/master/governance.md#sigs

This sounds more like a user community than it does a group that is advancing the project


### In scope

#### Code, Binaries and Services
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Are there OWNERS files maintained by the SIG in the Kubernetes org?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

currently, no


- New features for supporting big data or data science use cases
- CRDs and Operators for big data tooling
- KEPs relating to either new features or new subprojects in support of big data

#### Cross-cutting and Externally Facing Processes

- Promoting best practices for Kubernetes integrations
- Advising big data communities on Kubernetes features
- Shepherding issues and pull requests from community members
- Hosting demos and discussions of big data integrations for Kubernetes

### Out of scope

- Promoting or otherwise advocating for any specific big data project
- Software and tooling communities that have no intersection with data science or big data.

## Roles and Organization Management

This SIG adheres to the Roles and Organization Management outlined in [sig-governance]
and opts-in to updates and modifications to [sig-governance].

### Additional responsibilities of Chairs

- Ensure that regular meetings have at least one SIG chair present, or that the meeting is canceled.
- Record meeting minutes
- Post teleconference recordings
- Represent the SIG at events and community meetings wherever possible
- Actively promote diversity and inclusion in the SIG
- Uphold the Kubernetes Code of Conduct especially in terms of personal behavior and responsibility

### Subproject Creation

Any subprojects that are deemed necessary to promote big data or data science use cases are to
be the responsibility of SIG Technical Leads, assembled for that purpose.

### To Do

- Whether or not to formalise a working definition of what conssitutes a big data or data science related project,
and if so how to codify that definition, remains an open question.

[sig-governance]: https://github.com/kubernetes/community/blob/master/committee-steering/governance/sig-governance.md
[sig-subprojects]: https://github.com/kubernetes/community/blob/master/sig-YOURSIG/README.md#subprojects
[Kubernetes Charter README]: https://github.com/kubernetes/community/blob/master/committee-steering/governance/README.md
7 changes: 4 additions & 3 deletions sigs.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -576,9 +576,10 @@ sigs:
- name: Big Data
dir: sig-big-data
mission_statement: >
Covers deploying and operating big data applications (Spark, Kafka,
Hadoop, Flink, Storm, etc) on Kubernetes. We focus on integrations with
big data applications and architecting the best ways to run them on Kubernetes.
Serve as a community resource for advising big data and data science related software projects
on techniques and best practices for integrating with Kubernetes.
Represents the concerns of users from big data communities to Kubernetes for the purposes of
driving new features and other enhancements, based on big data use cases.
charter_link:
label: big-data
leadership:
Expand Down