[wlug_org] Second draft of WellyLUG guidelines

[Jamie Baddeley]

Can I propose this is our second draft?

What are the views on this?

(note my additions)

Once we have agreement, I suppose we can present this to the lug on
monday.

jamie

On Thu, 2004-05-06 at 18:56, Tony Wills wrote:
> Guidelines:
> 
> The following is a guide to help the WellyLug avoid unnecessary conflict and assist us 
> in achieving our goals which are:
a) To exchange Linux and Open Source Software knowledge and experience.

b) To encourage the use of Linux and Open Source Software 

> They are by their nature optional but are designed to help facilitate
> smoother interpersonal relations. These are not rules. They are simply some common sense practical tips to help keep our LUG humming. Humming is good.
> 
>       1. Try to keep all commentary civil, and be courteous. Try to refrain from using coarse or insulting language.
>          [Constructive criticism in the spirit of genuine dialogue is welcome, but insults directed towards other members will not be
>          well received.]
> 
>       2. Some people are interested in the political aspects of free and
>          open source software. Others are more interested from a hobbyist
>          perspective. The LUG embraces both.
> 
>       3. If you are in serious conflict with someone by e-mail, take a deep 
> breath and wait an hour or sleep on it before replying! And if it still winds you up, then take it off list.
> 

4. 	No advertising on the list. If you must, then please take it
	offlist. (OK. We have 1 rule)


> 
> Keep in mind the following:
> 
>        * It's a much better feeling to resolve a conflict in a way that
>          improves the relationship you have with your fellow members,
>          which benefits everyone including yourself.
>        * Look beyond short term frustrations to the longer term future of
>          the group.
>        * Sometimes people might have a bad day. Forgive them. No one is immune to a visit from Mr Grumpy.
>        * Clarify individual perceptions involved in the conflict. You
>          can't solve a problem if you don't know what it is about. Sort
>          the parts of the conflict - ask what it is about. Avoid ghost
Umm, what are ghost conflicts?
>          conflicts - get to the heart of the matter and avoid side
>          issues. Clarify what, if any, values are involved. If you pause
>          to think about it, you may recognise that the parties involved
>          need each other to be most effective in forming a healthy LUG
>          community. Additionally, clarify your perceptions of the other
>          party. Avoid stereotyping. Try to listen carefully. Recognise the
>          other's needs and values. Try to Empathise - ask why they feel the way
>          they do. Clear up misconceptions you may have of them.
>