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
Post call comments by Olivier Crepin- Leblond, submitted later due to poor telephone connection:
Two comments:
- on the inclusion of the code of conduct
I am concerned about removing the code of conduct altogether and
therefore object to it.
The current code of conduct defines the type of contravention a mailing
list posting falls under and in the nearly 2 years I have Chaired the
ALAC, I have had to quote it on several instances. Agreed you may have
not heard about it, but I have had to act on several postings to have
them removed from the archives, the poster asked to stop their offensive
postings, spam to be removed from WIKIs, and even had to issue a few
formal warnings. The current code of conduct clearly allows the Chair to
perform such actions under 22.15
The Ombudsman Code of conduct is good, but does not go far enough in my
opinion re: the type of posting that is inappropriate and the type of
action that can be taken by the Chair against such a posting re-occuring.
- on the definitions
I had really bad mobile phone reception during this part of the call (I
dropped a dozen times) so perhaps I missed the consensus. Clearly we
need to separate a "glossary" from a "definitions" section. In any legal
document there is a section that defines words which take a special
meaning in the document so let's make sure we keep that in the document.
In both cases, code of conduct and definitions, Alan is absolutely right
that Web addresses will likely change after 5 years. I suggest that the
documents be given a document name and a document filing code that will
make them easily searchable under any system or using Google -- which
will always find them even if the URLs change. You can then refer to
these documents by their full name and by their filing code. (a bit like
a serial number or docket filing number)
