Hi,

I think if we had a separate list, the threading would get confused.  plus there is a large fuzzy space between Procedural and Policy.  for example on issue that is the current cause of various forms of stress, the cause and solution may be procedural, but what makes it an issue is a policy issue - transparency and accountability.  Of course I have absolutely no problem with list proliferation, mail tools seem to file them quite nicely so i read topics when i want to, sometimes even combining several lists into one folder.

As for handling it, I think we can all learn to avoid threads that have red flag subject line tags  like {NCUC-issue}  or [NCUC].  If a non-nuc want to read it, cool, easier than the archive.  But it they don't the bypass or hit delete.  Could even set up a private filter to delete anything with [NCUC] in it.  Of course we NCUC'er would be to be diligent about including the subject line tag.


avri


On 17 Nov 2011, at 11:57, David Cake wrote:

> 	Just to address Alains comments about our 'dirty laundry' - I agree with the general NCUC feeling that a separate NCUC list for policy discussion would probably be a mistake, I think an NCUC list for NCUC internal procedural issues would be the optimum - but I'm loathe to create a separate email list for what is usually a very small number of messages, especially given the confusion that might result between the two (as soon as two separate lists existed, I would foresee a regular quantity of messages to the wrong list). Suggestions for how better to manage the issue welcome.
> 	Regards
> 		David