Merge pull request #1181 from parispittman/patch-4

Automatic merge from submit-queue.

Update Information file

Added preliminary information

@castrojo
This commit is contained in:
Kubernetes Submit Queue 2017-10-19 18:56:54 -07:00 committed by GitHub
commit 8a564819e5
2 changed files with 43 additions and 1 deletions

View File

@ -0,0 +1,43 @@
# 2017 Kubernetes Contributor Summit Information
## What:
The Contributor Summit provides an avenue for Kubernetes contributors to connect face to face and mindshare about future community development and community governance endeavors.
In some sense, the summit is a real-life extension of the community meetings and SIG meetings.
## When:
* December 5th, 2017 (before KubeCon)
* All day event with happy hour reception to close
Exact times TBU
## Where:
Austin Convention Center
500 E Cesar Chavez St,
Austin, TX 78701
(same location as KubeCon)
## Invitations:
Selected attendees are Kubernetes upstream contributors including SIG members and lottery winners from a [members of standing](https://github.com/kubernetes/community/blob/master/community-membership.md) pool.
We realize that this is not the best approach now that our community is growing in exponential ways. In 2018, we will be unfolding a new strategy for bringing our contributors together so all voices can be heard.
Invitees will begin going out on October 19th.
## Format:
"loosely-structured unconference"
Rather than speakers and presentations, we will have moderators/facilitators and discussion topics, alongside all-day completely unstructured hacking.
The discussion sessions will be in an open fishbowl format — rings of chairs, with inner rings driving the discussion — where anyone can contribute. The various sessions will be proposed and voted on by the community in the weeks leading up to the event. This allows the community to motivate the events of the day without dedicating precious day-of time to choosing the sessions and making a schedule.
There will be 3 rooms dedicated to these sessions running in parallel all day. Each session should last between 45 minutes and an hour.
Then, there will be 2 smaller rooms for hacking / unstructured discussion all day.
## Call for Topics
Invites will include an area to list your proposed topic to lead for a potential session. Schedule will be announced at least one week before the event.
## Desired Outcomes
* Generate notes from the sessions to feed the project's documentation and knowledge base, and also to keep non-attendees plugged in
* Make (and document) recommendations and decisions for the near-term and mid-term future of the project
* Come up with upcoming action items, as well as leaders for those action items, for the various topics that we discuss
Further details to be updated on this doc. Please check back for a complete guide.

View File

@ -1 +0,0 @@
More info forthcoming about the 2017 Kubernetes Developer's Summit!