Adam Peake wrote:
I didn't ask ALS to disclose details of their structures, In fact, you did. On October 7 your mail (Message ID <p06240804c3362fc0a332@[192.168.0.2]>) included this:
"All ALS will "Post on the Internet (on the ALAC's website or elsewhere) publicly-accessible, current information about the ALS's goals, structure, description of constituent group(s)/membership [including how to join the group], working mechanisms, leadership, and contact(s)."
My suggestions were twofold, (1) to make sure information about policies processes flowed to the ALS (ALAC delegate's responsibility), (2) the ALS had a means of disseminating that information, asking for comment on it, and a means to provide any comment back to the ALAC (and from there whatever policy process might be going on.) Agreed... and this is the order in which the process should take place. Any policy initiative for which ICANN is soliciting the advice of At-Large requires supporting data _first_.
We're waiting.
For example, Nick's just told us about the new "news-backgrounders" that are being produced. These should be getting out to the ALS, being presented on your websites. No, Nick didn't "just" tell us... that exact same information was conveyed to NARALO at the San Juan meeting, which was many months ago. Given that most journalists work on deadlines measured in hours and days rather than months, the speed of this process is unacceptable. If ICANN wants timely feedback it has an obligation to provide timely information. And ALAC has a primary role in pressing for this to happen.
We're waiting.
I'm suggesting your task as an ALS officer is to make sure that information received is made available to your members and others. First something has to be received.
We're waiting. - Evan