Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

This policy outlines how the yunity project uses money. In short, this policy states that the yunity project doesn't use money as an organization; the yunity organization should avoid expenditure at all costs and if money is spent it is done through proxies and recorded.

Herein,

  • 'money' refers to any currency, whether bank notes, coins or an electronic balance.
  • 'resource' refers to anything that is not money.
Panel
titleContents

Table of Contents
indent20px

Protocol


This is a set of actions for acquiring the necessary resources for the project where each action should be considered more preferable than the one following it.

1. Avoidance

If we can avoid money being spent for yunity to achieve it's mission and vision, we should. Not using money avoids us spending time and energy documenting and dealing with money. Avoidance of expenditure should be the starting consideration.

  1. Do we need it? Take a moment to consider whether we need this resource to achieve our goals.
  2. Can we get it without any financial transaction?
    1. Reclaim: Many resources are abandoned, discarded or unused.
    2. Construct: Make the thing from existing resources.
    3. Borrow: Many of the resources we need, others have.
    4. Donation: Some people have things they don't use. (this is different to someone purchasing a resource explicitly to donate it, see below)

2. Proxy transaction

No one is expected to spend money to purchase resources for the yunity organization. If a contributor, other individual or organization wishes to purchase a resource to donate to yunity to help achieve its goals, they can. For anything that is explicitly purchased to donate to yunity, it is recommended to record the name of purchaser, date of transaction and a copy of receipt. Recording these details is optional but highly recommended; it is not to glorify donors but to indicate where yunity is still reliant on money. Knowing where our dependencies lie will help us achieve even lower running costs in the future.

Changes


Changes to this policy are to be made using the result of Online systemic consensus where at least one week is given for each the proposal forming phase and the voting phase and the #core-team Slack channel has been notified.