Update SIG info (contact info / charter)

[justaugustus]

A wild SIG charter has appeared...

/assign @calebamiles @jdumars @tpepper
Signed-off-by: Stephen Augustus foo@agst.us

[justaugustus]

Announced on k-sig-release, k-sig-release-leads, and steering: https://groups.google.com/d/topic/kubernetes-sig-release/CIe4ekG7GkE/discussion
Maintaining lazy consensus hold until Friday, November 2nd, EOD PT.
/hold

[justaugustus]

Adding our Steering liaisons / reviewers.
/assign @timothysc @spiffxp
/committee steering

rel: kubernetes/steering#31

[timothysc]

There are some things that should be removed, but I'd also like to see an addition of what where things live that you currently own. e.g. the entire instructions for the release process

[justaugustus]

I think I've addressed everyone's comments. Most of it was just tweaking language.

There are some things that should be removed, but I'd also like to see an addition of what where things live that you currently own. e.g. the entire instructions for the release process

@timothysc -- I've removed the subprojects section. k/sig-release is the canonical location for all things SIG Release related, so instructions on the relevant processes can be found here. Processes related to the Release Team, for example, would be found in k/sig-release/release-team.

I would want additional SIG Release subprojects / WGs to follow the same structure:

k/sig-release
   |- release-team
   |- release-engineering
   |- licensing
   |- lts  

If you're specifically referring to build / release processes, instead of putting that information in the charter, I'd want to formally turn up the Release Engineering team and then task them with building out the documentation (as I know precious little about that process and it's also something that would be subject to change).

Does that sound reasonable to you?

[timothysc]

Minor nit then LGTM from me.

[timothysc]

/lgtm

[justaugustus]

Removing lazy consensus hold.
/hold cancel

[justaugustus]

Thanks everyone who reviewed this!
Ready for a final /approve.

[timothysc]

@spiffxp for final comments.

[calebamiles]

I would caveat this by saying that we don't currently have any technical leads in deference to subproject leads

[justaugustus]

The intent was that we don't require Technical Leads, either now or in the future, as our Chairs are capable of executing technical duties, as well as the fact that we'll have multiple subproject chairs for specific areas. Do you feel that's captured here or disagree with that sentiment?

[jdumars]

Asking the SIG release chair to be "technical" is not inclusionary language. It also implies vague powers for technical arbitration that rightly belongs to sub-projects. Chairs are responsible for the organization, facilitation, and administrivia of the umbrella group. In that regard, SIG Release is not different than any other SIG WRT chairs. I would strike this language.

[justaugustus]

Yeah, realizing now that the phrasing didn't match my intent. So stricken.

[justaugustus]

@calebamiles / @tpepper -- I've addressed your comments. PTAL when you have a chance.
I'm dropping a hold on this again, to ensure we have consensus with the Chairs before merging.

/hold

[justaugustus]

Charter has been moved to k/community per Steering request (@timothysc + @spiffxp), so this PR just contains updates to contact info and a link to the charter now.

Ready for a /lgtm.
/hold cancel

[jdumars]

I'll let @calebamiles clear his change request, and then we can LGTM.

[timothysc]

I'm fine with any other changes now, it's your wheelhouse.

[timothysc]

/unassign @timothysc

[calebamiles]

/lgtm

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: calebamiles, justaugustus, timothysc

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [calebamiles,justaugustus]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment