Summary Minutes and Action Items
1. Attendance Introduction, Welcome Meeting Outline
Roll call was held
2. Introduction and Review of Drafting Team's Status
Introduction was held.
CLO noted that Toronto was the drop-dead date for a new set of ALAC ROPs.
HR: We have decided to go through the definitions and more fully define the definitions.
HR: I think the rules referring to this needs more fully understandable english
We will strive for plain simple English with the definition of each term at the end.
HR: I think that, in terms of structure, we need an introduction that gives a background and a bit of At-Large history.
HR: Many rules have bits and pieces of information. We don't need this in the rules. This should be in the introduction.
HR: We need the relationship of the RALOs in the introduction.
HR: We need to note that the ICANN Bylaws take precedence over all rules.
HR: The final sections would be the selection of a Board member.
AG: When one comes up with a capitalized term, they are defined in line. That is then echoed in the glossary. Will we do so in this document?
HR: This has not been decided.
AG:I propose that we define the terms in line as well as in the glossary.
CLO: We should use a glossary which is specifc to our needs and link it to ICANN's searchable database of acronyms.
AG: If we are going to use acronyms. we need to define the acronyms..
CNN: We should have a definition section that is also defined locally.
AI: firm - AI: Staff to help draft a glossary/preamble and/or confirm/suggest style formats to allow both display and print of all definitions within the amended ROPs.
AG: Thought putting code of conduct should not be in the ROPs. It can be someplace else, but not the ROPs.
CLO: We need to be sure that the link in our master document does not change. - information.
AG - PDMDT - Info to be moved to sandbox.
ST: We should look at the sandbox template.
AG: The group has worked through half of the responsibilities. We will hopefully have a list by next week. At that point, we will review the daft. At that point, we will send it to the definitions team.
CLO: There will be a number of things that each DT will come up with and define..
3. Committee of the whole Discussion
AG: We are looking to develop a reasonable mode. We will outline the general way in which we will use Robert's Rules.
CLO: At the end of each meeting, we should be updating Staff with updates to the template.
CLO: until a drafting team has come to consensus, it will not go into the template.
x
4. Next Meeting and review of AIs
17th September
x
