Proposal: Enable gitvote for steering repo

[mrbobbytables]

Proposal

Currently, when steering votes on an issue they make some sort of comment along the lines of "+1 with steering hat on".
This does work and is suitable for most scenarios, however gitvote as used by the CNCF's TOC looks like a better solution (example vote) with some handy functionality like being able to check status, post weekly vote updates etc.

This could potentially be enabled for the community repo for various charter votes or other instances where a SIG or group would like to call a public vote.

/committee steering

[BenTheElder]

It looks like the CNCF is centrally hosting this so we don't need to run anything?

[mrbobbytables]

It looks like the CNCF is centrally hosting this so we don't need to run anything?

Yup! No need for us to run anything. 👍

[justaugustus]

+1!

[justaugustus]

I've just configured gitvote for TODO Group Steering.
Linking the tracking issue here as a reference point: todogroup/governance#326

[BenTheElder]

Explicit +1 (steering)

cc @kubernetes/steering-committee please comment +1 / -1.

If we enable this we can switch to 👍 / 👎 on the issue body for future issues.

[pacoxu]

+1

[palnabarun]

+1 (steering)

[pohly]

+1 (steering)

[mrbobbytables]

gitvote has now been enabled for this repo, we'll need to configure it before it can be used however.

I would also suggest enabling it on the community repo so that charter changes etc can be easily checked.

With that I'm going to close this out, and we can follow up on the other actions separately.