Decide on a name for the Metagov + OpenCollective Integration “product”

[velefante]

Our team is in the process of brainstorming a name for this product, which is a new feature in Open Collective that will allow collectives to open a vote on their expense approvals in Slack using Metagov's tools, PolicyKit and the Metagov Gateway.

The feature will function as follows: An admin of an Open Collective page will see a button that says (something along the lines of) “Add policy to vote on expenses in Slack.” When they click the button, they will be able to create a voting process in their Slack channel for their Open Collective expenses and set the parameters for the voting process such as: how long the vote will stay open, the specific channel where voting takes place, specific eligible voters, quorum (how many votes constitutes a “pass”), etc.

What should we name this tool???

Some ideas include:

"____"... powered by Metagov Gateway and PolicyKit

Collective Voice (+1 - Val) OpenVote (+1 on this - Val) Slack Vote External Vote Gateway (by PolicyKit and Metagov) Remote Vote

[c-host]

I propose naming this tool/integration "Collective Voice". The "superuser" bot added to a collective's Open Collective account would also be named Collective Voice. This more accurately represents the tool as both:

1. a check on administrative power, and
2. a reflection of how collective action is exercised by communities

It also opens up possibilities for representation of decision-making metadata and discovery on Open Collective, something that I will file a new issue for.