Matrix bot for official consensus process
Find a file
2024-08-04 16:39:13 -05:00
.gitignore first commit after removing hardcoded credentials 2024-08-04 16:38:24 -05:00
config.example.json first commit after removing hardcoded credentials 2024-08-04 16:38:24 -05:00
deploy.sh first commit after removing hardcoded credentials 2024-08-04 16:38:24 -05:00
go.mod first commit after removing hardcoded credentials 2024-08-04 16:38:24 -05:00
go.sum first commit after removing hardcoded credentials 2024-08-04 16:38:24 -05:00
layerzero-consensus-bot.service first commit after removing hardcoded credentials 2024-08-04 16:38:24 -05:00
main.go first commit after removing hardcoded credentials 2024-08-04 16:38:24 -05:00
README.md readme formatting 2024-08-04 16:39:13 -05:00

Layer Zero Consensus Bot

This is a matrix bot which lives in the layerzero members channel and provides formal strucuter for a consensus process .

Mostly this exists because matrix polls are not supported by every matrix client. Also, it's nice to have our own record of this stuff.

The bot is deployed to the matrix server under the systemd service unit layerzero-consensus-bot.

Deployment

Consensus bot runs as a systemd service unit. You can see the service unit file layerzero-consensus-bot.service

Consensus bot has its own matrix account. To deploy it, you will need to copy config.example.json to config.json and fill in the relevant login information. The login information can be found on the Layer Zero collection of our Vaultwarden https://pass.cyberia.club. If you don't have access, just ask!

To deploy the consensus bot (once the config.json is filled out), try deploy.sh. You may have to modify the script for your local environment.

Decisions at layer zero

Layer Zero follows the "do-ocracy" model, by which people who utilize the space and do things have the right to do them. We ask that you be kind and courteous to others while doing things and making decisions.

If you want to mount something on the wall, simply do it. If you want to rearrange the couches, go ahead.

However, certain big decisions are made via consensus.

when not to use consensus

I want to paint the wall red

Ask people at layer zero if they'd be fine with you painting the wall red then, paint the wall red. those who show up and do work are the ones who decide how the work is completed.

Can i buy a small multimeter from alibaba with club money?

probably yes, however, you may have to find the right person to ask to buy it for you or recieve re-imbursement from. Ask for help and someone will get you to the right person.

Can i use the printer (laser printer or 3d printer) to print an item?

YES!! Resources at layer zero are community resources, they are there to be used. Please use them! If you don't know how to connect to the printer and use it, ask for help and someone will direct you to the right person.

Can i come up with a better lock system?

Sure! Take on the project, take responsibility, keep everyone informed, and do what you will with the locks. Layer Zero is built on trust.

Examples of things that do not require consensus:

  • bringing in a bicycle and working on it
  • scheduling a music jam at layer zero
  • use up a table to stitch my clothing
  • bring in my own soldering setup
  • donating things to layer zero
  • signing layer zero up for an event (pride, etc)
  • reorganizing the furniture
  • screwing things into the walls
  • mounting stuff on the ceiling (BE SAFE!)
  • reorganizing the shelves
  • buying new shelves yourself and installing them at LZ

when to use consensus

Basically:

  • adding a new member to layer zero
  • spending a lot of layer zero money
  • changing consensus rules

how does consensus-bot work?

You must be in the private "layer zero members lounge" channel in matrix

then, type !help

it will explain itself to you :D