[consulting] List Mom Policies

[Dan Robinson]

ultimately a list lives or dies by how useful it is to people.  I
wouldn't get too crazy regarding rules and regulations.  Publish the
Mission, publish a short list of do's and don'ts.  Gently push
conversations that don't belong here off the list (explain when and
why).  Use off-list communication to coach list participants.

In the list of specific "dont's" you have:

		      *	Pricing on list ( Illegal -> price fixing)
 		      * How do I code X -> Use the development list
 		      * How do I use drupal (as a user) -> 
			    Use the support list
 		      * organizing conferences -> 
			    Use the conference list
		      * Details of a particular RFP collaboration ->
			    Keep details off list, post summary at end.(1) 


You could summarize by saying - "Don't use this list for anything that
another list has already been set up to handle". 

I don't understand the "Pricing" issue?

My $.03

Dan

> This list mom's have been talking a bit about having a written
> policy about what goes on the consultant list. This is how far
> we got in our discussion today. I think this will be the 
> practice we will try to follow at this point. 
>
>
>
>  Consulting list Policy:
>
>  	   Mission: The mission of the consulting list is to enhance
>  		    drupal consulting by enabling consultant to
>  		    consultant conversations, especially the sharing
>  		    of best practices.
>
>
>  	   Process: This list is a collection of professionals who
>  		    provide Drupal services from strategy to design to
>  		    development. As such, this list is a high quality
>  		    conversation, with participants working to
>  		    maximize the signal to noise ratio.
>
>
>  	  What is in: On this list it is great to talk about:
>
>  		     * Current projects, architecture
>  		     * RFP's -> Request for proposals
>  		     * Request for subcontract help
>  		     * Contracting issues
>  		     * Consulting Marketing
>  		     * Consulting support documents
>  		     * Sharing/suggestions on best practices to approach 
> 		       a particular problem
> 		     * Announcements/requests for RFP collaboration
> 				 -> Details go offlist	      
>
>
>  	  What is off: On this list is it is a problem to talk about:
>  		       (Do not do it)
>
>  		      *	Pricing on list ( Illegal -> price fixing)
>  		      * How do I code X -> Use the development list
>  		      * How do I use drupal (as a user) -> 
> 			    Use the support list
>  		      * organizing conferences -> 
> 			    Use the conference list
> 		      * Details of a particular RFP collaboration ->
> 			    Keep details off list, post summary at end.(1) 
>
>
>
>
>
> 	Footnotes: 
>
> 	(1) - As an example of an RFP collaboration: 
>
> 	      Person1 posts: RFP #xyz: I have a project $XYZ that
> 			       looks like $ABC and I would like to
> 			       have proposals submited.  please reply
> 			       off list.
>
> 	     Person2 posts:   I've responded, and could use a partner to do $X
> 	     Person3 posts:   I've responded to $X off list.... 
>
> 	     Person1 posts: RFP #XYZ: RFP summary: We got a good response
> 			    to the RFP and we are succesful meeting our
> 			    needs. (or not as the case may be)
>
>
>
>
> 	
>
>
> _______________________________________________
> consulting mailing list
> consulting at drupal.org
> http://lists.drupal.org/mailman/listinfo/consulting
>
>