Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add remote voting #106

Open
wants to merge 3 commits into
base: master
Choose a base branch
from
Open

Add remote voting #106

wants to merge 3 commits into from

Conversation

slifty
Copy link
Member

@slifty slifty commented Nov 17, 2019

This adds support for remote voting on issues.

This changes a whole lot of stuff.  First, it sets up a structure for
distribution of money that is inline with how we have functioned the
past two years.  By codifying it we are able to pay Corporate Overlords
through targeted allocations (which has significantly better tax
implications than guaranteed payments).

It also makes the Comptroller's role a bit more explicit, provides
restrictions on a project's ability to create debt, creates a structure
for projects to loan (or give) each other money, and makes the need for
invoices more explicit.

This also creates the concept of the BIFFUD Operating Branch which is
responsible for setting up operating processes.

This also adds a bit more clairty around the difference between
a Project's "coffers" and corporate "coffers" while also changing the
definition of Spoils of War to isolate project expense / income
completely from corporate expenses.
This makes it so someone can be a Corporate Overlord without being
a legal owner.  This is important for folks who aren't based in the USA
or who otherwise might not want legal ownership of the company for
whatever weird reason.

This is a change to section 0 and 1, so we need complete consensus.
We're gonna need it.

Also this is often asked for.
1. Enough votes are cast as to reach a verdict.
2. The sitting Overmind determines that the vote should be closed.

The remote voting mechanism shall be determined by the Overmind.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should Keeper of Lore be responsible / have involved in this determination?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sure - up for it.

@@ -519,6 +519,17 @@ Here's a summary table:
| ~ corporate | Majority | GitHub |
| + minutes | Apathetic Support | GitHub |

### Remote Voting
Calls to vote made during a plotting session can be voted on remotely by Corporate Overlords. This is because time is not linear, it is only perceived linearly, therefore all moments of time are actually identical.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What?

### Remote Voting
Calls to vote made during a plotting session can be voted on remotely by Corporate Overlords. This is because time is not linear, it is only perceived linearly, therefore all moments of time are actually identical.

Only Corporate Overlords with an active (non hibernating) status at the time of the initial plotting session are able to vote, and the totals needed for a given vote are based on the active corporate overlords at that time.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think something that might come up as a question is if a Corporate Overlord misses four plotting sessions in a row but has voted remotely, does that still put the Corporate Overlord into hibernation, even though they've been participating remotely? I would argue that a strict interpretation is that the Corporate Overlord still enters hibernation because forms of participation that are not attendance at plotting sessions are not used to determine hibernation status. If this is the intent, do we need to clarify this?

The vote shall remain open until at least one of the following conditions holds:

1. Enough votes are cast as to reach a verdict.
2. The sitting Overmind determines that the vote should be closed.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This leaves open a possibility that a vote can remain open indefinitely, when:

  1. Not enough votes are cast.
  2. and the sitting Overmind decides not to close the vote.

Not sure what the implications of this, but it seems we should impose mandatory expiration on a vote? A vote will be considered closed after X amount of time has elapsed. (A week? Time between plotting sessions? A year?)

If this is too late to amend now I can propose this next time.

@louh
Copy link
Member

louh commented Nov 25, 2019

Remote voting passes: https://doodle.com/poll/ayx8rytvdnz2nwe9

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants