Moneyless Budget: Difference between revisions
(→example: missing "R") |
No edit summary |
||
Line 5: | Line 5: | ||
Clear definition of actual needs also can improve finding alternatives and involve more people into the process of planning and creating a budget. | Clear definition of actual needs also can improve finding alternatives and involve more people into the process of planning and creating a budget. | ||
As money on its own have no use (since it doesn't even exist in physical reality, just in imagination of some human beings), any project can state its needs and dependencies directly. All not available yet resources and help can stay published as a ''' | As money on its own have no use (since it doesn't even exist in physical reality, just in imagination of some human beings), any project can state its needs and dependencies directly. All not available yet resources and help can stay published as a '''wish list''' of a project. | ||
== | == Example == | ||
Instead of stating ''''We need 5 mln BS'''' for Sharewiki this year | |||
More direct and realistic budget for Sharewiki: | |||
* domain name | * domain name | ||
* hosting for a website | * hosting for a website | ||
Line 17: | Line 17: | ||
* help with administrating the server | * help with administrating the server | ||
* etc. (but not any money!) | * etc. (but not any money!) | ||
which again makes clear and precise ''' | which again makes clear and precise '''wish list'''! | ||
[[Category:Other concepts]] | [[Category:Other concepts]] | ||
{{IsIn|Moneyless}} | {{IsIn|Moneyless}} |
Revision as of 22:39, 30 August 2013
short theory
Approach for managing resources needed by a given project, in particular project never accepts money, only direct donation of real resources. Not accepting money (imaginary/fictional pseudo resource) helps to better realize actual needs and dependencies of the project.
Clear definition of actual needs also can improve finding alternatives and involve more people into the process of planning and creating a budget.
As money on its own have no use (since it doesn't even exist in physical reality, just in imagination of some human beings), any project can state its needs and dependencies directly. All not available yet resources and help can stay published as a wish list of a project.
Example
Instead of stating 'We need 5 mln BS' for Sharewiki this year
More direct and realistic budget for Sharewiki:
- domain name
- hosting for a website
- hosting for backups
- help with administrating the server
- etc. (but not any money!)
which again makes clear and precise wish list!