[Resolve] some comments about blocking

[Sheri Herndon]

>Delivered-To: sheri@speakeasy.org
>Date: Mon, 7 Apr 2003 13:06:51 -0700 (PDT)
>From: ".:.:cburn:.:." <chris@www.regenerationtv.com>
>To: Sheri Herndon <sheri@speakeasy.org>
>Subject: Re: Fwd: Re: [Resolve] how does blocking occur on the lists
>X-Scanned-By: MIMEDefang 2.20 (www . roaringpenguin . com / mimedefang)
>
>forward if you like:
>
>yo.
>
>yes, blocking must be articulated in the context of the violation
>of the groups principles of unity, or a violation of the mission
>statement of the organization. simply blocking is not acceptable.
>why?
>
>1. it allows the group to be manipulated by one person
>2. it allows personality conflicts to dominate group process by
>not demanding that blocks be articulated in the context of the
>mission or principles.
>
>the group can decide if the reason for the block is justifiable.
>if not, the group can move forward even when someone declares a
>block. the group and that individual may decide to part ways if
>the block is considered frivolous.
>
>it is important, i think, to adopt the "consensus minus two"
>requirement which says that in order for a block to occur, it
>not only needs articulation in the context of mission and principles,
>but it requires 3 people. that is, consensus can be reached with
>two people blocking.
>
>trainings and process development are critical to a groups
>functionality. consensus only works when a group has common ground
>on which to work; namely, either a carefully crafted mission statement
>or carefully crafted principles of unity.
>
>word,
>chris
>
>
>
>
>
>On Mon, 7 Apr 2003, Sheri Herndon wrote:
>
>>  hola chris,
>>  xoxox
>>  do you have info on consensus and blocking on line?
>>  how are you?
>>  are you home?
>>  available.
>>  xoxo
>>
>>  >Delivered-To: sheri@speakeasy.org
>>  >Delivered-To: sheri@indymedia.org
>>  >Delivered-To: resolve@indymedia.org
>>  >From: Sarsnic@aol.com
>>  >To: resolve@indymedia.org
>>  >Subject: Re: [Resolve] how does blocking occur on the lists
>>  >Sender: resolve-admin@lists.indymedia.org
>>  >X-BeenThere: resolve@lists.indymedia.org
>>  >X-Mailman-Version: 2.0.13
>>  >List-Help: <mailto:resolve-request@lists.indymedia.org?subject=help>
>>  >List-Post: <mailto:resolve@lists.indymedia.org>
>>  >List-Subscribe: <http://lists.indymedia.org/mailman/listinfo/resolve>,
>>  >	<mailto:resolve-request@lists.indymedia.org?subject=subscribe>
>>  >List-Id: A list to discuss and implement an indymedia network-wide
>>  >conflict resolution plan <resolve.lists.indymedia.org>
>>  >List-Unsubscribe: <http://lists.indymedia.org/mailman/listinfo/resolve>,
>>  >	<mailto:resolve-request@lists.indymedia.org?subject=unsubscribe>
>>  >List-Archive: <http://lists.indymedia.org/mailman/public/resolve/>
>>  >Date: Mon, 07 Apr 2003 15:18:40 -0400
>>  >
>>  >yeah, like here in Houston we ran into some really confusing issues
>>  >about blocks because food not bombs formal consesnsus which we have
>>  >been trying to implement specifies that:
>>  >
>>  >>A concern must be based upon the principles of the group to justify
>>  >>a block to consensus.
>>  >
>>  >But then we didn't know how we are supposd to achieve a consensus
>>  >about whether a block is or isnt' based on the principles of the
>>  >group
>>  >
>>  >Peace
>>  >Nick
>>  >
>>  >_______________________________________________
>>  >Resolve mailing list
>>  >Resolve@lists.indymedia.org
>>  >http://lists.indymedia.org/mailman/listinfo/resolve
>>
>>
>>  --
>>  You never change things by fighting the existing reality.
>>  To change something, build a NEW model that makes the existing 
>>model obsolete.
>>
>>  Buckminster Fuller
>>


-- 
You never change things by fighting the existing reality. 
To change something, build a NEW model that makes the existing model obsolete.

Buckminster Fuller