[gnso-rpm-wg] Need to Complete and Post SOIs ASAP
psc at vlaw-dc.com
Sun Apr 10 17:57:23 UTC 2016
Thanks for that very useful clarification, Greg.
Philip S. Corwin, Founding Principal
1155 F Street, NW
Washington, DC 20004
"Luck is the residue of design" -- Branch Rickey
From: gnso-rpm-wg-bounces at icann.org [mailto:gnso-rpm-wg-bounces at icann.org] On Behalf Of Greg Shatan via gnso-rpm-wg
Sent: Sunday, April 10, 2016 1:00 PM
To: gnso-rpm-wg at icann.org
Subject: Re: [gnso-rpm-wg] Need to Complete and Post SOIs ASAP
I would add one more note for those adding/updating SOIs, especially ICANN newcomers. There seems to be some confusion about what to do when the SOI form or the WG asks for Stakeholder Group/Constituency (SG/C) affiliation.
Where the SOI (and this Working Group) asks for SG/C affiliation, this refers to formal membership in a SG and/or a C (i.e., you have applied for and been granted membership by that SG and/or C, or you are a designated representative to that SG/C on behalf of an organization or employer). It does not refer to an aspiration or alignment with the goals of an SG/C -- just actual membership.
A number of participants seem to be listing SG/Cs (on their SOIs and in the WG records) without being members. This is incorrect and could be confusing and/or misleading.
However, consider this an invitation rather than a problem: all of the SGs and Cs are happy to take membership applications from applicants that meet their membership criteria. The ICANN experience can be a lot more meaningful and productive when you are a member of an SG/C (or an AC, such as ALAC). So, if you are not a member of an SG/C or an AC, look at the various organizations and see if there's one that seems appropriate, and apply. If none fit, or you would simply prefer to continue as an "Individual" participant in ICANN activities, that is fine, too. Regardless, it's important that the SOIs and WG records accurately reflect a participant's actual and present status.
Thanks for your attention to this.
P.S. I'm with George -- Question 12 should be answered accurately and updated when necessary. Nothing is self-evident when looking at a SOI, except what's there. I'm checking mine as soon as I send this email....
On Sun, Apr 10, 2016 at 12:22 PM, George Kirikos via gnso-rpm-wg <gnso-rpm-wg at icann.org<mailto:gnso-rpm-wg at icann.org>> wrote:
Many (most?) members who already had SOIs on the wiki prior to this
working group's creation will need to update their SOI in order to add
this working group to the answer to #12:
"12) Please identify any Working Groups or other chartered teams in
which you are participating (include acronyms, if applicable):"
Perhaps an ICANN staff member, if they have bulk access, can
add/append this working group to each of the SOIs of members listed
That would save 100+ members from having to log-in individually (if
they even remember their passwords) to make the updates themselves.
On Sun, Apr 10, 2016 at 12:12 PM, Phil Corwin via gnso-rpm-wg
<gnso-rpm-wg at icann.org<mailto:gnso-rpm-wg at icann.org>> wrote:
> Dear WG Members:
> I have been alerted by our excellent and hardworking ICANN support staff
> that many of those who have joined this RPM WG as members have yet to file
> their Statement of Interest, and have also failed to respond to reminders
> sent by staff.
> Filing an SOI is not an option but a requirement. Those who fail to do so
> will not be permitted to join our meetings/conference calls and will
> essentially be relegated to observer status.
> Therefore, if you have not yet filed your SOI please take a few minutes (and
> that’s all it takes) and get it done so that you can participate in our
> first meeting on April 21st.
> Thanks and best regards,
> Philip S. Corwin, Founding Principal
> Virtualaw LLC
> 1155 F Street, NW
> Suite 1050
> Washington, DC 20004
> Twitter: @VlawDC
> "Luck is the residue of design" -- Branch Rickey
> gnso-rpm-wg mailing list
> gnso-rpm-wg at icann.org<mailto:gnso-rpm-wg at icann.org>
gnso-rpm-wg mailing list
gnso-rpm-wg at icann.org<mailto:gnso-rpm-wg at icann.org>
No virus found in this message.
Checked by AVG - www.avg.com<http://www.avg.com>
Version: 2016.0.7497 / Virus Database: 4545/11942 - Release Date: 04/02/16
Internal Virus Database is out of date.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the gnso-rpm-wg