Difference between revisions of ":IMAR"

From MediaWiki
Jump to: navigation, search
m (→‎Members)
(→‎Members)
 
(One intermediate revision by one user not shown)
Line 33: Line 33:
  
 
There is work on invlusive democracy which is claimed to fit the requirements of an RBE. There is documentation about it in http://democraciainclusiva.org (in Spanish).
 
There is work on invlusive democracy which is claimed to fit the requirements of an RBE. There is documentation about it in http://democraciainclusiva.org (in Spanish).
 +
 +
== General description ==
 +
IMAR is described very briefly on the main Team page, but more in depth (non-technically, though) in [[Team:IMAR/Governing]]. IMAR is not intended on dealing with anything other than its specific purpose: the intelligent management of available resources. What resources will be available are not an "a priori" concern, but "a posteriori" concern. This means that IMAR is focused first in management (which requires goals), by intelligently (smart and holistic algorithms) allocating the available resources (related to each specific goal).
 +
 +
It is important noting that RBE10K does not intend on having labour (classes), social roles (specialisation), discipline (punishment), or duty/obligation (imposition). RBE10K will likely not have rights either (because this type of society cannot protect them, so it is pointless having them). There will be no minimum of social contributions: if someone doesn't want to do any social contributions, so be it (ideally people would try to stimulate or persuade that someone to contribute, but still respecting that individual's choice to be uninvolved). It is estimated that whatever (non-destructive) someone does, it will benefit the community one way or another, e.g. if someone wants to play the guitar all day and not contribute to any communal tasks, eventually this person will be a source of entertainment for everybody as a musician. All work will be voluntary, peer-supported, and peer-reviewed.
 +
 +
IMAR depends on the implementation of a qualifying system using a type of meritocracy. There will be qualifying conditions to enable an individual to perform a task, e.g. preparing food in communal kitchens will require a degree of past experience in the kitchen as a kitchen hand, and having shown responsibility (merit), both intended to prevent waste (e.g. burning the food, or making it so salty or spicy hot that becomes inedible) or conflicts (e.g. placing an extra pressure on others due to not showing up on time). Gaining experience and merit will also be aimed at motivating social contributions, e.g. someone highly skilled at making films may request the participation of a number of people with a high degree of merit in certain areas, for a film that could be a highly desirable activity to many. This type of meritocracy aims also at minimising the occurrence of imposed authority or politics, by means of objective, measurable, and peer-reviewed qualification.
 +
 +
At first everybody will expect from each other to help set-up the community as per the plan, and at the time of signing up (through the website we're working on at this time) each one will have the opportunity to sign up to specific tasks, so that it is known which tasks cannot be accomplished because there are no people willing to do. IMAR will not be required at this stage, nor during the construction stage. The project will only be viable once everything needed (to be purchased or to be done) is organised and allocated. It will be in everybody's interest to having all tasks required allocated. Each one chooses voluntarily which tasks they commit to do, and then participates in organisation and coordination teams to ensure capability, suitability, feasibility and honesty, to minimise surprises, and to ensure everybody knows what to begin doing as soon as they land, in a similar way to ants knowing what to do as soon as they become adults and begin working straight away. People will not be obligated to fulfil a role they've committed to, however the whole community will depend on each one fulfilling on their promise, so there will be (gentle) peer pressure, and ideally a supporting and encouraging environment.
 +
 +
The community will remain in this busy and special stage until whatever had been planned is finished. Once this happens (we'll aim at no more than 6 months for this stage), the community will enter a normal running mode. Here is when IMAR will be implemented (people will have continued working on it all this time, as it will be an open-source software, and its database would have been filled during the whole construction stage with information about the available resources, both brought and local).
 +
 +
There will be two types of enterprises in RBE10K:
 +
# Communal activities related to addressing needs.
 +
# Any other activities, which will be a manifestation of the individual interests of the inhabitants of the community.
 +
 +
The first type is the one that RBE10K intends to define by designing and planning for it before engaging in its implementation. IMAR will be involved primarily in this type, and will be available to the other type for anyone who would like to use it to coordinate their personal enterprise. E.g. IMAR will be primarily involved in the production of sufficient and nutritious food. Someone may engage in the production of spices, and record objectives and tasks in IMAR, so that people can sign-up. The priority for the latter will be significantly lower than the former, because obviously it is more important having sufficient tasteless food than having insufficient tasty food.
 +
 +
IMAR will not dictate what to do. It will have the following structure:
 +
# Registry of objectives. E.g. ensure sustained production of 2000 kcal of food per person per day for the following 6 months.
 +
## Each objective will have required tasks to achieve it, and involve certain resources. It will also be clearly outlined and documented.
 +
## Objectives will be prioritised according to the priority of related needs and goals.
 +
# Registry of tasks related to given objectives. E.g. weeding row X of greenhouse Y on day Z.
 +
## People will be able to list (on their personal notebook/tablet) upcoming tasks, and register wherever they want, or have sufficient merit or recorded capabilities required
 +
## Tasks will be clearly outlined and documented, so that anyone signing up for one will know what to do and how, step by step, through a wiki, videos, and other materials.
 +
# Registry of people's merit and expertise in a number of categories (people's merit and expertise will be considered human resources, not the individuals themselves)
 +
## People will be noted by supervisor peers (with greater expertise in a given area) for social contributions, increase contributors' merit and expertise. This will be on itself a task to fulfil.
 +
## Supervision will include training and sharing knowledge. It will be expected that, as time goes by, everybody increases their skills and merit in all areas related to social contributions, to prevent specialisation (which leads to trade and labour)
 +
# Registry of resources required for a given task. E.g. weeding requires a given level of expertise and merit (trustworthiness), a supervisor of a given level of expertise and merit, and specific tools
 +
# Registry of resources produced by a given task. E.g. weeding of a whole row produces a number of kg of weeds somewhere between 2 and 10. Weeds may be a resource required for other tasks, like making compost.
 +
# Monitoring interface including warnings, publicly accessible, to alert of priority tasks that have not been allocated, and the consequences. E.g. weeding in greenhouse Y has not been performed for 10 days, and the crop may fail as a consequence, causing the goal of producing 2000kcal of food per person per day in the next month to drop by 10%
 +
 +
Defining what will be produced depends on many factors. The most important is what we need (RBE10K's scope doesn't include defining production of things that are not needed). Another factor is what we can source within the community so there is no need to purchase, e.g. producing compressed earth bricks is preferable to purchasing bricks, fabricating our own toilet seats "may" be more economical than purchasing them already made, but purchasing notebooks/tablets is preferable to relying on our own capacity to produce such equipment.
  
 
== Members ==
 
== Members ==
Line 67: Line 100:
 
User=[[User:A.zhemchugov]]
 
User=[[User:A.zhemchugov]]
 
Activities=Contributor
 
Activities=Contributor
 +
</data>
 +
 +
<data table="RBE10K_Team_Members">
 +
Name=Danielle
 +
User=[[User:Dan]]
 +
Activities=General Ray of Sunshine :)
 
</data>
 
</data>
  

Latest revision as of 23:49, 31 July 2013

Contents

[edit] Team

<data table="RBE10K_Teams" template="Infobox RBE10K_Teams"> Coordinators=User:Ziggy Activities=Establishing the requirements of the software, Proposing methods of implementation, Developing such methods </data>

See all teams.

[edit] Objectives

[edit] Purpose

The IMAR (Intelligent Management of Available Resources) is the governing system of an RBE entity. Entities can be production systems, buildings, cities, or groups of cities. The primary objectives of such system are:

[edit] Priorities

There are a number of priorities sorted according to common sense and in agreement with the general tennets of the RBEM principles. However, priorities may change by consensus if required. These are generally applicable equally to any of the entities implementing IMAR, however variations may be introduced if required, provided that the community's IMAR priorities are maintained or adjusted for.

  1. Preserve Human Life, except for when such Human Life exercise their self-determination requesting otherwise
  2. Preserve Human Health, except for those specific areas in which individuals exercise their self-determination not have their health preserved
  3. Preserve Enviromental biodiversity
  4. Provide for Physiological Human Needs
  5. Provide for Safety Human Needs
  6. Maximise Self-reliance
  7. Maximise Sustainability
  8. Preserve Environmental Pristinness
  9. Provide for, mediate, assist, or enable all other Human Needs

[edit] Governing System

{{#ifeq:|Category|The main {{#ifeq:||article|page}}{{#if:|s}} for this category {{#if:|are|is}}|Main {{#ifeq:||article|page}}{{#if:|s}}:}} Governing System{{#if: 
|{{#if:|, | and }}[[{{{2}}}|{{{2}}}]]}}{{#if:
|{{#if:|, |, and }}[[{{{3}}}|{{{3}}}]]}}{{#if:
|{{#if:|, |, and }}[[{{{4}}}|{{{4}}}]]}}{{#if:
|{{#if:|, |, and }}[[{{{5}}}|{{{5}}}]]}}{{#if:
|{{#if:|, |, and }}[[{{{6}}}|{{{6}}}]]}}{{#if:
|{{#if:|, |, and }}[[{{{7}}}|{{{7}}}]]}}{{#if:
|{{#if:|, |, and }}[[{{{8}}}|{{{8}}}]]}}{{#if:
|{{#if:|, |, and }}[[{{{9}}}|{{{9}}}]]}}{{#if:
|, and [[{{{10}}}|{{{10}}}]]}}{{#if: | (too many parameters in {{main}})}}

The main article is currently a journal article, ane requires being wikified.

There is work on invlusive democracy which is claimed to fit the requirements of an RBE. There is documentation about it in http://democraciainclusiva.org (in Spanish).

[edit] General description

IMAR is described very briefly on the main Team page, but more in depth (non-technically, though) in Team:IMAR/Governing. IMAR is not intended on dealing with anything other than its specific purpose: the intelligent management of available resources. What resources will be available are not an "a priori" concern, but "a posteriori" concern. This means that IMAR is focused first in management (which requires goals), by intelligently (smart and holistic algorithms) allocating the available resources (related to each specific goal).

It is important noting that RBE10K does not intend on having labour (classes), social roles (specialisation), discipline (punishment), or duty/obligation (imposition). RBE10K will likely not have rights either (because this type of society cannot protect them, so it is pointless having them). There will be no minimum of social contributions: if someone doesn't want to do any social contributions, so be it (ideally people would try to stimulate or persuade that someone to contribute, but still respecting that individual's choice to be uninvolved). It is estimated that whatever (non-destructive) someone does, it will benefit the community one way or another, e.g. if someone wants to play the guitar all day and not contribute to any communal tasks, eventually this person will be a source of entertainment for everybody as a musician. All work will be voluntary, peer-supported, and peer-reviewed.

IMAR depends on the implementation of a qualifying system using a type of meritocracy. There will be qualifying conditions to enable an individual to perform a task, e.g. preparing food in communal kitchens will require a degree of past experience in the kitchen as a kitchen hand, and having shown responsibility (merit), both intended to prevent waste (e.g. burning the food, or making it so salty or spicy hot that becomes inedible) or conflicts (e.g. placing an extra pressure on others due to not showing up on time). Gaining experience and merit will also be aimed at motivating social contributions, e.g. someone highly skilled at making films may request the participation of a number of people with a high degree of merit in certain areas, for a film that could be a highly desirable activity to many. This type of meritocracy aims also at minimising the occurrence of imposed authority or politics, by means of objective, measurable, and peer-reviewed qualification.

At first everybody will expect from each other to help set-up the community as per the plan, and at the time of signing up (through the website we're working on at this time) each one will have the opportunity to sign up to specific tasks, so that it is known which tasks cannot be accomplished because there are no people willing to do. IMAR will not be required at this stage, nor during the construction stage. The project will only be viable once everything needed (to be purchased or to be done) is organised and allocated. It will be in everybody's interest to having all tasks required allocated. Each one chooses voluntarily which tasks they commit to do, and then participates in organisation and coordination teams to ensure capability, suitability, feasibility and honesty, to minimise surprises, and to ensure everybody knows what to begin doing as soon as they land, in a similar way to ants knowing what to do as soon as they become adults and begin working straight away. People will not be obligated to fulfil a role they've committed to, however the whole community will depend on each one fulfilling on their promise, so there will be (gentle) peer pressure, and ideally a supporting and encouraging environment.

The community will remain in this busy and special stage until whatever had been planned is finished. Once this happens (we'll aim at no more than 6 months for this stage), the community will enter a normal running mode. Here is when IMAR will be implemented (people will have continued working on it all this time, as it will be an open-source software, and its database would have been filled during the whole construction stage with information about the available resources, both brought and local).

There will be two types of enterprises in RBE10K:

  1. Communal activities related to addressing needs.
  2. Any other activities, which will be a manifestation of the individual interests of the inhabitants of the community.

The first type is the one that RBE10K intends to define by designing and planning for it before engaging in its implementation. IMAR will be involved primarily in this type, and will be available to the other type for anyone who would like to use it to coordinate their personal enterprise. E.g. IMAR will be primarily involved in the production of sufficient and nutritious food. Someone may engage in the production of spices, and record objectives and tasks in IMAR, so that people can sign-up. The priority for the latter will be significantly lower than the former, because obviously it is more important having sufficient tasteless food than having insufficient tasty food.

IMAR will not dictate what to do. It will have the following structure:

  1. Registry of objectives. E.g. ensure sustained production of 2000 kcal of food per person per day for the following 6 months.
    1. Each objective will have required tasks to achieve it, and involve certain resources. It will also be clearly outlined and documented.
    2. Objectives will be prioritised according to the priority of related needs and goals.
  2. Registry of tasks related to given objectives. E.g. weeding row X of greenhouse Y on day Z.
    1. People will be able to list (on their personal notebook/tablet) upcoming tasks, and register wherever they want, or have sufficient merit or recorded capabilities required
    2. Tasks will be clearly outlined and documented, so that anyone signing up for one will know what to do and how, step by step, through a wiki, videos, and other materials.
  3. Registry of people's merit and expertise in a number of categories (people's merit and expertise will be considered human resources, not the individuals themselves)
    1. People will be noted by supervisor peers (with greater expertise in a given area) for social contributions, increase contributors' merit and expertise. This will be on itself a task to fulfil.
    2. Supervision will include training and sharing knowledge. It will be expected that, as time goes by, everybody increases their skills and merit in all areas related to social contributions, to prevent specialisation (which leads to trade and labour)
  4. Registry of resources required for a given task. E.g. weeding requires a given level of expertise and merit (trustworthiness), a supervisor of a given level of expertise and merit, and specific tools
  5. Registry of resources produced by a given task. E.g. weeding of a whole row produces a number of kg of weeds somewhere between 2 and 10. Weeds may be a resource required for other tasks, like making compost.
  6. Monitoring interface including warnings, publicly accessible, to alert of priority tasks that have not been allocated, and the consequences. E.g. weeding in greenhouse Y has not been performed for 10 days, and the crop may fail as a consequence, causing the goal of producing 2000kcal of food per person per day in the next month to drop by 10%

Defining what will be produced depends on many factors. The most important is what we need (RBE10K's scope doesn't include defining production of things that are not needed). Another factor is what we can source within the community so there is no need to purchase, e.g. producing compressed earth bricks is preferable to purchasing bricks, fabricating our own toilet seats "may" be more economical than purchasing them already made, but purchasing notebooks/tablets is preferable to relying on our own capacity to produce such equipment.

[edit] Members

{{#css:Template:RBE10K TableRows/css}}{{#css: 

 	.col1 {width:{{#if:|{{#explode:{{{widths}}}| |0}}|{{#switch:{{#ifeq: x | | 0 |
 {{#ifeq: x | | 1 |
    {{#ifeq:  Activities  | | 2 |
       {{#ifeq:  | | 3 |
         {{#ifeq:  | | 4 | 
           {{#ifeq:   | | 5 |
             {{#ifeq:   | | 6 |
               {{#ifeq:   | | 7 |
                {{#ifeq:   | | 8 | 9
                 }}
               }}
             }}
           }}
         }}
       }}
    }}
 }}

}}|2=20|3=15|4=12|5=10}}}}%; } .col2 {width:{{#if:|{{#explode:{{{widths}}}| |1}}|{{#switch:{{#ifeq: x | | 0 | 

 {{#ifeq: x | | 1 |
    {{#ifeq:  Activities  | | 2 |
       {{#ifeq:  | | 3 |
         {{#ifeq:  | | 4 | 
           {{#ifeq:   | | 5 |
             {{#ifeq:   | | 6 |
               {{#ifeq:   | | 7 |
                {{#ifeq:   | | 8 | 9
                 }}
               }}
             }}
           }}
         }}
       }}
    }}
 }}

}}|2=80|3={{#if:|70|15}}|4=12|5=10}}}}%; } .col3 {width:{{#if:|{{#explode:{{{widths}}}| |2}}|{{#switch:{{#ifeq: x | | 0 | 

 {{#ifeq: x | | 1 |
    {{#ifeq: x | | 2 |
       {{#ifeq:  | | 3 |
         {{#ifeq:  | | 4 | 
           {{#ifeq:   | | 5 |
             {{#ifeq:   | | 6 |
               {{#ifeq:   | | 7 |
                {{#ifeq:   | | 8 | 9
                 }}
               }}
             }}
           }}
         }}
       }}
    }}
 }}

}}|3=70|4={{#if:|64|12}}|5=10}}}}%; } .col4 {width:{{#if:|{{#explode:{{{widths}}}| |3}}|{{#switch:{{#ifeq: x | | 0 | 

 {{#ifeq: x | | 1 |
    {{#ifeq: x | | 2 |
       {{#ifeq: x | | 3 |
         {{#ifeq:  | | 4 | 
           {{#ifeq:   | | 5 |
             {{#ifeq:   | | 6 |
               {{#ifeq:   | | 7 |
                {{#ifeq:   | | 8 | 9
                 }}
               }}
             }}
           }}
         }}
       }}
    }}
 }}

}}|4=64|5=10}}}}%; } .col5 {width:{{#if:|{{#explode:{{{widths}}}| |4}}|60}}%; } .col6 {width:{{#explode:{{{widths}}}| |5}}%; } .col7 {width:{{#explode:{{{widths}}}| |6}}%; } .col8 {width:{{#explode:{{{widths}}}| |7}}%; } .col9 {width:{{#explode:{{{widths}}}| |8}}%; }

}}
{{#if:1| Name | Name }}
{{#if:1| User | User }}
{{#ifeq: Activities | Activities |
{{#if:1| Activities | Activities }}
| }}{{#ifeq:|-|
{{#if:1|'''''|}}
| }}{{#ifeq:|-|
{{#if:1|'''''|}}
| }}{{#ifeq:|-|
{{#if:1|'''''|}}
| }}{{#ifeq:|-|
{{#if:1|'''''|}}
| }}{{#ifeq:|-|
{{#if:1|'''''|}}
| }}{{#ifeq:|-|
{{#if:1|'''''|}}
| }}

{{#wdbq: RBE10K_Team_Members | criteria = _SourceArticle=:IMAR | sort = Name |{!RBE10K_TableRows ! {$Name} ! {$User!N/A} ! {$Activities} !} |

}}


<data table="RBE10K_Team_Members"> Name=Ziggy User=User:Ziggy Activities=Software developer </data>

<data table="RBE10K_Team_Members"> Name=Termitor User=User:Termitor Activities=Software developer </data>

<data table="RBE10K_Team_Members"> Name=Peter User=User:Galcon Activities=Software developer </data>

<data table="RBE10K_Team_Members"> Name=Alfonso User=User:Wahrheit Activities=Software developer and Economist </data>

<data table="RBE10K_Team_Members"> Name=Alexander User=User:A.zhemchugov Activities=Contributor </data>

<data table="RBE10K_Team_Members"> Name=Danielle User=User:Dan Activities=General Ray of Sunshine :) </data>

[edit] Requests

{{#css:Template:RBE10K TableRows/css}}{{#css: 

 	.colteam_requests1 {width:{{#if:30 15 55|{{#explode:30 15 55| |0}}|{{#switch:{{#ifeq: x | | 0 |
 {{#ifeq: x | | 1 |
    {{#ifeq:  Description  | | 2 |
       {{#ifeq:  | | 3 |
         {{#ifeq:  | | 4 | 
           {{#ifeq:   | | 5 |
             {{#ifeq:   | | 6 |
               {{#ifeq:   | | 7 |
                {{#ifeq:   | | 8 | 9
                 }}
               }}
             }}
           }}
         }}
       }}
    }}
 }}

}}|2=20|3=15|4=12|5=10}}}}%; } .colteam_requests2 {width:{{#if:30 15 55|{{#explode:30 15 55| |1}}|{{#switch:{{#ifeq: x | | 0 | 

 {{#ifeq: x | | 1 |
    {{#ifeq:  Description  | | 2 |
       {{#ifeq:  | | 3 |
         {{#ifeq:  | | 4 | 
           {{#ifeq:   | | 5 |
             {{#ifeq:   | | 6 |
               {{#ifeq:   | | 7 |
                {{#ifeq:   | | 8 | 9
                 }}
               }}
             }}
           }}
         }}
       }}
    }}
 }}

}}|2=80|3={{#if:|70|15}}|4=12|5=10}}}}%; } .colteam_requests3 {width:{{#if:30 15 55|{{#explode:30 15 55| |2}}|{{#switch:{{#ifeq: x | | 0 | 

 {{#ifeq: x | | 1 |
    {{#ifeq: x | | 2 |
       {{#ifeq:  | | 3 |
         {{#ifeq:  | | 4 | 
           {{#ifeq:   | | 5 |
             {{#ifeq:   | | 6 |
               {{#ifeq:   | | 7 |
                {{#ifeq:   | | 8 | 9
                 }}
               }}
             }}
           }}
         }}
       }}
    }}
 }}

}}|3=70|4={{#if:|64|12}}|5=10}}}}%; } .colteam_requests4 {width:{{#if:30 15 55|{{#explode:30 15 55| |3}}|{{#switch:{{#ifeq: x | | 0 | 

 {{#ifeq: x | | 1 |
    {{#ifeq: x | | 2 |
       {{#ifeq: x | | 3 |
         {{#ifeq:  | | 4 | 
           {{#ifeq:   | | 5 |
             {{#ifeq:   | | 6 |
               {{#ifeq:   | | 7 |
                {{#ifeq:   | | 8 | 9
                 }}
               }}
             }}
           }}
         }}
       }}
    }}
 }}

}}|4=64|5=10}}}}%; } .colteam_requests5 {width:{{#if:30 15 55|{{#explode:30 15 55| |4}}|60}}%; } .colteam_requests6 {width:{{#explode:30 15 55| |5}}%; } .colteam_requests7 {width:{{#explode:30 15 55| |6}}%; } .colteam_requests8 {width:{{#explode:30 15 55| |7}}%; } .colteam_requests9 {width:{{#explode:30 15 55| |8}}%; }

}}
{{#if:1| Name | Name }}
{{#if:1| Ref | Ref }}
{{#ifeq: Description | Description |
{{#if:1| Description | Description }}
| }}{{#ifeq:|-|
{{#if:1|'''''|}}
| }}{{#ifeq:|-|
{{#if:1|'''''|}}
| }}{{#ifeq:|-|
{{#if:1|'''''|}}
| }}{{#ifeq:|-|
{{#if:1|'''''|}}
| }}{{#ifeq:|-|
{{#if:1|'''''|}}
| }}{{#ifeq:|-|
{{#if:1|'''''|}}
| }}

{{#wdbq: RBE10K_Team_Requests | criteria = _SourceArticle=:IMAR | sort = Name |{!RBE10K_TableRows ! widths=30 15 55! {$Name} ! {$Ref!N/A} ! {$Description} !} |

}}
Retrieved from "https://rbem.org/wiki/index.php?title=:IMAR&oldid=10040"
Personal tools
Namespaces

Variants
Actions
Navigation
Toolbox