Subprojects are about ensuring that code ownership ultimately
lands with a single SIG. There were a few cloud-provider-foo
subprojects that listed dual ownership due to ongoing
discussion of the future of some SIGs. I asked the SIG chairs
involved to make a decision about which SIG these subprojects
should fall to until that discussion is resolved.
cloud-provider-azure -> sig-azure
cloud-provider-gcp -> sig-cloud-provider
cloud-provider-openstack -> sig-cloud-provider
Make the existing SIGs
- SIG AWS
- SIG Azure
- SIG GCP
- SIG OpenStack
the "owners" for the repositories which will be created to host provider
specific code. Other SIGs will be charted as needed/desired for other
providers at a later time.
Update SIG leads for sig-openstack based on discussion at KubeCon NA
2017 deep dive session and confirmed in subsequent online
communications. New year, new responsibilities!
Update sig-openstack meeting time to 0000 UTC Thursdays (Which equates to
Wednesdays in the local time zones in the Americas) to better accomodate
the folks actually working on the provider in the APAC region.
After discussion in the kubernetes-sig-openstack group, this
patch clarifies the mission of sig-openstack to cover all
interactions between the Kubernetes and OpenStack communities.
Add shared link for sig-openstack meeting minutes, the old link does not
include share information which means it's not viewable for folks who
haven't already been granted access.
As we closed out 2016 we ran a poll to select new meeting times for the
coming year. As discussed in the last meeting there was no clear winner
in the results but there were a handful of slots in particular that came
up as "least bad".
In the hope of encouraging participation from those who have not been able
to attend in the past we are going to trial running a 1500 UTC meeting time,
alternating with our traditional 2100 UTC meeting time. Meetings remain
only every second week for now.
Introduce basic premise of sig-openstack, add links to open issues and
pull requests. Remove IRC channel as it is not a primary mechanism of
communication for the group at this point, the main avenue for IM is
slack.kubernetes.com.
As GitHub doesn't allow to view the list of team members within an organization for the users, who are not the members of the organization, this list has been created to be viewable by everyone.