Skip to end of banner
Go to start of banner

2015-02-03 - Structure

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Minutes

Present: Doug W, Joachim T. 

Apologies: None

Location: Nürnberg

[Meeting begins 12:10]

JT: konsensieren.eu: why use an non-person (yunity) account: pros and cons?

DW: Non-person account makes things easier - one account, one username and one password: people don't need to make an account. This makes konsensierung creation as easy as possible, with participants only requiring slack and konsensieren, not email as well.

JT: Personal accounts to set up konsensierungen provides most transparency and gets it to become routine. 

DW: Participation does not require an account, but setting up a konsensierung does.

JT: yunity konsensieren account is not transparent, suggestion: setting up konsensierungen only via personal accounts and use slack for announcing votes, access via (link) after testing.

DW: Short-comings of konsensieren.eu: English date-setting is broken, alteration of date and time not possible (although implied), votes are anonymous, no integrated NW&V. Why were we in support of non-anonymous voting?

    • JT: For reevaluation questions can be asked to resistant person asked why someone is highly resistant
    • DW: Plus accountability fosters responsibility

DW: Possibility of using the wiki for systemic consensus. Pro: Platform in use, people have accounts, keeps all sections of systemic consensus in one place, instantly documented, can. Con: Not designed for systemic consensus, people have to be responsible and disciplined to do the stages in the correct order, voting cannot be done synchronously (votes infuenced by others), people can't 'break' other peoples entries.

JT: konsensieren.eu is the better technical solution right now, although I want to test different approaches. With konsensieren.eu we can analyze resistance to find out THAT there is high resistance in a good solution and then ask for who and why. Find a better technical solution in long run, either with the konsensieren.eu team or with our own software.

[Meeting ends: 13:30]



Outcomes

Protocol for participating in online systemic consensus

Systemic consensuses will be announced on Slack.

  • Please see the guidance on deciding how you will participate in the decision on the [wiki].

Opening the link will take you to konsensieren.eu - an online systemic consensus tool.

  • The first thing you'll be offered is a tutorial, which is helpful and doesn't take long.
  • Please record your Needs Wants and Values on the Titanpad linked in the description, and take some time to read those of others.
  • You can make suggestions within the given time period.
    • Please provide full, real name and email address.
    • Please see the guidance on formulating good suggestions [wiki]
    • Where possible, make suggestions based on the values that you find in the konsensierung description.
  •  Voting will occur once the suggestion phase has ended (no more suggestions can be made). You can then vote over the given time period
    • Please provide full, real name and email address.
  • The result of the vote will be visible at the end of the voting time period.

Protocol for creation of online systemic consensus

To create a konsensierung, please make an account on konsensieren.eu with your full, real name and a picture.

  • Check on how to ask questions in the [wiki].
  • Make sure to include Zero and Further Solutions options.
  • Please set time and date in Deutsch! (there is a bug when you try to do it in English).
  • Please set the period for suggestions to end before the voting period begins.
  • You cannot change time and date once set.
  • You can then send a link to slack to get the vote started


consent on:

-using konsensieren.eu for online decision making

-putting link fot titanpad with NWVs in description + visualthesaurus link for evaluation of NWVs also link to wiki for protocols 

-Slack link leads to wiki decisions list

  • No labels