Re: Media Access (ACTION-197)

Hi Jonathan, 

because of travel I was not able to attend the meeting. W3C has several 
setups that may help. A public working group does not mean that everybody 
can just join a meeting or dial into the WG Call. We have a member 
confidential list. So we can send the (changed) conference call details 
there to avoid unwanted people to join. This doesn't prevent leaking of 
course. But it is different from the current setup where we publish dial-in 
information to the public. 

The charter only talks about the publication of the proceedings, not of all 
our talks. Proceedings are minutes and the mailing-list and the Drafts. Not 
all conversation. So we have that option. 

BTW, I don't think a "Policy" will help because we do not have any power 
arbitrary press folks smuggling into a call. 

Best, 

Rigo

On Wednesday 09 May 2012 15:59:57 Jonathan Mayer wrote:
> I was tasked on today's call with thinking through alternative media
> access policies.  Here's a rough outline of design points: Are media
> allowed to listen to calls and meetings?
> If yes, may they reference their first-hand experience in their reporting?
>  (If not, they'll have to cite our oh-so-reliable minutes and second-hand
> descriptions.) If yes, what degree of first-hand reporting will be
> permissible? Quotation
> Direct quotes (e.g. "I want a lunch break")
> Paraphrasing (e.g. noted that he wanted a lunch break)
> Collective sentiment (e.g. several wanted to break for lunch)
> 
> Attribution
> Identification (e.g. Jonathan Mayer from Stanford said)
> Background (e.g. a researcher said)
> None (e.g. a participant in the working group said)
> 
> Impressions (e.g. he looked hungry)
> Procedure (e.g. there was a vote to break for lunch)
> Conduct (e.g. he left to get lunch)
> 
> Will we provide media briefings?
> 
> 
> In selecting which policy we adopt, we have to weigh the concerns of
> certain industry participants—erroneously negative publicity, corporate
> media policy, and the attendant chilling effects of both—against the
> importance of transparency in this process.  Given the broad spectrum of
> design points, there seems to me a lot of scope for compromise.
> 
> Jonathan

Received on Monday, 14 May 2012 15:14:11 UTC