The problem with ALAC Statements
Let's talk about how the ALAC generates a "Statement" and what our NA reps on the ALAC can do to fix this problem. We saw an abuse of process in the ALAC Statement on the JPA which was put forward without an ALAC vote (for that matter, it was put forward even without ALAC-member consensus: "Whilst this document is not tendered to you as formally constituted consensus of the views of all of the At-Large community on this important matter..."). We recently have witnessed the ALAC "Joint Statement" that once again was not subject to a vote of the ALAC nor was it a product of any wide-reaching discussions. Further, almost all recent ALAC documents have had a public comment period of extremely limited duration: The (non-joint) ALAC Statement on GNSO Improvements had a one week window for comments; the Statement on the Draft Operating Plan as well as the Statement on Travel Policy had a 10-day window for comment. Frankly, this sucks. Even ICANN routinely allows 3-4 weeks for comments. I see the same types of things going on in the NCUC where members are given one or two days maximum to elicit organizational feedback in response to a position "already" taken by the leadership. More and more, we are witnessing the emergence of private fiefdoms wherein just one or two people within a constituent group call the shots and generate the Statements without any truly broad consultation. We don't need this kind of pattern to take hold in the ALAC. It's time for our reps to take a principled stand on this issue and to insist on proper methodologies; otherwise, the NARALO should formally consider seceding from the ALAC. ____________________________________________________________________________________ Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ
Well, you had me agreeing with most everything you said right up until that last paragraph. Maybe there is something we can do that would be a little less drastic? D Darlene A. Thompson Community Access Program Administrator Nunavut Dept. of Education / N-CAP P.O. Box 1000, Station 910 Iqaluit, NU X0A 0H0 Phone: (867) 975-5631 Fax: (867) 975-5610 E-mail: dthompson@gov.nu.ca -----Original Message----- From: na-discuss-bounces@atlarge-lists.icann.org [mailto:na-discuss-bounces@atlarge-lists.icann.org] On Behalf Of Danny Younger Sent: Friday, April 25, 2008 9:48 AM To: NA Discuss Subject: [NA-Discuss] The problem with ALAC Statements Let's talk about how the ALAC generates a "Statement" and what our NA reps on the ALAC can do to fix this problem. We saw an abuse of process in the ALAC Statement on the JPA which was put forward without an ALAC vote (for that matter, it was put forward even without ALAC-member consensus: "Whilst this document is not tendered to you as formally constituted consensus of the views of all of the At-Large community on this important matter..."). We recently have witnessed the ALAC "Joint Statement" that once again was not subject to a vote of the ALAC nor was it a product of any wide-reaching discussions. Further, almost all recent ALAC documents have had a public comment period of extremely limited duration: The (non-joint) ALAC Statement on GNSO Improvements had a one week window for comments; the Statement on the Draft Operating Plan as well as the Statement on Travel Policy had a 10-day window for comment. Frankly, this sucks. Even ICANN routinely allows 3-4 weeks for comments. I see the same types of things going on in the NCUC where members are given one or two days maximum to elicit organizational feedback in response to a position "already" taken by the leadership. More and more, we are witnessing the emergence of private fiefdoms wherein just one or two people within a constituent group call the shots and generate the Statements without any truly broad consultation. We don't need this kind of pattern to take hold in the ALAC. It's time for our reps to take a principled stand on this issue and to insist on proper methodologies; otherwise, the NARALO should formally consider seceding from the ALAC. ________________________________________________________________________ ____________ Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ ------ NA-Discuss mailing list NA-Discuss@atlarge-lists.icann.org http://atlarge-lists.icann.org/mailman/listinfo/na-discuss_atlarge-lists .icann.org Visit the NARALO online at http://www.naralo.org ------
Thompson, Darlene wrote:
Well, you had me agreeing with most everything you said right up until that last paragraph. Maybe there is something we can do that would be a little less drastic?
IMO the ALAC is still poisoned by having one-third of its VOTING members not be responsible to the community. You don't see one third of other constituencies having ICANN NomComm appointees parachuted in. This silliness is compounded by the fact that these appointees, in turn, get one third of the vote to select ALAC' NomComm members. The problem is certainly not with the individuals -- folks like Alan and Vanda have been absolutely critical to the recent maturing of ALAC -- but they belong in roles of senior advisors rather than leadership. The issue is not one of individual skill as much as it is the importing of ICANN bureaucratic culture into At-Large. We require a very different, community-centric cultural model -- one that so far has been totally foreign within ICANN. That requires a bottom-up approach that can only work if ALAC is 100% responsible to its community. The ICANN-bred elitism of ALAC is fading, though at an unacceptably glacial speed. At one point Robert was serving as the consciousness of ALAC to keep its policy discussions as open as possible, but for whatever reasons he's gone quiet lately. There was absolutely no excuse for the most recent GNSO-related discussions to happen on the ALAC internal list, which is why I started the thread here at na-discuss. And I'm told that other RALOs were able to discuss the recent joint statement because their RALO reps engaged them sooner. Given that some of the RALO reps on the joint statement were not RALO appointees and thus not responsible to their regions, I fault ALAC and support staff for not making accommodations to allow all regions to be equally engaged. I do not at all share Danny's eagerness to cede from the global at-large infrastructure. It merely makes us look like whiners and impedes the general advancement of At-Large policy. We need to work from within. My anger -- and the statement I drafted on top of Danny's -- were in response to a lack of time to respond, and were done as a last resort given a time frame of hours. But Beau's reply, in opposition to our opposition, :-) made all the sense in the world. I've asked Nick and Cheryl to extend the comment period by one week, giving us time to engage rather than oppose. In future we need to push ALAC -- and ensure that _it_ pushes as appropriate -- for the appropriate comment periods and mechanisms necessary to engage the community culture. This is doable, but it requires the continuation of an ongoing -- and sometimes painful -- thought-shift at the ALAC level. I would really appreciate if some NARALO members step forward to help figure out how to bring our concerns into the existing ALAC documents, even if the result indicates a diversity of views rather than a single consensus. Frankly, now that I've heard Alan's position I think we're not really far apart in views -- let's see how much common ground we really do have and how much our input can improve the ALAC position rather than undermine it. (At very least, I like the GNSO move to change its NomComm people from voting reps to non-voting advisors -- a step we should all be advocating with the ALAC reviewers, IMO.) That's it for now. My head hurts. - Evan
At 25/04/2008 11:28 AM, Evan Leibovitch wrote:
(At very least, I like the GNSO move to change its NomComm people from voting reps to non-voting advisors -- a step we should all be advocating with the ALAC reviewers, IMO.)
For the record, it is not a GNSO move, but rather the opinion of one faction within the GNSO.
That's it for now. My head hurts.
Mine too! Alan
- Evan
participants (4)
-
Alan Greenberg -
Danny Younger -
Evan Leibovitch -
Thompson, Darlene