Skip to content

Adding requirement for the organization team to be created #90

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

Closed
wants to merge 1 commit into from
Closed

Adding requirement for the organization team to be created #90

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
1 change: 1 addition & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -72,6 +72,7 @@ The community meeting calendar is available as an [iCal to subscribe to] (https:
* Put a description of the topic in the welcome message
* Set "Join the group" and "Post" to "Public"
* Ask a repo maintainer to create a github label, if one doesn't already exist: area/foo
* Ask organization maintainer to create a SIG-team within the [Kubernetes GitHub organization](https://github.com/orgs/kubernetes/teams)
Copy link
Contributor

Choose a reason for hiding this comment

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

@sarahnovotny do we have a standard when we crate a SIG? Since we have a ton of SIGs already, and we are waiting on more standards, I am wondering if it would be prudent to leave this off.

Copy link
Contributor

Choose a reason for hiding this comment

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

the standards for creating a SIG are outlined in README.md. Basically, it's a loose consensus that some topic is not covered in existing SIGs and that there is a need to create a new one. There is work going on in the kubernetes-pm group discussing this. https://groups.google.com/forum/?utm_medium=email&utm_source=footer#!msg/kubernetes-pm/joQ_q0MaJ0w/hMdaklE-AgAJ

I think SIG teams is the plan.

* If you wish, request a new [kubernetes.slack.com](http://kubernetes.slack.com) channel (#sig-foo) from @sarahnovotny. New users can join at [slack.kubernetes.io](http://slack.kubernetes.io).
* Organize video meetings as needed. No need to wait for the [Weekly Community Video Conference](community/README.md) to discuss. Please report summary of SIG activities there.
* Request a Zoom account from @sarahnovotny if you expect more than 30 attendees or attendees from China.
Expand Down