<<<
Chronological Index
>>> <<<
Thread Index
>>>
[gnso-osc-ccc] ACTIONS/SUMMARY: OSC Communications Work Team
- To: gnso-osc-ccc <gnso-osc-ccc@xxxxxxxxx>
- Subject: [gnso-osc-ccc] ACTIONS/SUMMARY: OSC Communications Work Team
- From: Julie Hedlund <julie.hedlund@xxxxxxxxx>
- Date: Wed, 2 Sep 2009 14:39:53 -0700
Dear Work Team members,
Here are the action items and summary from today's meeting. These also are
posted on the wiki at:
https://st.icann.org/icann-osc/index.cgi?osc_communications_team. Our next
meeting will be held on 16 September at 1900 UTC. Please let me know if you
have any questions.
Thank you.
Best regards,
Julie
Action Items:
Tasks 1 and 2: Website "design scrum" (Steve, Chris, Ken, and Scott)
--The sub team is looking at the structure of a new GNSO website
Task 3: Soliciting Meaningful Feedback (Helen and Zbynek)
--Work Team members should review the Draft Recommendations (attached) from
Zbynek. Julie circulated the ICANN policy translation procedures and notes from
the meeting with Christina Rodriguez.
Task 4: Improve Coordination with ICANN Structures (Mason)
--Mason will complete his analysis of what is being done already in ICANN and
what needs to be done. Mason will draft an outline/template document for output.
Summary:
Tasks 1 and 2: Chris reported that the sub team is meeting in Marina del Rey to
look at the structure of a new GNSO web site. Scott noted that he will be
leveraging information of surveys for 230 ICANN web site users, may of whom are
new to the ICANN world.
Task 3: Zbynek asked for Work Team feedback on his draft recommendations. Steve
noted that it would be useful to have information on the current procedure for
translation ICANN policy documents and Zbynek added it would be good to have
notes and the recording of the call with Christina Rodriguez. Julie circulated
the current translation procedures document and her notes from the call, but
unfortunately the call was not recorded.
Task 4: Mason has been engaged in identifying problems, determining what is
already being done in ICANN, and what needs to be done. In addition to the
recommendations Mason is developing, he also will consider codes of conduct for
ICANN blogs/public forums and better communications at meetings.
Output Format: Mason agreed to set up a document template.
<<<
Chronological Index
>>> <<<
Thread Index
>>>
|