A private discussion to wordsmith a public policy, isn't really a transparent process. 

The larger At-Large community should be able to both see the discussions taking place and  also contribute in all steps of the process. I stand by my statement that only - confidential - matters should be discussed on the internal ALAC list. All other discussions, especially items related to policy should be public. 

Might I suggest second the process called for by Jean, that being that a  document be drafted (and agreed by both ALAC and the larger at-large community) to define what specific items are for the internal list. Having a well defined policy will make it clear what indeed to be privately discussed, and what by default should be open and public.

regards

Robert




On 6-Dec-07, at 7:33 AM, Jacqueline A. Morris wrote:

Didn’t the ALAC agree to this ages ago?  And haven’t all the policy issues been discussed on the public list?
If you’re talking about final wordsmithing on a document for 24-48 hours  after a month in discussion on the public list, I don’t see that as being a violation of transparency and openness. More a  practical way to finally get a document finished and approved by ALAC to send out in time!
Jacqueline
 
From: alac-bounces@atlarge-lists.icann.org [mailto:alac-bounces@atlarge-lists.icann.org] On Behalf Of Robert Guerra
Sent: Wednesday, December 05, 2007 15:17
To: At-Large Worldwide
Subject: [At-Large] Discussions should be transparent / Open ...
 
 
I've repeatedly been raising the issue - that in fact the ALAC internal list should be for confidential matters, while all discussions (especially policy) should take place on the more open and transparent public at-large list.
 
Any support on this matter would be most welcome.
 
 
regards,
 
Robert
---
Robert Guerra <rguerra@privaterra.ca>
Managing Director, Privaterra
Tel +1 416 893 0377
 

No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.5.503 / Virus Database: 269.16.15/1173 - Release Date: 12/5/2007 21:29


No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.5.503 / Virus Database: 269.16.15/1173 - Release Date: 12/5/2007 21:29