>The first responsibility of the organizer is to deploy the governance system. This task is documented in the Deployment Guide.
> Once the governance system is up and running, the organizer is responsible for governing the day-to-day function of the community, as described in the Governance Guide.
>The governance automation — invoked by the GitHub action — executes on behalf of a dedicated GitHub user, which represents the governance system itself. You must create a new GitHub user, designated as the governance automation user — and name it appropriately, as it will speak to the community users via GitHub comments.
> For instance, the Plurality Book Project — @pluralitybook on GitHub — uses a dedicated user called Plurality Book DAO — @pluralitybook-dao on GitHub — to operate the governance system.
account
otameshi-dao
> Invite the automation user to your organization with Owner privileges.
organization
これ?
これか
>Under "Organization permissions" make the following choices:
これが見つからない
>Deploy governance for your project repository
> You are now ready to deploy governance on your project repository. This can be accomplished with a single command:
$GOV4GIT_RELEASE
v2.1.3
>403 You need admin access to the organization before adding a repository to it.