[Harp-L] RE: Jam Format
I have a legitimate comment only on item (a):
(a) talk to the club admin. and have them assisting you.
For instance, during the start of the show you (1) publicly announce the request to those sitting in the crowd not to play over someone else's set and (2) if someone abuses the rule, the waiter or a watchdog person comes up and asks to follow the rule - that attracts attention of others and works well for a normal person.
So, in the first case, potential rule abusers would think twice before breaking the rule publicly as everyone knows that there is a rule - in contrast with the situation when there was no announcement meaning that whatever not prohibited is allowed - so they would feel the pressure to control themselves. And as the others - more responsible or those without the harps:) - heard the announcement they'd feel committed to shout at the abuser or make him/her shut up in a more polite manner:).
***
As for items (b) and (c), I think that requires some time - over a month or so - you can compile sort of a black list, etc. and of course there should be one single person singing up people for the jam and keeping the order of songs/performers.
Hope that helps,
Alex
Help save paper! Do you really need to print this email?
>>> "Bill Kumpe" <bkumpe@xxxxxxx> 29/03/2010 00:58 >>>
I think you guys are dead on with what has been presented so far. Would
anyone like to offer expert input on how to handle:
(a) Gussers who sit in the crowd and play all over someone else's set
(b) People who interrupt or refuse to follow the jam format
(c) People who object to the concept of a jam format
This e-mail message may contain confidential and/or privileged material.
Delivery of this message to any person other than the intended recipient(s) does not in any way waive privilege or confidentiality.
The information transmitted is intended only for the person or entity to whom or which it is addressed.
Unauthorized use, disclosure or copying is strictly prohibited.
The sender accepts no liability for the proper transmission of this communication or for any delay in its receipt.
This archive was generated by a fusion of
Pipermail 0.09 (Mailman edition) and
MHonArc 2.6.8.