Wednesday, 24 June 2009
Summary of input to meeting
This summarizes public input into the broad topics outlined by the committee.
- The deadlines were very helpful
- It would helpful to include meeting agendas as part of that deadline
- Need to consider how to avoid overloading people with the number of documents
- Expectation that earlier provision of documents will mean fewer presentations at meetings about a report, and more discussion of a report
- Documents themselves are too long and complex – acts as a barrier to entry
- There is a significant need for documents in plain language
- Need to present fewer acronyms, and to provide explanation of acronyms when they do appear (a glossary on each document?)
- Translations of documents need to be made more easily and readily available (and supporting documentation also needs to be translated)
- Translations of documents need to be provided to the same document deadlines
- Three meetings a year around the globe make participation difficult (time and cost)
- Consider reducing the number of meetings
- Consider the use of a hub city for meetings
- Look at expanding/improving remote participation
- Need more information about meeting agendas to entice people
- There’s not been a meeting in North America for some time
Public comment process
- Too many public comment periods (have different types?)
- Consider having a rule that no public comment periods will be open during a meeting (as people don’t have time to review or respond)
What it is | The Board Committee on Public Participation is holding an open session to ask the community what it thinks about a number of new ideas for improving participation within ICANN, plus to allow the community to make their own suggestions.
Why it's Important | Participation is an important issue for ICANN as an organization. This is an opportunity for community members to enter into free and open discussion about what improvements could be made with Board members.
Who should attend? | All those interested in improving participation within ICANN.
What it is | Organizational Reviews examine individually each of the key structures of ICANN; at the end of each OR process a set of recommendations is issued for each of the structures that have been reviewed. From a horizontal analysis of these recommendations emerged interrelationships and dependencies that are visible only when considering ICANN as a system rather than a collection of parts. During this workshop the Structural Improvements Committee will present for discussion the key findings from this analysis, and proposals to deal with these interrelationships.
Why it's Important | This is an occasion for the community to participate to the debate on ways to solve interrelations and dependencies from different OR processes.
Who should attend? | Members of the Structural Improvements Committee and the Board, interested Community Members