From PolicyCalendar at icann.org Mon Feb 4 14:08:53 2019 From: PolicyCalendar at icann.org (ICANN Policy Calendar) Date: Mon, 4 Feb 2019 12:08:53 +0000 Subject: [NCSG-FC] NCSG Finance Committee Meeting on 06 February 2019 at 1400 UTC Message-ID: <5d768ae98a864181bb83f9fa072f03fb@PMBX112-W1-CA-1.PEXCH112.ICANN.ORG> Dear All, Please find participation details for the NCSG Finance Committee Meeting on 06 February 2019 at 1400 UTC Adobe Connect: https://participate.icann.org/ncsg Time Zones: https://tinyurl.com/yas66ghe Dial out request: please send an email to Maryam.bakoshi at icann.org off-list. Audio dial-in details below: [https://cobranding-pgi.s3.amazonaws.com/1/Logo1.png] You're invited. You've been invited to a GlobalMeet? audio meeting. Have the meeting call you. Click the Connect Me link below. No need to dial-in. Connect Me [go.conferencinghub.com] Not at your computer? You can join by dialing one of the access numbers below. Mobile: tel://16054755604,*,,9922790467# Phone Only Controls : https://go.conferencinghub.com/2xdh7 Access Number: 1-605-475-5604 Guest Passcode: 992 279 0467 Additional Access: USA: 1-605-475-5604 USA: 1-719-457-6209 Canada, Calgary: +1 403 407 5793 Canada, Montreal: +1 514 669 5928 Canada, Toronto: +1 647 426 9172 Canada, Vancouver: +1 604 222 7836 Argentina, Buenos Aires: +54 (0) 11 5172 6003 Argentina (toll free): 0800 800 1223 Australia, Sydney: +61 (0) 2 8017 6064 Australia, Melbourne: +61 (0) 3 8687 0553 Australia, Brisbane: +61 (0) 7 3015 0535 Australia (toll free): 1 800 804 786 Austria (toll free): 0800 070 981 Bahrain, Manama: +973 1619 8739 Bahrain (toll free): 800 04212 Belarus (toll free): 8 820 0011 0341 Belgium, Brussels: +32 (0) 2 400 6928 Belgium (toll free): 0800 39279 Bosnia and Herzegovina: +387 7031 1442 Brazil, Sao Paulo: +55 11 4935 7169 Brazil, Rio de Janeiro: +55 21 4560 0072 Brazil (toll free): 0800 887 0233 Bulgaria, Sofia: +359 (0) 2 491 6045 Bulgaria (toll free): 00800 111 4950 Cambodia, Phnom Penh: +855 23 965 723 Canada (toll free): 1 855 950 3717 Chile, Santiago: +56 (0) 2 2666 0696 Chile (toll free): 171 800 835 783 China (national): +400 613 8103 China, Beijing: +86 10 5667 0003 China, Shanghai: +86 21 2039 7081 Colombia, Bogota: +57 1 508 8137 Colombia (toll free): 01 800 755 0102 Costa Rica (toll free): 800 542 5328 Croatia (toll free): 0800 805 940 Cyprus (toll free): 800 97424 Czech Republic, Prague: +420 225 986 554 Czech Republic (toll free): 800 701 532 Denmark, Copenhagen: +45 32 72 78 10 Denmark (toll free): 80 70 35 86 Egypt (toll free): 0800 000 0593 Estonia, Tallinn: +372 622 6551 Estonia (toll free): 800 011 1589 Fiji (toll free): 00800 3322 Finland, Helsinki: +358 (0) 9 2310 1677 Finland (toll free): 0800 772 236 France, Paris: +33 (0) 1 70 37 16 56 France (toll free): 0800 946 531 France (national): 0811 655 100 France (national): 0821 231 671 Georgia, Tbilisi: +995 32 2 050 778 Germany, Frankfurt: +49 (0) 69 2222 10612 Germany, Munich: +49 (0) 89 2030 31207 Germany (national): 01801 003 899 Germany (toll free): 0800 588 9170 Greece, Athens: +30 211 181 3824 Greece (toll free): 00800 128 913 Hong Kong: +852 3018 9111 Hong Kong (toll free): 800 901 787 Hungary, Budapest: +36 1408 8953 Hungary (toll free): 068 001 9673 Iceland (toll free): 800 9847 India, Delhi: +91 11 6310 0268 India, Mumbai: +91 22 6310 0298 India, Chennai: +91 44 6310 0234 India, Bangalore: +91 80 6760 8755 India (toll free): 1800 3010 1582 Indonesia, Jakarta: +62 21 2188 9084 Indonesia (toll free): 007 803 321 8927 Ireland, Dublin: +353 (0) 1 526 9421 Ireland (national): 0818 270 271 Ireland (toll free): 1800 937 649 Ireland (national): 1890 907 630 Israel, Tel Aviv: +972 (0)3 721 7943 Israel (toll free): 1809 213 168 Italy, Milan: +39 02 3600 8006 Italy, Rome: +39 06 8750 0676 Italy (toll free): 800 146 094 Japan, Tokyo: +81 3 4560 1270 Japan, Osaka: +81 6 4560 2410 Japan (toll free): 0120 305 211 Japan (mobile): 0120 632 611 Japan (national): 0570 085 744 Jordan (toll free): 0800 22172 Kazakhstan (toll free): 8800 333 7554 Kenya, Nairobi: +254 (0)207 643 581 South Korea, Seoul: +82 (0) 2 6007 0079 South Korea (toll free): 00798 6136 1454 Kuwait (national): +965 2206 3002 Latvia, Riga: +371 6601 3627 Latvia (toll free): 8000 4418 Lithuania, Vilnius: +370 5205 5468 Lithuania (toll free): 8800 31449 Luxembourg: +352 2088 1749 Luxembourg (toll free): 800 28433 Macau (national): +853 6262 1676 Malaysia, Kuala Lumpur: +60 (0) 3 7724 8010 Malaysia (toll free): 1 800 816 152 Mexico, Guadalajara: +52 33 4162 4504 Mexico, Mexico City: +52 55 8421 0326 Mexico, Monterrey: +52 81 4162 5648 Mexico (toll free): 01 800 733 4102 Morocco, Casablanca: +212 (0) 520 48 0022 Morocco (toll free): 0800 091 296 Netherlands, Amsterdam: +31 (0) 20 716 8345 Netherlands (toll free): 0800 020 2597 New Zealand, Christchurch: +64 (0) 3 974 2596 New Zealand, Wellington: +64 (0) 4 909 4674 New Zealand, Auckland: +64 (0) 9 929 1825 New Zealand (toll free): 0800 452 947 Nigeria, Lagos: +234 1 277 3944 Norway, Oslo: +47 21 00 48 15 Norway (toll free): 800 56081 Oman (toll free): 800 77265 Pakistan, Islamabad: +92 5181 08863 Panama, Panama City: +507 8 335 913 Panama (toll free): 00800 223 1390 Peru, Lima: +51 (0) 1 700 9571 Philippines, Manila: +63 (0)2 395 3426 Philippines (toll free): 1 800 111 013 99 Poland, Warsaw: +48 22 295 3570 Poland (toll free): 00 800 121 4356 Portugal, Lisbon: +351 21 316 4093 Portugal (toll free): 800 784 442 Qatar (freephone): 00 800 100 491 Romania, Bucharest: +40 (0) 21 529 3992 Romania (toll free): 0800 801 035 Russia, Moscow: +7 495 646 9181 Russia (toll free): 8 800 500 9241 Saudi Arabia (toll free): 800 844 6641 Saudi Arabia (toll free): 800 850 0219 Serbia (toll free): 0800 190 712 Singapore: +65 6654 9112 Singapore (toll free): 800 616 3192 Slovakia, Bratislava: +421 (0)2 3321 5498 Slovakia (toll free): 0800 002 002 Slovenia, Ljubljana: +386 1600 8695 Slovenia (toll free): 0800 81193 South Africa, Johannesburg: +27 (0)11 589 8321 South Africa (toll free): 0800 999 434 Spain, Madrid: +34 91 114 6653 Spain, Barcelona: +34 93 800 1946 Spain (toll free): 900 828 035 Sri Lanka, Sri Lanka: +94 720 910 333 Sweden, Stockholm: +46 (0) 8 5065 3956 Sweden (toll free): 0200 125 588 Switzerland, Geneva: +41 (0) 22 595 4795 Switzerland, Zurich: +41 (0) 44 580 7207 Switzerland (toll free): 0800 740 360 Taiwan, Taipei: +886 (0) 2 2650 7329 Taiwan (toll free): 0800 666 596 Thailand, Bangkok: +66 (0) 2104 0761 Thailand (toll free): 001 800 6136 1473 Tunisia, Tunis: +216 31 378 101 Turkey, Istanbul: +90 212 375 50 49 Turkey (toll free): 00800 4488 26642 Ukraine (toll free): 0800 500 896 UAE (toll free): 8000 3570 2662 UK (03): +44 (0)330 336 6002 UK (toll free): 0800 358 6385 UK (national): 0844 473 5010 UK (national): 0845 545 0015 USA /Canada (toll free): 1-866-398-2885 Uruguay (toll free): 0004 019 0152 Venezuela, Caracas: +58 212 720 2164 Venezuela (toll free): 0 800 162 7451 Vietnam, Hanoi: +84 24 4458 3312 Vietnam, Ho Chi Minh: +84 28 4458 1322 Vietnam (toll free): 1800 9226 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 11287 bytes Desc: not available URL: From maryam.bakoshi at icann.org Mon Feb 4 14:09:19 2019 From: maryam.bakoshi at icann.org (Maryam Bakoshi) Date: Mon, 4 Feb 2019 12:09:19 +0000 Subject: [NCSG-FC] NCSG Finance Committee Meeting on 06 February 2019 at 1400 UTC Message-ID: <4E335091-973B-4760-BBBF-167C132B122E@icann.org> Dear All, Please find participation details for the NCSG Finance Committee Meeting on 06 February 2019 at 1400 UTC Adobe Connect: https://participate.icann.org/ncsg Time Zones: https://tinyurl.com/yas66ghe Dial out request: please send an email to Maryam.bakoshi at icann.org off-list. Audio dial-in details below: [https://cobranding-pgi.s3.amazonaws.com/1/Logo1.png] You're invited. You've been invited to a GlobalMeet? audio meeting. Have the meeting call you. Click the Connect Me link below. No need to dial-in. Connect Me [go.conferencinghub.com] Not at your computer? You can join by dialing one of the access numbers below. Mobile: tel://16054755604,*,,9922790467# Phone Only Controls : https://go.conferencinghub.com/2xdh7 Access Number: 1-605-475-5604 Guest Passcode: 992 279 0467 Additional Access: USA: 1-605-475-5604 USA: 1-719-457-6209 Canada, Calgary: +1 403 407 5793 Canada, Montreal: +1 514 669 5928 Canada, Toronto: +1 647 426 9172 Canada, Vancouver: +1 604 222 7836 Argentina, Buenos Aires: +54 (0) 11 5172 6003 Argentina (toll free): 0800 800 1223 Australia, Sydney: +61 (0) 2 8017 6064 Australia, Melbourne: +61 (0) 3 8687 0553 Australia, Brisbane: +61 (0) 7 3015 0535 Australia (toll free): 1 800 804 786 Austria (toll free): 0800 070 981 Bahrain, Manama: +973 1619 8739 Bahrain (toll free): 800 04212 Belarus (toll free): 8 820 0011 0341 Belgium, Brussels: +32 (0) 2 400 6928 Belgium (toll free): 0800 39279 Bosnia and Herzegovina: +387 7031 1442 Brazil, Sao Paulo: +55 11 4935 7169 Brazil, Rio de Janeiro: +55 21 4560 0072 Brazil (toll free): 0800 887 0233 Bulgaria, Sofia: +359 (0) 2 491 6045 Bulgaria (toll free): 00800 111 4950 Cambodia, Phnom Penh: +855 23 965 723 Canada (toll free): 1 855 950 3717 Chile, Santiago: +56 (0) 2 2666 0696 Chile (toll free): 171 800 835 783 China (national): +400 613 8103 China, Beijing: +86 10 5667 0003 China, Shanghai: +86 21 2039 7081 Colombia, Bogota: +57 1 508 8137 Colombia (toll free): 01 800 755 0102 Costa Rica (toll free): 800 542 5328 Croatia (toll free): 0800 805 940 Cyprus (toll free): 800 97424 Czech Republic, Prague: +420 225 986 554 Czech Republic (toll free): 800 701 532 Denmark, Copenhagen: +45 32 72 78 10 Denmark (toll free): 80 70 35 86 Egypt (toll free): 0800 000 0593 Estonia, Tallinn: +372 622 6551 Estonia (toll free): 800 011 1589 Fiji (toll free): 00800 3322 Finland, Helsinki: +358 (0) 9 2310 1677 Finland (toll free): 0800 772 236 France, Paris: +33 (0) 1 70 37 16 56 France (toll free): 0800 946 531 France (national): 0811 655 100 France (national): 0821 231 671 Georgia, Tbilisi: +995 32 2 050 778 Germany, Frankfurt: +49 (0) 69 2222 10612 Germany, Munich: +49 (0) 89 2030 31207 Germany (national): 01801 003 899 Germany (toll free): 0800 588 9170 Greece, Athens: +30 211 181 3824 Greece (toll free): 00800 128 913 Hong Kong: +852 3018 9111 Hong Kong (toll free): 800 901 787 Hungary, Budapest: +36 1408 8953 Hungary (toll free): 068 001 9673 Iceland (toll free): 800 9847 India, Delhi: +91 11 6310 0268 India, Mumbai: +91 22 6310 0298 India, Chennai: +91 44 6310 0234 India, Bangalore: +91 80 6760 8755 India (toll free): 1800 3010 1582 Indonesia, Jakarta: +62 21 2188 9084 Indonesia (toll free): 007 803 321 8927 Ireland, Dublin: +353 (0) 1 526 9421 Ireland (national): 0818 270 271 Ireland (toll free): 1800 937 649 Ireland (national): 1890 907 630 Israel, Tel Aviv: +972 (0)3 721 7943 Israel (toll free): 1809 213 168 Italy, Milan: +39 02 3600 8006 Italy, Rome: +39 06 8750 0676 Italy (toll free): 800 146 094 Japan, Tokyo: +81 3 4560 1270 Japan, Osaka: +81 6 4560 2410 Japan (toll free): 0120 305 211 Japan (mobile): 0120 632 611 Japan (national): 0570 085 744 Jordan (toll free): 0800 22172 Kazakhstan (toll free): 8800 333 7554 Kenya, Nairobi: +254 (0)207 643 581 South Korea, Seoul: +82 (0) 2 6007 0079 South Korea (toll free): 00798 6136 1454 Kuwait (national): +965 2206 3002 Latvia, Riga: +371 6601 3627 Latvia (toll free): 8000 4418 Lithuania, Vilnius: +370 5205 5468 Lithuania (toll free): 8800 31449 Luxembourg: +352 2088 1749 Luxembourg (toll free): 800 28433 Macau (national): +853 6262 1676 Malaysia, Kuala Lumpur: +60 (0) 3 7724 8010 Malaysia (toll free): 1 800 816 152 Mexico, Guadalajara: +52 33 4162 4504 Mexico, Mexico City: +52 55 8421 0326 Mexico, Monterrey: +52 81 4162 5648 Mexico (toll free): 01 800 733 4102 Morocco, Casablanca: +212 (0) 520 48 0022 Morocco (toll free): 0800 091 296 Netherlands, Amsterdam: +31 (0) 20 716 8345 Netherlands (toll free): 0800 020 2597 New Zealand, Christchurch: +64 (0) 3 974 2596 New Zealand, Wellington: +64 (0) 4 909 4674 New Zealand, Auckland: +64 (0) 9 929 1825 New Zealand (toll free): 0800 452 947 Nigeria, Lagos: +234 1 277 3944 Norway, Oslo: +47 21 00 48 15 Norway (toll free): 800 56081 Oman (toll free): 800 77265 Pakistan, Islamabad: +92 5181 08863 Panama, Panama City: +507 8 335 913 Panama (toll free): 00800 223 1390 Peru, Lima: +51 (0) 1 700 9571 Philippines, Manila: +63 (0)2 395 3426 Philippines (toll free): 1 800 111 013 99 Poland, Warsaw: +48 22 295 3570 Poland (toll free): 00 800 121 4356 Portugal, Lisbon: +351 21 316 4093 Portugal (toll free): 800 784 442 Qatar (freephone): 00 800 100 491 Romania, Bucharest: +40 (0) 21 529 3992 Romania (toll free): 0800 801 035 Russia, Moscow: +7 495 646 9181 Russia (toll free): 8 800 500 9241 Saudi Arabia (toll free): 800 844 6641 Saudi Arabia (toll free): 800 850 0219 Serbia (toll free): 0800 190 712 Singapore: +65 6654 9112 Singapore (toll free): 800 616 3192 Slovakia, Bratislava: +421 (0)2 3321 5498 Slovakia (toll free): 0800 002 002 Slovenia, Ljubljana: +386 1600 8695 Slovenia (toll free): 0800 81193 South Africa, Johannesburg: +27 (0)11 589 8321 South Africa (toll free): 0800 999 434 Spain, Madrid: +34 91 114 6653 Spain, Barcelona: +34 93 800 1946 Spain (toll free): 900 828 035 Sri Lanka, Sri Lanka: +94 720 910 333 Sweden, Stockholm: +46 (0) 8 5065 3956 Sweden (toll free): 0200 125 588 Switzerland, Geneva: +41 (0) 22 595 4795 Switzerland, Zurich: +41 (0) 44 580 7207 Switzerland (toll free): 0800 740 360 Taiwan, Taipei: +886 (0) 2 2650 7329 Taiwan (toll free): 0800 666 596 Thailand, Bangkok: +66 (0) 2104 0761 Thailand (toll free): 001 800 6136 1473 Tunisia, Tunis: +216 31 378 101 Turkey, Istanbul: +90 212 375 50 49 Turkey (toll free): 00800 4488 26642 Ukraine (toll free): 0800 500 896 UAE (toll free): 8000 3570 2662 UK (03): +44 (0)330 336 6002 UK (toll free): 0800 358 6385 UK (national): 0844 473 5010 UK (national): 0845 545 0015 USA /Canada (toll free): 1-866-398-2885 Uruguay (toll free): 0004 019 0152 Venezuela, Caracas: +58 212 720 2164 Venezuela (toll free): 0 800 162 7451 Vietnam, Hanoi: +84 24 4458 3312 Vietnam, Ho Chi Minh: +84 28 4458 1322 Vietnam (toll free): 1800 9226 -- Many thanks, Maryam Bakoshi | SO/AC Collaboration Services Sr. Coordinator ICANN | Internet Corporation got Assigned Names and Numbers S: Maryam.bakoshi.icann | T: +44 7846 471777 -------------- next part -------------- An HTML attachment was scrubbed... URL: From thatomfikwe at gmail.com Mon Feb 4 16:15:12 2019 From: thatomfikwe at gmail.com (Thato Mfikwe) Date: Mon, 4 Feb 2019 16:15:12 +0200 Subject: [NCSG-FC] NCSG Finance Committee Meeting on 06 February 2019 at 1400 UTC In-Reply-To: <4E335091-973B-4760-BBBF-167C132B122E@icann.org> References: <4E335091-973B-4760-BBBF-167C132B122E@icann.org> Message-ID: Hi Maryam, Can you reschedule the meeting for Friday anytime because on Wednesday around 13h00 UTC, I will be in a meeting, thanks. Thato Mfikwe. On Mon, Feb 4, 2019 at 2:09 PM Maryam Bakoshi wrote: > Dear All, > > > > Please find participation details for the *NCSG Finance Committee Meeting > on 06 February 2019 at 1400 UTC* > > > > *Adobe Connect*: https://participate.icann.org/ncsg > > > > *Time Zones*: https://tinyurl.com/yas66ghe > > > > *Dial out request*: please send an email to Maryam.bakoshi at icann.org > off-list. > > > > *Audio dial-in details below:* > > [image: https://cobranding-pgi.s3.amazonaws.com/1/Logo1.png] > > *You're invited.* > You've been invited to a GlobalMeet? audio meeting. > > *Have the meeting call you.* > Click the Connect Me link below. *No need to dial-in.* > > > > *Connect Me [go.conferencinghub.com] > * > > > > *Not at your computer?* > You can join by dialing one of the access numbers below. > > > > *Mobile:* > > tel://16054755604,*,,9922790467# > > *Phone Only Controls :* > > https://go.conferencinghub.com/2xdh7 > > *Access Number:* > > 1-605-475-5604 > > *Guest Passcode:* > > 992 279 0467 > > *Additional Access:* > > USA: > > 1-605-475-5604 > > USA: > > 1-719-457-6209 > > Canada, Calgary: > > +1 403 407 5793 > > Canada, Montreal: > > +1 514 669 5928 > > Canada, Toronto: > > +1 647 426 9172 > > Canada, Vancouver: > > +1 604 222 7836 > > Argentina, Buenos Aires: > > +54 (0) 11 5172 6003 > > Argentina (toll free): > > 0800 800 1223 > > Australia, Sydney: > > +61 (0) 2 8017 6064 > > Australia, Melbourne: > > +61 (0) 3 8687 0553 > > Australia, Brisbane: > > +61 (0) 7 3015 0535 > > Australia (toll free): > > 1 800 804 786 > > Austria (toll free): > > 0800 070 981 > > Bahrain, Manama: > > +973 1619 8739 > > Bahrain (toll free): > > 800 04212 > > Belarus (toll free): > > 8 820 0011 0341 > > Belgium, Brussels: > > +32 (0) 2 400 6928 > > Belgium (toll free): > > 0800 39279 > > Bosnia and Herzegovina: > > +387 7031 1442 > > Brazil, Sao Paulo: > > +55 11 4935 7169 > > Brazil, Rio de Janeiro: > > +55 21 4560 0072 > > Brazil (toll free): > > 0800 887 0233 > > Bulgaria, Sofia: > > +359 (0) 2 491 6045 > > Bulgaria (toll free): > > 00800 111 4950 > > Cambodia, Phnom Penh: > > +855 23 965 723 > > Canada (toll free): > > 1 855 950 3717 > > Chile, Santiago: > > +56 (0) 2 2666 0696 > > Chile (toll free): > > 171 800 835 783 > > China (national): > > +400 613 8103 > > China, Beijing: > > +86 10 5667 0003 > > China, Shanghai: > > +86 21 2039 7081 > > Colombia, Bogota: > > +57 1 508 8137 > > Colombia (toll free): > > 01 800 755 0102 > > Costa Rica (toll free): > > 800 542 5328 > > Croatia (toll free): > > 0800 805 940 > > Cyprus (toll free): > > 800 97424 > > Czech Republic, Prague: > > +420 225 986 554 > > Czech Republic (toll free): > > 800 701 532 > > Denmark, Copenhagen: > > +45 32 72 78 10 > > Denmark (toll free): > > 80 70 35 86 > > Egypt (toll free): > > 0800 000 0593 > > Estonia, Tallinn: > > +372 622 6551 > > Estonia (toll free): > > 800 011 1589 > > Fiji (toll free): > > 00800 3322 > > Finland, Helsinki: > > +358 (0) 9 2310 1677 > > Finland (toll free): > > 0800 772 236 > > France, Paris: > > +33 (0) 1 70 37 16 56 > > France (toll free): > > 0800 946 531 > > France (national): > > 0811 655 100 > > France (national): > > 0821 231 671 > > Georgia, Tbilisi: > > +995 32 2 050 778 > > Germany, Frankfurt: > > +49 (0) 69 2222 10612 > > Germany, Munich: > > +49 (0) 89 2030 31207 > > Germany (national): > > 01801 003 899 > > Germany (toll free): > > 0800 588 9170 > > Greece, Athens: > > +30 211 181 3824 > > Greece (toll free): > > 00800 128 913 > > Hong Kong: > > +852 3018 9111 > > Hong Kong (toll free): > > 800 901 787 > > Hungary, Budapest: > > +36 1408 8953 > > Hungary (toll free): > > 068 001 9673 > > Iceland (toll free): > > 800 9847 > > India, Delhi: > > +91 11 6310 0268 > > India, Mumbai: > > +91 22 6310 0298 > > India, Chennai: > > +91 44 6310 0234 > > India, Bangalore: > > +91 80 6760 8755 > > India (toll free): > > 1800 3010 1582 > > Indonesia, Jakarta: > > +62 21 2188 9084 > > Indonesia (toll free): > > 007 803 321 8927 > > Ireland, Dublin: > > +353 (0) 1 526 9421 > > Ireland (national): > > 0818 270 271 > > Ireland (toll free): > > 1800 937 649 > > Ireland (national): > > 1890 907 630 > > Israel, Tel Aviv: > > +972 (0)3 721 7943 > > Israel (toll free): > > 1809 213 168 > > Italy, Milan: > > +39 02 3600 8006 > > Italy, Rome: > > +39 06 8750 0676 > > Italy (toll free): > > 800 146 094 > > Japan, Tokyo: > > +81 3 4560 1270 > > Japan, Osaka: > > +81 6 4560 2410 > > Japan (toll free): > > 0120 305 211 > > Japan (mobile): > > 0120 632 611 > > Japan (national): > > 0570 085 744 > > Jordan (toll free): > > 0800 22172 > > Kazakhstan (toll free): > > 8800 333 7554 > > Kenya, Nairobi: > > +254 (0)207 643 581 > > South Korea, Seoul: > > +82 (0) 2 6007 0079 > > South Korea (toll free): > > 00798 6136 1454 > > Kuwait (national): > > +965 2206 3002 > > Latvia, Riga: > > +371 6601 3627 > > Latvia (toll free): > > 8000 4418 > > Lithuania, Vilnius: > > +370 5205 5468 > > Lithuania (toll free): > > 8800 31449 > > Luxembourg: > > +352 2088 1749 > > Luxembourg (toll free): > > 800 28433 > > Macau (national): > > +853 6262 1676 > > Malaysia, Kuala Lumpur: > > +60 (0) 3 7724 8010 > > Malaysia (toll free): > > 1 800 816 152 > > Mexico, Guadalajara: > > +52 33 4162 4504 > > Mexico, Mexico City: > > +52 55 8421 0326 > > Mexico, Monterrey: > > +52 81 4162 5648 > > Mexico (toll free): > > 01 800 733 4102 > > Morocco, Casablanca: > > +212 (0) 520 48 0022 > > Morocco (toll free): > > 0800 091 296 > > Netherlands, Amsterdam: > > +31 (0) 20 716 8345 > > Netherlands (toll free): > > 0800 020 2597 > > New Zealand, Christchurch: > > +64 (0) 3 974 2596 > > New Zealand, Wellington: > > +64 (0) 4 909 4674 > > New Zealand, Auckland: > > +64 (0) 9 929 1825 > > New Zealand (toll free): > > 0800 452 947 > > Nigeria, Lagos: > > +234 1 277 3944 > > Norway, Oslo: > > +47 21 00 48 15 > > Norway (toll free): > > 800 56081 > > Oman (toll free): > > 800 77265 > > Pakistan, Islamabad: > > +92 5181 08863 > > Panama, Panama City: > > +507 8 335 913 > > Panama (toll free): > > 00800 223 1390 > > Peru, Lima: > > +51 (0) 1 700 9571 > > Philippines, Manila: > > +63 (0)2 395 3426 > > Philippines (toll free): > > 1 800 111 013 99 > > Poland, Warsaw: > > +48 22 295 3570 > > Poland (toll free): > > 00 800 121 4356 > > Portugal, Lisbon: > > +351 21 316 4093 > > Portugal (toll free): > > 800 784 442 > > Qatar (freephone): > > 00 800 100 491 > > Romania, Bucharest: > > +40 (0) 21 529 3992 > > Romania (toll free): > > 0800 801 035 > > Russia, Moscow: > > +7 495 646 9181 > > Russia (toll free): > > 8 800 500 9241 > > Saudi Arabia (toll free): > > 800 844 6641 > > Saudi Arabia (toll free): > > 800 850 0219 > > Serbia (toll free): > > 0800 190 712 > > Singapore: > > +65 6654 9112 > > Singapore (toll free): > > 800 616 3192 > > Slovakia, Bratislava: > > +421 (0)2 3321 5498 > > Slovakia (toll free): > > 0800 002 002 > > Slovenia, Ljubljana: > > +386 1600 8695 > > Slovenia (toll free): > > 0800 81193 > > South Africa, Johannesburg: > > +27 (0)11 589 8321 > > South Africa (toll free): > > 0800 999 434 > > Spain, Madrid: > > +34 91 114 6653 > > Spain, Barcelona: > > +34 93 800 1946 > > Spain (toll free): > > 900 828 035 > > Sri Lanka, Sri Lanka: > > +94 720 910 333 > > Sweden, Stockholm: > > +46 (0) 8 5065 3956 > > Sweden (toll free): > > 0200 125 588 > > Switzerland, Geneva: > > +41 (0) 22 595 4795 > > Switzerland, Zurich: > > +41 (0) 44 580 7207 > > Switzerland (toll free): > > 0800 740 360 > > Taiwan, Taipei: > > +886 (0) 2 2650 7329 > > Taiwan (toll free): > > 0800 666 596 > > Thailand, Bangkok: > > +66 (0) 2104 0761 > > Thailand (toll free): > > 001 800 6136 1473 > > Tunisia, Tunis: > > +216 31 378 101 > > Turkey, Istanbul: > > +90 212 375 50 49 > > Turkey (toll free): > > 00800 4488 26642 > > Ukraine (toll free): > > 0800 500 896 > > UAE (toll free): > > 8000 3570 2662 > > UK (03): > > +44 (0)330 336 6002 > > UK (toll free): > > 0800 358 6385 > > UK (national): > > 0844 473 5010 > > UK (national): > > 0845 545 0015 > > USA /Canada (toll free): > > 1-866-398-2885 > > Uruguay (toll free): > > 0004 019 0152 > > Venezuela, Caracas: > > +58 212 720 2164 > > Venezuela (toll free): > > 0 800 162 7451 > > Vietnam, Hanoi: > > +84 24 4458 3312 > > Vietnam, Ho Chi Minh: > > +84 28 4458 1322 > > Vietnam (toll free): > > 1800 9226 > > > > > > > > > > > > > > > > > > > > -- > > Many thanks, > > > > *Maryam Bakoshi* | SO/AC Collaboration Services Sr. Coordinator > > *ICANN* | Internet Corporation got Assigned Names and Numbers > > *S*: Maryam.bakoshi.icann | *T*: +44 7846 471777 > > > _______________________________________________ > NCSG-FC mailing list > NCSG-FC at lists.ncsg.is > https://lists.ncsg.is/mailman/listinfo/ncsg-fc > -------------- next part -------------- An HTML attachment was scrubbed... URL: From PolicyCalendar at icann.org Mon Feb 4 19:51:24 2019 From: PolicyCalendar at icann.org (ICANN Policy Calendar) Date: Mon, 4 Feb 2019 17:51:24 +0000 Subject: [NCSG-FC] NCSG Finance Committee Meeting on Friday 08 February 2019 at 1400 UTC Message-ID: <1972cb9fb2bd4714ab3bb2b531af9cc5@PMBX112-W1-CA-1.PEXCH112.ICANN.ORG> Dear All, Please find participation details for the NCSG Finance Committee Meeting on Friday 08 February 2019 at 1400 UTC Adobe Connect: https://participate.icann.org/ncsg Time Zones: https://tinyurl.com/yce94nnc Dial out request: please send an email to Maryam.bakoshi at icann.org off-list. Audio dial-in details below: [https://cobranding-pgi.s3.amazonaws.com/1/Logo1.png] You're invited. You've been invited to a GlobalMeet? audio meeting. Have the meeting call you. Click the Connect Me link below. No need to dial-in. Connect Me [go.conferencinghub.com] Not at your computer? You can join by dialing one of the access numbers below. Mobile: tel://16054755604,*,,9922790467# Phone Only Controls : https://go.conferencinghub.com/2xdh7 Access Number: 1-605-475-5604 Guest Passcode: 992 279 0467 Additional Access: USA: 1-605-475-5604 USA: 1-719-457-6209 Canada, Calgary: +1 403 407 5793 Canada, Montreal: +1 514 669 5928 Canada, Toronto: +1 647 426 9172 Canada, Vancouver: +1 604 222 7836 Argentina, Buenos Aires: +54 (0) 11 5172 6003 Argentina (toll free): 0800 800 1223 Australia, Sydney: +61 (0) 2 8017 6064 Australia, Melbourne: +61 (0) 3 8687 0553 Australia, Brisbane: +61 (0) 7 3015 0535 Australia (toll free): 1 800 804 786 Austria (toll free): 0800 070 981 Bahrain, Manama: +973 1619 8739 Bahrain (toll free): 800 04212 Belarus (toll free): 8 820 0011 0341 Belgium, Brussels: +32 (0) 2 400 6928 Belgium (toll free): 0800 39279 Bosnia and Herzegovina: +387 7031 1442 Brazil, Sao Paulo: +55 11 4935 7169 Brazil, Rio de Janeiro: +55 21 4560 0072 Brazil (toll free): 0800 887 0233 Bulgaria, Sofia: +359 (0) 2 491 6045 Bulgaria (toll free): 00800 111 4950 Cambodia, Phnom Penh: +855 23 965 723 Canada (toll free): 1 855 950 3717 Chile, Santiago: +56 (0) 2 2666 0696 Chile (toll free): 171 800 835 783 China (national): +400 613 8103 China, Beijing: +86 10 5667 0003 China, Shanghai: +86 21 2039 7081 Colombia, Bogota: +57 1 508 8137 Colombia (toll free): 01 800 755 0102 Costa Rica (toll free): 800 542 5328 Croatia (toll free): 0800 805 940 Cyprus (toll free): 800 97424 Czech Republic, Prague: +420 225 986 554 Czech Republic (toll free): 800 701 532 Denmark, Copenhagen: +45 32 72 78 10 Denmark (toll free): 80 70 35 86 Egypt (toll free): 0800 000 0593 Estonia, Tallinn: +372 622 6551 Estonia (toll free): 800 011 1589 Fiji (toll free): 00800 3322 Finland, Helsinki: +358 (0) 9 2310 1677 Finland (toll free): 0800 772 236 France, Paris: +33 (0) 1 70 37 16 56 France (toll free): 0800 946 531 France (national): 0811 655 100 France (national): 0821 231 671 Georgia, Tbilisi: +995 32 2 050 778 Germany, Frankfurt: +49 (0) 69 2222 10612 Germany, Munich: +49 (0) 89 2030 31207 Germany (national): 01801 003 899 Germany (toll free): 0800 588 9170 Greece, Athens: +30 211 181 3824 Greece (toll free): 00800 128 913 Hong Kong: +852 3018 9111 Hong Kong (toll free): 800 901 787 Hungary, Budapest: +36 1408 8953 Hungary (toll free): 068 001 9673 Iceland (toll free): 800 9847 India, Delhi: +91 11 6310 0268 India, Mumbai: +91 22 6310 0298 India, Chennai: +91 44 6310 0234 India, Bangalore: +91 80 6760 8755 India (toll free): 1800 3010 1582 Indonesia, Jakarta: +62 21 2188 9084 Indonesia (toll free): 007 803 321 8927 Ireland, Dublin: +353 (0) 1 526 9421 Ireland (national): 0818 270 271 Ireland (toll free): 1800 937 649 Ireland (national): 1890 907 630 Israel, Tel Aviv: +972 (0)3 721 7943 Israel (toll free): 1809 213 168 Italy, Milan: +39 02 3600 8006 Italy, Rome: +39 06 8750 0676 Italy (toll free): 800 146 094 Japan, Tokyo: +81 3 4560 1270 Japan, Osaka: +81 6 4560 2410 Japan (toll free): 0120 305 211 Japan (mobile): 0120 632 611 Japan (national): 0570 085 744 Jordan (toll free): 0800 22172 Kazakhstan (toll free): 8800 333 7554 Kenya, Nairobi: +254 (0)207 643 581 South Korea, Seoul: +82 (0) 2 6007 0079 South Korea (toll free): 00798 6136 1454 Kuwait (national): +965 2206 3002 Latvia, Riga: +371 6601 3627 Latvia (toll free): 8000 4418 Lithuania, Vilnius: +370 5205 5468 Lithuania (toll free): 8800 31449 Luxembourg: +352 2088 1749 Luxembourg (toll free): 800 28433 Macau (national): +853 6262 1676 Malaysia, Kuala Lumpur: +60 (0) 3 7724 8010 Malaysia (toll free): 1 800 816 152 Mexico, Guadalajara: +52 33 4162 4504 Mexico, Mexico City: +52 55 8421 0326 Mexico, Monterrey: +52 81 4162 5648 Mexico (toll free): 01 800 733 4102 Morocco, Casablanca: +212 (0) 520 48 0022 Morocco (toll free): 0800 091 296 Netherlands, Amsterdam: +31 (0) 20 716 8345 Netherlands (toll free): 0800 020 2597 New Zealand, Christchurch: +64 (0) 3 974 2596 New Zealand, Wellington: +64 (0) 4 909 4674 New Zealand, Auckland: +64 (0) 9 929 1825 New Zealand (toll free): 0800 452 947 Nigeria, Lagos: +234 1 277 3944 Norway, Oslo: +47 21 00 48 15 Norway (toll free): 800 56081 Oman (toll free): 800 77265 Pakistan, Islamabad: +92 5181 08863 Panama, Panama City: +507 8 335 913 Panama (toll free): 00800 223 1390 Peru, Lima: +51 (0) 1 700 9571 Philippines, Manila: +63 (0)2 395 3426 Philippines (toll free): 1 800 111 013 99 Poland, Warsaw: +48 22 295 3570 Poland (toll free): 00 800 121 4356 Portugal, Lisbon: +351 21 316 4093 Portugal (toll free): 800 784 442 Qatar (freephone): 00 800 100 491 Romania, Bucharest: +40 (0) 21 529 3992 Romania (toll free): 0800 801 035 Russia, Moscow: +7 495 646 9181 Russia (toll free): 8 800 500 9241 Saudi Arabia (toll free): 800 844 6641 Saudi Arabia (toll free): 800 850 0219 Serbia (toll free): 0800 190 712 Singapore: +65 6654 9112 Singapore (toll free): 800 616 3192 Slovakia, Bratislava: +421 (0)2 3321 5498 Slovakia (toll free): 0800 002 002 Slovenia, Ljubljana: +386 1600 8695 Slovenia (toll free): 0800 81193 South Africa, Johannesburg: +27 (0)11 589 8321 South Africa (toll free): 0800 999 434 Spain, Madrid: +34 91 114 6653 Spain, Barcelona: +34 93 800 1946 Spain (toll free): 900 828 035 Sri Lanka, Sri Lanka: +94 720 910 333 Sweden, Stockholm: +46 (0) 8 5065 3956 Sweden (toll free): 0200 125 588 Switzerland, Geneva: +41 (0) 22 595 4795 Switzerland, Zurich: +41 (0) 44 580 7207 Switzerland (toll free): 0800 740 360 Taiwan, Taipei: +886 (0) 2 2650 7329 Taiwan (toll free): 0800 666 596 Thailand, Bangkok: +66 (0) 2104 0761 Thailand (toll free): 001 800 6136 1473 Tunisia, Tunis: +216 31 378 101 Turkey, Istanbul: +90 212 375 50 49 Turkey (toll free): 00800 4488 26642 Ukraine (toll free): 0800 500 896 UAE (toll free): 8000 3570 2662 UK (03): +44 (0)330 336 6002 UK (toll free): 0800 358 6385 UK (national): 0844 473 5010 UK (national): 0845 545 0015 USA /Canada (toll free): 1-866-398-2885 Uruguay (toll free): 0004 019 0152 Venezuela, Caracas: +58 212 720 2164 Venezuela (toll free): 0 800 162 7451 Vietnam, Hanoi: +84 24 4458 3312 Vietnam, Ho Chi Minh: +84 28 4458 1322 Vietnam (toll free): 1800 9226 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 11417 bytes Desc: not available URL: From rbeauregardlacroix at gmail.com Tue Feb 5 02:24:42 2019 From: rbeauregardlacroix at gmail.com (=?UTF-8?Q?Rapha=C3=ABl_Beauregard=2DLacroix?=) Date: Mon, 4 Feb 2019 19:24:42 -0500 Subject: [NCSG-FC] NCSG Finance Committee Meeting on Friday 08 February 2019 at 1400 UTC In-Reply-To: <1972cb9fb2bd4714ab3bb2b531af9cc5@PMBX112-W1-CA-1.PEXCH112.ICANN.ORG> References: <1972cb9fb2bd4714ab3bb2b531af9cc5@PMBX112-W1-CA-1.PEXCH112.ICANN.ORG> Message-ID: Hi all I am not available in those ET morning time slots, except certain Mondays and Tuesdays. Hence, I apologise for my absence. I will send a short update re our database management service provider as a separate email. Best, On Mon, Feb 4, 2019 at 12:51 PM ICANN Policy Calendar < PolicyCalendar at icann.org> wrote: > Dear All, > > > Please find participation details for the *NCSG Finance Committee Meeting > on Friday 08 February 2019 at 1400 UTC* > > > *Adobe Connect*: https://participate.icann.org/ncsg > > > *Time Zones*: https://tinyurl.com/yce94nnc > > > *Dial out request*: please send an email to Maryam.bakoshi at icann.org > off-list. > > > *Audio dial-in details below:* > > [image: https://cobranding-pgi.s3.amazonaws.com/1/Logo1.png] > > *You're invited.* > You've been invited to a GlobalMeet? audio meeting. > > *Have the meeting call you.* > Click the Connect Me link below. *No need to dial-in.* > > > *Connect Me [go.conferencinghub.com] > * > > > *Not at your computer?* > You can join by dialing one of the access numbers below. > > > *Mobile:* > > tel://16054755604,*,,9922790467# > > *Phone Only Controls :* > > https://go.conferencinghub.com/2xdh7 > > *Access Number:* > > 1-605-475-5604 > > *Guest Passcode:* > > 992 279 0467 > > *Additional Access:* > > USA: > > 1-605-475-5604 > > USA: > > 1-719-457-6209 > > Canada, Calgary: > > +1 403 407 5793 > > Canada, Montreal: > > +1 514 669 5928 > > Canada, Toronto: > > +1 647 426 9172 > > Canada, Vancouver: > > +1 604 222 7836 > > Argentina, Buenos Aires: > > +54 (0) 11 5172 6003 > > Argentina (toll free): > > 0800 800 1223 > > Australia, Sydney: > > +61 (0) 2 8017 6064 > > Australia, Melbourne: > > +61 (0) 3 8687 0553 > > Australia, Brisbane: > > +61 (0) 7 3015 0535 > > Australia (toll free): > > 1 800 804 786 > > Austria (toll free): > > 0800 070 981 > > Bahrain, Manama: > > +973 1619 8739 > > Bahrain (toll free): > > 800 04212 > > Belarus (toll free): > > 8 820 0011 0341 > > Belgium, Brussels: > > +32 (0) 2 400 6928 > > Belgium (toll free): > > 0800 39279 > > Bosnia and Herzegovina: > > +387 7031 1442 > > Brazil, Sao Paulo: > > +55 11 4935 7169 > > Brazil, Rio de Janeiro: > > +55 21 4560 0072 > > Brazil (toll free): > > 0800 887 0233 > > Bulgaria, Sofia: > > +359 (0) 2 491 6045 > > Bulgaria (toll free): > > 00800 111 4950 > > Cambodia, Phnom Penh: > > +855 23 965 723 > > Canada (toll free): > > 1 855 950 3717 > > Chile, Santiago: > > +56 (0) 2 2666 0696 > > Chile (toll free): > > 171 800 835 783 > > China (national): > > +400 613 8103 > > China, Beijing: > > +86 10 5667 0003 > > China, Shanghai: > > +86 21 2039 7081 > > Colombia, Bogota: > > +57 1 508 8137 > > Colombia (toll free): > > 01 800 755 0102 > > Costa Rica (toll free): > > 800 542 5328 > > Croatia (toll free): > > 0800 805 940 > > Cyprus (toll free): > > 800 97424 > > Czech Republic, Prague: > > +420 225 986 554 > > Czech Republic (toll free): > > 800 701 532 > > Denmark, Copenhagen: > > +45 32 72 78 10 > > Denmark (toll free): > > 80 70 35 86 > > Egypt (toll free): > > 0800 000 0593 > > Estonia, Tallinn: > > +372 622 6551 > > Estonia (toll free): > > 800 011 1589 > > Fiji (toll free): > > 00800 3322 > > Finland, Helsinki: > > +358 (0) 9 2310 1677 > > Finland (toll free): > > 0800 772 236 > > France, Paris: > > +33 (0) 1 70 37 16 56 > > France (toll free): > > 0800 946 531 > > France (national): > > 0811 655 100 > > France (national): > > 0821 231 671 > > Georgia, Tbilisi: > > +995 32 2 050 778 > > Germany, Frankfurt: > > +49 (0) 69 2222 10612 > > Germany, Munich: > > +49 (0) 89 2030 31207 > > Germany (national): > > 01801 003 899 > > Germany (toll free): > > 0800 588 9170 > > Greece, Athens: > > +30 211 181 3824 > > Greece (toll free): > > 00800 128 913 > > Hong Kong: > > +852 3018 9111 > > Hong Kong (toll free): > > 800 901 787 > > Hungary, Budapest: > > +36 1408 8953 > > Hungary (toll free): > > 068 001 9673 > > Iceland (toll free): > > 800 9847 > > India, Delhi: > > +91 11 6310 0268 > > India, Mumbai: > > +91 22 6310 0298 > > India, Chennai: > > +91 44 6310 0234 > > India, Bangalore: > > +91 80 6760 8755 > > India (toll free): > > 1800 3010 1582 > > Indonesia, Jakarta: > > +62 21 2188 9084 > > Indonesia (toll free): > > 007 803 321 8927 > > Ireland, Dublin: > > +353 (0) 1 526 9421 > > Ireland (national): > > 0818 270 271 > > Ireland (toll free): > > 1800 937 649 > > Ireland (national): > > 1890 907 630 > > Israel, Tel Aviv: > > +972 (0)3 721 7943 > > Israel (toll free): > > 1809 213 168 > > Italy, Milan: > > +39 02 3600 8006 > > Italy, Rome: > > +39 06 8750 0676 > > Italy (toll free): > > 800 146 094 > > Japan, Tokyo: > > +81 3 4560 1270 > > Japan, Osaka: > > +81 6 4560 2410 > > Japan (toll free): > > 0120 305 211 > > Japan (mobile): > > 0120 632 611 > > Japan (national): > > 0570 085 744 > > Jordan (toll free): > > 0800 22172 > > Kazakhstan (toll free): > > 8800 333 7554 > > Kenya, Nairobi: > > +254 (0)207 643 581 > > South Korea, Seoul: > > +82 (0) 2 6007 0079 > > South Korea (toll free): > > 00798 6136 1454 > > Kuwait (national): > > +965 2206 3002 > > Latvia, Riga: > > +371 6601 3627 > > Latvia (toll free): > > 8000 4418 > > Lithuania, Vilnius: > > +370 5205 5468 > > Lithuania (toll free): > > 8800 31449 > > Luxembourg: > > +352 2088 1749 > > Luxembourg (toll free): > > 800 28433 > > Macau (national): > > +853 6262 1676 > > Malaysia, Kuala Lumpur: > > +60 (0) 3 7724 8010 > > Malaysia (toll free): > > 1 800 816 152 > > Mexico, Guadalajara: > > +52 33 4162 4504 > > Mexico, Mexico City: > > +52 55 8421 0326 > > Mexico, Monterrey: > > +52 81 4162 5648 > > Mexico (toll free): > > 01 800 733 4102 > > Morocco, Casablanca: > > +212 (0) 520 48 0022 > > Morocco (toll free): > > 0800 091 296 > > Netherlands, Amsterdam: > > +31 (0) 20 716 8345 > > Netherlands (toll free): > > 0800 020 2597 > > New Zealand, Christchurch: > > +64 (0) 3 974 2596 > > New Zealand, Wellington: > > +64 (0) 4 909 4674 > > New Zealand, Auckland: > > +64 (0) 9 929 1825 > > New Zealand (toll free): > > 0800 452 947 > > Nigeria, Lagos: > > +234 1 277 3944 > > Norway, Oslo: > > +47 21 00 48 15 > > Norway (toll free): > > 800 56081 > > Oman (toll free): > > 800 77265 > > Pakistan, Islamabad: > > +92 5181 08863 > > Panama, Panama City: > > +507 8 335 913 > > Panama (toll free): > > 00800 223 1390 > > Peru, Lima: > > +51 (0) 1 700 9571 > > Philippines, Manila: > > +63 (0)2 395 3426 > > Philippines (toll free): > > 1 800 111 013 99 > > Poland, Warsaw: > > +48 22 295 3570 > > Poland (toll free): > > 00 800 121 4356 > > Portugal, Lisbon: > > +351 21 316 4093 > > Portugal (toll free): > > 800 784 442 > > Qatar (freephone): > > 00 800 100 491 > > Romania, Bucharest: > > +40 (0) 21 529 3992 > > Romania (toll free): > > 0800 801 035 > > Russia, Moscow: > > +7 495 646 9181 > > Russia (toll free): > > 8 800 500 9241 > > Saudi Arabia (toll free): > > 800 844 6641 > > Saudi Arabia (toll free): > > 800 850 0219 > > Serbia (toll free): > > 0800 190 712 > > Singapore: > > +65 6654 9112 > > Singapore (toll free): > > 800 616 3192 > > Slovakia, Bratislava: > > +421 (0)2 3321 5498 > > Slovakia (toll free): > > 0800 002 002 > > Slovenia, Ljubljana: > > +386 1600 8695 > > Slovenia (toll free): > > 0800 81193 > > South Africa, Johannesburg: > > +27 (0)11 589 8321 > > South Africa (toll free): > > 0800 999 434 > > Spain, Madrid: > > +34 91 114 6653 > > Spain, Barcelona: > > +34 93 800 1946 > > Spain (toll free): > > 900 828 035 > > Sri Lanka, Sri Lanka: > > +94 720 910 333 > > Sweden, Stockholm: > > +46 (0) 8 5065 3956 > > Sweden (toll free): > > 0200 125 588 > > Switzerland, Geneva: > > +41 (0) 22 595 4795 > > Switzerland, Zurich: > > +41 (0) 44 580 7207 > > Switzerland (toll free): > > 0800 740 360 > > Taiwan, Taipei: > > +886 (0) 2 2650 7329 > > Taiwan (toll free): > > 0800 666 596 > > Thailand, Bangkok: > > +66 (0) 2104 0761 > > Thailand (toll free): > > 001 800 6136 1473 > > Tunisia, Tunis: > > +216 31 378 101 > > Turkey, Istanbul: > > +90 212 375 50 49 > > Turkey (toll free): > > 00800 4488 26642 > > Ukraine (toll free): > > 0800 500 896 > > UAE (toll free): > > 8000 3570 2662 > > UK (03): > > +44 (0)330 336 6002 > > UK (toll free): > > 0800 358 6385 > > UK (national): > > 0844 473 5010 > > UK (national): > > 0845 545 0015 > > USA /Canada (toll free): > > 1-866-398-2885 > > Uruguay (toll free): > > 0004 019 0152 > > Venezuela, Caracas: > > +58 212 720 2164 > > Venezuela (toll free): > > 0 800 162 7451 > > Vietnam, Hanoi: > > +84 24 4458 3312 > > Vietnam, Ho Chi Minh: > > +84 28 4458 1322 > > Vietnam (toll free): > > 1800 9226 > > > > > > > > > _______________________________________________ > NCSG-FC mailing list > NCSG-FC at lists.ncsg.is > https://lists.ncsg.is/mailman/listinfo/ncsg-fc > -------------- next part -------------- An HTML attachment was scrubbed... URL: From rbeauregardlacroix at gmail.com Tue Feb 5 02:31:35 2019 From: rbeauregardlacroix at gmail.com (=?UTF-8?Q?Rapha=C3=ABl_Beauregard=2DLacroix?=) Date: Mon, 4 Feb 2019 19:31:35 -0500 Subject: [NCSG-FC] Feb update on CIVI issues and our relation with Wapix Message-ID: Dear all, Some of you may be in the loop, and some of you may not be. Some of us from the EC, along with the help of Farzaneh, have been trying to get Wapix to solve the various major and outstanding issues regarding the membership management software, CIVI, and the front end we use in order to evaluate member applications and accept or reject them. These issues have prevented us from accepting new members. I know there has been concerns over what we are paying them. Now that I see the level of service, I also agree that what we pay is too much, but for now the focus has been to get the machine to work - at least minimally so, so that we can accept new members. Once this is done, and once we can consider the overall service we have gotten since January, I will have a more thorough look at the contract we have with them, and I will eventually try discuss of certain arrangements, so that what we pay reflects the actual quality of the service. Have a nice evening, -------------- next part -------------- An HTML attachment was scrubbed... URL: From farzaneh.badii at gmail.com Tue Feb 5 02:44:35 2019 From: farzaneh.badii at gmail.com (farzaneh badii) Date: Mon, 4 Feb 2019 19:44:35 -0500 Subject: [NCSG-FC] Feb update on CIVI issues and our relation with Wapix In-Reply-To: References: Message-ID: Hi Rapha?l, The company we worked with worked really well until around October. The problems were resolved quickly. when they gave us their proposal, it was too much for us to afford so I put a halt, on the whole, revamp of the system. But we still could use the system. From October on, we have been having trouble to resolve the tickets. I am going to send them an email informing them of the issues again. The problem is that CIVI management costs are high. This happened during Tapani as well, despite the high costs service was not great. But there are other companies that are cheaper and you can have customized service. I agree that the service we are getting now is not worth the cost so we should reconsider if the situation does not improve. Farzaneh On Mon, Feb 4, 2019 at 7:31 PM Rapha?l Beauregard-Lacroix < rbeauregardlacroix at gmail.com> wrote: > Dear all, > > Some of you may be in the loop, and some of you may not be. > > Some of us from the EC, along with the help of Farzaneh, have been trying > to get Wapix to solve the various major and outstanding issues regarding > the membership management software, CIVI, and the front end we use in order > to evaluate member applications and accept or reject them. These issues > have prevented us from accepting new members. > > I know there has been concerns over what we are paying them. Now that I > see the level of service, I also agree that what we pay is too much, but > for now the focus has been to get the machine to work - at least minimally > so, so that we can accept new members. > > Once this is done, and once we can consider the overall service we have > gotten since January, I will have a more thorough look at the contract we > have with them, and I will eventually try discuss of certain arrangements, > so that what we pay reflects the actual quality of the service. > > Have a nice evening, > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From rbeauregardlacroix at gmail.com Tue Feb 5 04:55:11 2019 From: rbeauregardlacroix at gmail.com (=?UTF-8?Q?Rapha=C3=ABl_Beauregard=2DLacroix?=) Date: Mon, 4 Feb 2019 21:55:11 -0500 Subject: [NCSG-FC] Feb update on CIVI issues and our relation with Wapix In-Reply-To: References: Message-ID: Thanks for your email, and I did not mean to question earlier decisions! In any case changing provider has its own costs too... On Mon, Feb 4, 2019 at 7:45 PM farzaneh badii wrote: > Hi Rapha?l, > > The company we worked with worked really well until around October. The > problems were resolved quickly. when they gave us their proposal, it was > too much for us to afford so I put a halt, on the whole, revamp of the > system. But we still could use the system. From October on, we have been > having trouble to resolve the tickets. > > I am going to send them an email informing them of the issues again. The > problem is that CIVI management costs are high. This happened during Tapani > as well, despite the high costs service was not great. But there are other > companies that are cheaper and you can have customized service. I agree > that the service we are getting now is not worth the cost so we should > reconsider if the situation does not improve. > > > Farzaneh > > > On Mon, Feb 4, 2019 at 7:31 PM Rapha?l Beauregard-Lacroix < > rbeauregardlacroix at gmail.com> wrote: > >> Dear all, >> >> Some of you may be in the loop, and some of you may not be. >> >> Some of us from the EC, along with the help of Farzaneh, have been trying >> to get Wapix to solve the various major and outstanding issues regarding >> the membership management software, CIVI, and the front end we use in order >> to evaluate member applications and accept or reject them. These issues >> have prevented us from accepting new members. >> >> I know there has been concerns over what we are paying them. Now that I >> see the level of service, I also agree that what we pay is too much, but >> for now the focus has been to get the machine to work - at least minimally >> so, so that we can accept new members. >> >> Once this is done, and once we can consider the overall service we have >> gotten since January, I will have a more thorough look at the contract we >> have with them, and I will eventually try discuss of certain arrangements, >> so that what we pay reflects the actual quality of the service. >> >> Have a nice evening, >> >> -------------- next part -------------- An HTML attachment was scrubbed... URL: From farzaneh.badii at gmail.com Tue Feb 5 05:00:16 2019 From: farzaneh.badii at gmail.com (farzaneh badii) Date: Mon, 4 Feb 2019 22:00:16 -0500 Subject: [NCSG-FC] Feb update on CIVI issues and our relation with Wapix In-Reply-To: References: Message-ID: :) Past decision if wrong must be acknowledged and corrected. I just wanted to say in the beginning there was not this problem so lets see if there will be improvement. Lets give them some time, (I sent them another email about the tickets) and see what will happen. If it does not improve we should certainly consider moving to another provider, we have more experience with what we want now and hopefully, it will not cost us too much volunteer time. Farzaneh On Mon, Feb 4, 2019 at 9:55 PM Rapha?l Beauregard-Lacroix < rbeauregardlacroix at gmail.com> wrote: > Thanks for your email, and I did not mean to question earlier decisions! > In any case changing provider has its own costs too... > > > On Mon, Feb 4, 2019 at 7:45 PM farzaneh badii > wrote: > >> Hi Rapha?l, >> >> The company we worked with worked really well until around October. The >> problems were resolved quickly. when they gave us their proposal, it was >> too much for us to afford so I put a halt, on the whole, revamp of the >> system. But we still could use the system. From October on, we have been >> having trouble to resolve the tickets. >> >> I am going to send them an email informing them of the issues again. The >> problem is that CIVI management costs are high. This happened during Tapani >> as well, despite the high costs service was not great. But there are other >> companies that are cheaper and you can have customized service. I agree >> that the service we are getting now is not worth the cost so we should >> reconsider if the situation does not improve. >> >> >> Farzaneh >> >> >> On Mon, Feb 4, 2019 at 7:31 PM Rapha?l Beauregard-Lacroix < >> rbeauregardlacroix at gmail.com> wrote: >> >>> Dear all, >>> >>> Some of you may be in the loop, and some of you may not be. >>> >>> Some of us from the EC, along with the help of Farzaneh, have been >>> trying to get Wapix to solve the various major and outstanding issues >>> regarding the membership management software, CIVI, and the front end we >>> use in order to evaluate member applications and accept or reject them. >>> These issues have prevented us from accepting new members. >>> >>> I know there has been concerns over what we are paying them. Now that I >>> see the level of service, I also agree that what we pay is too much, but >>> for now the focus has been to get the machine to work - at least minimally >>> so, so that we can accept new members. >>> >>> Once this is done, and once we can consider the overall service we have >>> gotten since January, I will have a more thorough look at the contract we >>> have with them, and I will eventually try discuss of certain arrangements, >>> so that what we pay reflects the actual quality of the service. >>> >>> Have a nice evening, >>> >>> -------------- next part -------------- An HTML attachment was scrubbed... URL: From PolicyCalendar at icann.org Thu Feb 7 23:17:01 2019 From: PolicyCalendar at icann.org (ICANN Policy Calendar) Date: Thu, 7 Feb 2019 21:17:01 +0000 Subject: [NCSG-FC] **REMINDER**NCSG Finance Committee Meeting on Friday 08 February 2019 at 1400 UTC Message-ID: Dear All, **REMINDER** Please find participation details for the NCSG Finance Committee Meeting on Friday 08 February 2019 at 1400 UTC Adobe Connect: https://participate.icann.org/ncsg Time Zones: https://tinyurl.com/yce94nnc Dial out request: please send an email to Maryam.bakoshi at icann.org off-list. Audio dial-in details below: [https://cobranding-pgi.s3.amazonaws.com/1/Logo1.png] You're invited. You've been invited to a GlobalMeet? audio meeting. Have the meeting call you. Click the Connect Me link below. No need to dial-in. Connect Me [go.conferencinghub.com] Not at your computer? You can join by dialing one of the access numbers below. Mobile: tel://16054755604,*,,9922790467# Phone Only Controls : https://go.conferencinghub.com/2xdh7 Access Number: 1-605-475-5604 Guest Passcode: 992 279 0467 Additional Access: USA: 1-605-475-5604 USA: 1-719-457-6209 Canada, Calgary: +1 403 407 5793 Canada, Montreal: +1 514 669 5928 Canada, Toronto: +1 647 426 9172 Canada, Vancouver: +1 604 222 7836 Argentina, Buenos Aires: +54 (0) 11 5172 6003 Argentina (toll free): 0800 800 1223 Australia, Sydney: +61 (0) 2 8017 6064 Australia, Melbourne: +61 (0) 3 8687 0553 Australia, Brisbane: +61 (0) 7 3015 0535 Australia (toll free): 1 800 804 786 Austria (toll free): 0800 070 981 Bahrain, Manama: +973 1619 8739 Bahrain (toll free): 800 04212 Belarus (toll free): 8 820 0011 0341 Belgium, Brussels: +32 (0) 2 400 6928 Belgium (toll free): 0800 39279 Bosnia and Herzegovina: +387 7031 1442 Brazil, Sao Paulo: +55 11 4935 7169 Brazil, Rio de Janeiro: +55 21 4560 0072 Brazil (toll free): 0800 887 0233 Bulgaria, Sofia: +359 (0) 2 491 6045 Bulgaria (toll free): 00800 111 4950 Cambodia, Phnom Penh: +855 23 965 723 Canada (toll free): 1 855 950 3717 Chile, Santiago: +56 (0) 2 2666 0696 Chile (toll free): 171 800 835 783 China (national): +400 613 8103 China, Beijing: +86 10 5667 0003 China, Shanghai: +86 21 2039 7081 Colombia, Bogota: +57 1 508 8137 Colombia (toll free): 01 800 755 0102 Costa Rica (toll free): 800 542 5328 Croatia (toll free): 0800 805 940 Cyprus (toll free): 800 97424 Czech Republic, Prague: +420 225 986 554 Czech Republic (toll free): 800 701 532 Denmark, Copenhagen: +45 32 72 78 10 Denmark (toll free): 80 70 35 86 Egypt (toll free): 0800 000 0593 Estonia, Tallinn: +372 622 6551 Estonia (toll free): 800 011 1589 Fiji (toll free): 00800 3322 Finland, Helsinki: +358 (0) 9 2310 1677 Finland (toll free): 0800 772 236 France, Paris: +33 (0) 1 70 37 16 56 France (toll free): 0800 946 531 France (national): 0811 655 100 France (national): 0821 231 671 Georgia, Tbilisi: +995 32 2 050 778 Germany, Frankfurt: +49 (0) 69 2222 10612 Germany, Munich: +49 (0) 89 2030 31207 Germany (national): 01801 003 899 Germany (toll free): 0800 588 9170 Greece, Athens: +30 211 181 3824 Greece (toll free): 00800 128 913 Hong Kong: +852 3018 9111 Hong Kong (toll free): 800 901 787 Hungary, Budapest: +36 1408 8953 Hungary (toll free): 068 001 9673 Iceland (toll free): 800 9847 India, Delhi: +91 11 6310 0268 India, Mumbai: +91 22 6310 0298 India, Chennai: +91 44 6310 0234 India, Bangalore: +91 80 6760 8755 India (toll free): 1800 3010 1582 Indonesia, Jakarta: +62 21 2188 9084 Indonesia (toll free): 007 803 321 8927 Ireland, Dublin: +353 (0) 1 526 9421 Ireland (national): 0818 270 271 Ireland (toll free): 1800 937 649 Ireland (national): 1890 907 630 Israel, Tel Aviv: +972 (0)3 721 7943 Israel (toll free): 1809 213 168 Italy, Milan: +39 02 3600 8006 Italy, Rome: +39 06 8750 0676 Italy (toll free): 800 146 094 Japan, Tokyo: +81 3 4560 1270 Japan, Osaka: +81 6 4560 2410 Japan (toll free): 0120 305 211 Japan (mobile): 0120 632 611 Japan (national): 0570 085 744 Jordan (toll free): 0800 22172 Kazakhstan (toll free): 8800 333 7554 Kenya, Nairobi: +254 (0)207 643 581 South Korea, Seoul: +82 (0) 2 6007 0079 South Korea (toll free): 00798 6136 1454 Kuwait (national): +965 2206 3002 Latvia, Riga: +371 6601 3627 Latvia (toll free): 8000 4418 Lithuania, Vilnius: +370 5205 5468 Lithuania (toll free): 8800 31449 Luxembourg: +352 2088 1749 Luxembourg (toll free): 800 28433 Macau (national): +853 6262 1676 Malaysia, Kuala Lumpur: +60 (0) 3 7724 8010 Malaysia (toll free): 1 800 816 152 Mexico, Guadalajara: +52 33 4162 4504 Mexico, Mexico City: +52 55 8421 0326 Mexico, Monterrey: +52 81 4162 5648 Mexico (toll free): 01 800 733 4102 Morocco, Casablanca: +212 (0) 520 48 0022 Morocco (toll free): 0800 091 296 Netherlands, Amsterdam: +31 (0) 20 716 8345 Netherlands (toll free): 0800 020 2597 New Zealand, Christchurch: +64 (0) 3 974 2596 New Zealand, Wellington: +64 (0) 4 909 4674 New Zealand, Auckland: +64 (0) 9 929 1825 New Zealand (toll free): 0800 452 947 Nigeria, Lagos: +234 1 277 3944 Norway, Oslo: +47 21 00 48 15 Norway (toll free): 800 56081 Oman (toll free): 800 77265 Pakistan, Islamabad: +92 5181 08863 Panama, Panama City: +507 8 335 913 Panama (toll free): 00800 223 1390 Peru, Lima: +51 (0) 1 700 9571 Philippines, Manila: +63 (0)2 395 3426 Philippines (toll free): 1 800 111 013 99 Poland, Warsaw: +48 22 295 3570 Poland (toll free): 00 800 121 4356 Portugal, Lisbon: +351 21 316 4093 Portugal (toll free): 800 784 442 Qatar (freephone): 00 800 100 491 Romania, Bucharest: +40 (0) 21 529 3992 Romania (toll free): 0800 801 035 Russia, Moscow: +7 495 646 9181 Russia (toll free): 8 800 500 9241 Saudi Arabia (toll free): 800 844 6641 Saudi Arabia (toll free): 800 850 0219 Serbia (toll free): 0800 190 712 Singapore: +65 6654 9112 Singapore (toll free): 800 616 3192 Slovakia, Bratislava: +421 (0)2 3321 5498 Slovakia (toll free): 0800 002 002 Slovenia, Ljubljana: +386 1600 8695 Slovenia (toll free): 0800 81193 South Africa, Johannesburg: +27 (0)11 589 8321 South Africa (toll free): 0800 999 434 Spain, Madrid: +34 91 114 6653 Spain, Barcelona: +34 93 800 1946 Spain (toll free): 900 828 035 Sri Lanka, Sri Lanka: +94 720 910 333 Sweden, Stockholm: +46 (0) 8 5065 3956 Sweden (toll free): 0200 125 588 Switzerland, Geneva: +41 (0) 22 595 4795 Switzerland, Zurich: +41 (0) 44 580 7207 Switzerland (toll free): 0800 740 360 Taiwan, Taipei: +886 (0) 2 2650 7329 Taiwan (toll free): 0800 666 596 Thailand, Bangkok: +66 (0) 2104 0761 Thailand (toll free): 001 800 6136 1473 Tunisia, Tunis: +216 31 378 101 Turkey, Istanbul: +90 212 375 50 49 Turkey (toll free): 00800 4488 26642 Ukraine (toll free): 0800 500 896 UAE (toll free): 8000 3570 2662 UK (03): +44 (0)330 336 6002 UK (toll free): 0800 358 6385 UK (national): 0844 473 5010 UK (national): 0845 545 0015 USA /Canada (toll free): 1-866-398-2885 Uruguay (toll free): 0004 019 0152 Venezuela, Caracas: +58 212 720 2164 Venezuela (toll free): 0 800 162 7451 Vietnam, Hanoi: +84 24 4458 3312 Vietnam, Ho Chi Minh: +84 28 4458 1322 Vietnam (toll free): 1800 9226 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 11449 bytes Desc: not available URL: From PolicyCalendar at icann.org Fri Feb 8 15:42:23 2019 From: PolicyCalendar at icann.org (ICANN Policy Calendar) Date: Fri, 8 Feb 2019 13:42:23 +0000 Subject: [NCSG-FC] **REMINDER**NCSG Finance Committee Meeting on Friday 08 February 2019 at 1400 UTC Message-ID: <2008afb6c77c4413a78a7694dc12b376@PMBX112-W1-CA-1.PEXCH112.ICANN.ORG> Dear All, **REMINDER** Please find participation details for the NCSG Finance Committee Meeting on Friday 08 February 2019 at 1400 UTC Adobe Connect: https://participate.icann.org/ncsg Time Zones: https://tinyurl.com/yce94nnc Dial out request: please send an email to Maryam.bakoshi at icann.org off-list. Audio dial-in details below: [https://cobranding-pgi.s3.amazonaws.com/1/Logo1.png] You're invited. You've been invited to a GlobalMeet? audio meeting. Have the meeting call you. Click the Connect Me link below. No need to dial-in. Connect Me [go.conferencinghub.com] Not at your computer? You can join by dialing one of the access numbers below. Mobile: tel://16054755604,*,,9922790467# Phone Only Controls : https://go.conferencinghub.com/2xdh7 Access Number: 1-605-475-5604 Guest Passcode: 992 279 0467 Additional Access: USA: 1-605-475-5604 USA: 1-719-457-6209 Canada, Calgary: +1 403 407 5793 Canada, Montreal: +1 514 669 5928 Canada, Toronto: +1 647 426 9172 Canada, Vancouver: +1 604 222 7836 Argentina, Buenos Aires: +54 (0) 11 5172 6003 Argentina (toll free): 0800 800 1223 Australia, Sydney: +61 (0) 2 8017 6064 Australia, Melbourne: +61 (0) 3 8687 0553 Australia, Brisbane: +61 (0) 7 3015 0535 Australia (toll free): 1 800 804 786 Austria (toll free): 0800 070 981 Bahrain, Manama: +973 1619 8739 Bahrain (toll free): 800 04212 Belarus (toll free): 8 820 0011 0341 Belgium, Brussels: +32 (0) 2 400 6928 Belgium (toll free): 0800 39279 Bosnia and Herzegovina: +387 7031 1442 Brazil, Sao Paulo: +55 11 4935 7169 Brazil, Rio de Janeiro: +55 21 4560 0072 Brazil (toll free): 0800 887 0233 Bulgaria, Sofia: +359 (0) 2 491 6045 Bulgaria (toll free): 00800 111 4950 Cambodia, Phnom Penh: +855 23 965 723 Canada (toll free): 1 855 950 3717 Chile, Santiago: +56 (0) 2 2666 0696 Chile (toll free): 171 800 835 783 China (national): +400 613 8103 China, Beijing: +86 10 5667 0003 China, Shanghai: +86 21 2039 7081 Colombia, Bogota: +57 1 508 8137 Colombia (toll free): 01 800 755 0102 Costa Rica (toll free): 800 542 5328 Croatia (toll free): 0800 805 940 Cyprus (toll free): 800 97424 Czech Republic, Prague: +420 225 986 554 Czech Republic (toll free): 800 701 532 Denmark, Copenhagen: +45 32 72 78 10 Denmark (toll free): 80 70 35 86 Egypt (toll free): 0800 000 0593 Estonia, Tallinn: +372 622 6551 Estonia (toll free): 800 011 1589 Fiji (toll free): 00800 3322 Finland, Helsinki: +358 (0) 9 2310 1677 Finland (toll free): 0800 772 236 France, Paris: +33 (0) 1 70 37 16 56 France (toll free): 0800 946 531 France (national): 0811 655 100 France (national): 0821 231 671 Georgia, Tbilisi: +995 32 2 050 778 Germany, Frankfurt: +49 (0) 69 2222 10612 Germany, Munich: +49 (0) 89 2030 31207 Germany (national): 01801 003 899 Germany (toll free): 0800 588 9170 Greece, Athens: +30 211 181 3824 Greece (toll free): 00800 128 913 Hong Kong: +852 3018 9111 Hong Kong (toll free): 800 901 787 Hungary, Budapest: +36 1408 8953 Hungary (toll free): 068 001 9673 Iceland (toll free): 800 9847 India, Delhi: +91 11 6310 0268 India, Mumbai: +91 22 6310 0298 India, Chennai: +91 44 6310 0234 India, Bangalore: +91 80 6760 8755 India (toll free): 1800 3010 1582 Indonesia, Jakarta: +62 21 2188 9084 Indonesia (toll free): 007 803 321 8927 Ireland, Dublin: +353 (0) 1 526 9421 Ireland (national): 0818 270 271 Ireland (toll free): 1800 937 649 Ireland (national): 1890 907 630 Israel, Tel Aviv: +972 (0)3 721 7943 Israel (toll free): 1809 213 168 Italy, Milan: +39 02 3600 8006 Italy, Rome: +39 06 8750 0676 Italy (toll free): 800 146 094 Japan, Tokyo: +81 3 4560 1270 Japan, Osaka: +81 6 4560 2410 Japan (toll free): 0120 305 211 Japan (mobile): 0120 632 611 Japan (national): 0570 085 744 Jordan (toll free): 0800 22172 Kazakhstan (toll free): 8800 333 7554 Kenya, Nairobi: +254 (0)207 643 581 South Korea, Seoul: +82 (0) 2 6007 0079 South Korea (toll free): 00798 6136 1454 Kuwait (national): +965 2206 3002 Latvia, Riga: +371 6601 3627 Latvia (toll free): 8000 4418 Lithuania, Vilnius: +370 5205 5468 Lithuania (toll free): 8800 31449 Luxembourg: +352 2088 1749 Luxembourg (toll free): 800 28433 Macau (national): +853 6262 1676 Malaysia, Kuala Lumpur: +60 (0) 3 7724 8010 Malaysia (toll free): 1 800 816 152 Mexico, Guadalajara: +52 33 4162 4504 Mexico, Mexico City: +52 55 8421 0326 Mexico, Monterrey: +52 81 4162 5648 Mexico (toll free): 01 800 733 4102 Morocco, Casablanca: +212 (0) 520 48 0022 Morocco (toll free): 0800 091 296 Netherlands, Amsterdam: +31 (0) 20 716 8345 Netherlands (toll free): 0800 020 2597 New Zealand, Christchurch: +64 (0) 3 974 2596 New Zealand, Wellington: +64 (0) 4 909 4674 New Zealand, Auckland: +64 (0) 9 929 1825 New Zealand (toll free): 0800 452 947 Nigeria, Lagos: +234 1 277 3944 Norway, Oslo: +47 21 00 48 15 Norway (toll free): 800 56081 Oman (toll free): 800 77265 Pakistan, Islamabad: +92 5181 08863 Panama, Panama City: +507 8 335 913 Panama (toll free): 00800 223 1390 Peru, Lima: +51 (0) 1 700 9571 Philippines, Manila: +63 (0)2 395 3426 Philippines (toll free): 1 800 111 013 99 Poland, Warsaw: +48 22 295 3570 Poland (toll free): 00 800 121 4356 Portugal, Lisbon: +351 21 316 4093 Portugal (toll free): 800 784 442 Qatar (freephone): 00 800 100 491 Romania, Bucharest: +40 (0) 21 529 3992 Romania (toll free): 0800 801 035 Russia, Moscow: +7 495 646 9181 Russia (toll free): 8 800 500 9241 Saudi Arabia (toll free): 800 844 6641 Saudi Arabia (toll free): 800 850 0219 Serbia (toll free): 0800 190 712 Singapore: +65 6654 9112 Singapore (toll free): 800 616 3192 Slovakia, Bratislava: +421 (0)2 3321 5498 Slovakia (toll free): 0800 002 002 Slovenia, Ljubljana: +386 1600 8695 Slovenia (toll free): 0800 81193 South Africa, Johannesburg: +27 (0)11 589 8321 South Africa (toll free): 0800 999 434 Spain, Madrid: +34 91 114 6653 Spain, Barcelona: +34 93 800 1946 Spain (toll free): 900 828 035 Sri Lanka, Sri Lanka: +94 720 910 333 Sweden, Stockholm: +46 (0) 8 5065 3956 Sweden (toll free): 0200 125 588 Switzerland, Geneva: +41 (0) 22 595 4795 Switzerland, Zurich: +41 (0) 44 580 7207 Switzerland (toll free): 0800 740 360 Taiwan, Taipei: +886 (0) 2 2650 7329 Taiwan (toll free): 0800 666 596 Thailand, Bangkok: +66 (0) 2104 0761 Thailand (toll free): 001 800 6136 1473 Tunisia, Tunis: +216 31 378 101 Turkey, Istanbul: +90 212 375 50 49 Turkey (toll free): 00800 4488 26642 Ukraine (toll free): 0800 500 896 UAE (toll free): 8000 3570 2662 UK (03): +44 (0)330 336 6002 UK (toll free): 0800 358 6385 UK (national): 0844 473 5010 UK (national): 0845 545 0015 USA /Canada (toll free): 1-866-398-2885 Uruguay (toll free): 0004 019 0152 Venezuela, Caracas: +58 212 720 2164 Venezuela (toll free): 0 800 162 7451 Vietnam, Hanoi: +84 24 4458 3312 Vietnam, Ho Chi Minh: +84 28 4458 1322 Vietnam (toll free): 1800 9226 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 11449 bytes Desc: not available URL: From thatomfikwe at gmail.com Fri Feb 8 16:10:41 2019 From: thatomfikwe at gmail.com (Thato Mfikwe) Date: Fri, 8 Feb 2019 16:10:41 +0200 Subject: [NCSG-FC] Fwd: **REMINDER**NCSG Finance Committee Meeting on Friday 08 February 2019 at 1400 UTC In-Reply-To: <2008afb6c77c4413a78a7694dc12b376@PMBX112-W1-CA-1.PEXCH112.ICANN.ORG> References: <2008afb6c77c4413a78a7694dc12b376@PMBX112-W1-CA-1.PEXCH112.ICANN.ORG> Message-ID: Hi all, Just a friendly reminder that the FC meeting has started, pleasee let me know if you cannot attend so that we can reschedule, thanks. Thato Mfikwe. ---------- Forwarded message --------- From: ICANN Policy Calendar Date: Fri, Feb 8, 2019 at 3:42 PM Subject: [NCSG-FC] **REMINDER**NCSG Finance Committee Meeting on Friday 08 February 2019 at 1400 UTC To: NCSG Finance Committee , Stephanie Perrin < stephanie.perrin at mail.utoronto.ca>, Maryam Bakoshi Dear All, ***REMINDER** * Please find participation details for the *NCSG Finance Committee Meeting on Friday 08 February 2019 at 1400 UTC* *Adobe Connect*: https://participate.icann.org/ncsg *Time Zones*: https://tinyurl.com/yce94nnc *Dial out request*: please send an email to Maryam.bakoshi at icann.org off-list. *Audio dial-in details below:* [image: https://cobranding-pgi.s3.amazonaws.com/1/Logo1.png] *You're invited.* You've been invited to a GlobalMeet? audio meeting. *Have the meeting call you.* Click the Connect Me link below. *No need to dial-in.* *Connect Me [go.conferencinghub.com] * *Not at your computer?* You can join by dialing one of the access numbers below. *Mobile:* tel://16054755604,*,,9922790467# *Phone Only Controls :* https://go.conferencinghub.com/2xdh7 *Access Number:* 1-605-475-5604 *Guest Passcode:* 992 279 0467 *Additional Access:* USA: 1-605-475-5604 USA: 1-719-457-6209 Canada, Calgary: +1 403 407 5793 Canada, Montreal: +1 514 669 5928 Canada, Toronto: +1 647 426 9172 Canada, Vancouver: +1 604 222 7836 Argentina, Buenos Aires: +54 (0) 11 5172 6003 Argentina (toll free): 0800 800 1223 Australia, Sydney: +61 (0) 2 8017 6064 Australia, Melbourne: +61 (0) 3 8687 0553 Australia, Brisbane: +61 (0) 7 3015 0535 Australia (toll free): 1 800 804 786 Austria (toll free): 0800 070 981 Bahrain, Manama: +973 1619 8739 Bahrain (toll free): 800 04212 Belarus (toll free): 8 820 0011 0341 Belgium, Brussels: +32 (0) 2 400 6928 Belgium (toll free): 0800 39279 Bosnia and Herzegovina: +387 7031 1442 Brazil, Sao Paulo: +55 11 4935 7169 Brazil, Rio de Janeiro: +55 21 4560 0072 Brazil (toll free): 0800 887 0233 Bulgaria, Sofia: +359 (0) 2 491 6045 Bulgaria (toll free): 00800 111 4950 Cambodia, Phnom Penh: +855 23 965 723 Canada (toll free): 1 855 950 3717 Chile, Santiago: +56 (0) 2 2666 0696 Chile (toll free): 171 800 835 783 China (national): +400 613 8103 China, Beijing: +86 10 5667 0003 China, Shanghai: +86 21 2039 7081 Colombia, Bogota: +57 1 508 8137 Colombia (toll free): 01 800 755 0102 Costa Rica (toll free): 800 542 5328 Croatia (toll free): 0800 805 940 Cyprus (toll free): 800 97424 Czech Republic, Prague: +420 225 986 554 Czech Republic (toll free): 800 701 532 Denmark, Copenhagen: +45 32 72 78 10 Denmark (toll free): 80 70 35 86 Egypt (toll free): 0800 000 0593 Estonia, Tallinn: +372 622 6551 Estonia (toll free): 800 011 1589 Fiji (toll free): 00800 3322 Finland, Helsinki: +358 (0) 9 2310 1677 Finland (toll free): 0800 772 236 France, Paris: +33 (0) 1 70 37 16 56 France (toll free): 0800 946 531 France (national): 0811 655 100 France (national): 0821 231 671 Georgia, Tbilisi: +995 32 2 050 778 Germany, Frankfurt: +49 (0) 69 2222 10612 Germany, Munich: +49 (0) 89 2030 31207 Germany (national): 01801 003 899 Germany (toll free): 0800 588 9170 Greece, Athens: +30 211 181 3824 Greece (toll free): 00800 128 913 Hong Kong: +852 3018 9111 Hong Kong (toll free): 800 901 787 Hungary, Budapest: +36 1408 8953 Hungary (toll free): 068 001 9673 Iceland (toll free): 800 9847 India, Delhi: +91 11 6310 0268 India, Mumbai: +91 22 6310 0298 India, Chennai: +91 44 6310 0234 India, Bangalore: +91 80 6760 8755 India (toll free): 1800 3010 1582 Indonesia, Jakarta: +62 21 2188 9084 Indonesia (toll free): 007 803 321 8927 Ireland, Dublin: +353 (0) 1 526 9421 Ireland (national): 0818 270 271 Ireland (toll free): 1800 937 649 Ireland (national): 1890 907 630 Israel, Tel Aviv: +972 (0)3 721 7943 Israel (toll free): 1809 213 168 Italy, Milan: +39 02 3600 8006 Italy, Rome: +39 06 8750 0676 Italy (toll free): 800 146 094 Japan, Tokyo: +81 3 4560 1270 Japan, Osaka: +81 6 4560 2410 Japan (toll free): 0120 305 211 Japan (mobile): 0120 632 611 Japan (national): 0570 085 744 Jordan (toll free): 0800 22172 Kazakhstan (toll free): 8800 333 7554 Kenya, Nairobi: +254 (0)207 643 581 South Korea, Seoul: +82 (0) 2 6007 0079 South Korea (toll free): 00798 6136 1454 Kuwait (national): +965 2206 3002 Latvia, Riga: +371 6601 3627 Latvia (toll free): 8000 4418 Lithuania, Vilnius: +370 5205 5468 Lithuania (toll free): 8800 31449 Luxembourg: +352 2088 1749 Luxembourg (toll free): 800 28433 Macau (national): +853 6262 1676 Malaysia, Kuala Lumpur: +60 (0) 3 7724 8010 Malaysia (toll free): 1 800 816 152 Mexico, Guadalajara: +52 33 4162 4504 Mexico, Mexico City: +52 55 8421 0326 Mexico, Monterrey: +52 81 4162 5648 Mexico (toll free): 01 800 733 4102 Morocco, Casablanca: +212 (0) 520 48 0022 Morocco (toll free): 0800 091 296 Netherlands, Amsterdam: +31 (0) 20 716 8345 Netherlands (toll free): 0800 020 2597 New Zealand, Christchurch: +64 (0) 3 974 2596 New Zealand, Wellington: +64 (0) 4 909 4674 New Zealand, Auckland: +64 (0) 9 929 1825 New Zealand (toll free): 0800 452 947 Nigeria, Lagos: +234 1 277 3944 Norway, Oslo: +47 21 00 48 15 Norway (toll free): 800 56081 Oman (toll free): 800 77265 Pakistan, Islamabad: +92 5181 08863 Panama, Panama City: +507 8 335 913 Panama (toll free): 00800 223 1390 Peru, Lima: +51 (0) 1 700 9571 Philippines, Manila: +63 (0)2 395 3426 Philippines (toll free): 1 800 111 013 99 Poland, Warsaw: +48 22 295 3570 Poland (toll free): 00 800 121 4356 Portugal, Lisbon: +351 21 316 4093 Portugal (toll free): 800 784 442 Qatar (freephone): 00 800 100 491 Romania, Bucharest: +40 (0) 21 529 3992 Romania (toll free): 0800 801 035 Russia, Moscow: +7 495 646 9181 Russia (toll free): 8 800 500 9241 Saudi Arabia (toll free): 800 844 6641 Saudi Arabia (toll free): 800 850 0219 Serbia (toll free): 0800 190 712 Singapore: +65 6654 9112 Singapore (toll free): 800 616 3192 Slovakia, Bratislava: +421 (0)2 3321 5498 Slovakia (toll free): 0800 002 002 Slovenia, Ljubljana: +386 1600 8695 Slovenia (toll free): 0800 81193 South Africa, Johannesburg: +27 (0)11 589 8321 South Africa (toll free): 0800 999 434 Spain, Madrid: +34 91 114 6653 Spain, Barcelona: +34 93 800 1946 Spain (toll free): 900 828 035 Sri Lanka, Sri Lanka: +94 720 910 333 Sweden, Stockholm: +46 (0) 8 5065 3956 Sweden (toll free): 0200 125 588 Switzerland, Geneva: +41 (0) 22 595 4795 Switzerland, Zurich: +41 (0) 44 580 7207 Switzerland (toll free): 0800 740 360 Taiwan, Taipei: +886 (0) 2 2650 7329 Taiwan (toll free): 0800 666 596 Thailand, Bangkok: +66 (0) 2104 0761 Thailand (toll free): 001 800 6136 1473 Tunisia, Tunis: +216 31 378 101 Turkey, Istanbul: +90 212 375 50 49 Turkey (toll free): 00800 4488 26642 Ukraine (toll free): 0800 500 896 UAE (toll free): 8000 3570 2662 UK (03): +44 (0)330 336 6002 UK (toll free): 0800 358 6385 UK (national): 0844 473 5010 UK (national): 0845 545 0015 USA /Canada (toll free): 1-866-398-2885 Uruguay (toll free): 0004 019 0152 Venezuela, Caracas: +58 212 720 2164 Venezuela (toll free): 0 800 162 7451 Vietnam, Hanoi: +84 24 4458 3312 Vietnam, Ho Chi Minh: +84 28 4458 1322 Vietnam (toll free): 1800 9226 _______________________________________________ NCSG-FC mailing list NCSG-FC at lists.ncsg.is https://lists.ncsg.is/mailman/listinfo/ncsg-fc -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: invite.ics Type: application/ics Size: 11449 bytes Desc: not available URL: From remmyn at gmail.com Fri Feb 8 16:15:02 2019 From: remmyn at gmail.com (Remmy Nweke) Date: Fri, 8 Feb 2019 15:15:02 +0100 Subject: [NCSG-FC] **REMINDER**NCSG Finance Committee Meeting on Friday 08 February 2019 at 1400 UTC In-Reply-To: References: <2008afb6c77c4413a78a7694dc12b376@PMBX112-W1-CA-1.PEXCH112.ICANN.ORG> Message-ID: Thanks I had requested a dial out on +2348033592762 because I am on the road. Thanks On Fri, 8 Feb 2019, 3:11 p.m. Thato Mfikwe Hi all, > > Just a friendly reminder that the FC meeting has started, pleasee let me > know if you cannot attend so that we can reschedule, thanks. > > Thato Mfikwe. > > ---------- Forwarded message --------- > From: ICANN Policy Calendar > Date: Fri, Feb 8, 2019 at 3:42 PM > Subject: [NCSG-FC] **REMINDER**NCSG Finance Committee Meeting on Friday 08 > February 2019 at 1400 UTC > To: NCSG Finance Committee , Stephanie Perrin < > stephanie.perrin at mail.utoronto.ca>, Maryam Bakoshi < > maryam.bakoshi at icann.org> > > > Dear All, > > > > ***REMINDER** * > > > Please find participation details for the *NCSG Finance Committee Meeting > on Friday 08 February 2019 at 1400 UTC* > > > *Adobe Connect*: https://participate.icann.org/ncsg > > > *Time Zones*: https://tinyurl.com/yce94nnc > > > *Dial out request*: please send an email to Maryam.bakoshi at icann.org > off-list. > > > *Audio dial-in details below:* > > [image: https://cobranding-pgi.s3.amazonaws.com/1/Logo1.png] > > *You're invited.* > You've been invited to a GlobalMeet? audio meeting. > > *Have the meeting call you.* > Click the Connect Me link below. *No need to dial-in.* > > > *Connect Me [go.conferencinghub.com] > * > > > *Not at your computer?* > You can join by dialing one of the access numbers below. > > > *Mobile:* > > tel://16054755604,*,,9922790467# > > *Phone Only Controls :* > > https://go.conferencinghub.com/2xdh7 > > *Access Number:* > > 1-605-475-5604 > > *Guest Passcode:* > > 992 279 0467 > > *Additional Access:* > > USA: > > 1-605-475-5604 > > USA: > > 1-719-457-6209 > > Canada, Calgary: > > +1 403 407 5793 > > Canada, Montreal: > > +1 514 669 5928 > > Canada, Toronto: > > +1 647 426 9172 > > Canada, Vancouver: > > +1 604 222 7836 > > Argentina, Buenos Aires: > > +54 (0) 11 5172 6003 > > Argentina (toll free): > > 0800 800 1223 > > Australia, Sydney: > > +61 (0) 2 8017 6064 > > Australia, Melbourne: > > +61 (0) 3 8687 0553 > > Australia, Brisbane: > > +61 (0) 7 3015 0535 > > Australia (toll free): > > 1 800 804 786 > > Austria (toll free): > > 0800 070 981 > > Bahrain, Manama: > > +973 1619 8739 > > Bahrain (toll free): > > 800 04212 > > Belarus (toll free): > > 8 820 0011 0341 > > Belgium, Brussels: > > +32 (0) 2 400 6928 > > Belgium (toll free): > > 0800 39279 > > Bosnia and Herzegovina: > > +387 7031 1442 > > Brazil, Sao Paulo: > > +55 11 4935 7169 > > Brazil, Rio de Janeiro: > > +55 21 4560 0072 > > Brazil (toll free): > > 0800 887 0233 > > Bulgaria, Sofia: > > +359 (0) 2 491 6045 > > Bulgaria (toll free): > > 00800 111 4950 > > Cambodia, Phnom Penh: > > +855 23 965 723 > > Canada (toll free): > > 1 855 950 3717 > > Chile, Santiago: > > +56 (0) 2 2666 0696 > > Chile (toll free): > > 171 800 835 783 > > China (national): > > +400 613 8103 > > China, Beijing: > > +86 10 5667 0003 > > China, Shanghai: > > +86 21 2039 7081 > > Colombia, Bogota: > > +57 1 508 8137 > > Colombia (toll free): > > 01 800 755 0102 > > Costa Rica (toll free): > > 800 542 5328 > > Croatia (toll free): > > 0800 805 940 > > Cyprus (toll free): > > 800 97424 > > Czech Republic, Prague: > > +420 225 986 554 > > Czech Republic (toll free): > > 800 701 532 > > Denmark, Copenhagen: > > +45 32 72 78 10 > > Denmark (toll free): > > 80 70 35 86 > > Egypt (toll free): > > 0800 000 0593 > > Estonia, Tallinn: > > +372 622 6551 > > Estonia (toll free): > > 800 011 1589 > > Fiji (toll free): > > 00800 3322 > > Finland, Helsinki: > > +358 (0) 9 2310 1677 > > Finland (toll free): > > 0800 772 236 > > France, Paris: > > +33 (0) 1 70 37 16 56 > > France (toll free): > > 0800 946 531 > > France (national): > > 0811 655 100 > > France (national): > > 0821 231 671 > > Georgia, Tbilisi: > > +995 32 2 050 778 > > Germany, Frankfurt: > > +49 (0) 69 2222 10612 > > Germany, Munich: > > +49 (0) 89 2030 31207 > > Germany (national): > > 01801 003 899 > > Germany (toll free): > > 0800 588 9170 > > Greece, Athens: > > +30 211 181 3824 > > Greece (toll free): > > 00800 128 913 > > Hong Kong: > > +852 3018 9111 > > Hong Kong (toll free): > > 800 901 787 > > Hungary, Budapest: > > +36 1408 8953 > > Hungary (toll free): > > 068 001 9673 > > Iceland (toll free): > > 800 9847 > > India, Delhi: > > +91 11 6310 0268 > > India, Mumbai: > > +91 22 6310 0298 > > India, Chennai: > > +91 44 6310 0234 > > India, Bangalore: > > +91 80 6760 8755 > > India (toll free): > > 1800 3010 1582 > > Indonesia, Jakarta: > > +62 21 2188 9084 > > Indonesia (toll free): > > 007 803 321 8927 > > Ireland, Dublin: > > +353 (0) 1 526 9421 > > Ireland (national): > > 0818 270 271 > > Ireland (toll free): > > 1800 937 649 > > Ireland (national): > > 1890 907 630 > > Israel, Tel Aviv: > > +972 (0)3 721 7943 > > Israel (toll free): > > 1809 213 168 > > Italy, Milan: > > +39 02 3600 8006 > > Italy, Rome: > > +39 06 8750 0676 > > Italy (toll free): > > 800 146 094 > > Japan, Tokyo: > > +81 3 4560 1270 > > Japan, Osaka: > > +81 6 4560 2410 > > Japan (toll free): > > 0120 305 211 > > Japan (mobile): > > 0120 632 611 > > Japan (national): > > 0570 085 744 > > Jordan (toll free): > > 0800 22172 > > Kazakhstan (toll free): > > 8800 333 7554 > > Kenya, Nairobi: > > +254 (0)207 643 581 > > South Korea, Seoul: > > +82 (0) 2 6007 0079 > > South Korea (toll free): > > 00798 6136 1454 > > Kuwait (national): > > +965 2206 3002 > > Latvia, Riga: > > +371 6601 3627 > > Latvia (toll free): > > 8000 4418 > > Lithuania, Vilnius: > > +370 5205 5468 > > Lithuania (toll free): > > 8800 31449 > > Luxembourg: > > +352 2088 1749 > > Luxembourg (toll free): > > 800 28433 > > Macau (national): > > +853 6262 1676 > > Malaysia, Kuala Lumpur: > > +60 (0) 3 7724 8010 > > Malaysia (toll free): > > 1 800 816 152 > > Mexico, Guadalajara: > > +52 33 4162 4504 > > Mexico, Mexico City: > > +52 55 8421 0326 > > Mexico, Monterrey: > > +52 81 4162 5648 > > Mexico (toll free): > > 01 800 733 4102 > > Morocco, Casablanca: > > +212 (0) 520 48 0022 > > Morocco (toll free): > > 0800 091 296 > > Netherlands, Amsterdam: > > +31 (0) 20 716 8345 > > Netherlands (toll free): > > 0800 020 2597 > > New Zealand, Christchurch: > > +64 (0) 3 974 2596 > > New Zealand, Wellington: > > +64 (0) 4 909 4674 > > New Zealand, Auckland: > > +64 (0) 9 929 1825 > > New Zealand (toll free): > > 0800 452 947 > > Nigeria, Lagos: > > +234 1 277 3944 > > Norway, Oslo: > > +47 21 00 48 15 > > Norway (toll free): > > 800 56081 > > Oman (toll free): > > 800 77265 > > Pakistan, Islamabad: > > +92 5181 08863 > > Panama, Panama City: > > +507 8 335 913 > > Panama (toll free): > > 00800 223 1390 > > Peru, Lima: > > +51 (0) 1 700 9571 > > Philippines, Manila: > > +63 (0)2 395 3426 > > Philippines (toll free): > > 1 800 111 013 99 > > Poland, Warsaw: > > +48 22 295 3570 > > Poland (toll free): > > 00 800 121 4356 > > Portugal, Lisbon: > > +351 21 316 4093 > > Portugal (toll free): > > 800 784 442 > > Qatar (freephone): > > 00 800 100 491 > > Romania, Bucharest: > > +40 (0) 21 529 3992 > > Romania (toll free): > > 0800 801 035 > > Russia, Moscow: > > +7 495 646 9181 > > Russia (toll free): > > 8 800 500 9241 > > Saudi Arabia (toll free): > > 800 844 6641 > > Saudi Arabia (toll free): > > 800 850 0219 > > Serbia (toll free): > > 0800 190 712 > > Singapore: > > +65 6654 9112 > > Singapore (toll free): > > 800 616 3192 > > Slovakia, Bratislava: > > +421 (0)2 3321 5498 > > Slovakia (toll free): > > 0800 002 002 > > Slovenia, Ljubljana: > > +386 1600 8695 > > Slovenia (toll free): > > 0800 81193 > > South Africa, Johannesburg: > > +27 (0)11 589 8321 > > South Africa (toll free): > > 0800 999 434 > > Spain, Madrid: > > +34 91 114 6653 > > Spain, Barcelona: > > +34 93 800 1946 > > Spain (toll free): > > 900 828 035 > > Sri Lanka, Sri Lanka: > > +94 720 910 333 > > Sweden, Stockholm: > > +46 (0) 8 5065 3956 > > Sweden (toll free): > > 0200 125 588 > > Switzerland, Geneva: > > +41 (0) 22 595 4795 > > Switzerland, Zurich: > > +41 (0) 44 580 7207 > > Switzerland (toll free): > > 0800 740 360 > > Taiwan, Taipei: > > +886 (0) 2 2650 7329 > > Taiwan (toll free): > > 0800 666 596 > > Thailand, Bangkok: > > +66 (0) 2104 0761 > > Thailand (toll free): > > 001 800 6136 1473 > > Tunisia, Tunis: > > +216 31 378 101 > > Turkey, Istanbul: > > +90 212 375 50 49 > > Turkey (toll free): > > 00800 4488 26642 > > Ukraine (toll free): > > 0800 500 896 > > UAE (toll free): > > 8000 3570 2662 > > UK (03): > > +44 (0)330 336 6002 > > UK (toll free): > > 0800 358 6385 > > UK (national): > > 0844 473 5010 > > UK (national): > > 0845 545 0015 > > USA /Canada (toll free): > > 1-866-398-2885 > > Uruguay (toll free): > > 0004 019 0152 > > Venezuela, Caracas: > > +58 212 720 2164 > > Venezuela (toll free): > > 0 800 162 7451 > > Vietnam, Hanoi: > > +84 24 4458 > -------------- next part -------------- An HTML attachment was scrubbed... URL: From stephanie.perrin at mail.utoronto.ca Fri Feb 8 16:35:12 2019 From: stephanie.perrin at mail.utoronto.ca (Stephanie Perrin) Date: Fri, 8 Feb 2019 14:35:12 +0000 Subject: [NCSG-FC] Fwd: **REMINDER**NCSG Finance Committee Meeting on Friday 08 February 2019 at 1400 UTC In-Reply-To: References: <2008afb6c77c4413a78a7694dc12b376@PMBX112-W1-CA-1.PEXCH112.ICANN.ORG> Message-ID: <309c348b-5dd4-0cf0-6f36-2c258d36964f@mail.utoronto.ca> Sorry I was late, we have also EPDP. It seems I went to the wrong adobe connect, nobody is there?? Stephanie On 2019-02-08 09:10, Thato Mfikwe wrote: Hi all, Just a friendly reminder that the FC meeting has started, pleasee let me know if you cannot attend so that we can reschedule, thanks. Thato Mfikwe. ---------- Forwarded message --------- From: ICANN Policy Calendar > Date: Fri, Feb 8, 2019 at 3:42 PM Subject: [NCSG-FC] **REMINDER**NCSG Finance Committee Meeting on Friday 08 February 2019 at 1400 UTC To: NCSG Finance Committee >, Stephanie Perrin >, Maryam Bakoshi > Dear All, **REMINDER** Please find participation details for the NCSG Finance Committee Meeting on Friday 08 February 2019 at 1400 UTC Adobe Connect: https://participate.icann.org/ncsg Time Zones: https://tinyurl.com/yce94nnc Dial out request: please send an email to Maryam.bakoshi at icann.org off-list. Audio dial-in details below: [https://cobranding-pgi.s3.amazonaws.com/1/Logo1.png] You're invited. You've been invited to a GlobalMeet? audio meeting. Have the meeting call you. Click the Connect Me link below. No need to dial-in. Connect Me [go.conferencinghub.com] Not at your computer? You can join by dialing one of the access numbers below. Mobile: tel://16054755604,*,,9922790467# Phone Only Controls : https://go.conferencinghub.com/2xdh7 Access Number: 1-605-475-5604 Guest Passcode: 992 279 0467 Additional Access: USA: 1-605-475-5604 USA: 1-719-457-6209 Canada, Calgary: +1 403 407 5793 Canada, Montreal: +1 514 669 5928 Canada, Toronto: +1 647 426 9172 Canada, Vancouver: +1 604 222 7836 Argentina, Buenos Aires: +54 (0) 11 5172 6003 Argentina (toll free): 0800 800 1223 Australia, Sydney: +61 (0) 2 8017 6064 Australia, Melbourne: +61 (0) 3 8687 0553 Australia, Brisbane: +61 (0) 7 3015 0535 Australia (toll free): 1 800 804 786 Austria (toll free): 0800 070 981 Bahrain, Manama: +973 1619 8739 Bahrain (toll free): 800 04212 Belarus (toll free): 8 820 0011 0341 Belgium, Brussels: +32 (0) 2 400 6928 Belgium (toll free): 0800 39279 Bosnia and Herzegovina: +387 7031 1442 Brazil, Sao Paulo: +55 11 4935 7169 Brazil, Rio de Janeiro: +55 21 4560 0072 Brazil (toll free): 0800 887 0233 Bulgaria, Sofia: +359 (0) 2 491 6045 Bulgaria (toll free): 00800 111 4950 Cambodia, Phnom Penh: +855 23 965 723 Canada (toll free): 1 855 950 3717 Chile, Santiago: +56 (0) 2 2666 0696 Chile (toll free): 171 800 835 783 China (national): +400 613 8103 China, Beijing: +86 10 5667 0003 China, Shanghai: +86 21 2039 7081 Colombia, Bogota: +57 1 508 8137 Colombia (toll free): 01 800 755 0102 Costa Rica (toll free): 800 542 5328 Croatia (toll free): 0800 805 940 Cyprus (toll free): 800 97424 Czech Republic, Prague: +420 225 986 554 Czech Republic (toll free): 800 701 532 Denmark, Copenhagen: +45 32 72 78 10 Denmark (toll free): 80 70 35 86 Egypt (toll free): 0800 000 0593 Estonia, Tallinn: +372 622 6551 Estonia (toll free): 800 011 1589 Fiji (toll free): 00800 3322 Finland, Helsinki: +358 (0) 9 2310 1677 Finland (toll free): 0800 772 236 France, Paris: +33 (0) 1 70 37 16 56 France (toll free): 0800 946 531 France (national): 0811 655 100 France (national): 0821 231 671 Georgia, Tbilisi: +995 32 2 050 778 Germany, Frankfurt: +49 (0) 69 2222 10612 Germany, Munich: +49 (0) 89 2030 31207 Germany (national): 01801 003 899 Germany (toll free): 0800 588 9170 Greece, Athens: +30 211 181 3824 Greece (toll free): 00800 128 913 Hong Kong: +852 3018 9111 Hong Kong (toll free): 800 901 787 Hungary, Budapest: +36 1408 8953 Hungary (toll free): 068 001 9673 Iceland (toll free): 800 9847 India, Delhi: +91 11 6310 0268 India, Mumbai: +91 22 6310 0298 India, Chennai: +91 44 6310 0234 India, Bangalore: +91 80 6760 8755 India (toll free): 1800 3010 1582 Indonesia, Jakarta: +62 21 2188 9084 Indonesia (toll free): 007 803 321 8927 Ireland, Dublin: +353 (0) 1 526 9421 Ireland (national): 0818 270 271 Ireland (toll free): 1800 937 649 Ireland (national): 1890 907 630 Israel, Tel Aviv: +972 (0)3 721 7943 Israel (toll free): 1809 213 168 Italy, Milan: +39 02 3600 8006 Italy, Rome: +39 06 8750 0676 Italy (toll free): 800 146 094 Japan, Tokyo: +81 3 4560 1270 Japan, Osaka: +81 6 4560 2410 Japan (toll free): 0120 305 211 Japan (mobile): 0120 632 611 Japan (national): 0570 085 744 Jordan (toll free): 0800 22172 Kazakhstan (toll free): 8800 333 7554 Kenya, Nairobi: +254 (0)207 643 581 South Korea, Seoul: +82 (0) 2 6007 0079 South Korea (toll free): 00798 6136 1454 Kuwait (national): +965 2206 3002 Latvia, Riga: +371 6601 3627 Latvia (toll free): 8000 4418 Lithuania, Vilnius: +370 5205 5468 Lithuania (toll free): 8800 31449 Luxembourg: +352 2088 1749 Luxembourg (toll free): 800 28433 Macau (national): +853 6262 1676 Malaysia, Kuala Lumpur: +60 (0) 3 7724 8010 Malaysia (toll free): 1 800 816 152 Mexico, Guadalajara: +52 33 4162 4504 Mexico, Mexico City: +52 55 8421 0326 Mexico, Monterrey: +52 81 4162 5648 Mexico (toll free): 01 800 733 4102 Morocco, Casablanca: +212 (0) 520 48 0022 Morocco (toll free): 0800 091 296 Netherlands, Amsterdam: +31 (0) 20 716 8345 Netherlands (toll free): 0800 020 2597 New Zealand, Christchurch: +64 (0) 3 974 2596 New Zealand, Wellington: +64 (0) 4 909 4674 New Zealand, Auckland: +64 (0) 9 929 1825 New Zealand (toll free): 0800 452 947 Nigeria, Lagos: +234 1 277 3944 Norway, Oslo: +47 21 00 48 15 Norway (toll free): 800 56081 Oman (toll free): 800 77265 Pakistan, Islamabad: +92 5181 08863 Panama, Panama City: +507 8 335 913 Panama (toll free): 00800 223 1390 Peru, Lima: +51 (0) 1 700 9571 Philippines, Manila: +63 (0)2 395 3426 Philippines (toll free): 1 800 111 013 99 Poland, Warsaw: +48 22 295 3570 Poland (toll free): 00 800 121 4356 Portugal, Lisbon: +351 21 316 4093 Portugal (toll free): 800 784 442 Qatar (freephone): 00 800 100 491 Romania, Bucharest: +40 (0) 21 529 3992 Romania (toll free): 0800 801 035 Russia, Moscow: +7 495 646 9181 Russia (toll free): 8 800 500 9241 Saudi Arabia (toll free): 800 844 6641 Saudi Arabia (toll free): 800 850 0219 Serbia (toll free): 0800 190 712 Singapore: +65 6654 9112 Singapore (toll free): 800 616 3192 Slovakia, Bratislava: +421 (0)2 3321 5498 Slovakia (toll free): 0800 002 002 Slovenia, Ljubljana: +386 1600 8695 Slovenia (toll free): 0800 81193 South Africa, Johannesburg: +27 (0)11 589 8321 South Africa (toll free): 0800 999 434 Spain, Madrid: +34 91 114 6653 Spain, Barcelona: +34 93 800 1946 Spain (toll free): 900 828 035 Sri Lanka, Sri Lanka: +94 720 910 333 Sweden, Stockholm: +46 (0) 8 5065 3956 Sweden (toll free): 0200 125 588 Switzerland, Geneva: +41 (0) 22 595 4795 Switzerland, Zurich: +41 (0) 44 580 7207 Switzerland (toll free): 0800 740 360 Taiwan, Taipei: +886 (0) 2 2650 7329 Taiwan (toll free): 0800 666 596 Thailand, Bangkok: +66 (0) 2104 0761 Thailand (toll free): 001 800 6136 1473 Tunisia, Tunis: +216 31 378 101 Turkey, Istanbul: +90 212 375 50 49 Turkey (toll free): 00800 4488 26642 Ukraine (toll free): 0800 500 896 UAE (toll free): 8000 3570 2662 UK (03): +44 (0)330 336 6002 UK (toll free): 0800 358 6385 UK (national): 0844 473 5010 UK (national): 0845 545 0015 USA /Canada (toll free): 1-866-398-2885 Uruguay (toll free): 0004 019 0152 Venezuela, Caracas: +58 212 720 2164 Venezuela (toll free): 0 800 162 7451 Vietnam, Hanoi: +84 24 4458 3312 Vietnam, Ho Chi Minh: +84 28 4458 1322 Vietnam (toll free): 1800 9226 _______________________________________________ NCSG-FC mailing list NCSG-FC at lists.ncsg.is https://lists.ncsg.is/mailman/listinfo/ncsg-fc -------------- next part -------------- An HTML attachment was scrubbed... URL: From PolicyCalendar at icann.org Fri Feb 8 16:35:45 2019 From: PolicyCalendar at icann.org (ICANN Policy Calendar) Date: Fri, 8 Feb 2019 14:35:45 +0000 Subject: [NCSG-FC] NCSG Finance Committee Meeting on Tuesday 12 February 2019 at 1300 UTC Message-ID: <78d10c4614594e9daa757cc56bf975ee@PMBX112-W1-CA-1.PEXCH112.ICANN.ORG> Dear All, Please find participation details for the NCSG Finance Committee Meeting on Friday 08 February 2019 at 1300 UTC Adobe Connect: https://participate.icann.org/ncsg Time Zones: https://tinyurl.com/y7co9em9 Dial out request: please send an email to Maryam.bakoshi at icann.org off-list. Audio dial-in details below: [https://cobranding-pgi.s3.amazonaws.com/1/Logo1.png] You're invited. You've been invited to a GlobalMeet? audio meeting. Have the meeting call you. Click the Connect Me link below. No need to dial-in. Connect Me [go.conferencinghub.com] Not at your computer? You can join by dialing one of the access numbers below. Mobile: tel://16054755604,*,,9922790467# Phone Only Controls : https://go.conferencinghub.com/2xdh7 Access Number: 1-605-475-5604 Guest Passcode: 992 279 0467 Additional Access: USA: 1-605-475-5604 USA: 1-719-457-6209 Canada, Calgary: +1 403 407 5793 Canada, Montreal: +1 514 669 5928 Canada, Toronto: +1 647 426 9172 Canada, Vancouver: +1 604 222 7836 Argentina, Buenos Aires: +54 (0) 11 5172 6003 Argentina (toll free): 0800 800 1223 Australia, Sydney: +61 (0) 2 8017 6064 Australia, Melbourne: +61 (0) 3 8687 0553 Australia, Brisbane: +61 (0) 7 3015 0535 Australia (toll free): 1 800 804 786 Austria (toll free): 0800 070 981 Bahrain, Manama: +973 1619 8739 Bahrain (toll free): 800 04212 Belarus (toll free): 8 820 0011 0341 Belgium, Brussels: +32 (0) 2 400 6928 Belgium (toll free): 0800 39279 Bosnia and Herzegovina: +387 7031 1442 Brazil, Sao Paulo: +55 11 4935 7169 Brazil, Rio de Janeiro: +55 21 4560 0072 Brazil (toll free): 0800 887 0233 Bulgaria, Sofia: +359 (0) 2 491 6045 Bulgaria (toll free): 00800 111 4950 Cambodia, Phnom Penh: +855 23 965 723 Canada (toll free): 1 855 950 3717 Chile, Santiago: +56 (0) 2 2666 0696 Chile (toll free): 171 800 835 783 China (national): +400 613 8103 China, Beijing: +86 10 5667 0003 China, Shanghai: +86 21 2039 7081 Colombia, Bogota: +57 1 508 8137 Colombia (toll free): 01 800 755 0102 Costa Rica (toll free): 800 542 5328 Croatia (toll free): 0800 805 940 Cyprus (toll free): 800 97424 Czech Republic, Prague: +420 225 986 554 Czech Republic (toll free): 800 701 532 Denmark, Copenhagen: +45 32 72 78 10 Denmark (toll free): 80 70 35 86 Egypt (toll free): 0800 000 0593 Estonia, Tallinn: +372 622 6551 Estonia (toll free): 800 011 1589 Fiji (toll free): 00800 3322 Finland, Helsinki: +358 (0) 9 2310 1677 Finland (toll free): 0800 772 236 France, Paris: +33 (0) 1 70 37 16 56 France (toll free): 0800 946 531 France (national): 0811 655 100 France (national): 0821 231 671 Georgia, Tbilisi: +995 32 2 050 778 Germany, Frankfurt: +49 (0) 69 2222 10612 Germany, Munich: +49 (0) 89 2030 31207 Germany (national): 01801 003 899 Germany (toll free): 0800 588 9170 Greece, Athens: +30 211 181 3824 Greece (toll free): 00800 128 913 Hong Kong: +852 3018 9111 Hong Kong (toll free): 800 901 787 Hungary, Budapest: +36 1408 8953 Hungary (toll free): 068 001 9673 Iceland (toll free): 800 9847 India, Delhi: +91 11 6310 0268 India, Mumbai: +91 22 6310 0298 India, Chennai: +91 44 6310 0234 India, Bangalore: +91 80 6760 8755 India (toll free): 1800 3010 1582 Indonesia, Jakarta: +62 21 2188 9084 Indonesia (toll free): 007 803 321 8927 Ireland, Dublin: +353 (0) 1 526 9421 Ireland (national): 0818 270 271 Ireland (toll free): 1800 937 649 Ireland (national): 1890 907 630 Israel, Tel Aviv: +972 (0)3 721 7943 Israel (toll free): 1809 213 168 Italy, Milan: +39 02 3600 8006 Italy, Rome: +39 06 8750 0676 Italy (toll free): 800 146 094 Japan, Tokyo: +81 3 4560 1270 Japan, Osaka: +81 6 4560 2410 Japan (toll free): 0120 305 211 Japan (mobile): 0120 632 611 Japan (national): 0570 085 744 Jordan (toll free): 0800 22172 Kazakhstan (toll free): 8800 333 7554 Kenya, Nairobi: +254 (0)207 643 581 South Korea, Seoul: +82 (0) 2 6007 0079 South Korea (toll free): 00798 6136 1454 Kuwait (national): +965 2206 3002 Latvia, Riga: +371 6601 3627 Latvia (toll free): 8000 4418 Lithuania, Vilnius: +370 5205 5468 Lithuania (toll free): 8800 31449 Luxembourg: +352 2088 1749 Luxembourg (toll free): 800 28433 Macau (national): +853 6262 1676 Malaysia, Kuala Lumpur: +60 (0) 3 7724 8010 Malaysia (toll free): 1 800 816 152 Mexico, Guadalajara: +52 33 4162 4504 Mexico, Mexico City: +52 55 8421 0326 Mexico, Monterrey: +52 81 4162 5648 Mexico (toll free): 01 800 733 4102 Morocco, Casablanca: +212 (0) 520 48 0022 Morocco (toll free): 0800 091 296 Netherlands, Amsterdam: +31 (0) 20 716 8345 Netherlands (toll free): 0800 020 2597 New Zealand, Christchurch: +64 (0) 3 974 2596 New Zealand, Wellington: +64 (0) 4 909 4674 New Zealand, Auckland: +64 (0) 9 929 1825 New Zealand (toll free): 0800 452 947 Nigeria, Lagos: +234 1 277 3944 Norway, Oslo: +47 21 00 48 15 Norway (toll free): 800 56081 Oman (toll free): 800 77265 Pakistan, Islamabad: +92 5181 08863 Panama, Panama City: +507 8 335 913 Panama (toll free): 00800 223 1390 Peru, Lima: +51 (0) 1 700 9571 Philippines, Manila: +63 (0)2 395 3426 Philippines (toll free): 1 800 111 013 99 Poland, Warsaw: +48 22 295 3570 Poland (toll free): 00 800 121 4356 Portugal, Lisbon: +351 21 316 4093 Portugal (toll free): 800 784 442 Qatar (freephone): 00 800 100 491 Romania, Bucharest: +40 (0) 21 529 3992 Romania (toll free): 0800 801 035 Russia, Moscow: +7 495 646 9181 Russia (toll free): 8 800 500 9241 Saudi Arabia (toll free): 800 844 6641 Saudi Arabia (toll free): 800 850 0219 Serbia (toll free): 0800 190 712 Singapore: +65 6654 9112 Singapore (toll free): 800 616 3192 Slovakia, Bratislava: +421 (0)2 3321 5498 Slovakia (toll free): 0800 002 002 Slovenia, Ljubljana: +386 1600 8695 Slovenia (toll free): 0800 81193 South Africa, Johannesburg: +27 (0)11 589 8321 South Africa (toll free): 0800 999 434 Spain, Madrid: +34 91 114 6653 Spain, Barcelona: +34 93 800 1946 Spain (toll free): 900 828 035 Sri Lanka, Sri Lanka: +94 720 910 333 Sweden, Stockholm: +46 (0) 8 5065 3956 Sweden (toll free): 0200 125 588 Switzerland, Geneva: +41 (0) 22 595 4795 Switzerland, Zurich: +41 (0) 44 580 7207 Switzerland (toll free): 0800 740 360 Taiwan, Taipei: +886 (0) 2 2650 7329 Taiwan (toll free): 0800 666 596 Thailand, Bangkok: +66 (0) 2104 0761 Thailand (toll free): 001 800 6136 1473 Tunisia, Tunis: +216 31 378 101 Turkey, Istanbul: +90 212 375 50 49 Turkey (toll free): 00800 4488 26642 Ukraine (toll free): 0800 500 896 UAE (toll free): 8000 3570 2662 UK (03): +44 (0)330 336 6002 UK (toll free): 0800 358 6385 UK (national): 0844 473 5010 UK (national): 0845 545 0015 USA /Canada (toll free): 1-866-398-2885 Uruguay (toll free): 0004 019 0152 Venezuela, Caracas: +58 212 720 2164 Venezuela (toll free): 0 800 162 7451 Vietnam, Hanoi: +84 24 4458 3312 Vietnam, Ho Chi Minh: +84 28 4458 1322 Vietnam (toll free): 1800 9226 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 11418 bytes Desc: not available URL: From remmyn at gmail.com Fri Feb 8 16:57:13 2019 From: remmyn at gmail.com (Remmy Nweke) Date: Fri, 8 Feb 2019 15:57:13 +0100 Subject: [NCSG-FC] Fwd: **REMINDER**NCSG Finance Committee Meeting on Friday 08 February 2019 at 1400 UTC In-Reply-To: <309c348b-5dd4-0cf0-6f36-2c258d36964f@mail.utoronto.ca> References: <2008afb6c77c4413a78a7694dc12b376@PMBX112-W1-CA-1.PEXCH112.ICANN.ORG> <309c348b-5dd4-0cf0-6f36-2c258d36964f@mail.utoronto.ca> Message-ID: Sorry for the mix-up I this meeting is shifted till Tuesday next week. Regards Remmy On Fri, 8 Feb 2019, 3:35 p.m. Stephanie Perrin < stephanie.perrin at mail.utoronto.ca wrote: > Sorry I was late, we have also EPDP. It seems I went to the wrong adobe > connect, nobody is there?? > > Stephanie > On 2019-02-08 09:10, Thato Mfikwe wrote: > > Hi all, > > Just a friendly reminder that the FC meeting has started, pleasee let me > know if you cannot attend so that we can reschedule, thanks. > > Thato Mfikwe. > > ---------- Forwarded message --------- > From: ICANN Policy Calendar > Date: Fri, Feb 8, 2019 at 3:42 PM > Subject: [NCSG-FC] **REMINDER**NCSG Finance Committee Meeting on Friday 08 > February 2019 at 1400 UTC > To: NCSG Finance Committee , Stephanie Perrin < > stephanie.perrin at mail.utoronto.ca>, Maryam Bakoshi < > maryam.bakoshi at icann.org> > > > Dear All, > > > > ***REMINDER** * > > > Please find participation details for the *NCSG Finance Committee Meeting > on Friday 08 February 2019 at 1400 UTC* > > > *Adobe Connect*: https://participate.icann.org/ncsg > > > *Time Zones*: https://tinyurl.com/yce94nnc > > > *Dial out request*: please send an email to Maryam.bakoshi at icann.org > off-list. > > > *Audio dial-in details below:* > > > [image: https://cobranding-pgi.s3.amazonaws.com/1/Logo1.png] > > *You're invited.* > You've been invited to a GlobalMeet? audio meeting. > > *Have the meeting call you.* > Click the Connect Me link below. *No need to dial-in.* > > > > *Connect Me [go.conferencinghub.com] > * > > > > > *Not at your computer?* > You can join by dialing one of the access numbers below. > > > *Mobile:* > > tel://16054755604,*,,9922790467# > > *Phone Only Controls :* > > https://go.conferencinghub.com/2xdh7 > > *Access Number:* > > 1-605-475-5604 > > *Guest Passcode:* > > 992 279 0467 > > *Additional Access:* > > USA: > > 1-605-475-5604 > > USA: > > 1-719-457-6209 > > Canada, Calgary: > > +1 403 407 5793 > > Canada, Montreal: > > +1 514 669 5928 > > Canada, Toronto: > > +1 647 426 9172 > > Canada, Vancouver: > > +1 604 222 7836 > > Argentina, Buenos Aires: > > +54 (0) 11 5172 6003 > > Argentina (toll free): > > 0800 800 1223 > > Australia, Sydney: > > +61 (0) 2 8017 6064 > > Australia, Melbourne: > > +61 (0) 3 8687 0553 > > Australia, Brisbane: > > +61 (0) 7 3015 0535 > > Australia (toll free): > > 1 800 804 786 > > Austria (toll free): > > 0800 070 981 > > Bahrain, Manama: > > +973 1619 8739 > > Bahrain (toll free): > > 800 04212 > > Belarus (toll free): > > 8 820 0011 0341 > > Belgium, Brussels: > > +32 (0) 2 400 6928 > > Belgium (toll free): > > 0800 39279 > > Bosnia and Herzegovina: > > +387 7031 1442 > > Brazil, Sao Paulo: > > +55 11 4935 7169 > > Brazil, Rio de Janeiro: > > +55 21 4560 0072 > > Brazil (toll free): > > 0800 887 0233 > > Bulgaria, Sofia: > > +359 (0) 2 491 6045 > > Bulgaria (toll free): > > 00800 111 4950 > > Cambodia, Phnom Penh: > > +855 23 965 723 > > Canada (toll free): > > 1 855 950 3717 > > Chile, Santiago: > > +56 (0) 2 2666 0696 > > Chile (toll free): > > 171 800 835 783 > > China (national): > > +400 613 8103 > > China, Beijing: > > +86 10 5667 0003 > > China, Shanghai: > > +86 21 2039 7081 > > Colombia, Bogota: > > +57 1 508 8137 > > Colombia (toll free): > > 01 800 755 0102 > > Costa Rica (toll free): > > 800 542 5328 > > Croatia (toll free): > > 0800 805 940 > > Cyprus (toll free): > > 800 97424 > > Czech Republic, Prague: > > +420 225 986 554 > > Czech Republic (toll free): > > 800 701 532 > > Denmark, Copenhagen: > > +45 32 72 78 10 > > Denmark (toll free): > > 80 70 35 86 > > Egypt (toll free): > > 0800 000 0593 > > Estonia, Tallinn: > > +372 622 6551 > > Estonia (toll free): > > 800 011 1589 > > Fiji (toll free): > > 00800 3322 > > Finland, Helsinki: > > +358 (0) 9 2310 1677 > > Finland (toll free): > > 0800 772 236 > > France, Paris: > > +33 (0) 1 70 37 16 56 > > France (toll free): > > 0800 946 531 > > France (national): > > 0811 655 100 > > France (national): > > 0821 231 671 > > Georgia, Tbilisi: > > +995 32 2 050 778 > > Germany, Frankfurt: > > +49 (0) 69 2222 10612 > > Germany, Munich: > > +49 (0) 89 2030 31207 > > Germany (national): > > 01801 003 899 > > Germany (toll free): > > 0800 588 9170 > > Greece, Athens: > > +30 211 181 3824 > > Greece (toll free): > > 00800 128 913 > > Hong Kong: > > +852 3018 9111 > > Hong Kong (toll free): > > 800 901 787 > > Hungary, Budapest: > > +36 1408 8953 > > Hungary (toll free): > > 068 001 9673 > > Iceland (toll free): > > 800 9847 > > India, Delhi: > > +91 11 6310 0268 > > India, Mumbai: > > +91 22 6310 0298 > > India, Chennai: > > +91 44 6310 0234 > > India, Bangalore: > > +91 80 6760 8755 > > India (toll free): > > 1800 3010 1582 > > Indonesia, Jakarta: > > +62 21 2188 9084 > > Indonesia (toll free): > > 007 803 321 8927 > > Ireland, Dublin: > > +353 (0) 1 526 9421 > > Ireland (national): > > 0818 270 271 > > Ireland (toll free): > > 1800 937 649 > > Ireland (national): > > 1890 907 630 > > Israel, Tel Aviv: > > +972 (0)3 721 7943 > > Israel (toll free): > > 1809 213 168 > > Italy, Milan: > > +39 02 3600 8006 > > Italy, Rome: > > +39 06 8750 0676 > > Italy (toll free): > > 800 146 094 > > Japan, Tokyo: > > +81 3 4560 1270 > > Japan, Osaka: > > +81 6 4560 2410 > > Japan (toll free): > > 0120 305 211 > > Japan (mobile): > > 0120 632 611 > > Japan (national): > > 0570 085 744 > > Jordan (toll free): > > 0800 22172 > > Kazakhstan (toll free): > > 8800 333 7554 > > Kenya, Nairobi: > > +254 (0)207 643 581 > > South Korea, Seoul: > > +82 (0) 2 6007 0079 > > South Korea (toll free): > > 00798 6136 1454 > > Kuwait (national): > > +965 2206 3002 > > Latvia, Riga: > > +371 6601 3627 > > Latvia (toll free): > > 8000 4418 > > Lithuania, Vilnius: > > +370 5205 5468 > > Lithuania (toll free): > > 8800 31449 > > Luxembourg: > > +352 2088 1749 > > Luxembourg (toll free): > > 800 28433 > > Macau (national): > > +853 6262 1676 > > Malaysia, Kuala Lumpur: > > +60 (0) 3 7724 8010 > > Malaysia (toll free): > > 1 800 816 152 > > Mexico, Guadalajara: > > +52 33 4162 4504 > > Mexico, Mexico City: > > +52 55 8421 0326 > > Mexico, Monterrey: > > +52 81 4162 5648 > > Mexico (toll free): > > 01 800 733 4102 > > Morocco, Casablanca: > > +212 (0) 520 48 0022 > > Morocco (toll free): > > 0800 091 296 > > Netherlands, Amsterdam: > > +31 (0) 20 716 8345 > > Netherlands (toll free): > > 0800 020 2597 > > New Zealand, Christchurch: > > +64 (0) 3 974 2596 > > New Zealand, Wellington: > > +64 (0) 4 909 4674 > > New Zealand, Auckland: > > +64 (0) 9 929 1825 > > New Zealand (toll free): > > 0800 452 947 > > Nigeria, Lagos: > > +234 1 277 3944 > > Norway, Oslo: > > +47 21 00 48 15 > > Norway (toll free): > > 800 56081 > > Oman (toll free): > > 800 77265 > > Pakistan, Islamabad: > > +92 5181 08863 > > Panama, Panama City: > > +507 8 335 913 > > Panama (toll free): > > 00800 223 1390 > > Peru, Lima: > > +51 (0) 1 700 9571 > > Philippines, Manila: > > +63 (0)2 395 3426 > > Philippines (toll free): > > 1 800 111 013 99 > > Poland, Warsaw: > > +48 22 295 3570 > > Poland (toll free): > > 00 800 121 4356 > > Portugal, Lisbon: > > +351 21 316 4093 > > Portugal (toll free): > > 800 784 442 > > Qatar (freephone): > > 00 800 100 491 > > Romania, Bucharest: > > +40 (0) 21 529 3992 > > Romania (toll free): > > 0800 801 035 > > Russia, Moscow: > > +7 495 646 9181 > > Russia (toll free): > > 8 800 500 9241 > > Saudi Arabia (toll free): > > 800 844 6641 > > From bruna.mrtns at gmail.com Sat Feb 9 05:30:25 2019 From: bruna.mrtns at gmail.com (Bruna Martins dos Santos) Date: Sat, 9 Feb 2019 01:30:25 -0200 Subject: [NCSG-FC] Fwd: **REMINDER**NCSG Finance Committee Meeting on Friday 08 February 2019 at 1400 UTC In-Reply-To: <1d368246-7642-3f44-92da-6c12b888683b@mail.utoronto.ca> References: <2008afb6c77c4413a78a7694dc12b376@PMBX112-W1-CA-1.PEXCH112.ICANN.ORG> <309c348b-5dd4-0cf0-6f36-2c258d36964f@mail.utoronto.ca> <1d368246-7642-3f44-92da-6c12b888683b@mail.utoronto.ca> Message-ID: Apologies for not attending the meeting earlier. I spent the entire day (9 to 7) in meetings and was not able to connect. I hope the FC can provide a short summary of the discussions. Best, bruna Em sex, 8 de fev de 2019 ?s 12:59, Stephanie Perrin < stephanie.perrin at mail.utoronto.ca> escreveu: > No my fault, I am sorry I was too late. Will have to miss it on Tuesday, > have EPDP meeting... > > cheers Stephanie > On 2019-02-08 09:57, Remmy Nweke wrote: > > Sorry for the mix-up > I this meeting is shifted till Tuesday next week. > Regards > Remmy > > On Fri, 8 Feb 2019, 3:35 p.m. Stephanie Perrin < > stephanie.perrin at mail.utoronto.ca wrote: > >> Sorry I was late, we have also EPDP. It seems I went to the wrong adobe >> connect, nobody is there?? >> >> Stephanie >> On 2019-02-08 09:10, Thato Mfikwe wrote: >> >> Hi all, >> >> Just a friendly reminder that the FC meeting has started, pleasee let me >> know if you cannot attend so that we can reschedule, thanks. >> >> Thato Mfikwe. >> >> ---------- Forwarded message --------- >> From: ICANN Policy Calendar >> Date: Fri, Feb 8, 2019 at 3:42 PM >> Subject: [NCSG-FC] **REMINDER**NCSG Finance Committee Meeting on Friday >> 08 February 2019 at 1400 UTC >> To: NCSG Finance Committee , Stephanie Perrin < >> stephanie.perrin at mail.utoronto.ca>, Maryam Bakoshi < >> maryam.bakoshi at icann.org> >> >> >> Dear All, >> >> >> >> ***REMINDER** * >> >> >> Please find participation details for the *NCSG Finance Committee >> Meeting on Friday 08 February 2019 at 1400 UTC* >> >> >> *Adobe Connect*: https://participate.icann.org/ncsg >> >> >> *Time Zones*: https://tinyurl.com/yce94nnc >> >> >> *Dial out request*: please send an email to Maryam.bakoshi at icann.org >> off-list. >> >> >> *Audio dial-in details below:* >> >> >> [image: https://cobranding-pgi.s3.amazonaws.com/1/Logo1.png] >> >> *You're invited.* >> You've been invited to a GlobalMeet? audio meeting. >> >> *Have the meeting call you.* >> Click the Connect Me link below. *No need to dial-in.* >> >> >> >> *Connect Me [go.conferencinghub.com] >> * >> >> >> >> >> *Not at your computer?* >> You can join by dialing one of the access numbers below. >> >> >> *Mobile:* >> >> tel://16054755604,*,,9922790467# >> >> *Phone Only Controls :* >> >> https://go.conferencinghub.com/2xdh7 >> >> *Access Number:* >> >> 1-605-475-5604 >> >> *Guest Passcode:* >> >> 992 279 0467 >> >> *Additional Access:* >> >> USA: >> >> 1-605-475-5604 >> >> USA: >> >> 1-719-457-6209 >> >> Canada, Calgary: >> >> +1 403 407 5793 >> >> Canada, Montreal: >> >> +1 514 669 5928 >> >> Canada, Toronto: >> >> +1 647 426 9172 >> >> Canada, Vancouver: >> >> +1 604 222 7836 >> >> Argentina, Buenos Aires: >> >> +54 (0) 11 5172 6003 >> >> Argentina (toll free): >> >> 0800 800 1223 >> >> Australia, Sydney: >> >> +61 (0) 2 8017 6064 >> >> Australia, Melbourne: >> >> +61 (0) 3 8687 0553 >> >> Australia, Brisbane: >> >> +61 (0) 7 3015 0535 >> >> Australia (toll free): >> >> 1 800 804 786 >> >> Austria (toll free): >> >> 0800 070 981 >> >> Bahrain, Manama: >> >> +973 1619 8739 >> >> Bahrain (toll free): >> >> 800 04212 >> >> Belarus (toll free): >> >> 8 820 0011 0341 >> >> Belgium, Brussels: >> >> +32 (0) 2 400 6928 >> >> Belgium (toll free): >> >> 0800 39279 >> >> Bosnia and Herzegovina: >> >> +387 7031 1442 >> >> Brazil, Sao Paulo: >> >> +55 11 4935 7169 >> >> Brazil, Rio de Janeiro: >> >> +55 21 4560 0072 >> >> Brazil (toll free): >> >> 0800 887 0233 >> >> Bulgaria, Sofia: >> >> +359 (0) 2 491 6045 >> >> Bulgaria (toll free): >> >> 00800 111 4950 >> >> Cambodia, Phnom Penh: >> >> +855 23 965 723 >> >> Canada (toll free): >> >> 1 855 950 3717 >> >> Chile, Santiago: >> >> +56 (0) 2 2666 0696 >> >> Chile (toll free): >> >> 171 800 835 783 >> >> China (national): >> >> +400 613 8103 >> >> China, Beijing: >> >> +86 10 5667 0003 >> >> China, Shanghai: >> >> +86 21 2039 7081 >> >> Colombia, Bogota: >> >> +57 1 508 8137 >> >> Colombia (toll free): >> >> 01 800 755 0102 >> >> Costa Rica (toll free): >> >> 800 542 5328 >> >> Croatia (toll free): >> >> 0800 805 940 >> >> Cyprus (toll free): >> >> 800 97424 >> >> Czech Republic, Prague: >> >> +420 225 986 554 >> >> Czech Republic (toll free): >> >> 800 701 532 >> >> Denmark, Copenhagen: >> >> +45 32 72 78 10 >> >> Denmark (toll free): >> >> 80 70 35 86 >> >> Egypt (toll free): >> >> 0800 000 0593 >> >> Estonia, Tallinn: >> >> +372 622 6551 >> >> Estonia (toll free): >> >> 800 011 1589 >> >> Fiji (toll free): >> >> 00800 3322 >> >> Finland, Helsinki: >> >> +358 (0) 9 2310 1677 >> >> Finland (toll free): >> >> 0800 772 236 >> >> France, Paris: >> >> +33 (0) 1 70 37 16 56 >> >> France (toll free): >> >> 0800 946 531 >> >> France (national): >> >> 0811 655 100 >> >> France (national): >> >> 0821 231 671 >> >> Georgia, Tbilisi: >> >> +995 32 2 050 778 >> >> Germany, Frankfurt: >> >> +49 (0) 69 2222 10612 >> >> Germany, Munich: >> >> +49 (0) 89 2030 31207 >> >> Germany (national): >> >> 01801 003 899 >> >> Germany (toll free): >> >> 0800 588 9170 >> >> Greece, Athens: >> >> +30 211 181 3824 >> >> Greece (toll free): >> >> 00800 128 913 >> >> Hong Kong: >> >> +852 3018 9111 >> >> Hong Kong (toll free): >> >> 800 901 787 >> >> Hungary, Budapest: >> >> +36 1408 8953 >> >> Hungary (toll free): >> >> 068 001 9673 >> >> Iceland (toll free): >> >> 800 9847 >> >> India, Delhi: >> >> +91 11 6310 0268 >> >> India, Mumbai: >> >> +91 22 6310 0298 >> >> India, Chennai: >> >> +91 44 6310 0234 >> >> India, Bangalore: >> >> +91 80 6760 8755 >> >> India (toll free): >> >> 1800 3010 1582 >> >> Indonesia, Jakarta: >> >> +62 21 2188 9084 >> >> Indonesia (toll free): >> >> 007 803 321 8927 >> >> Ireland, Dublin: >> >> +353 (0) 1 526 9421 >> >> Ireland (national): >> >> 0818 270 271 >> >> Ireland (toll free): >> >> 1800 937 649 >> >> Ireland (national): >> >> 1890 907 630 >> >> Israel, Tel Aviv: >> >> +972 (0)3 721 7943 >> >> Israel (toll free): >> >> 1809 213 168 >> >> Italy, Milan: >> >> +39 02 3600 8006 >> >> Italy, Rome: >> >> +39 06 8750 0676 >> >> Italy (toll free): >> >> 800 146 094 >> >> Japan, Tokyo: >> >> +81 3 4560 1270 >> >> Japan, Osaka: >> >> +81 6 4560 2410 >> >> Japan (toll free): >> >> 0120 305 211 >> >> Japan (mobile): >> >> 0120 632 611 >> >> Japan (national): >> >> 0570 085 744 >> >> Jordan (toll free): >> >> 0800 22172 >> >> Kazakhstan (toll free): >> >> 8800 333 7554 >> >> Kenya, Nairobi: >> >> +254 (0)207 643 581 >> >> South Korea, Seoul: >> >> +82 (0) 2 6007 0079 >> >> South Korea (toll free): >> >> 00798 6136 1454 >> >> Kuwait (national): >> >> +965 2206 3002 >> >> Latvia, Riga: >> >> +371 6601 3627 >> >> Latvia (toll free): >> >> 8000 4418 >> >> Lithuania, Vilnius: >> >> +370 5205 5468 >> >> Lithuania (toll free): >> >> 8800 31449 >> >> Luxembourg: >> >> +352 2088 1749 >> >> Luxembourg (toll free): >> >> 800 28433 >> >> Macau (national): >> >> +853 6262 1676 >> >> Malaysia, Kuala Lumpur: >> >> +60 (0) 3 7724 8010 >> >> Malaysia (toll free): >> >> 1 800 816 152 >> >> Mexico, Guadalajara: >> >> +52 33 4162 4504 >> >> Mexico, Mexico City: >> >> +52 55 8421 0326 >> >> Mexico, Monterrey: >> >> +52 81 4162 5648 >> >> Mexico (toll free): >> >> 01 800 733 4102 >> >> Morocco, Casablanca: >> >> +212 (0) 520 48 0022 >> >> Morocco (toll free): >> >> 0800 091 296 >> >> Netherlands, Amsterdam: >> >> +31 (0) 20 716 8345 >> >> Netherlands (toll free): >> >> 0800 020 2597 >> >> New Zealand, Christchurch: >> >> +64 (0) 3 974 2596 >> >> New Zealand, Wellington: >> >> +64 (0) 4 909 4674 >> >> New Zealand, Auckland: >> >> +64 (0) 9 929 1825 >> >> New Zealand (toll free): >> >> 0800 452 947 >> >> Nigeria, Lagos: >> >> +234 1 277 3944 >> >> Norway, Oslo: >> >> +47 21 00 48 15 >> >> Norway (toll free): >> >> 800 56081 >> >> Oman (toll free): >> >> 800 77265 >> >> Pakistan, Islamabad: >> >> +92 5181 08863 >> >> Panama, Panama City: >> >> +507 8 335 913 >> >> Panama (toll free): >> >> 00800 223 1390 >> >> Peru, Lima: >> >> +51 (0) 1 700 9571 >> >> Philippines, Manila: >> >> +63 (0)2 395 3426 >> >> Philippines (toll free): >> >> 1 800 111 013 99 >> >> Poland, Warsaw: >> >> +48 22 295 3570 >> >> Poland (toll free): >> >> 00 800 121 4356 >> >> Portugal, Lisbon: >> >> +351 21 316 4093 >> >> Portugal (toll free): >> >> 800 784 442 >> >> Qatar (freephone): >> >> 00 800 100 491 >> >> Romania, Bucharest: >> >> +40 (0) 21 529 3992 >> >> Romania (toll free): >> >> 0800 801 035 >> >> Russia, Moscow: >> >> +7 495 646 9181 >> >> Russia (toll free): >> >> 8 800 500 9241 >> >> Saudi Arabia (toll free): >> >> 800 844 6641 >> >> wrote: > Dear Stephanie, > Thanks for your notes which is hereby acknowledged. > > Having gone through the trend and responses, I wish to sustain Thato's > position and responses and wish also to reiterate that there is no need to > spoil for war as none of the ABR is for any individual good but for the > betterment of NCSG in general. > > For now, we have only one chair and vice chair (secretariat). > > However, I see no reason for cancelling any ABR outside the fact of > alleged duplicate as explained by you on CIVI CRM and will suggest that FC > chair withdraw that one precisely. I must also confess, I am not aware it > has been covered in any other budget plan or line. > > Moving forward, we must take the two NCSG constituted Committees (PC and > FC) along as equal branches to make NCSG stand strong and encourage them to > deliver on their Charter-driven mandates. > > Apologies as you know they should have been discussed and Mr. Chair has > also apologised but I earnestly think the communication gap that exist > needs to be deliberately closed with your kind support and the whole EC. > > Like I noted earlier, every of the ABR were in good faith and were never > done to undermine your office or NCSG and hereby solicit your understanding. > > Please accept my highest regards and assurances. > ____ > REMMY NWEKE, mNGE, > Lead Strategist/Group Executive Editor, > DigitalSENSE Africa Media [*Multiple-award winning medium*] > (DigitalSENSE Business News > ; ITREALMS > , NaijaAgroNet > ) > Block F1, Shop 133 Moyosore Aboderin Plaza, Bolade Junction, Oshodi-Lagos > M: 234-8033592762, 8023122558, 8051000475, T: @ITRealms > > Author: A Decade of ICT Reportage in Nigeria > > > *2019 Nigeria DigitalSENSE Forum on IG4D & Nigeria IPv6 Roundtable > * > JOIN us!! > > *Vice President, African Civil Society on the Information Society (ACSIS > ) > > *NPOC FC Rep @ICANN Non-Commercial Stakeholders Group (NCSG)* > > _________________________________________________________________ > *Confidentiality Notice:* The information in this document and attachments > are confidential and may also be privileged information. It is intended > only for the use of the named recipient. Remmy Nweke does not accept legal > responsibility for the contents of this e-mail. If you are not the intended > recipient, please notify me immediately, then delete this document and do > not disclose the contents of this document to any other person, nor make > any copies. Violators may face court persecution. > > > > On Sun, Feb 10, 2019 at 6:31 PM Thato Mfikwe > wrote: > >> Hi Stepahnie, >> >> Thanks for your comments, please find my responses below. >> >> Thato Mfikwe. >> >> Dear Finance Committee Co-chairs: >> >> *1. The Finance committee has only 1 Chairperson and it has never agreed >> to having 2 co-chairs.* >> >> >> It has come to my attention that three ABRs were sent in to the process >> without my knowledge, and using my signature since I am responsible for the >> NCSG ABRs. >> https://community.icann.org/display/projfinadhocws/NCSG+-+FY20+Additional+Budget+Requests >> >> >> *2. I do not understand when you say your siganture was used because that >> would be fraudulent, so please elaborate what you mean because the ABRs >> were sent under the NCSG FC name not your name.* >> >> >> The Finance Committee is not a separate constituency, and at the moment >> it does not have the authority to act independently in this manner. Even >> if it did, such ABRs should have been discussed on the FC list. These >> had to be shared and discussed with the NCSG EC at a minimum, not sent in >> covertly. >> >> >> *3. The ABR process has been difficult to coordinate even after the FC >> developed a tem[plate it was not accepted and I was not aware that there is >> a standard pprocedure for submitting ABR (please share). I acknowlege that >> it was my mistake to submit without engaging the FC, which is one of the >> reasons why we were supposed to have a meeting last Friday to discuss all >> the mentioned ABRs, secondly, the ABR process was short and there was not >> sufficient time to discuss and submit on time but nonetheless, the FC >> discussed the need to attend ICANN meetings and participate in outreach >> efforts for NCSG. Currently there is no clear guideline on how ABRs should >> be submitted, unless I am missing something. On the issue of engagement >> with the EC, what other decisions need to be taken by the EC and what >> decisions does the FC or PC decide on? If no clarity is provided, then >> these issues will keep emerging from time to time.* >> >> *On the opposite, the decision to open a bank acount was not preceeded by >> FC engagement or collaboration, what makes this instance different.* >> >> >> Please explain what happened here.... I know I have been terribly busy, >> what with the EPDP, the RDS II review, the budget and various other >> comments. However, I don't think I have forgotten anything with respect to >> the ABRs, and I am pretty sure I did not know about these requests. >> >> The one for CIVICRM is totally counterproductive....the amounts are >> wrong, and since we now have this funding in the core budget in the amount >> of 20K, we do not need to ask for it in an ABR. >> >> >> *4. I was not aware that the CIVI CRM is part of ICANN core budget, so >> you may remove this ABR if that is the case. Anyway, amount were derived >> from the SLA and related documents, maybe there could have been an >> oversight.* >> >> >> Without discussing in detail the merit of these requests, I would like >> you to please withdraw them and ask them to be taken off the website by COB >> Monday. You cannot send things in in my name without consultation, because >> I take my responsibilities seriously. Furthermore, and now I am speaking >> to the merits of the requests, if seems to me they contradict our overall >> budget comments supporting restraint. The tone suggests that the Finance >> Committee does not trust leadership to manage the money that is entrusted >> to the NCSG, and that the Finance Committee needs to be enabled to step up >> and manage it. This reflects very badly on our stakeholder group, and is >> not a position I support, and not just because I am the current Chair....I >> do not see any evidence of financial mismanagement over the many years that >> NCUC has handled the only money we receive officially. Recent events in >> NPOC, I know very little about, but the money that caused the friction had >> nothing to do with the PIR funding, as far as I can ascertain. >> >> >> *5. Could you please kindly share how budget comments are contradicted by >> submitted ABRs by the FC? As mentioned no ABR was sent in your name. The FC >> is responsible for approving and authosing expenditure, everything done >> should be guided by the charter not trust on an individual. The FC has >> never said that it does not trust leadership, where is that coming from? >> Also please elaborate what yuou mean when saying the FC needs to be >> enabled? Is it currently disabled, if so how? Also be informed that the FC >> accounts for all monies received, irrespective of source, so inclusion is >> key in finance related decisions and actions* >> >> >> I am deeply sympathetic to the need for regional outreach and >> development, this is what is behind the security and human rights outreach >> request, but we should have discussed these additional requests to >> coordinate, and to get the facts straight. >> >> >> *6. I agree, we have been attempting to discuss fundraising issues >> without any progress in the last 12 months or so, and these discussions are >> also planned to take place with community members durng ICANN64. The >> charter also clearly states that the FC must develop and eploy a >> fundraising plan.* >> >> *7. Lastly, most of the things you outlined here were supposed to be >> discussed in the meeeting that never took place in order to ensure that we >> have a structured way of working because currently it seems like the FC has >> no clear guideline on how it should operate.* >> >> *8. Is there any decision that the FC can make independently or not? For >> instance, FC action plans,do they need approval from the EC, if so why is >> the NCSG treasure not seating in NCSG EC meetings because this is one of >> the reasons why the FC will always be seen as opposing decisions or acting >> in contrary because transparency within the EC leaves a lot to be desired >> in regard to the FC.* >> >> >> *9. I am still yet to remember any decision that was taken by the FC that >> was supported by the EC. I proposed the FC have a meeting next week, when >> you are available to put most these issues to rest. You may cancelthe CIVI >> CRM ABR only until the FC as agreed to removal of all submitted ABRs.* >> *My proposal, the current chair of NCSG needs to help bridge the >> communiacation and engagement gap that exists within the EC and the FC not >> further widen the gap by challenging or putting unncessary pressure. Also >> note that the FC does not have opportunity to travel and participate in >> ICANN meetings besides squatting for ICANN fellowships which are never >> guaranteed, thanks.* >> >> On Sat, Feb 9, 2019 at 11:18 PM Stephanie Perrin < >> stephanie.perrin at mail.utoronto.ca> wrote: >> >>> Dear Finance Committee Co-chairs: >>> >>> It has come to my attention that three ABRs were sent in to the process >>> without my knowledge, and using my signature since I am responsible for the >>> NCSG ABRs. >>> https://community.icann.org/display/projfinadhocws/NCSG+-+FY20+Additional+Budget+Requests >>> >>> The Finance Committee is not a separate constituency, and at the moment >>> it does not have the authority to act independently in this manner. Even >>> if it did, such ABRs should have been discussed on the FC list. These >>> had to be shared and discussed with the NCSG EC at a minimum, not sent in >>> covertly. >>> >>> Please explain what happened here.... I know I have been terribly busy, >>> what with the EPDP, the RDS II review, the budget and various other >>> comments. However, I don't think I have forgotten anything with respect to >>> the ABRs, and I am pretty sure I did not know about these requests. >>> >>> >>> The one for CIVICRM is totally counterproductive....the amounts are >>> wrong, and since we now have this funding in the core budget in the amount >>> of 20K, we do not need to ask for it in an ABR. >>> >>> Without discussing in detail the merit of these requests, I would like >>> you to please withdraw them and ask them to be taken off the website by COB >>> Monday. You cannot send things in in my name without consultation, because >>> I take my responsibilities seriously. Furthermore, and now I am speaking >>> to the merits of the requests, if seems to me they contradict our overall >>> budget comments supporting restraint. The tone suggests that the Finance >>> Committee does not trust leadership to manage the money that is entrusted >>> to the NCSG, and that the Finance Committee needs to be enabled to step up >>> and manage it. This reflects very badly on our stakeholder group, and is >>> not a position I support, and not just because I am the current Chair....I >>> do not see any evidence of financial mismanagement over the many years that >>> NCUC has handled the only money we receive officially. Recent events in >>> NPOC, I know very little about, but the money that caused the friction had >>> nothing to do with the PIR funding, as far as I can ascertain. >>> >>> I am deeply sympathetic to the need for regional outreach and >>> development, this is what is behind the security and human rights outreach >>> request, but we should have discussed these additional requests to >>> coordinate, and to get the facts straight. >>> >>> Kind regards, >>> >>> Stephanie Perrin >>> NCSG Chair >>> _______________________________________________ >>> NCSG-FC mailing list >>> NCSG-FC at lists.ncsg.is >>> https://lists.ncsg.is/mailman/listinfo/ncsg-fc >>> >> _______________________________________________ >> NCSG-FC mailing list >> NCSG-FC at lists.ncsg.is >> https://lists.ncsg.is/mailman/listinfo/ncsg-fc >> > _______________________________________________ > NCSG-FC mailing list > NCSG-FC at lists.ncsg.is > https://lists.ncsg.is/mailman/listinfo/ncsg-fc > -------------- next part -------------- An HTML attachment was scrubbed... URL: From thatomfikwe at gmail.com Mon Feb 11 04:14:18 2019 From: thatomfikwe at gmail.com (Thato Mfikwe) Date: Mon, 11 Feb 2019 04:14:18 +0200 Subject: [NCSG-FC] Urgent: NCSG ABRs In-Reply-To: References: Message-ID: Another clarity, when ABR swere submitted, they did not have they were not bearibg the NCSG Chairss name, not sure why the name was inserted. Will follow up. Thato Mfikwe. On Sat, Feb 9, 2019 at 11:18 PM Stephanie Perrin < stephanie.perrin at mail.utoronto.ca> wrote: > Dear Finance Committee Co-chairs: > > It has come to my attention that three ABRs were sent in to the process > without my knowledge, and using my signature since I am responsible for the > NCSG ABRs. > https://community.icann.org/display/projfinadhocws/NCSG+-+FY20+Additional+Budget+Requests > > The Finance Committee is not a separate constituency, and at the moment it > does not have the authority to act independently in this manner. Even if > it did, such ABRs should have been discussed on the FC list. These had > to be shared and discussed with the NCSG EC at a minimum, not sent in > covertly. > > Please explain what happened here.... I know I have been terribly busy, > what with the EPDP, the RDS II review, the budget and various other > comments. However, I don't think I have forgotten anything with respect to > the ABRs, and I am pretty sure I did not know about these requests. > > > The one for CIVICRM is totally counterproductive....the amounts are wrong, > and since we now have this funding in the core budget in the amount of 20K, > we do not need to ask for it in an ABR. > > Without discussing in detail the merit of these requests, I would like you > to please withdraw them and ask them to be taken off the website by COB > Monday. You cannot send things in in my name without consultation, because > I take my responsibilities seriously. Furthermore, and now I am speaking > to the merits of the requests, if seems to me they contradict our overall > budget comments supporting restraint. The tone suggests that the Finance > Committee does not trust leadership to manage the money that is entrusted > to the NCSG, and that the Finance Committee needs to be enabled to step up > and manage it. This reflects very badly on our stakeholder group, and is > not a position I support, and not just because I am the current Chair....I > do not see any evidence of financial mismanagement over the many years that > NCUC has handled the only money we receive officially. Recent events in > NPOC, I know very little about, but the money that caused the friction had > nothing to do with the PIR funding, as far as I can ascertain. > > I am deeply sympathetic to the need for regional outreach and development, > this is what is behind the security and human rights outreach request, but > we should have discussed these additional requests to coordinate, and to > get the facts straight. > > Kind regards, > > Stephanie Perrin > NCSG Chair > _______________________________________________ > NCSG-FC mailing list > NCSG-FC at lists.ncsg.is > https://lists.ncsg.is/mailman/listinfo/ncsg-fc > -------------- next part -------------- An HTML attachment was scrubbed... URL: From bruna.mrtns at gmail.com Mon Feb 11 04:51:45 2019 From: bruna.mrtns at gmail.com (Bruna Martins dos Santos) Date: Mon, 11 Feb 2019 00:51:45 -0200 Subject: [NCSG-FC] Urgent: NCSG ABRs In-Reply-To: References: Message-ID: Dear all, Thanks for the email, Steph. I am still surprised by the lack of transparency regarding the submission of such ABRs. Especially because, as you mentioned, the FC is indeed not a constituency and we never had a committee like the policy committee or any of the ECs submitting requests under our stakeholder group without notifying the members or the chair, who often is the person who responds for the constituency of the stakeholder group. Thato and Remmy, it is actually a shock to me that you are alleging that there is no clear procedure for submitting ABRs - once you click on the submission form you can see that you need to mention the chair's name and both me and Stephanie sent in consultations to our lists looking for suggestions to be discussed with the ec - this was very clear in my email. To consider that the FC considered it ok to submit an ABR without notifying the chairs is appaling. I dont think its clear to the FC that we all want to work together in identifying possible areas for outreaching and fundraising, and I mentioned it to Thato in the call we had a few weeks ago. But in order for us to provide full support to the FCs activities we need to (a) understand your goals and (b) develop an strategic plan and lastly (c) be able to fully trust in each other. When we learn that the FC has submitted 3 ABRs without even letting the SG know, the attitude makes it seem as if you both dont trust us. Also important to note that the template developed by the FC to collect ABRs suggestions was not adopted especially in light of the deadline, the proposal only got to us 2 weeks before the deadline - a period in which the proposals should be taking form before us chairs reporting them to the community and submitting. And in my emails about this I explained that this could be a solution for next years submissions, bc we would have time to improve the forms and submission process. I can say I am actually glad we did not accept the template, because it could have resulted in many more submissions without any of the NCSG and its constituencies chairs being notified. Having said that, I support Stephanie's request for the withdrawal of such ABRs, they look unfinished and reflect very poorly on NCSG and its constituencies. best, bruna Em seg, 11 de fev de 2019 ?s 00:14, Thato Mfikwe escreveu: > Another clarity, when ABR swere submitted, they did not have they were not > bearibg the NCSG Chairss name, not sure why the name was inserted. Will > follow up. > > Thato Mfikwe. > > On Sat, Feb 9, 2019 at 11:18 PM Stephanie Perrin < > stephanie.perrin at mail.utoronto.ca> wrote: > >> Dear Finance Committee Co-chairs: >> >> It has come to my attention that three ABRs were sent in to the process >> without my knowledge, and using my signature since I am responsible for the >> NCSG ABRs. >> https://community.icann.org/display/projfinadhocws/NCSG+-+FY20+Additional+Budget+Requests >> >> The Finance Committee is not a separate constituency, and at the moment >> it does not have the authority to act independently in this manner. Even >> if it did, such ABRs should have been discussed on the FC list. These >> had to be shared and discussed with the NCSG EC at a minimum, not sent in >> covertly. >> >> Please explain what happened here.... I know I have been terribly busy, >> what with the EPDP, the RDS II review, the budget and various other >> comments. However, I don't think I have forgotten anything with respect to >> the ABRs, and I am pretty sure I did not know about these requests. >> >> >> The one for CIVICRM is totally counterproductive....the amounts are >> wrong, and since we now have this funding in the core budget in the amount >> of 20K, we do not need to ask for it in an ABR. >> >> Without discussing in detail the merit of these requests, I would like >> you to please withdraw them and ask them to be taken off the website by COB >> Monday. You cannot send things in in my name without consultation, because >> I take my responsibilities seriously. Furthermore, and now I am speaking >> to the merits of the requests, if seems to me they contradict our overall >> budget comments supporting restraint. The tone suggests that the Finance >> Committee does not trust leadership to manage the money that is entrusted >> to the NCSG, and that the Finance Committee needs to be enabled to step up >> and manage it. This reflects very badly on our stakeholder group, and is >> not a position I support, and not just because I am the current Chair....I >> do not see any evidence of financial mismanagement over the many years that >> NCUC has handled the only money we receive officially. Recent events in >> NPOC, I know very little about, but the money that caused the friction had >> nothing to do with the PIR funding, as far as I can ascertain. >> >> I am deeply sympathetic to the need for regional outreach and >> development, this is what is behind the security and human rights outreach >> request, but we should have discussed these additional requests to >> coordinate, and to get the facts straight. >> >> Kind regards, >> >> Stephanie Perrin >> NCSG Chair >> _______________________________________________ >> NCSG-FC mailing list >> NCSG-FC at lists.ncsg.is >> https://lists.ncsg.is/mailman/listinfo/ncsg-fc >> > _______________________________________________ > NCSG-FC mailing list > NCSG-FC at lists.ncsg.is > https://lists.ncsg.is/mailman/listinfo/ncsg-fc > -- *Bruna Martins dos Santos * Skype ID: bruna.martinsantos @boomartins -------------- next part -------------- An HTML attachment was scrubbed... URL: From PolicyCalendar at icann.org Mon Feb 11 15:04:04 2019 From: PolicyCalendar at icann.org (ICANN Policy Calendar) Date: Mon, 11 Feb 2019 13:04:04 +0000 Subject: [NCSG-FC] Canceled: NCSG Finance Committee Meeting on Tuesday 12 February 2019 at 1300 UTC Message-ID: Dear All, Please find participation details for the NCSG Finance Committee Meeting on Friday 08 February 2019 at 1300 UTC Adobe Connect: https://participate.icann.org/ncsg Time Zones: https://tinyurl.com/y7co9em9 Dial out request: please send an email to Maryam.bakoshi at icann.org off-list. Audio dial-in details below: [https://cobranding-pgi.s3.amazonaws.com/1/Logo1.png] You're invited. You've been invited to a GlobalMeet? audio meeting. Have the meeting call you. Click the Connect Me link below. No need to dial-in. Connect Me [go.conferencinghub.com] Not at your computer? You can join by dialing one of the access numbers below. Mobile: tel://16054755604,*,,9922790467# Phone Only Controls : https://go.conferencinghub.com/2xdh7 Access Number: 1-605-475-5604 Guest Passcode: 992 279 0467 Additional Access: USA: 1-605-475-5604 USA: 1-719-457-6209 Canada, Calgary: +1 403 407 5793 Canada, Montreal: +1 514 669 5928 Canada, Toronto: +1 647 426 9172 Canada, Vancouver: +1 604 222 7836 Argentina, Buenos Aires: +54 (0) 11 5172 6003 Argentina (toll free): 0800 800 1223 Australia, Sydney: +61 (0) 2 8017 6064 Australia, Melbourne: +61 (0) 3 8687 0553 Australia, Brisbane: +61 (0) 7 3015 0535 Australia (toll free): 1 800 804 786 Austria (toll free): 0800 070 981 Bahrain, Manama: +973 1619 8739 Bahrain (toll free): 800 04212 Belarus (toll free): 8 820 0011 0341 Belgium, Brussels: +32 (0) 2 400 6928 Belgium (toll free): 0800 39279 Bosnia and Herzegovina: +387 7031 1442 Brazil, Sao Paulo: +55 11 4935 7169 Brazil, Rio de Janeiro: +55 21 4560 0072 Brazil (toll free): 0800 887 0233 Bulgaria, Sofia: +359 (0) 2 491 6045 Bulgaria (toll free): 00800 111 4950 Cambodia, Phnom Penh: +855 23 965 723 Canada (toll free): 1 855 950 3717 Chile, Santiago: +56 (0) 2 2666 0696 Chile (toll free): 171 800 835 783 China (national): +400 613 8103 China, Beijing: +86 10 5667 0003 China, Shanghai: +86 21 2039 7081 Colombia, Bogota: +57 1 508 8137 Colombia (toll free): 01 800 755 0102 Costa Rica (toll free): 800 542 5328 Croatia (toll free): 0800 805 940 Cyprus (toll free): 800 97424 Czech Republic, Prague: +420 225 986 554 Czech Republic (toll free): 800 701 532 Denmark, Copenhagen: +45 32 72 78 10 Denmark (toll free): 80 70 35 86 Egypt (toll free): 0800 000 0593 Estonia, Tallinn: +372 622 6551 Estonia (toll free): 800 011 1589 Fiji (toll free): 00800 3322 Finland, Helsinki: +358 (0) 9 2310 1677 Finland (toll free): 0800 772 236 France, Paris: +33 (0) 1 70 37 16 56 France (toll free): 0800 946 531 France (national): 0811 655 100 France (national): 0821 231 671 Georgia, Tbilisi: +995 32 2 050 778 Germany, Frankfurt: +49 (0) 69 2222 10612 Germany, Munich: +49 (0) 89 2030 31207 Germany (national): 01801 003 899 Germany (toll free): 0800 588 9170 Greece, Athens: +30 211 181 3824 Greece (toll free): 00800 128 913 Hong Kong: +852 3018 9111 Hong Kong (toll free): 800 901 787 Hungary, Budapest: +36 1408 8953 Hungary (toll free): 068 001 9673 Iceland (toll free): 800 9847 India, Delhi: +91 11 6310 0268 India, Mumbai: +91 22 6310 0298 India, Chennai: +91 44 6310 0234 India, Bangalore: +91 80 6760 8755 India (toll free): 1800 3010 1582 Indonesia, Jakarta: +62 21 2188 9084 Indonesia (toll free): 007 803 321 8927 Ireland, Dublin: +353 (0) 1 526 9421 Ireland (national): 0818 270 271 Ireland (toll free): 1800 937 649 Ireland (national): 1890 907 630 Israel, Tel Aviv: +972 (0)3 721 7943 Israel (toll free): 1809 213 168 Italy, Milan: +39 02 3600 8006 Italy, Rome: +39 06 8750 0676 Italy (toll free): 800 146 094 Japan, Tokyo: +81 3 4560 1270 Japan, Osaka: +81 6 4560 2410 Japan (toll free): 0120 305 211 Japan (mobile): 0120 632 611 Japan (national): 0570 085 744 Jordan (toll free): 0800 22172 Kazakhstan (toll free): 8800 333 7554 Kenya, Nairobi: +254 (0)207 643 581 South Korea, Seoul: +82 (0) 2 6007 0079 South Korea (toll free): 00798 6136 1454 Kuwait (national): +965 2206 3002 Latvia, Riga: +371 6601 3627 Latvia (toll free): 8000 4418 Lithuania, Vilnius: +370 5205 5468 Lithuania (toll free): 8800 31449 Luxembourg: +352 2088 1749 Luxembourg (toll free): 800 28433 Macau (national): +853 6262 1676 Malaysia, Kuala Lumpur: +60 (0) 3 7724 8010 Malaysia (toll free): 1 800 816 152 Mexico, Guadalajara: +52 33 4162 4504 Mexico, Mexico City: +52 55 8421 0326 Mexico, Monterrey: +52 81 4162 5648 Mexico (toll free): 01 800 733 4102 Morocco, Casablanca: +212 (0) 520 48 0022 Morocco (toll free): 0800 091 296 Netherlands, Amsterdam: +31 (0) 20 716 8345 Netherlands (toll free): 0800 020 2597 New Zealand, Christchurch: +64 (0) 3 974 2596 New Zealand, Wellington: +64 (0) 4 909 4674 New Zealand, Auckland: +64 (0) 9 929 1825 New Zealand (toll free): 0800 452 947 Nigeria, Lagos: +234 1 277 3944 Norway, Oslo: +47 21 00 48 15 Norway (toll free): 800 56081 Oman (toll free): 800 77265 Pakistan, Islamabad: +92 5181 08863 Panama, Panama City: +507 8 335 913 Panama (toll free): 00800 223 1390 Peru, Lima: +51 (0) 1 700 9571 Philippines, Manila: +63 (0)2 395 3426 Philippines (toll free): 1 800 111 013 99 Poland, Warsaw: +48 22 295 3570 Poland (toll free): 00 800 121 4356 Portugal, Lisbon: +351 21 316 4093 Portugal (toll free): 800 784 442 Qatar (freephone): 00 800 100 491 Romania, Bucharest: +40 (0) 21 529 3992 Romania (toll free): 0800 801 035 Russia, Moscow: +7 495 646 9181 Russia (toll free): 8 800 500 9241 Saudi Arabia (toll free): 800 844 6641 Saudi Arabia (toll free): 800 850 0219 Serbia (toll free): 0800 190 712 Singapore: +65 6654 9112 Singapore (toll free): 800 616 3192 Slovakia, Bratislava: +421 (0)2 3321 5498 Slovakia (toll free): 0800 002 002 Slovenia, Ljubljana: +386 1600 8695 Slovenia (toll free): 0800 81193 South Africa, Johannesburg: +27 (0)11 589 8321 South Africa (toll free): 0800 999 434 Spain, Madrid: +34 91 114 6653 Spain, Barcelona: +34 93 800 1946 Spain (toll free): 900 828 035 Sri Lanka, Sri Lanka: +94 720 910 333 Sweden, Stockholm: +46 (0) 8 5065 3956 Sweden (toll free): 0200 125 588 Switzerland, Geneva: +41 (0) 22 595 4795 Switzerland, Zurich: +41 (0) 44 580 7207 Switzerland (toll free): 0800 740 360 Taiwan, Taipei: +886 (0) 2 2650 7329 Taiwan (toll free): 0800 666 596 Thailand, Bangkok: +66 (0) 2104 0761 Thailand (toll free): 001 800 6136 1473 Tunisia, Tunis: +216 31 378 101 Turkey, Istanbul: +90 212 375 50 49 Turkey (toll free): 00800 4488 26642 Ukraine (toll free): 0800 500 896 UAE (toll free): 8000 3570 2662 UK (03): +44 (0)330 336 6002 UK (toll free): 0800 358 6385 UK (national): 0844 473 5010 UK (national): 0845 545 0015 USA /Canada (toll free): 1-866-398-2885 Uruguay (toll free): 0004 019 0152 Venezuela, Caracas: +58 212 720 2164 Venezuela (toll free): 0 800 162 7451 Vietnam, Hanoi: +84 24 4458 3312 Vietnam, Ho Chi Minh: +84 28 4458 1322 Vietnam (toll free): 1800 9226 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 10197 bytes Desc: not available URL: From thatomfikwe at gmail.com Mon Feb 11 15:05:27 2019 From: thatomfikwe at gmail.com (Thato Mfikwe) Date: Mon, 11 Feb 2019 15:05:27 +0200 Subject: [NCSG-FC] Urgent: NCSG ABRs In-Reply-To: References: Message-ID: Hi all, I requested Maryam to remove all ABRs subnitted by the FC as per the request from the NCUC and NCSG chairs. The lack of communication is becoming a serious problem, as I dont remember seeing any call for ABR submissions on the NCSG mailing list and last year it was still not clear how ABRs will be subbmitted. The only thing solicited this year was just community comments not participation. There was still no discussion within the FC on submitted ABRs? We must be objective in our critism. It is only an assumption or excuse that, "had the ABR template been acceppted, then it means all requests submitted were not going to be discussed with Chairs or ECs", because the discussion was about to be made public before it got rejected by 2 chairs at FC level, there was no intend to faciltate community submissions single handedly, the proceess was intended to be inclusive as that is how it started off. If nobody is getting joy or gaining trust from FC activities and actions, then it would be proper to get a clear recommendation on what needs to be done to further prevent this problems from reoccuring. Anyway this is the first incident of the FC where something was submitted without consultation, but if this warrants action then I do not see the reason why we should be throwing words around as apposed to making recommendations and taking action. Is the FC that horrible, if so, what do you recommend? NOTE: The FC values inputs from observers, although decisions and voting is made by the FC members themselves according to the charter. My action as per your recommendation: I removed the ABRs, so what other change do you wish to see happen? Thato Mfikwe. On Mon, Feb 11, 2019 at 4:52 AM Bruna Martins dos Santos < bruna.mrtns at gmail.com> wrote: > Dear all, > > Thanks for the email, Steph. I am still surprised by the lack of > transparency regarding the submission of such ABRs. > > Especially because, as you mentioned, the FC is indeed not a constituency > and we never had a committee like the policy committee or any of the ECs > submitting requests under our stakeholder group without notifying the > members or the chair, who often is the person who responds for the > constituency of the stakeholder group. > > Thato and Remmy, it is actually a shock to me that you are alleging that > there is no clear procedure for submitting ABRs - once you click on the > submission form you can see that you need to mention the chair's name and > both me and Stephanie sent in consultations to our lists looking for > suggestions to be discussed with the ec - this was very clear in my email. > To consider that the FC considered it ok to submit an ABR without notifying > the chairs is appaling. > > I dont think its clear to the FC that we all want to work together in > identifying possible areas for outreaching and fundraising, and I mentioned > it to Thato in the call we had a few weeks ago. But in order for us to > provide full support to the FCs activities we need to (a) understand your > goals and (b) develop an strategic plan and lastly (c) be able to fully > trust in each other. When we learn that the FC has submitted 3 ABRs without > even letting the SG know, the attitude makes it seem as if you both dont > trust us. > > Also important to note that the template developed by the FC to collect > ABRs suggestions was not adopted especially in light of the deadline, the > proposal only got to us 2 weeks before the deadline - a period in which the > proposals should be taking form before us chairs reporting them to the > community and submitting. And in my emails about this I explained that this > could be a solution for next years submissions, bc we would have time to > improve the forms and submission process. I can say I am actually glad we > did not accept the template, because it could have resulted in many more > submissions without any of the NCSG and its constituencies chairs being > notified. > > Having said that, I support Stephanie's request for the withdrawal of such > ABRs, they look unfinished and reflect very poorly on NCSG and its > constituencies. > > best, > bruna > > > > > Em seg, 11 de fev de 2019 ?s 00:14, Thato Mfikwe > escreveu: > >> Another clarity, when ABR swere submitted, they did not have they were >> not bearibg the NCSG Chairss name, not sure why the name was inserted. >> Will follow up. >> >> Thato Mfikwe. >> >> On Sat, Feb 9, 2019 at 11:18 PM Stephanie Perrin < >> stephanie.perrin at mail.utoronto.ca> wrote: >> >>> Dear Finance Committee Co-chairs: >>> >>> It has come to my attention that three ABRs were sent in to the process >>> without my knowledge, and using my signature since I am responsible for the >>> NCSG ABRs. >>> https://community.icann.org/display/projfinadhocws/NCSG+-+FY20+Additional+Budget+Requests >>> >>> The Finance Committee is not a separate constituency, and at the moment >>> it does not have the authority to act independently in this manner. Even >>> if it did, such ABRs should have been discussed on the FC list. These >>> had to be shared and discussed with the NCSG EC at a minimum, not sent in >>> covertly. >>> >>> Please explain what happened here.... I know I have been terribly busy, >>> what with the EPDP, the RDS II review, the budget and various other >>> comments. However, I don't think I have forgotten anything with respect to >>> the ABRs, and I am pretty sure I did not know about these requests. >>> >>> >>> The one for CIVICRM is totally counterproductive....the amounts are >>> wrong, and since we now have this funding in the core budget in the amount >>> of 20K, we do not need to ask for it in an ABR. >>> >>> Without discussing in detail the merit of these requests, I would like >>> you to please withdraw them and ask them to be taken off the website by COB >>> Monday. You cannot send things in in my name without consultation, because >>> I take my responsibilities seriously. Furthermore, and now I am speaking >>> to the merits of the requests, if seems to me they contradict our overall >>> budget comments supporting restraint. The tone suggests that the Finance >>> Committee does not trust leadership to manage the money that is entrusted >>> to the NCSG, and that the Finance Committee needs to be enabled to step up >>> and manage it. This reflects very badly on our stakeholder group, and is >>> not a position I support, and not just because I am the current Chair....I >>> do not see any evidence of financial mismanagement over the many years that >>> NCUC has handled the only money we receive officially. Recent events in >>> NPOC, I know very little about, but the money that caused the friction had >>> nothing to do with the PIR funding, as far as I can ascertain. >>> >>> I am deeply sympathetic to the need for regional outreach and >>> development, this is what is behind the security and human rights outreach >>> request, but we should have discussed these additional requests to >>> coordinate, and to get the facts straight. >>> >>> Kind regards, >>> >>> Stephanie Perrin >>> NCSG Chair >>> _______________________________________________ >>> NCSG-FC mailing list >>> NCSG-FC at lists.ncsg.is >>> https://lists.ncsg.is/mailman/listinfo/ncsg-fc >>> >> _______________________________________________ >> NCSG-FC mailing list >> NCSG-FC at lists.ncsg.is >> https://lists.ncsg.is/mailman/listinfo/ncsg-fc >> > > > -- > *Bruna Martins dos Santos * > > Skype ID: bruna.martinsantos > @boomartins > _______________________________________________ > NCSG-FC mailing list > NCSG-FC at lists.ncsg.is > https://lists.ncsg.is/mailman/listinfo/ncsg-fc > -------------- next part -------------- An HTML attachment was scrubbed... URL: From maryam.bakoshi at icann.org Mon Feb 11 22:46:08 2019 From: maryam.bakoshi at icann.org (Maryam Bakoshi) Date: Mon, 11 Feb 2019 20:46:08 +0000 Subject: [NCSG-FC] URGENT - Doodle Poll: NCSG FC Meeting Message-ID: <27726D8B-0B75-4F10-9F31-37930DC36658@icann.org> Dear All, Please complete the doodle poll below to determine a date/time for NCSG GC call. https://doodle.com/poll/kryppns3xxp2apnq Please be so kind as to complete the doodle poll as soon as possible. -- Many thanks, Maryam Bakoshi | SO/AC Collaboration Services Sr. Coordinator ICANN | Internet Corporation got Assigned Names and Numbers S: Maryam.bakoshi.icann | T: +44 7846 471777 -------------- next part -------------- An HTML attachment was scrubbed... URL: From remmyn at gmail.com Tue Feb 12 00:20:27 2019 From: remmyn at gmail.com (Remmy Nweke) Date: Mon, 11 Feb 2019 23:20:27 +0100 Subject: [NCSG-FC] URGENT - Doodle Poll: NCSG FC Meeting In-Reply-To: <27726D8B-0B75-4F10-9F31-37930DC36658@icann.org> References: <27726D8B-0B75-4F10-9F31-37930DC36658@icann.org> Message-ID: Thanks Done ____ REMMY NWEKE, mNGE, Lead Strategist/Group Executive Editor, DigitalSENSE Africa Media [*Multiple-award winning medium*] (DigitalSENSE Business News ; ITREALMS , NaijaAgroNet ) Block F1, Shop 133 Moyosore Aboderin Plaza, Bolade Junction, Oshodi-Lagos M: 234-8033592762, 8023122558, 8051000475, T: @ITRealms Author: A Decade of ICT Reportage in Nigeria *2019 Nigeria DigitalSENSE Forum on IG4D & Nigeria IPv6 Roundtable * JOIN us!! *Vice President, African Civil Society on the Information Society (ACSIS ) *NPOC FC Rep @ICANN Non-Commercial Stakeholders Group (NCSG)* _________________________________________________________________ *Confidentiality Notice:* The information in this document and attachments are confidential and may also be privileged information. It is intended only for the use of the named recipient. Remmy Nweke does not accept legal responsibility for the contents of this e-mail. If you are not the intended recipient, please notify me immediately, then delete this document and do not disclose the contents of this document to any other person, nor make any copies. Violators may face court persecution. On Mon, Feb 11, 2019 at 9:46 PM Maryam Bakoshi wrote: > Dear All, > > > > Please complete the doodle poll below to determine a date/time for NCSG GC > call. > > > > https://doodle.com/poll/kryppns3xxp2apnq > > > > Please be so kind as to complete the doodle poll as soon as possible. > > > > -- > > Many thanks, > > > > *Maryam Bakoshi* | SO/AC Collaboration Services Sr. Coordinator > > *ICANN* | Internet Corporation got Assigned Names and Numbers > > *S*: Maryam.bakoshi.icann | *T*: +44 7846 471777 > > > _______________________________________________ > NCSG-FC mailing list > NCSG-FC at lists.ncsg.is > https://lists.ncsg.is/mailman/listinfo/ncsg-fc > -------------- next part -------------- An HTML attachment was scrubbed... URL: From remmyn at gmail.com Tue Feb 12 02:01:51 2019 From: remmyn at gmail.com (Remmy Nweke) Date: Tue, 12 Feb 2019 01:01:51 +0100 Subject: [NCSG-FC] Urgent: NCSG ABRs In-Reply-To: References: Message-ID: Thanks Thato for further clarification. Dear all, I am sure by now it's obvious there is no perfidious intended, it's all for betterment of NCSG and I am sure better if not improved strategy will soon emerge. I wish to sincerely apologize once again to the chair @Stephanie for the insertion of her name in one of the ABRs. I, like Thato was not privy to that and anyone in your kind of situation should have been alarmed as well among other popup issues thereof. Hope our apologies on that mixup will be considered for acceptance. Thanks. Like noted earlier, we must do something to strengthen FC and NCSG excom communication moving forward and possibly consider inclusion of reps to their respective constituencies and even have joint session even twice a year or quarterly pending when Communication channels are strengthened. I thank you all for your understanding. Regards Remmy On Mon, 11 Feb 2019, 2:05 p.m. Thato Mfikwe Hi all, > > I requested Maryam to remove all ABRs subnitted by the FC as per the > request from the NCUC and NCSG chairs. > > The lack of communication is becoming a serious problem, as I dont > remember seeing any call for ABR submissions on the NCSG mailing list and > last year it was still not clear how ABRs will be subbmitted. The only > thing solicited this year was just community comments not participation. > > There was still no discussion within the FC on submitted ABRs? We must be > objective in our critism. > > It is only an assumption or excuse that, "had the ABR template been > acceppted, then it means all requests submitted were not going to be > discussed with Chairs or ECs", because the discussion was about to be made > public before it got rejected by 2 chairs at FC level, there was no intend > to faciltate community submissions single handedly, the proceess was > intended to be inclusive as that is how it started off. > > If nobody is getting joy or gaining trust from FC activities and actions, > then it would be proper to get a clear recommendation on what needs to be > done to further prevent this problems from reoccuring. Anyway this is the > first incident of the FC where something was submitted without > consultation, but if this warrants action then I do not see the reason why > we should be throwing words around as apposed to making recommendations and > taking action. Is the FC that horrible, if so, what do you recommend? > > NOTE: The FC values inputs from observers, although decisions and voting > is made by the FC members themselves according to the charter. > > My action as per your recommendation: I removed the ABRs, so what other > change do you wish to see happen? > > Thato Mfikwe. > > On Mon, Feb 11, 2019 at 4:52 AM Bruna Martins dos Santos < > bruna.mrtns at gmail.com> wrote: > >> Dear all, >> >> Thanks for the email, Steph. I am still surprised by the lack of >> transparency regarding the submission of such ABRs. >> >> Especially because, as you mentioned, the FC is indeed not a constituency >> and we never had a committee like the policy committee or any of the ECs >> submitting requests under our stakeholder group without notifying the >> members or the chair, who often is the person who responds for the >> constituency of the stakeholder group. >> >> Thato and Remmy, it is actually a shock to me that you are alleging that >> there is no clear procedure for submitting ABRs - once you click on the >> submission form you can see that you need to mention the chair's name and >> both me and Stephanie sent in consultations to our lists looking for >> suggestions to be discussed with the ec - this was very clear in my email. >> To consider that the FC considered it ok to submit an ABR without notifying >> the chairs is appaling. >> >> I dont think its clear to the FC that we all want to work together in >> identifying possible areas for outreaching and fundraising, and I mentioned >> it to Thato in the call we had a few weeks ago. But in order for us to >> provide full support to the FCs activities we need to (a) understand your >> goals and (b) develop an strategic plan and lastly (c) be able to fully >> trust in each other. When we learn that the FC has submitted 3 ABRs without >> even letting the SG know, the attitude makes it seem as if you both dont >> trust us. >> >> Also important to note that the template developed by the FC to collect >> ABRs suggestions was not adopted especially in light of the deadline, the >> proposal only got to us 2 weeks before the deadline - a period in which the >> proposals should be taking form before us chairs reporting them to the >> community and submitting. And in my emails about this I explained that this >> could be a solution for next years submissions, bc we would have time to >> improve the forms and submission process. I can say I am actually glad we >> did not accept the template, because it could have resulted in many more >> submissions without any of the NCSG and its constituencies chairs being >> notified. >> >> Having said that, I support Stephanie's request for the withdrawal of >> such ABRs, they look unfinished and reflect very poorly on NCSG and its >> constituencies. >> >> best, >> bruna >> >> >> >> >> Em seg, 11 de fev de 2019 ?s 00:14, Thato Mfikwe >> escreveu: >> >>> Another clarity, when ABR swere submitted, they did not have they were >>> not bearibg the NCSG Chairss name, not sure why the name was inserted. >>> Will follow up. >>> >>> Thato Mfikwe. >>> >>> On Sat, Feb 9, 2019 at 11:18 PM Stephanie Perrin < >>> stephanie.perrin at mail.utoronto.ca> wrote: >>> >>>> Dear Finance Committee Co-chairs: >>>> >>>> It has come to my attention that three ABRs were sent in to the process >>>> without my knowledge, and using my signature since I am responsible for the >>>> NCSG ABRs. >>>> https://community.icann.org/display/projfinadhocws/NCSG+-+FY20+Additional+Budget+Requests >>>> >>>> The Finance Committee is not a separate constituency, and at the moment >>>> it does not have the authority to act independently in this manner. Even >>>> if it did, such ABRs should have been discussed on the FC list. These >>>> had to be shared and discussed with the NCSG EC at a minimum, not sent in >>>> covertly. >>>> >>>> Please explain what happened here.... I know I have been terribly busy, >>>> what with the EPDP, the RDS II review, the budget and various other >>>> comments. However, I don't think I have forgotten anything with respect to >>>> the ABRs, and I am pretty sure I did not know about these requests. >>>> >>>> >>>> The one for CIVICRM is totally counterproductive....the amounts are >>>> wrong, and since we now have this funding in the core budget in the amount >>>> of 20K, we do not need to ask for it in an ABR. >>>> >>>> Without discussing in detail the merit of these requests, I would like >>>> you to please withdraw them and ask them to be taken off the website by COB >>>> Monday. You cannot send things in in my name without consultation, because >>>> I take my responsibilities seriously. Furthermore, and now I am speaking >>>> to the merits of the requests, if seems to me they contradict our overall >>>> budget comments supporting restraint. The tone suggests that the Finance >>>> Committee does not trust leadership to manage the money that is entrusted >>>> to the NCSG, and that the Finance Committee needs to be enabled to step up >>>> and manage it. This reflects very badly on our stakeholder group, and is >>>> not a position I support, and not just because I am the current Chair....I >>>> do not see any evidence of financial mismanagement over the many years that >>>> NCUC has handled the only money we receive officially. Recent events in >>>> NPOC, I know very little about, but the money that caused the friction had >>>> nothing to do with the PIR funding, as far as I can ascertain. >>>> >>>> I am deeply sympathetic to the need for regional outreach and >>>> development, this is what is behind the security and human rights outreach >>>> request, but we should have discussed these additional requests to >>>> coordinate, and to get the facts straight. >>>> >>>> Kind regards, >>>> >>>> Stephanie Perrin >>>> NCSG Chair >>>> _______________________________________________ >>>> NCSG-FC mailing list >>>> NCSG-FC at lists.ncsg.is >>>> https://lists.ncsg.is/mailman/listinfo/ncsg-fc >>>> >>> _______________________________________________ >>> NCSG-FC mailing list >>> NCSG-FC at lists.ncsg.is >>> https://lists.ncsg.is/mailman/listinfo/ncsg-fc >>> >> >> >> -- >> *Bruna Martins dos Santos * >> >> Skype ID: bruna.martinsantos >> @boomartins >> _______________________________________________ >> NCSG-FC mailing list >> NCSG-FC at lists.ncsg.is >> https://lists.ncsg.is/mailman/listinfo/ncsg-fc >> > _______________________________________________ > NCSG-FC mailing list > NCSG-FC at lists.ncsg.is > https://lists.ncsg.is/mailman/listinfo/ncsg-fc > -------------- next part -------------- An HTML attachment was scrubbed... URL: From rbeauregardlacroix at gmail.com Tue Feb 12 04:46:02 2019 From: rbeauregardlacroix at gmail.com (=?UTF-8?Q?Rapha=C3=ABl_Beauregard=2DLacroix?=) Date: Mon, 11 Feb 2019 21:46:02 -0500 Subject: [NCSG-FC] Urgent: NCSG ABRs In-Reply-To: References: Message-ID: Thank you Thato for your prompt action. Reading you I do believe there is a honest misunderstanding about the role of the FC within the NCSG. I will take the time at a later point, but hopefully not in the too distant future, to provide everyone with an answer to certain of your statements for further discussion. Have a nice evening, On Mon, Feb 11, 2019 at 7:02 PM Remmy Nweke wrote: > Thanks Thato for further clarification. > > Dear all, > > I am sure by now it's obvious there is no perfidious intended, it's all > for betterment of NCSG and I am sure better if not improved strategy will > soon emerge. > > I wish to sincerely apologize once again to the chair @Stephanie for the > insertion of her name in one of the ABRs. > > I, like Thato was not privy to that and anyone in your kind of situation > should have been alarmed as well among other popup issues thereof. > > Hope our apologies on that mixup will be considered for acceptance. Thanks. > > Like noted earlier, we must do something to strengthen FC and NCSG excom > communication moving forward and possibly consider inclusion of reps to > their respective constituencies and even have joint session even twice a > year or quarterly pending when Communication channels are strengthened. > > I thank you all for your understanding. > > Regards > Remmy > > On Mon, 11 Feb 2019, 2:05 p.m. Thato Mfikwe >> Hi all, >> >> I requested Maryam to remove all ABRs subnitted by the FC as per the >> request from the NCUC and NCSG chairs. >> >> The lack of communication is becoming a serious problem, as I dont >> remember seeing any call for ABR submissions on the NCSG mailing list and >> last year it was still not clear how ABRs will be subbmitted. The only >> thing solicited this year was just community comments not participation. >> >> There was still no discussion within the FC on submitted ABRs? We must be >> objective in our critism. >> >> It is only an assumption or excuse that, "had the ABR template been >> acceppted, then it means all requests submitted were not going to be >> discussed with Chairs or ECs", because the discussion was about to be made >> public before it got rejected by 2 chairs at FC level, there was no intend >> to faciltate community submissions single handedly, the proceess was >> intended to be inclusive as that is how it started off. >> >> If nobody is getting joy or gaining trust from FC activities and actions, >> then it would be proper to get a clear recommendation on what needs to be >> done to further prevent this problems from reoccuring. Anyway this is the >> first incident of the FC where something was submitted without >> consultation, but if this warrants action then I do not see the reason why >> we should be throwing words around as apposed to making recommendations and >> taking action. Is the FC that horrible, if so, what do you recommend? >> >> NOTE: The FC values inputs from observers, although decisions and voting >> is made by the FC members themselves according to the charter. >> >> My action as per your recommendation: I removed the ABRs, so what other >> change do you wish to see happen? >> >> Thato Mfikwe. >> >> On Mon, Feb 11, 2019 at 4:52 AM Bruna Martins dos Santos < >> bruna.mrtns at gmail.com> wrote: >> >>> Dear all, >>> >>> Thanks for the email, Steph. I am still surprised by the lack of >>> transparency regarding the submission of such ABRs. >>> >>> Especially because, as you mentioned, the FC is indeed not a >>> constituency and we never had a committee like the policy committee or any >>> of the ECs submitting requests under our stakeholder group without >>> notifying the members or the chair, who often is the person who responds >>> for the constituency of the stakeholder group. >>> >>> Thato and Remmy, it is actually a shock to me that you are alleging that >>> there is no clear procedure for submitting ABRs - once you click on the >>> submission form you can see that you need to mention the chair's name and >>> both me and Stephanie sent in consultations to our lists looking for >>> suggestions to be discussed with the ec - this was very clear in my email. >>> To consider that the FC considered it ok to submit an ABR without notifying >>> the chairs is appaling. >>> >>> I dont think its clear to the FC that we all want to work together in >>> identifying possible areas for outreaching and fundraising, and I mentioned >>> it to Thato in the call we had a few weeks ago. But in order for us to >>> provide full support to the FCs activities we need to (a) understand your >>> goals and (b) develop an strategic plan and lastly (c) be able to fully >>> trust in each other. When we learn that the FC has submitted 3 ABRs without >>> even letting the SG know, the attitude makes it seem as if you both dont >>> trust us. >>> >>> Also important to note that the template developed by the FC to collect >>> ABRs suggestions was not adopted especially in light of the deadline, the >>> proposal only got to us 2 weeks before the deadline - a period in which the >>> proposals should be taking form before us chairs reporting them to the >>> community and submitting. And in my emails about this I explained that this >>> could be a solution for next years submissions, bc we would have time to >>> improve the forms and submission process. I can say I am actually glad we >>> did not accept the template, because it could have resulted in many more >>> submissions without any of the NCSG and its constituencies chairs being >>> notified. >>> >>> Having said that, I support Stephanie's request for the withdrawal of >>> such ABRs, they look unfinished and reflect very poorly on NCSG and its >>> constituencies. >>> >>> best, >>> bruna >>> >>> >>> >>> >>> Em seg, 11 de fev de 2019 ?s 00:14, Thato Mfikwe >>> escreveu: >>> >>>> Another clarity, when ABR swere submitted, they did not have they were >>>> not bearibg the NCSG Chairss name, not sure why the name was inserted. >>>> Will follow up. >>>> >>>> Thato Mfikwe. >>>> >>>> On Sat, Feb 9, 2019 at 11:18 PM Stephanie Perrin < >>>> stephanie.perrin at mail.utoronto.ca> wrote: >>>> >>>>> Dear Finance Committee Co-chairs: >>>>> >>>>> It has come to my attention that three ABRs were sent in to the >>>>> process without my knowledge, and using my signature since I am responsible >>>>> for the NCSG ABRs. >>>>> https://community.icann.org/display/projfinadhocws/NCSG+-+FY20+Additional+Budget+Requests >>>>> >>>>> The Finance Committee is not a separate constituency, and at the >>>>> moment it does not have the authority to act independently in this manner. >>>>> Even if it did, such ABRs should have been discussed on the FC list. >>>>> These had to be shared and discussed with the NCSG EC at a minimum, not >>>>> sent in covertly. >>>>> >>>>> Please explain what happened here.... I know I have been terribly >>>>> busy, what with the EPDP, the RDS II review, the budget and various other >>>>> comments. However, I don't think I have forgotten anything with respect to >>>>> the ABRs, and I am pretty sure I did not know about these requests. >>>>> >>>>> >>>>> The one for CIVICRM is totally counterproductive....the amounts are >>>>> wrong, and since we now have this funding in the core budget in the amount >>>>> of 20K, we do not need to ask for it in an ABR. >>>>> >>>>> Without discussing in detail the merit of these requests, I would like >>>>> you to please withdraw them and ask them to be taken off the website by COB >>>>> Monday. You cannot send things in in my name without consultation, because >>>>> I take my responsibilities seriously. Furthermore, and now I am speaking >>>>> to the merits of the requests, if seems to me they contradict our overall >>>>> budget comments supporting restraint. The tone suggests that the Finance >>>>> Committee does not trust leadership to manage the money that is entrusted >>>>> to the NCSG, and that the Finance Committee needs to be enabled to step up >>>>> and manage it. This reflects very badly on our stakeholder group, and is >>>>> not a position I support, and not just because I am the current Chair....I >>>>> do not see any evidence of financial mismanagement over the many years that >>>>> NCUC has handled the only money we receive officially. Recent events in >>>>> NPOC, I know very little about, but the money that caused the friction had >>>>> nothing to do with the PIR funding, as far as I can ascertain. >>>>> >>>>> I am deeply sympathetic to the need for regional outreach and >>>>> development, this is what is behind the security and human rights outreach >>>>> request, but we should have discussed these additional requests to >>>>> coordinate, and to get the facts straight. >>>>> >>>>> Kind regards, >>>>> >>>>> Stephanie Perrin >>>>> NCSG Chair >>>>> _______________________________________________ >>>>> NCSG-FC mailing list >>>>> NCSG-FC at lists.ncsg.is >>>>> https://lists.ncsg.is/mailman/listinfo/ncsg-fc >>>>> >>>> _______________________________________________ >>>> NCSG-FC mailing list >>>> NCSG-FC at lists.ncsg.is >>>> https://lists.ncsg.is/mailman/listinfo/ncsg-fc >>>> >>> >>> >>> -- >>> *Bruna Martins dos Santos * >>> >>> Skype ID: bruna.martinsantos >>> @boomartins >>> _______________________________________________ >>> NCSG-FC mailing list >>> NCSG-FC at lists.ncsg.is >>> https://lists.ncsg.is/mailman/listinfo/ncsg-fc >>> >> _______________________________________________ >> NCSG-FC mailing list >> NCSG-FC at lists.ncsg.is >> https://lists.ncsg.is/mailman/listinfo/ncsg-fc >> > _______________________________________________ > NCSG-FC mailing list > NCSG-FC at lists.ncsg.is > https://lists.ncsg.is/mailman/listinfo/ncsg-fc > -------------- next part -------------- An HTML attachment was scrubbed... URL: From maryam.bakoshi at icann.org Tue Feb 12 20:38:42 2019 From: maryam.bakoshi at icann.org (Maryam Bakoshi) Date: Tue, 12 Feb 2019 18:38:42 +0000 Subject: [NCSG-FC] URGENT - Doodle Poll: NCSG FC Meeting In-Reply-To: <27726D8B-0B75-4F10-9F31-37930DC36658@icann.org> References: <27726D8B-0B75-4F10-9F31-37930DC36658@icann.org> Message-ID: Dear All, This is a gentle reminder to please confirm your availability today for the doodle poll below: https://doodle.com/poll/kryppns3xxp2apnq -- Many thanks, Maryam Bakoshi | SO/AC Collaboration Services Sr. Coordinator ICANN | Internet Corporation got Assigned Names and Numbers S: Maryam.bakoshi.icann | T: +44 7846 471777 From: Maryam Bakoshi Date: Monday, 11 February 2019 at 20:46 To: NCSG Finance Committee Subject: URGENT - Doodle Poll: NCSG FC Meeting Dear All, Please complete the doodle poll below to determine a date/time for NCSG GC call. https://doodle.com/poll/kryppns3xxp2apnq Please be so kind as to complete the doodle poll as soon as possible. -- Many thanks, Maryam Bakoshi | SO/AC Collaboration Services Sr. Coordinator ICANN | Internet Corporation got Assigned Names and Numbers S: Maryam.bakoshi.icann | T: +44 7846 471777 -------------- next part -------------- An HTML attachment was scrubbed... URL: From maryam.bakoshi at icann.org Tue Feb 12 23:52:54 2019 From: maryam.bakoshi at icann.org (Maryam Bakoshi) Date: Tue, 12 Feb 2019 21:52:54 +0000 Subject: [NCSG-FC] URGENT - Doodle Poll: NCSG FC Meeting In-Reply-To: References: <27726D8B-0B75-4F10-9F31-37930DC36658@icann.org> Message-ID: Dear All, Unfortunately, the result of the doodle poll does not favour the majority on any of the dates/times polled. Please advice. -- Many thanks, Maryam Bakoshi | SO/AC Collaboration Services Sr. Coordinator ICANN | Internet Corporation got Assigned Names and Numbers S: Maryam.bakoshi.icann | T: +44 7846 471777 From: Maryam Bakoshi Date: Tuesday, 12 February 2019 at 18:38 To: NCSG Finance Committee Subject: Re: URGENT - Doodle Poll: NCSG FC Meeting Dear All, This is a gentle reminder to please confirm your availability today for the doodle poll below: https://doodle.com/poll/kryppns3xxp2apnq -- Many thanks, Maryam Bakoshi | SO/AC Collaboration Services Sr. Coordinator ICANN | Internet Corporation got Assigned Names and Numbers S: Maryam.bakoshi.icann | T: +44 7846 471777 From: Maryam Bakoshi Date: Monday, 11 February 2019 at 20:46 To: NCSG Finance Committee Subject: URGENT - Doodle Poll: NCSG FC Meeting Dear All, Please complete the doodle poll below to determine a date/time for NCSG GC call. https://doodle.com/poll/kryppns3xxp2apnq Please be so kind as to complete the doodle poll as soon as possible. -- Many thanks, Maryam Bakoshi | SO/AC Collaboration Services Sr. Coordinator ICANN | Internet Corporation got Assigned Names and Numbers S: Maryam.bakoshi.icann | T: +44 7846 471777 -------------- next part -------------- An HTML attachment was scrubbed... URL: From remmyn at gmail.com Wed Feb 13 00:43:56 2019 From: remmyn at gmail.com (Remmy Nweke) Date: Tue, 12 Feb 2019 23:43:56 +0100 Subject: [NCSG-FC] URGENT - Doodle Poll: NCSG FC Meeting In-Reply-To: References: <27726D8B-0B75-4F10-9F31-37930DC36658@icann.org> Message-ID: Lets try next week then. regards ____ REMMY NWEKE, mNGE, Lead Strategist/Group Executive Editor, DigitalSENSE Africa Media [*Multiple-award winning medium*] (DigitalSENSE Business News ; ITREALMS , NaijaAgroNet ) Block F1, Shop 133 Moyosore Aboderin Plaza, Bolade Junction, Oshodi-Lagos M: 234-8033592762, 8023122558, 8051000475, T: @ITRealms Author: A Decade of ICT Reportage in Nigeria *2019 Nigeria DigitalSENSE Forum on IG4D & Nigeria IPv6 Roundtable * JOIN us!! *Vice President, African Civil Society on the Information Society (ACSIS ) *NPOC FC Rep @ICANN Non-Commercial Stakeholders Group (NCSG)* _________________________________________________________________ *Confidentiality Notice:* The information in this document and attachments are confidential and may also be privileged information. It is intended only for the use of the named recipient. Remmy Nweke does not accept legal responsibility for the contents of this e-mail. If you are not the intended recipient, please notify me immediately, then delete this document and do not disclose the contents of this document to any other person, nor make any copies. Violators may face court persecution. On Tue, Feb 12, 2019 at 11:14 PM Maryam Bakoshi wrote: > Dear All, > > > > Unfortunately, the result > > of the doodle poll does not favour the majority on any of the dates/times > polled. > > > > Please advice. > > > > -- > > Many thanks, > > > > *Maryam Bakoshi* | SO/AC Collaboration Services Sr. Coordinator > > *ICANN* | Internet Corporation got Assigned Names and Numbers > > *S*: Maryam.bakoshi.icann | *T*: +44 7846 471777 > > > > > > *From: *Maryam Bakoshi > *Date: *Tuesday, 12 February 2019 at 18:38 > *To: *NCSG Finance Committee > *Subject: *Re: URGENT - Doodle Poll: NCSG FC Meeting > > > > Dear All, > > > > This is a gentle reminder to please confirm your availability today for > the doodle poll below: > > > > https://doodle.com/poll/kryppns3xxp2apnq > > > > -- > > Many thanks, > > > > *Maryam Bakoshi* | SO/AC Collaboration Services Sr. Coordinator > > *ICANN* | Internet Corporation got Assigned Names and Numbers > > *S*: Maryam.bakoshi.icann | *T*: +44 7846 471777 > > > > > > *From: *Maryam Bakoshi > *Date: *Monday, 11 February 2019 at 20:46 > *To: *NCSG Finance Committee > *Subject: *URGENT - Doodle Poll: NCSG FC Meeting > > > > Dear All, > > > > Please complete the doodle poll below to determine a date/time for NCSG GC > call. > > > > https://doodle.com/poll/kryppns3xxp2apnq > > > > Please be so kind as to complete the doodle poll as soon as possible. > > > > -- > > Many thanks, > > > > *Maryam Bakoshi* | SO/AC Collaboration Services Sr. Coordinator > > *ICANN* | Internet Corporation got Assigned Names and Numbers > > *S*: Maryam.bakoshi.icann | *T*: +44 7846 471777 > > > _______________________________________________ > NCSG-FC mailing list > NCSG-FC at lists.ncsg.is > https://lists.ncsg.is/mailman/listinfo/ncsg-fc > -------------- next part -------------- An HTML attachment was scrubbed... URL: From maryam.bakoshi at icann.org Wed Feb 13 14:28:10 2019 From: maryam.bakoshi at icann.org (Maryam Bakoshi) Date: Wed, 13 Feb 2019 12:28:10 +0000 Subject: [NCSG-FC] New Doodle Poll: NCSG FC Meeting Message-ID: <1F479990-C9D0-44D6-9DCA-E93FE84B7E4F@icann.org> Dear All, Please find below a new doodle poll with dates for next week. https://doodle.com/poll/5cy7a7tirdh2ffs3 This doodle poll will close on Friday 15 February at 1200 UTC -- Many thanks, Maryam Bakoshi | SO/AC Collaboration Services Sr. Coordinator ICANN | Internet Corporation got Assigned Names and Numbers S: Maryam.bakoshi.icann | T: +44 7846 471777 From: NCSG-FC on behalf of Remmy Nweke Reply-To: NCSG Finance Committee Date: Tuesday, 12 February 2019 at 22:44 To: NCSG Finance Committee Subject: [Ext] Re: [NCSG-FC] URGENT - Doodle Poll: NCSG FC Meeting Lets try next week then. regards ____ REMMY NWEKE, mNGE, Lead Strategist/Group Executive Editor, DigitalSENSE Africa Media [Multiple-award winning medium] (DigitalSENSE Business News [digitalsenseafrica.com.ng]; ITREALMS [itrealms.com.ng], NaijaAgroNet [naijaagronet.com.ng]) Block F1, Shop 133 Moyosore Aboderin Plaza, Bolade Junction, Oshodi-Lagos M: 234-8033592762, 8023122558, 8051000475, T: @ITRealms [twitter.com] Author: A Decade of ICT Reportage in Nigeria [facebook.com] 2019 Nigeria DigitalSENSE Forum on IG4D & Nigeria IPv6 Roundtable [digitalsenseafrica.com.ng] JOIN us!! *Vice President, African Civil Society on the Information Society (ACSIS [acsis-scasi.org]) NPOC FC Rep @ICANN Non-Commercial Stakeholders Group (NCSG) [gnso.icann.org] _________________________________________________________________ *Confidentiality Notice:* The information in this document and attachments are confidential and may also be privileged information. It is intended only for the use of the named recipient. Remmy Nweke does not accept legal responsibility for the contents of this e-mail. If you are not the intended recipient, please notify me immediately, then delete this document and do not disclose the contents of this document to any other person, nor make any copies. Violators may face court persecution. On Tue, Feb 12, 2019 at 11:14 PM Maryam Bakoshi > wrote: Dear All, Unfortunately, the result [doodle.com] of the doodle poll does not favour the majority on any of the dates/times polled. Please advice. -- Many thanks, Maryam Bakoshi | SO/AC Collaboration Services Sr. Coordinator ICANN | Internet Corporation got Assigned Names and Numbers S: Maryam.bakoshi.icann | T: +44 7846 471777 From: Maryam Bakoshi > Date: Tuesday, 12 February 2019 at 18:38 To: NCSG Finance Committee > Subject: Re: URGENT - Doodle Poll: NCSG FC Meeting Dear All, This is a gentle reminder to please confirm your availability today for the doodle poll below: https://doodle.com/poll/kryppns3xxp2apnq [doodle.com] -- Many thanks, Maryam Bakoshi | SO/AC Collaboration Services Sr. Coordinator ICANN | Internet Corporation got Assigned Names and Numbers S: Maryam.bakoshi.icann | T: +44 7846 471777 From: Maryam Bakoshi > Date: Monday, 11 February 2019 at 20:46 To: NCSG Finance Committee > Subject: URGENT - Doodle Poll: NCSG FC Meeting Dear All, Please complete the doodle poll below to determine a date/time for NCSG GC call. https://doodle.com/poll/kryppns3xxp2apnq [doodle.com] Please be so kind as to complete the doodle poll as soon as possible. -- Many thanks, Maryam Bakoshi | SO/AC Collaboration Services Sr. Coordinator ICANN | Internet Corporation got Assigned Names and Numbers S: Maryam.bakoshi.icann | T: +44 7846 471777 _______________________________________________ NCSG-FC mailing list NCSG-FC at lists.ncsg.is https://lists.ncsg.is/mailman/listinfo/ncsg-fc [lists.ncsg.is] -------------- next part -------------- An HTML attachment was scrubbed... URL: From thatomfikwe at gmail.com Wed Feb 13 15:01:59 2019 From: thatomfikwe at gmail.com (Thato Mfikwe) Date: Wed, 13 Feb 2019 15:01:59 +0200 Subject: [NCSG-FC] New Doodle Poll: NCSG FC Meeting In-Reply-To: <1F479990-C9D0-44D6-9DCA-E93FE84B7E4F@icann.org> References: <1F479990-C9D0-44D6-9DCA-E93FE84B7E4F@icann.org> Message-ID: Thanks Maryam. On Wed, Feb 13, 2019 at 2:28 PM Maryam Bakoshi wrote: > Dear All, > > > > Please find below a new doodle poll with dates for next week. > > https://doodle.com/poll/5cy7a7tirdh2ffs3 > > > > This doodle poll will close on *Friday 15 February at 1200 UTC* > > > > -- > > Many thanks, > > > > *Maryam Bakoshi* | SO/AC Collaboration Services Sr. Coordinator > > *ICANN* | Internet Corporation got Assigned Names and Numbers > > *S*: Maryam.bakoshi.icann | *T*: +44 7846 471777 > > > > > > *From: *NCSG-FC on behalf of Remmy Nweke < > remmyn at gmail.com> > *Reply-To: *NCSG Finance Committee > *Date: *Tuesday, 12 February 2019 at 22:44 > *To: *NCSG Finance Committee > *Subject: *[Ext] Re: [NCSG-FC] URGENT - Doodle Poll: NCSG FC Meeting > > > > Lets try next week then. > > regards > > ____ > > REMMY NWEKE, mNGE, > > Lead Strategist/Group Executive Editor, > DigitalSENSE Africa Media [*Multiple-award winning medium*] > (DigitalSENSE Business News [digitalsenseafrica.com.ng] > ; > ITREALMS [itrealms.com.ng] > , > NaijaAgroNet [naijaagronet.com.ng] > > ) > > Block F1, Shop 133 Moyosore Aboderin Plaza, Bolade Junction, Oshodi-Lagos > M: 234-8033592762, 8023122558, 8051000475, T: @ITRealms > [twitter.com] > > > Author: A Decade of ICT Reportage in Nigeria [facebook.com] > > > > > *2019 Nigeria DigitalSENSE Forum on IG4D & Nigeria IPv6 Roundtable > [digitalsenseafrica.com.ng] > * > > > JOIN us!! > > > > *Vice President, African Civil Society on the Information Society (ACSIS > [acsis-scasi.org] > > ) > > > > *NPOC FC Rep @ICANN Non-Commercial Stakeholders Group (NCSG)* > [gnso.icann.org] > > > _________________________________________________________________ > *Confidentiality Notice:* The information in this document and attachments > are confidential and may also be privileged information. It is intended > only for the use of the named recipient. Remmy Nweke does not accept legal > responsibility for the contents of this e-mail. If you are not the intended > recipient, please notify me immediately, then delete this document and do > not disclose the contents of this document to any other person, nor make > any copies. Violators may face court persecution. > > > > > > On Tue, Feb 12, 2019 at 11:14 PM Maryam Bakoshi > wrote: > > Dear All, > > > > Unfortunately, the result [doodle.com] > > of the doodle poll does not favour the majority on any of the dates/times > polled. > > > > Please advice. > > > > -- > > Many thanks, > > > > *Maryam Bakoshi* | SO/AC Collaboration Services Sr. Coordinator > > *ICANN* | Internet Corporation got Assigned Names and Numbers > > *S*: Maryam.bakoshi.icann | *T*: +44 7846 471777 > > > > > > *From: *Maryam Bakoshi > *Date: *Tuesday, 12 February 2019 at 18:38 > *To: *NCSG Finance Committee > *Subject: *Re: URGENT - Doodle Poll: NCSG FC Meeting > > > > Dear All, > > > > This is a gentle reminder to please confirm your availability today for > the doodle poll below: > > > > https://doodle.com/poll/kryppns3xxp2apnq [doodle.com] > > > > > -- > > Many thanks, > > > > *Maryam Bakoshi* | SO/AC Collaboration Services Sr. Coordinator > > *ICANN* | Internet Corporation got Assigned Names and Numbers > > *S*: Maryam.bakoshi.icann | *T*: +44 7846 471777 > > > > > > *From: *Maryam Bakoshi > *Date: *Monday, 11 February 2019 at 20:46 > *To: *NCSG Finance Committee > *Subject: *URGENT - Doodle Poll: NCSG FC Meeting > > > > Dear All, > > > > Please complete the doodle poll below to determine a date/time for NCSG GC > call. > > > > https://doodle.com/poll/kryppns3xxp2apnq [doodle.com] > > > > > Please be so kind as to complete the doodle poll as soon as possible. > > > > -- > > Many thanks, > > > > *Maryam Bakoshi* | SO/AC Collaboration Services Sr. Coordinator > > *ICANN* | Internet Corporation got Assigned Names and Numbers > > *S*: Maryam.bakoshi.icann | *T*: +44 7846 471777 > > > > _______________________________________________ > NCSG-FC mailing list > NCSG-FC at lists.ncsg.is > https://lists.ncsg.is/mailman/listinfo/ncsg-fc [lists.ncsg.is] > > > _______________________________________________ > NCSG-FC mailing list > NCSG-FC at lists.ncsg.is > https://lists.ncsg.is/mailman/listinfo/ncsg-fc > -------------- next part -------------- An HTML attachment was scrubbed... URL: From remmyn at gmail.com Wed Feb 20 10:39:50 2019 From: remmyn at gmail.com (Remmy Nweke) Date: Wed, 20 Feb 2019 09:39:50 +0100 Subject: [NCSG-FC] [Ext] NCSG Finance Committee meeting Agenda In-Reply-To: References: <95B9C960-A8A7-452D-9737-F925913B27FA@icann.org> <16A40E8B-F538-47B5-AEFC-C1E04F5CF283@icann.org> <36988298-0457-86d2-04e2-7414889dd2ce@mail.utoronto.ca> <64f3b36c-8d9e-c326-0d68-7133b74420e8@mail.utoronto.ca> Message-ID: Good morning all I did not know why I was not on this trend before now. Thanks for the discussion so far. 1. @Bruna I will like to suggest that if we want to make progress for now, there is need to extend the NCUC rep for FC it will help us in getting some things solve may be another term. We need an understanding of the issues at stake not face so to say 2. The NCUC charter seems to be in contrary with NCSG charter if my reading serves well and since NCSG is a harmonising entity for stakeholders here it supersedes other sub charter of its members. What we can do is to find a way of harmonizing this under NCSG. 3. I am still very ached that internal politics is clouding our moving forward instead of overall interest. For instance, Why is it that we very often have issues with FC and none with PC? What is in FC that cannot be resolved leading to all time spoil for war? Every thing is voluntary except I am missing something. 4. Sequel to my No1 suggestion. It's better to get the extension of tenure if possible to put the FC on stream that will afford it to run with every cooperation needed before new appointment otherwise new appointees will suffer hindwinking theory of the more you look the less you see, therefore back to basic. 5. I have done flying satisfactorily in my other life except if it will aid the job immensely at hand, especially as we intend to market the brand for effective donor support, which entails 1-1 effect and education of the community where necessary. I will suggest if possible a face to face of current FC to fast track things including the body language. We have had enough of lull in this space. Moreso since online has failed us which can be tagged along capacity building. I will appeal for caution as we have a lot to be done as earlier noted by NCSG chair. Regards Remmy On Wed, 20 Feb 2019, 1:09 a.m. Thato Mfikwe > No sure why you got left out of the below communique. Please find, thanks > > Thato Mfikwe.. > > > ---------- Forwarded message --------- > From: Thato Mfikwe > Date: Wed, Feb 20, 2019 at 2:07 AM > Subject: Re: [Ext] NCSG Finance Committee meeting Agenda > To: Stephanie Perrin > Cc: Bruna Martins dos Santos , Rapha?l > Beauregard-Lacroix , Joan Kerr < > joankerr at fbsc.org>, Maryam Bakoshi , farzaneh > badii > > > Hi Stephanie and Bruna, > > We still awaiting your confirmations on Doodle so that we can proceed with > the meeting before ICANN64. We need to finalise the FC meeting agenda and > wrap up FC Operational Procedures in order to prepare them for discussion > during the meeting in Kobe. > > The sooner we are able to hold this meeting, the sooner we can have the > Draft OP reviewed by the EC, thanks. > > Thato Mfikwe. > > > > On Tue, Feb 19, 2019 at 4:40 AM Stephanie Perrin < > stephanie.perrin at mail.utoronto.ca> wrote: > >> Absolutely the work must keep going....We have a meeting in Kobe, we need >> to discuss (I think) our collective vision for what the Finance Committee >> needs to address. There is work to do on the procedures, and we need to >> have a think about the whole issue of fund raising...what it means, what >> are the legal implications, what it would be used for. Do we need to start >> charging association fees? All these are valid questions raised by the >> Charter that do not seem to have been officially answered. We could at >> least record what our 2019 opinion is on these things... >> >> cheers Stephanie >> On 2019-02-18 18:06, Bruna Martins dos Santos wrote: >> >> Hey Thato, >> >> I dont think all planned meetings should come to an end, but the FC shall >> bear in mind that NCUC can have a new appointee to the committee. And maybe >> the FC can also use the Kobe meeting to discuss paths forward and how to >> better define its activities in a bottom-up way :) >> >> My reply was more of a doubt with regards to the FC activity considering >> that the term of one of the reps has terminated. >> >> NCUC call for FC appointee is still open, btw. The constituency can >> appoint one member and one observer, please consider applying. >> >> best, >> bruna >> >> Em sex, 15 de fev de 2019 ?s 18:58, Thato Mfikwe >> escreveu: >> >>> Hi Bruna, >>> >>> Termination, noted. Does it now mean that all planned meetings and work >>> must come to a halt? Thanks. >>> >>> Thato Mfikwe. >>> >>> On Fri, Feb 15, 2019 at 7:33 PM Bruna Martins dos Santos < >>> bruna.mrtns at gmail.com> wrote: >>> >>>> Hey Thato and all, >>>> >>>> Thanks for the email, before going through all the points I just wanted >>>> to respond to the:* "That is why it is vital that we create more rom >>>> for at least 6 more bodies within the FC." *If you take a look at >>>> both the NCSG Charter and NCUC Operating Procedures, I am afraid that the >>>> change you want to promote might be a little problematic as it would imply >>>> in a review of such texts. And I paste them below: >>>> >>>> *2.6.1. NCSG?FC Composition.* >>>> >>>> *The NCSG Finance Committee (FC) shall be comprised of one >>>> representative from each Recognized Constituency. Each Candidate >>>> Constituency is entitled to appoint an observer. The NCSG Chair will >>>> participate as an ex?officio member of the NCSG?FC and will be included in >>>> consensus process and votes. The FC may invite other members as needed to >>>> meet its goals and responsibilities.* >>>> >>>> *(NCSG Charter) * >>>> >>>> >>>> >>>> *II. Appointments The list of appointments by the NCUC EC is as >>>> follows: NCSG Executive Committee (2 NCUC members), NCSG Policy Committee >>>> (2 NCUC members), NCSG Finance Committee (1 member), (...) * >>>> *(NCUC Operating Procedures) * >>>> >>>> Fortunately the NCSG Charter allows us to have the NCSG chair as an >>>> ex-officio member and also constituency observers, so maybe we should be >>>> working in finding these observers who would help shaping the FC work >>>> before anything. >>>> >>>> On a suggestion note, I very much appreciate the work you and Remmy did >>>> with the Operating Procedures, but due to the fact that your mandate is now >>>> terminated (that meaning the FC Chair post is also vacant) I would advise >>>> the FC (a) to wait until NCUC nominates its representative at the Finance >>>> Committee to continue with this work and (b) that we once again conducted >>>> this work in an open way, maybe with proper consultation to both >>>> constituencies and stakeholder group mailing lists. >>>> >>>> Best, >>>> Bruna >>>> >>>> >>>> Em sex, 15 de fev de 2019 ?s 14:34, Thato Mfikwe >>>> escreveu: >>>> >>>>> Hi Stephanie, Joan and all, >>>>> >>>>> In response to comments, >>>>> >>>>> 1. The attempt to finalise the Draft Operational Procedures (OP) >>>>> >>>>> - V1will cleary articulate the roles and responsibilities of the FC, >>>>> synergy also needs to be maintained wih the charter itself. futermore, the >>>>> Charter is pretty clear on what need to be done, the OP intends to >>>>> articulate the process to be followed, it seems like we will need to >>>>> revisit this exercise in our next meeting. Will work on cleaning up the >>>>> Draft so that we can review and discuss sections where contestation still >>>>> remains. >>>>> >>>>> Since my engagement on this committee, I have be made aware of these >>>>> funding allocation contention from NPOC and all this issues should >>>>> partially be addressed by the Draft OP. Based on the last decision making >>>>> meeeting of the FC, after a call for comment on the OP around 5 moths ago, >>>>> this *link is for the updated and clean OP version (V2) after* FC >>>>> decisions and incorporation of public comments. >>>>> >>>>> "Remmy can you please assist by fixing the last section on ICANN >>>>> Terms and definitions on V2 of the Draft FC OP >>>>> >>>>> ? >>>>> >>>>> 2. The OP has always been work in progress for the FC, with addional >>>>> tasks of looking into ABRs, ICANN, budgets and plans, Reserve Fund, CCWG on >>>>> AP and many other comments at the same time. That is why it is vital that >>>>> we create more rom for alteast 6 more bodies within the FC. I would >>>>> recommend in the capacity of memebrs not just observers, if adopted then >>>>> this needs to be articulated in the Draft OP as the Charter does not >>>>> prohibit invitation of members in to the FC. >>>>> >>>>> Not exactly sure what you mean by flying around with our dime and >>>>> effect on reputation, please kindly elaborate. Is there anyone doing so or >>>>> planning to do such? >>>>> >>>>> 3. The autonomy of the FC also needs to be determined in decision >>>>> making and representation of the Treasury with the EC must be reviewed as >>>>> it is common practice in the civil sector. As FC members and observers, we >>>>> are allowed to disagree on decision and minority views will always be >>>>> recorded in all reports generated, consensus reached and decisions made. >>>>> The decisions of the FC need to be respected by its members so that it is >>>>> easier to filter through the public and EC engagememt processes. >>>>> >>>>> Still pending on the *Draft OP V2* >>>>> >>>>> are: >>>>> a. Light weight process ofr ABR submission >>>>> b. Tabling of the FC track or focus areas, like (to help with >>>>> recruitment of volunteers and additional members): >>>>> - ABR submissions and comments >>>>> - ICANN budgets and plans >>>>> - Reserve Fund and the Operational fund >>>>> - IANA and PTI plans and budget >>>>> - Auction Proceeds amongst other on-going activities >>>>> c. Please let me know about other additions needed on the OP V2 and >>>>> note that all red highted areas still need consensus vefore we can >>>>> circulated to the EC and for the lasy=t round of comments from the >>>>> community, let me know if you need any further information. >>>>> >>>>> I tried to incorporate all committee and public coments on the 2nd >>>>> version, thanks. >>>>> >>>>> >>>>> Thato Mfikwe. >>>>> >>>>> On Thu, Feb 14, 2019 at 5:42 PM Stephanie Perrin < >>>>> stephanie.perrin at mail.utoronto.ca> wrote: >>>>> >>>>>> Thanks for this suggestion Joan, and thanks for all this interest. I >>>>>> believe that the Finance Committee has indeed been working on procedures, >>>>>> and would appreciate it if Thato could share that link for easy reference. >>>>>> We need to get those procedures amended, circulated on the NCSG discussion >>>>>> list, and sent to the NCSG EC for approval. There are many misconceptions >>>>>> about finances, and I would like to get the facts on the table. One key >>>>>> fact is that the FC cannot do anything until it has procedures that have >>>>>> been approved by the NCSG-EC. >>>>>> >>>>>> Re this business of the PIR funds going to the NCUC....the NCUC has >>>>>> always made the call for those funds open to NPOC, NCSG, and non-affiliated >>>>>> members. It is my own view, as you have all heard before no doubt, that >>>>>> the funds must be disbursed through a merit-based decision-making process. >>>>>> WE have a ton of work being done by a very few people, and I am committed >>>>>> to making sure that noone is flying around on our dime and not contributing >>>>>> materially to the successful work, and thus the reputation, of this >>>>>> stakeholder group. I am not sure what NPOC wanted hitherto, but it would >>>>>> be helpful if we all remembered that NPOC is a new constituency and has had >>>>>> more than a few problems finding its feet and becoming active in our policy >>>>>> work. >>>>>> >>>>>> We now have to supervise the transition to PIR granting funds to >>>>>> NCSG, which was the driver for me opening a bank account, so that we could >>>>>> actually receive a cheque on behalf of the SG. In the meantime, I am >>>>>> paying the bills and seeking reimbursement from my personal accounts and >>>>>> credit cards, a situation that I can assure you I will be happy to >>>>>> surrender to the Finance Committee as soon as it gets its procedures passed >>>>>> (doubtful that will happen during my tenure). In all the bickering that >>>>>> has gone on over money and bank accounts and establishing e-entities, >>>>>> nobody has stepped forward to pay the next bill, which is due tomorrow in >>>>>> the amount of $577 US. There is nothing in the Charter about the NCSG >>>>>> shouldering this financial burden, I am just doing it, as Farzi did before >>>>>> me. >>>>>> >>>>>> I am sorry if I sound grumpy folks. I know we are all interested in >>>>>> moving forward but with all the work we are trying to deal with on the >>>>>> policy front, this is an unnecessary distraction, in my view. Let's get on >>>>>> with fixing those procedures, as Joan suggests. >>>>>> >>>>>> Stephanie >>>>>> >>>>>> >>>>>> On 2019-02-11 09:01, Joan Kerr wrote: >>>>>> >>>>>> Hi Maryam, All >>>>>> >>>>>> Thanks for the confirmation of removing the ABRs as per Thato's >>>>>> request. >>>>>> >>>>>> Thato, All >>>>>> >>>>>> I have reading the emails regarding the FC, and I think at the core >>>>>> of the confusion is the undefined role and responsibilities of the >>>>>> committee. I think this needs to be clarified and agreed on. I also think >>>>>> that a proper FC should be formed comprising of BOTH NPOC and NCUC members >>>>>> equally, especially to avoid the mess of the PIR block funding issue, where >>>>>> NPOC, had to accept the financial procedures of NCUC, resulting in an >>>>>> inequitable situation. From my perspective, I feel that the FC is >>>>>> struggling in its role, and is trying to find more equitable ways of >>>>>> dealing with funding, and is deliberating on ways to deal with it in a fair >>>>>> manner. Clear directions and expectations are definitely needed, and the >>>>>> NCSG Charter is probably a good place to start that discussion. >>>>>> >>>>>> Let's discuss forming a committee, clearly defining the roles, >>>>>> responsibilities and expectations. >>>>>> >>>>>> Thanks >>>>>> >>>>>> On Mon, Feb 11, 2019 at 7:53 AM Maryam Bakoshi < >>>>>> maryam.bakoshi at icann.org> wrote: >>>>>> >>>>>>> Dear Thato, >>>>>>> >>>>>>> >>>>>>> >>>>>>> As requested, I have asked for the 3 ABRs submitted by the FC to be >>>>>>> removed from ABR consideration. >>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> >>>>>>> Many thanks, >>>>>>> >>>>>>> >>>>>>> >>>>>>> *Maryam Bakoshi* | SO/AC Collaboration Services Sr. Coordinator >>>>>>> >>>>>>> *ICANN* | Internet Corporation got Assigned Names and Numbers >>>>>>> >>>>>>> *S*: Maryam.bakoshi.icann | *T*: +44 7846 471777 >>>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> >>>>>> Joan Kerr, >>>>>> >>>>>> Entrepreneur, Artist, Humanitarian >>>>>> >>>>>> T: +1 (416) 907-0783 >>>>>> >>>>>> Skype: joankerr_fbsc >>>>>> >>>>>> fbsc.org, www.fbsc.eco >>>>>> >>>>>> Chair: Victory Garden Leadership Implementation Team >>>>>> >>>>>> Chair, Sustainable Agriculture, Global Humanitarian Technology >>>>>> Conference >>>>>> >>>>>> Chair: IEEE Smart Villages Project, Sustainable Agriculture Working >>>>>> Group >>>>>> >>>>>> Chair: ICANN Not for Profit Operational Concerns Constituency >>>>>> >>>>>> Recipient of the United Nations Civil Society Award (WSIS 2004) >>>>>> >>>>>> Recipient, Region of Durham Community Partnership Award >>>>>> >>>>>> Advisor, IEEE Humanitarian Initiatives Committee >>>>>> >>>>>> Advisor, Climate Smart Agriculture Youth Network, (CSAYN) Global >>>>>> Coordination Unit >>>>>> >>>>>> >>>> >>>> -- >>>> *Bruna Martins dos Santos * >>>> >>>> Skype ID: bruna.martinsantos >>>> @boomartins >>>> >>> >> >> -- >> *Bruna Martins dos Santos * >> >> Skype ID: bruna.martinsantos >> @boomartins >> >> -------------- next part -------------- An HTML attachment was scrubbed... URL: From thatomfikwe at gmail.com Wed Feb 20 22:53:44 2019 From: thatomfikwe at gmail.com (thatomfikwe) Date: Wed, 20 Feb 2019 22:53:44 +0200 Subject: [NCSG-FC] [Ext] ICANN64 FC meeting preparations Message-ID: <5jyfwu2xk66oqy1s1u7a9dwe.1550696024335@email.android.com> Hi, When things are happening in parallel, with announcements for FC members replacement, makes the entire planning process for the Kobe meeting a mission. It would have been better if such announcements were made after ICANN64, they put the FC in a difficult position and the Kobe meeting is planned to revive the FC not create uncertainty and uncomfortable situations with members who will be leading deliberations. Not sure if such actions were well thought of or well planned. I am not exactly sure how we are going to proceed despite serveral attempts to hold a meeting with members before Kobe in order to discuss the planned agenda in detail and emerging issues. ICANN staff is just an email away, the Charter requires the FC to work with ICANN finance so if the committee is to be effective then it needs to establish or revive critical connections that will ensure that NCSG and its constituencies are fairly supported. Regarding the strong position of the community, what issues are they arguing? Do you think they are valid and what were the reposnes of members during that time? If you carefully review comments, they.were centered around?- the bank account and incorporation of NCSG. This is currently being dealt with and in progress, to also be further discussed and decided upon- the role of the FC, many disagree with a lot of what is stipulated on the Charter, whereas the Charter uses simple language When we review we need to be objective, even though it might seem like the vocal in the mailing list are the majority. If the FC is designed to have no autonomy then its efforts to correct mistakes of the past will always go unnoticed and unrecognised. Thato Mfikwe. Sent from my Samsung Galaxy smartphone.-------- Original message --------From: Stephanie Perrin Date: 20/02/2019 21:59 (GMT+02:00) To: Thato Mfikwe Cc: Maryam Bakoshi Subject: Re: [Ext] ICANN64 FC meeting preparations The event where the FC Chair, without informing his colleagues on Council or the PC, invited senior ICANN staff to one of the first FC meetings.? Nobody was prepared.? Most of us were unable to attend the last minute meeting.? Surprises are rarely appreciated, and noone knew the conditions under which staff had been invited.?? If you check back in the email archives you will be able to see the grumbling that ensued after that meeting.? Senior people are exceptionally busy at ICANN meetings....we don't invite them unless we have consensus that we are ready to meet them. We are by nature a consultative group.? The FC should always be consulted, so there is an open record for members to consult.? Many members have strongly held views on the FC and its mandate, and check the email archives. If there is nothing there, it is insufficiently transparent, at least in my view.? I believe that is a commonly held view. Stephanie On 2019-02-20 13:51, Thato Mfikwe wrote: Hi Sephanie, What was an embarrasment? Thato Mfikwe. On Wed, Feb 20, 2019 at 8:40 PM Stephanie Perrin wrote: Personally, I do not think we are ready to meet with ICANN Finance staff. However, it appears the request has gone.? We have already gone through this when Ed was chairing the Finance Committee, and it was an embarrassment in my opinion. Cheers Stephanie On 2019-02-20 03:27, Maryam Bakoshi wrote: Hi Thato, Good morning I hope this email meets you well. I have forwarded this request to Mary Wong, ICANN Staff.? I am also cc?ing Stephanie, so she is in the loop.? ? Many thanks, Maryam Bakoshi?| SO/AC Collaboration Services Sr. Coordinator? ICANN?| Internet Corporation for Assigned Names and Numbers? S: Maryam.bakoshi.icann |?T:??+44 7846 471777? On 20 Feb 2019, at 00:25, Thato Mfikwe wrote: Hi Maryam, Is it possible that we request the presence of one of ICANN Finance staff and ICANN legal in the FC meeting in Kobe which will be taking place on Wednesday, 15h15 - 16h45. Main support needed from ICANN staff: - Elaboration on legal implications on incorporation of NCSG and what it will mean for ICANN. - Advice on alternative sources of fundraising and opening a bank account in the name of NCSG. - Recommendation on how to best set up the Operational Procedures and ways of working with ICANN finance to support NCSG and constituency initiatives and activities. - Provision of clarity on how community comments are reflected in current and future ICANN operational and financial plans. We only have 2 weeks before the meeting. I hope this message, finds you well, thanks. Thato Mfikwe. -------------- next part -------------- An HTML attachment was scrubbed... URL: From stephanie.perrin at mail.utoronto.ca Wed Feb 20 23:25:58 2019 From: stephanie.perrin at mail.utoronto.ca (Stephanie Perrin) Date: Wed, 20 Feb 2019 21:25:58 +0000 Subject: [NCSG-FC] [Ext] ICANN64 FC meeting preparations In-Reply-To: <5jyfwu2xk66oqy1s1u7a9dwe.1550696024335@email.android.com> References: <5jyfwu2xk66oqy1s1u7a9dwe.1550696024335@email.android.com> Message-ID: <6e8404b1-94e0-6187-caa0-4565afe3c94e@mail.utoronto.ca> I think you must have meant this for Bruna, Thato. I am not the head of the NCUC, nor of NPOC. the heads of those constituencies are in charge of managing the selection of their members of the Finance Cttee, not me. ccing Bruna so she can respond. Other responses in line. Stephanie On 2019-02-20 15:53, thatomfikwe wrote: Hi, When things are happening in parallel, with announcements for FC members replacement, makes the entire planning process for the Kobe meeting a mission. It would have been better if such announcements were made after ICANN64, they put the FC in a difficult position and the Kobe meeting is planned to revive the FC not create uncertainty and uncomfortable situations with members who will be leading deliberations. Not sure if such actions were well thought of or well planned. see Bruna and Joan I am not exactly sure how we are going to proceed despite serveral attempts to hold a meeting with members before Kobe in order to discuss the planned agenda in detail and emerging issues. Do you have any idea how busy council is, and the epdp, and the WHOIS review cttee, and the comments process in general? We are running ragged. WE need more members to staff the working groups. ICANN staff is just an email away, the Charter requires the FC to work with ICANN finance so if the committee is to be effective then it needs to establish or revive critical connections that will ensure that NCSG and its constituencies are fairly supported. First we determine our own policy positions. Do we want paid memberships? Do we want to establish an entity, if so what? These are not issues to discuss with staff, they would not be authorized to express an opinion, nor should they. Regarding the strong position of the community, what issues are they arguing? Do you think they are valid and what were the reposnes of members during that time? not sure what this question is addressing If you carefully review comments, they.were centered around - the bank account and incorporation of NCSG. This is currently being dealt with and in progress, to also be further discussed and decided upon - the role of the FC, many disagree with a lot of what is stipulated on the Charter, whereas the Charter uses simple language Indeed, I cannot figure out for the life of me what the drafters of the Charter had in mind. Establishing an entity has serious financial repercussions. I have no idea where the money for that would come from. Fund raising is difficult at the best of times, to support us at ICANN....likely to be quite a chore. When we review we need to be objective, even though it might seem like the vocal in the mailing list are the majority. If the FC is designed to have no autonomy then its efforts to correct mistakes of the past will always go unnoticed and unrecognised. what specific mistakes are you talking about? Thato Mfikwe. Sent from my Samsung Galaxy smartphone. -------- Original message -------- From: Stephanie Perrin Date: 20/02/2019 21:59 (GMT+02:00) To: Thato Mfikwe Cc: Maryam Bakoshi Subject: Re: [Ext] ICANN64 FC meeting preparations The event where the FC Chair, without informing his colleagues on Council or the PC, invited senior ICANN staff to one of the first FC meetings. Nobody was prepared. Most of us were unable to attend the last minute meeting. Surprises are rarely appreciated, and noone knew the conditions under which staff had been invited. If you check back in the email archives you will be able to see the grumbling that ensued after that meeting. Senior people are exceptionally busy at ICANN meetings....we don't invite them unless we have consensus that we are ready to meet them. We are by nature a consultative group. The FC should always be consulted, so there is an open record for members to consult. Many members have strongly held views on the FC and its mandate, and check the email archives. If there is nothing there, it is insufficiently transparent, at least in my view. I believe that is a commonly held view. Stephanie On 2019-02-20 13:51, Thato Mfikwe wrote: Hi Sephanie, What was an embarrasment? Thato Mfikwe. On Wed, Feb 20, 2019 at 8:40 PM Stephanie Perrin > wrote: Personally, I do not think we are ready to meet with ICANN Finance staff. However, it appears the request has gone. We have already gone through this when Ed was chairing the Finance Committee, and it was an embarrassment in my opinion. Cheers Stephanie On 2019-02-20 03:27, Maryam Bakoshi wrote: Hi Thato, Good morning I hope this email meets you well. I have forwarded this request to Mary Wong, ICANN Staff. I am also cc?ing Stephanie, so she is in the loop. ? Many thanks, Maryam Bakoshi | SO/AC Collaboration Services Sr. Coordinator ICANN | Internet Corporation for Assigned Names and Numbers S: Maryam.bakoshi.icann | T: ?+44 7846 471777? On 20 Feb 2019, at 00:25, Thato Mfikwe > wrote: Hi Maryam, Is it possible that we request the presence of one of ICANN Finance staff and ICANN legal in the FC meeting in Kobe which will be taking place on Wednesday, 15h15 - 16h45. Main support needed from ICANN staff: - Elaboration on legal implications on incorporation of NCSG and what it will mean for ICANN. - Advice on alternative sources of fundraising and opening a bank account in the name of NCSG. - Recommendation on how to best set up the Operational Procedures and ways of working with ICANN finance to support NCSG and constituency initiatives and activities. - Provision of clarity on how community comments are reflected in current and future ICANN operational and financial plans. We only have 2 weeks before the meeting. I hope this message, finds you well, thanks. Thato Mfikwe. -------------- next part -------------- An HTML attachment was scrubbed... URL: From bruna.mrtns at gmail.com Thu Feb 21 00:30:31 2019 From: bruna.mrtns at gmail.com (Bruna Martins dos Santos) Date: Wed, 20 Feb 2019 19:30:31 -0300 Subject: [NCSG-FC] [Ext] ICANN64 FC meeting preparations In-Reply-To: <6e8404b1-94e0-6187-caa0-4565afe3c94e@mail.utoronto.ca> References: <5jyfwu2xk66oqy1s1u7a9dwe.1550696024335@email.android.com> <6e8404b1-94e0-6187-caa0-4565afe3c94e@mail.utoronto.ca> Message-ID: Hey Thato, I sincerely don't know how to deal with so many FC incidents. You have been claiming for the so-called 'independence' but all I have seen so far is a huge disregard for NSCG and its constituencies. So far you have added stuff to your Operating procedures that were not agreed with neither suggested by membership (such as the attempt of granting travel slots to the FC), submitted ABRs that involved the SG and its Constituencies activities without even notifying the leadership teams and now we have this invitation for staff to join the FC meeting in Kobe without, once again, consulting with membership - even despite the fact that on the thread about NCSG bank account several members considered that asking staff for advice at such stage (of the FC) would not be advisable. Sincerely it has been really hard trying to work with the FC when I know that despite of the advice that we might add to any discussions will be simply ignored. With regards to 'announcements for FC members replacement' I guess there is a little misunderstanding on your behalf here. All NCSG/NCUC/NPOC leadership positions have terms, even the appointed ones. And you might recall that back in Barcelona, when I became NCUC chair, we announced that the calls for NCUC appointees to all NCSG committees would be done at the beginning of this year. So this is not an attempt to shut down any committee, but simply NCUC complying with its operating procedures. If you have any interest in continuing at this position you should apply to be once again the NCUC appointee to the FC, and the EC will deliberate on this - I dont have a say in votings unless we have a tie. Other than coming back and forth with such discussions, I think the FC could be doing a little inreaching to membership. I am pretty sure that the FC members are all capable of doing these discussions and I would personally like to see you being involved with the ICANN Strategic Plan for Fiscal Years 2021 ? 2025 and maybe even being the penholders of this comment. Or even asking the mailing lists about what discussions they would like to see at the FC meeting in Kobe. Best, Bruna Em qua, 20 de fev de 2019 ?s 18:26, Stephanie Perrin < stephanie.perrin at mail.utoronto.ca> escreveu: > I think you must have meant this for Bruna, Thato. I am not the head of > the NCUC, nor of NPOC. the heads of those constituencies are in charge of > managing the selection of their members of the Finance Cttee, not me. > ccing Bruna so she can respond. Other responses in line. > > Stephanie > On 2019-02-20 15:53, thatomfikwe wrote: > > Hi, > > > When things are happening in parallel, with announcements for FC members > replacement, makes the entire planning process for the Kobe meeting a > mission. > > It would have been better if such announcements were made after ICANN64, > they put the FC in a difficult position and the Kobe meeting is planned to > revive the FC not create uncertainty and uncomfortable situations with > members who will be leading deliberations. Not sure if such actions were > well thought of or well planned. > > see Bruna and Joan > > > > I am not exactly sure how we are going to proceed despite serveral > attempts to hold a meeting with members before Kobe in order to discuss the > planned agenda in detail and emerging issues. > > Do you have any idea how busy council is, and the epdp, and the WHOIS > review cttee, and the comments process in general? We are running ragged. > WE need more members to staff the working groups. > > > ICANN staff is just an email away, the Charter requires the FC to work > with ICANN finance so if the committee is to be effective then it needs to > establish or revive critical connections that will ensure that NCSG and its > constituencies are fairly supported. > > First we determine our own policy positions. Do we want paid > memberships? Do we want to establish an entity, if so what? These are not > issues to discuss with staff, they would not be authorized to express an > opinion, nor should they. > > > Regarding the strong position of the community, what issues are they > arguing? Do you think they are valid and what were the reposnes of members > during that time? > > not sure what this question is addressing > > > If you carefully review comments, they.were centered around > - the bank account and incorporation of NCSG. This is currently being > dealt with and in progress, to also be further discussed and decided upon > - the role of the FC, many disagree with a lot of what is stipulated on > the Charter, whereas the Charter uses simple language > > Indeed, I cannot figure out for the life of me what the drafters of the > Charter had in mind. Establishing an entity has serious financial > repercussions. I have no idea where the money for that would come from. > Fund raising is difficult at the best of times, to support us at > ICANN....likely to be quite a chore. > > > When we review we need to be objective, even though it might seem like the > vocal in the mailing list are the majority. If the FC is designed to have > no autonomy then its efforts to correct mistakes of the past will always go > unnoticed and unrecognised. > > what specific mistakes are you talking about? > > > > > Thato Mfikwe. > > Sent from my Samsung Galaxy smartphone. > -------- Original message -------- > From: Stephanie Perrin > > Date: 20/02/2019 21:59 (GMT+02:00) > To: Thato Mfikwe > Cc: Maryam Bakoshi > Subject: Re: [Ext] ICANN64 FC meeting preparations > > The event where the FC Chair, without informing his colleagues on Council > or the PC, invited senior ICANN staff to one of the first FC meetings. > Nobody was prepared. Most of us were unable to attend the last minute > meeting. Surprises are rarely appreciated, and noone knew the conditions > under which staff had been invited. If you check back in the email > archives you will be able to see the grumbling that ensued after that > meeting. Senior people are exceptionally busy at ICANN meetings....we > don't invite them unless we have consensus that we are ready to meet them. > > We are by nature a consultative group. The FC should always be consulted, > so there is an open record for members to consult. Many members have > strongly held views on the FC and its mandate, and check the email > archives. If there is nothing there, it is insufficiently transparent, at > least in my view. I believe that is a commonly held view. > > Stephanie > > > On 2019-02-20 13:51, Thato Mfikwe wrote: > > Hi Sephanie, > > What was an embarrasment? > > Thato Mfikwe. > > On Wed, Feb 20, 2019 at 8:40 PM Stephanie Perrin < > stephanie.perrin at mail.utoronto.ca> wrote: > >> Personally, I do not think we are ready to meet with ICANN Finance staff. >> However, it appears the request has gone. We have already gone through >> this when Ed was chairing the Finance Committee, and it was an >> embarrassment in my opinion. >> >> >> Cheers Stephanie >> On 2019-02-20 03:27, Maryam Bakoshi wrote: >> >> Hi Thato, >> >> Good morning I hope this email meets you well. I have forwarded this >> request to Mary Wong, ICANN Staff. >> >> I am also cc?ing Stephanie, so she is in the loop. >> >> ? >> Many thanks, >> >> >> *Maryam Bakoshi* | SO/AC Collaboration Services Sr. Coordinator >> *ICANN* | Internet Corporation for Assigned Names and Numbers >> *S*: Maryam.bakoshi.icann | *T*: ?+44 7846 471777? >> >> On 20 Feb 2019, at 00:25, Thato Mfikwe wrote: >> >> Hi Maryam, >> >> Is it possible that we request the presence of one of ICANN Finance staff >> and ICANN legal in the FC meeting in Kobe which will be taking place on >> Wednesday, 15h15 - 16h45. >> >> Main support needed from ICANN staff: >> - Elaboration on legal implications on incorporation of NCSG and what it >> will mean for ICANN. >> - Advice on alternative sources of fundraising and opening a bank account >> in the name of NCSG. >> - Recommendation on how to best set up the Operational Procedures and >> ways of working with ICANN finance to support NCSG and constituency >> initiatives and activities. >> - Provision of clarity on how community comments are reflected in current >> and future ICANN operational and financial plans. >> >> We only have 2 weeks before the meeting. I hope this message, finds you >> well, thanks. >> >> Thato Mfikwe. >> >> -- *Bruna Martins dos Santos * Skype ID: bruna.martinsantos @boomartins -------------- next part -------------- An HTML attachment was scrubbed... URL: From remmyn at gmail.com Thu Feb 21 00:31:23 2019 From: remmyn at gmail.com (Remmy Nweke) Date: Wed, 20 Feb 2019 23:31:23 +0100 Subject: [NCSG-FC] [Ext] ICANN64 FC meeting preparations In-Reply-To: <6e8404b1-94e0-6187-caa0-4565afe3c94e@mail.utoronto.ca> References: <5jyfwu2xk66oqy1s1u7a9dwe.1550696024335@email.android.com> <6e8404b1-94e0-6187-caa0-4565afe3c94e@mail.utoronto.ca> Message-ID: Dear FC Sure the week has been busy. I have noticed in the NCUC call for FC representative that there is a discrepancy of NCUC charter and that of NCSG on FC on modalities of getting new members For the NCSG the chair of constituencies are the observers which is not the case with NCUC quoted charter thereof. Like I have maintained, it's better we resolve this discrepancy among others in charter as they come before further engagement so as to avoid engagement that will leave people on the street instead of the house and going round the house. Regards Remmy On Wed, 20 Feb 2019, 10:26 p.m. Stephanie Perrin < stephanie.perrin at mail.utoronto.ca wrote: > I think you must have meant this for Bruna, Thato. I am not the head of > the NCUC, nor of NPOC. the heads of those constituencies are in charge of > managing the selection of their members of the Finance Cttee, not me. > ccing Bruna so she can respond. Other responses in line. > > Stephanie > On 2019-02-20 15:53, thatomfikwe wrote: > > Hi, > > > When things are happening in parallel, with announcements for FC members > replacement, makes the entire planning process for the Kobe meeting a > mission. > > It would have been better if such announcements were made after ICANN64, > they put the FC in a difficult position and the Kobe meeting is planned to > revive the FC not create uncertainty and uncomfortable situations with > members who will be leading deliberations. Not sure if such actions were > well thought of or well planned. > > see Bruna and Joan > > > > I am not exactly sure how we are going to proceed despite serveral > attempts to hold a meeting with members before Kobe in order to discuss the > planned agenda in detail and emerging issues. > > Do you have any idea how busy council is, and the epdp, and the WHOIS > review cttee, and the comments process in general? We are running ragged. > WE need more members to staff the working groups. > > > ICANN staff is just an email away, the Charter requires the FC to work > with ICANN finance so if the committee is to be effective then it needs to > establish or revive critical connections that will ensure that NCSG and its > constituencies are fairly supported. > > First we determine our own policy positions. Do we want paid > memberships? Do we want to establish an entity, if so what? These are not > issues to discuss with staff, they would not be authorized to express an > opinion, nor should they. > > > Regarding the strong position of the community, what issues are they > arguing? Do you think they are valid and what were the reposnes of members > during that time? > > not sure what this question is addressing > > > If you carefully review comments, they.were centered around > - the bank account and incorporation of NCSG. This is currently being > dealt with and in progress, to also be further discussed and decided upon > - the role of the FC, many disagree with a lot of what is stipulated on > the Charter, whereas the Charter uses simple language > > Indeed, I cannot figure out for the life of me what the drafters of the > Charter had in mind. Establishing an entity has serious financial > repercussions. I have no idea where the money for that would come from. > Fund raising is difficult at the best of times, to support us at > ICANN....likely to be quite a chore. > > > When we review we need to be objective, even though it might seem like the > vocal in the mailing list are the majority. If the FC is designed to have > no autonomy then its efforts to correct mistakes of the past will always go > unnoticed and unrecognised. > > what specific mistakes are you talking about? > > > > > Thato Mfikwe. > > Sent from my Samsung Galaxy smartphone. > -------- Original message -------- > From: Stephanie Perrin > > Date: 20/02/2019 21:59 (GMT+02:00) > To: Thato Mfikwe > Cc: Maryam Bakoshi > Subject: Re: [Ext] ICANN64 FC meeting preparations > > The event where the FC Chair, without informing his colleagues on Council > or the PC, invited senior ICANN staff to one of the first FC meetings. > Nobody was prepared. Most of us were unable to attend the last minute > meeting. Surprises are rarely appreciated, and noone knew the conditions > under which staff had been invited. If you check back in the email > archives you will be able to see the grumbling that ensued after that > meeting. Senior people are exceptionally busy at ICANN meetings....we > don't invite them unless we have consensus that we are ready to meet them. > > We are by nature a consultative group. The FC should always be consulted, > so there is an open record for members to consult. Many members have > strongly held views on the FC and its mandate, and check the email > archives. If there is nothing there, it is insufficiently transparent, at > least in my view. I believe that is a commonly held view. > > Stephanie > > > On 2019-02-20 13:51, Thato Mfikwe wrote: > > Hi Sephanie, > > What was an embarrasment? > > Thato Mfikwe. > > On Wed, Feb 20, 2019 at 8:40 PM Stephanie Perrin < > stephanie.perrin at mail.utoronto.ca> wrote: > >> Personally, I do not think we are ready to meet with ICANN Finance staff. >> However, it appears the request has gone. We have already gone through >> this when Ed was chairing the Finance Committee, and it was an >> embarrassment in my opinion. >> >> >> Cheers Stephanie >> On 2019-02-20 03:27, Maryam Bakoshi wrote: >> >> Hi Thato, >> >> Good morning I hope this email meets you well. I have forwarded this >> request to Mary Wong, ICANN Staff. >> >> I am also cc?ing Stephanie, so she is in the loop. >> >> ? >> Many thanks, >> >> >> *Maryam Bakoshi* | SO/AC Collaboration Services Sr. Coordinator >> *ICANN* | Internet Corporation for Assigned Names and Numbers >> *S*: Maryam.bakoshi.icann | *T*: ?+44 7846 471777? >> >> On 20 Feb 2019, at 00:25, Thato Mfikwe wrote: >> >> Hi Maryam, >> >> Is it possible that we request the presence of one of ICANN Finance staff >> and ICANN legal in the FC meeting in Kobe which will be taking place on >> Wednesday, 15h15 - 16h45. >> >> Main support needed from ICANN staff: >> - Elaboration on legal implications on incorporation of NCSG and what it >> will mean for ICANN. >> - Advice on alternative sources of fundraising and opening a bank account >> in the name of NCSG. >> - Recommendation on how to best set up the Operational Procedures and >> ways of working with ICANN finance to support NCSG and constituency >> initiatives and activities. >> - Provision of clarity on how community comments are reflected in current >> and future ICANN operational and financial plans. >> >> We only have 2 weeks before the meeting. I hope this message, finds you >> well, thanks. >> >> Thato Mfikwe. >> >> _______________________________________________ > NCSG-FC mailing list > NCSG-FC at lists.ncsg.is > https://lists.ncsg.is/mailman/listinfo/ncsg-fc > On Wed, 20 Feb 2019, 10:26 p.m. Stephanie Perrin < stephanie.perrin at mail.utoronto.ca wrote: > I think you must have meant this for Bruna, Thato. I am not the head of > the NCUC, nor of NPOC. the heads of those constituencies are in charge of > managing the selection of their members of the Finance Cttee, not me. > ccing Bruna so she can respond. Other responses in line. > > Stephanie > On 2019-02-20 15:53, thatomfikwe wrote: > > Hi, > > > When things are happening in parallel, with announcements for FC members > replacement, makes the entire planning process for the Kobe meeting a > mission. > > It would have been better if such announcements were made after ICANN64, > they put the FC in a difficult position and the Kobe meeting is planned to > revive the FC not create uncertainty and uncomfortable situations with > members who will be leading deliberations. Not sure if such actions were > well thought of or well planned. > > see Bruna and Joan > > > > I am not exactly sure how we are going to proceed despite serveral > attempts to hold a meeting with members before Kobe in order to discuss the > planned agenda in detail and emerging issues. > > Do you have any idea how busy council is, and the epdp, and the WHOIS > review cttee, and the comments process in general? We are running ragged. > WE need more members to staff the working groups. > > > ICANN staff is just an email away, the Charter requires the FC to work > with ICANN finance so if the committee is to be effective then it needs to > establish or revive critical connections that will ensure that NCSG and its > constituencies are fairly supported. > > First we determine our own policy positions. Do we want paid > memberships? Do we want to establish an entity, if so what? These are not > issues to discuss with staff, they would not be authorized to express an > opinion, nor should they. > > > Regarding the strong position of the community, what issues are they > arguing? Do you think they are valid and what were the reposnes of members > during that time? > > not sure what this question is addressing > > > If you carefully review comments, they.were centered around > - the bank account and incorporation of NCSG. This is currently being > dealt with and in progress, to also be further discussed and decided upon > - the role of the FC, many disagree with a lot of what is stipulated on > the Charter, whereas the Charter uses simple language > > Indeed, I cannot figure out for the life of me what the drafters of the > Charter had in mind. Establishing an entity has serious financial > repercussions. I have no idea where the money for that would come from. > Fund raising is difficult at the best of times, to support us at > ICANN....likely to be quite a chore. > > > When we review we need to be objective, even though it might seem like the > vocal in the mailing list are the majority. If the FC is designed to have > no autonomy then its efforts to correct mistakes of the past will always go > unnoticed and unrecognised. > > what specific mistakes are you talking about? > > > > > Thato Mfikwe. > > Sent from my Samsung Galaxy smartphone. > -------- Original message -------- > From: Stephanie Perrin > > Date: 20/02/2019 21:59 (GMT+02:00) > To: Thato Mfikwe > Cc: Maryam Bakoshi > Subject: Re: [Ext] ICANN64 FC meeting preparations > > The event where the FC Chair, without informing his colleagues on Council > or the PC, invited senior ICANN staff to one of the first FC meetings. > Nobody was prepared. Most of us were unable to attend the last minute > meeting. Surprises are rarely appreciated, and noone knew the conditions > under which staff had been invited. If you check back in the email > archives you will be able to see the grumbling that ensued after that > meeting. Senior people are exceptionally busy at ICANN meetings....we > don't invite them unless we have consensus that we are ready to meet them. > > We are by nature a consultative group. The FC should always be consulted, > so there is an open record for members to consult. Many members have > strongly held views on the FC and its mandate, and check the email > archives. If there is nothing there, it is insufficiently transparent, at > least in my view. I believe that is a commonly held view. > > Stephanie > > > On 2019-02-20 13:51, Thato Mfikwe wrote: > > Hi Sephanie, > > What was an embarrasment? > > Thato Mfikwe. > > On Wed, Feb 20, 2019 at 8:40 PM Stephanie Perrin < > stephanie.perrin at mail.utoronto.ca> wrote: > >> Personally, I do not think we are ready to meet with ICANN Finance staff. >> However, it appears the request has gone. We have already gone through >> this when Ed was chairing the Finance Committee, and it was an >> embarrassment in my opinion. >> >> >> Cheers Stephanie >> On 2019-02-20 03:27, Maryam Bakoshi wrote: >> >> Hi Thato, >> >> Good morning I hope this email meets you well. I have forwarded this >> request to Mary Wong, ICANN Staff. >> >> I am also cc?ing Stephanie, so she is in the loop. >> >> ? >> Many thanks, >> >> >> *Maryam Bakoshi* | SO/AC Collaboration Services Sr. Coordinator >> *ICANN* | Internet Corporation for Assigned Names and Numbers >> *S*: Maryam.bakoshi.icann | *T*: ?+44 7846 471777? >> >> On 20 Feb 2019, at 00:25, Thato Mfikwe wrote: >> >> Hi Maryam, >> >> Is it possible that we request the presence of one of ICANN Finance staff >> and ICANN legal in the FC meeting in Kobe which will be taking place on >> Wednesday, 15h15 - 16h45. >> >> Main support needed from ICANN staff: >> - Elaboration on legal implications on incorporation of NCSG and what it >> will mean for ICANN. >> - Advice on alternative sources of fundraising and opening a bank account >> in the name of NCSG. >> - Recommendation on how to best set up the Operational Procedures and >> ways of working with ICANN finance to support NCSG and constituency >> initiatives and activities. >> - Provision of clarity on how community comments are reflected in current >> and future ICANN operational and financial plans. >> >> We only have 2 weeks before the meeting. I hope this message, finds you >> well, thanks. >> >> Thato Mfikwe. >> >> _______________________________________________ > NCSG-FC mailing list > NCSG-FC at lists.ncsg.is > https://lists.ncsg.is/mailman/listinfo/ncsg-fc > -------------- next part -------------- An HTML attachment was scrubbed... URL: From bruna.mrtns at gmail.com Thu Feb 21 00:41:54 2019 From: bruna.mrtns at gmail.com (Bruna Martins dos Santos) Date: Wed, 20 Feb 2019 19:41:54 -0300 Subject: [NCSG-FC] [Ext] ICANN64 FC meeting preparations In-Reply-To: References: <5jyfwu2xk66oqy1s1u7a9dwe.1550696024335@email.android.com> <6e8404b1-94e0-6187-caa0-4565afe3c94e@mail.utoronto.ca> Message-ID: Hey Remmy, About the composition of the FC, please refer to section 2.6.1 of the NCSG Charter : *2.6.1. NCSG?FC Composition.* *The NCSG Finance Committee (FC) shall be comprised of one representative from each Recognized Constituency. Each Candidate Constituency is entitled to appoint an observer. The NCSG Chair will participate as an ex?officio member of the NCSG?FC and will be included in consensus process and votes. The FC may invite other members as needed to meet its goals and responsibilities.* This is not a situation of a call for new members, but the case of the NCUC appointee to the FC which is the position Thato occupies at Finance Committee. best, Em qua, 20 de fev de 2019 ?s 19:31, Remmy Nweke escreveu: > Dear FC > Sure the week has been busy. > > I have noticed in the NCUC call for FC representative that there is a > discrepancy of NCUC charter and that of NCSG on FC on modalities of getting > new members > For the NCSG the chair of constituencies are the observers which is not > the case with NCUC quoted charter thereof. > > Like I have maintained, it's better we resolve this discrepancy among > others in charter as they come before further engagement so as to avoid > engagement that will leave people on the street instead of the house and > going round the house. > Regards > Remmy > > On Wed, 20 Feb 2019, 10:26 p.m. Stephanie Perrin < > stephanie.perrin at mail.utoronto.ca wrote: > >> I think you must have meant this for Bruna, Thato. I am not the head of >> the NCUC, nor of NPOC. the heads of those constituencies are in charge of >> managing the selection of their members of the Finance Cttee, not me. >> ccing Bruna so she can respond. Other responses in line. >> >> Stephanie >> On 2019-02-20 15:53, thatomfikwe wrote: >> >> Hi, >> >> >> When things are happening in parallel, with announcements for FC members >> replacement, makes the entire planning process for the Kobe meeting a >> mission. >> >> It would have been better if such announcements were made after ICANN64, >> they put the FC in a difficult position and the Kobe meeting is planned to >> revive the FC not create uncertainty and uncomfortable situations with >> members who will be leading deliberations. Not sure if such actions were >> well thought of or well planned. >> >> see Bruna and Joan >> >> >> >> I am not exactly sure how we are going to proceed despite serveral >> attempts to hold a meeting with members before Kobe in order to discuss the >> planned agenda in detail and emerging issues. >> >> Do you have any idea how busy council is, and the epdp, and the WHOIS >> review cttee, and the comments process in general? We are running ragged. >> WE need more members to staff the working groups. >> >> >> ICANN staff is just an email away, the Charter requires the FC to work >> with ICANN finance so if the committee is to be effective then it needs to >> establish or revive critical connections that will ensure that NCSG and its >> constituencies are fairly supported. >> >> First we determine our own policy positions. Do we want paid >> memberships? Do we want to establish an entity, if so what? These are not >> issues to discuss with staff, they would not be authorized to express an >> opinion, nor should they. >> >> >> Regarding the strong position of the community, what issues are they >> arguing? Do you think they are valid and what were the reposnes of members >> during that time? >> >> not sure what this question is addressing >> >> >> If you carefully review comments, they.were centered around >> - the bank account and incorporation of NCSG. This is currently being >> dealt with and in progress, to also be further discussed and decided upon >> - the role of the FC, many disagree with a lot of what is stipulated on >> the Charter, whereas the Charter uses simple language >> >> Indeed, I cannot figure out for the life of me what the drafters of the >> Charter had in mind. Establishing an entity has serious financial >> repercussions. I have no idea where the money for that would come from. >> Fund raising is difficult at the best of times, to support us at >> ICANN....likely to be quite a chore. >> >> >> When we review we need to be objective, even though it might seem like >> the vocal in the mailing list are the majority. If the FC is designed to >> have no autonomy then its efforts to correct mistakes of the past will >> always go unnoticed and unrecognised. >> >> what specific mistakes are you talking about? >> >> >> >> >> Thato Mfikwe. >> >> Sent from my Samsung Galaxy smartphone. >> -------- Original message -------- >> From: Stephanie Perrin >> >> Date: 20/02/2019 21:59 (GMT+02:00) >> To: Thato Mfikwe >> Cc: Maryam Bakoshi >> Subject: Re: [Ext] ICANN64 FC meeting preparations >> >> The event where the FC Chair, without informing his colleagues on Council >> or the PC, invited senior ICANN staff to one of the first FC meetings. >> Nobody was prepared. Most of us were unable to attend the last minute >> meeting. Surprises are rarely appreciated, and noone knew the conditions >> under which staff had been invited. If you check back in the email >> archives you will be able to see the grumbling that ensued after that >> meeting. Senior people are exceptionally busy at ICANN meetings....we >> don't invite them unless we have consensus that we are ready to meet them. >> >> We are by nature a consultative group. The FC should always be >> consulted, so there is an open record for members to consult. Many members >> have strongly held views on the FC and its mandate, and check the email >> archives. If there is nothing there, it is insufficiently transparent, at >> least in my view. I believe that is a commonly held view. >> >> Stephanie >> >> >> On 2019-02-20 13:51, Thato Mfikwe wrote: >> >> Hi Sephanie, >> >> What was an embarrasment? >> >> Thato Mfikwe. >> >> On Wed, Feb 20, 2019 at 8:40 PM Stephanie Perrin < >> stephanie.perrin at mail.utoronto.ca> wrote: >> >>> Personally, I do not think we are ready to meet with ICANN Finance >>> staff. However, it appears the request has gone. We have already gone >>> through this when Ed was chairing the Finance Committee, and it was an >>> embarrassment in my opinion. >>> >>> >>> Cheers Stephanie >>> On 2019-02-20 03:27, Maryam Bakoshi wrote: >>> >>> Hi Thato, >>> >>> Good morning I hope this email meets you well. I have forwarded this >>> request to Mary Wong, ICANN Staff. >>> >>> I am also cc?ing Stephanie, so she is in the loop. >>> >>> ? >>> Many thanks, >>> >>> >>> *Maryam Bakoshi* | SO/AC Collaboration Services Sr. Coordinator >>> *ICANN* | Internet Corporation for Assigned Names and Numbers >>> *S*: Maryam.bakoshi.icann | *T*: ?+44 7846 471777? >>> >>> On 20 Feb 2019, at 00:25, Thato Mfikwe wrote: >>> >>> Hi Maryam, >>> >>> Is it possible that we request the presence of one of ICANN Finance >>> staff and ICANN legal in the FC meeting in Kobe which will be taking place >>> on Wednesday, 15h15 - 16h45. >>> >>> Main support needed from ICANN staff: >>> - Elaboration on legal implications on incorporation of NCSG and what it >>> will mean for ICANN. >>> - Advice on alternative sources of fundraising and opening a bank >>> account in the name of NCSG. >>> - Recommendation on how to best set up the Operational Procedures and >>> ways of working with ICANN finance to support NCSG and constituency >>> initiatives and activities. >>> - Provision of clarity on how community comments are reflected in >>> current and future ICANN operational and financial plans. >>> >>> We only have 2 weeks before the meeting. I hope this message, finds you >>> well, thanks. >>> >>> Thato Mfikwe. >>> >>> _______________________________________________ >> NCSG-FC mailing list >> NCSG-FC at lists.ncsg.is >> https://lists.ncsg.is/mailman/listinfo/ncsg-fc >> > > On Wed, 20 Feb 2019, 10:26 p.m. Stephanie Perrin < > stephanie.perrin at mail.utoronto.ca wrote: > >> I think you must have meant this for Bruna, Thato. I am not the head of >> the NCUC, nor of NPOC. the heads of those constituencies are in charge of >> managing the selection of their members of the Finance Cttee, not me. >> ccing Bruna so she can respond. Other responses in line. >> >> Stephanie >> On 2019-02-20 15:53, thatomfikwe wrote: >> >> Hi, >> >> >> When things are happening in parallel, with announcements for FC members >> replacement, makes the entire planning process for the Kobe meeting a >> mission. >> >> It would have been better if such announcements were made after ICANN64, >> they put the FC in a difficult position and the Kobe meeting is planned to >> revive the FC not create uncertainty and uncomfortable situations with >> members who will be leading deliberations. Not sure if such actions were >> well thought of or well planned. >> >> see Bruna and Joan >> >> >> >> I am not exactly sure how we are going to proceed despite serveral >> attempts to hold a meeting with members before Kobe in order to discuss the >> planned agenda in detail and emerging issues. >> >> Do you have any idea how busy council is, and the epdp, and the WHOIS >> review cttee, and the comments process in general? We are running ragged. >> WE need more members to staff the working groups. >> >> >> ICANN staff is just an email away, the Charter requires the FC to work >> with ICANN finance so if the committee is to be effective then it needs to >> establish or revive critical connections that will ensure that NCSG and its >> constituencies are fairly supported. >> >> First we determine our own policy positions. Do we want paid >> memberships? Do we want to establish an entity, if so what? These are not >> issues to discuss with staff, they would not be authorized to express an >> opinion, nor should they. >> >> >> Regarding the strong position of the community, what issues are they >> arguing? Do you think they are valid and what were the reposnes of members >> during that time? >> >> not sure what this question is addressing >> >> >> If you carefully review comments, they.were centered around >> - the bank account and incorporation of NCSG. This is currently being >> dealt with and in progress, to also be further discussed and decided upon >> - the role of the FC, many disagree with a lot of what is stipulated on >> the Charter, whereas the Charter uses simple language >> >> Indeed, I cannot figure out for the life of me what the drafters of the >> Charter had in mind. Establishing an entity has serious financial >> repercussions. I have no idea where the money for that would come from. >> Fund raising is difficult at the best of times, to support us at >> ICANN....likely to be quite a chore. >> >> >> When we review we need to be objective, even though it might seem like >> the vocal in the mailing list are the majority. If the FC is designed to >> have no autonomy then its efforts to correct mistakes of the past will >> always go unnoticed and unrecognised. >> >> what specific mistakes are you talking about? >> >> >> >> >> Thato Mfikwe. >> >> Sent from my Samsung Galaxy smartphone. >> -------- Original message -------- >> From: Stephanie Perrin >> >> Date: 20/02/2019 21:59 (GMT+02:00) >> To: Thato Mfikwe >> Cc: Maryam Bakoshi >> Subject: Re: [Ext] ICANN64 FC meeting preparations >> >> The event where the FC Chair, without informing his colleagues on Council >> or the PC, invited senior ICANN staff to one of the first FC meetings. >> Nobody was prepared. Most of us were unable to attend the last minute >> meeting. Surprises are rarely appreciated, and noone knew the conditions >> under which staff had been invited. If you check back in the email >> archives you will be able to see the grumbling that ensued after that >> meeting. Senior people are exceptionally busy at ICANN meetings....we >> don't invite them unless we have consensus that we are ready to meet them. >> >> We are by nature a consultative group. The FC should always be >> consulted, so there is an open record for members to consult. Many members >> have strongly held views on the FC and its mandate, and check the email >> archives. If there is nothing there, it is insufficiently transparent, at >> least in my view. I believe that is a commonly held view. >> >> Stephanie >> >> >> On 2019-02-20 13:51, Thato Mfikwe wrote: >> >> Hi Sephanie, >> >> What was an embarrasment? >> >> Thato Mfikwe. >> >> On Wed, Feb 20, 2019 at 8:40 PM Stephanie Perrin < >> stephanie.perrin at mail.utoronto.ca> wrote: >> >>> Personally, I do not think we are ready to meet with ICANN Finance >>> staff. However, it appears the request has gone. We have already gone >>> through this when Ed was chairing the Finance Committee, and it was an >>> embarrassment in my opinion. >>> >>> >>> Cheers Stephanie >>> On 2019-02-20 03:27, Maryam Bakoshi wrote: >>> >>> Hi Thato, >>> >>> Good morning I hope this email meets you well. I have forwarded this >>> request to Mary Wong, ICANN Staff. >>> >>> I am also cc?ing Stephanie, so she is in the loop. >>> >>> ? >>> Many thanks, >>> >>> >>> *Maryam Bakoshi* | SO/AC Collaboration Services Sr. Coordinator >>> *ICANN* | Internet Corporation for Assigned Names and Numbers >>> *S*: Maryam.bakoshi.icann | *T*: ?+44 7846 471777? >>> >>> On 20 Feb 2019, at 00:25, Thato Mfikwe wrote: >>> >>> Hi Maryam, >>> >>> Is it possible that we request the presence of one of ICANN Finance >>> staff and ICANN legal in the FC meeting in Kobe which will be taking place >>> on Wednesday, 15h15 - 16h45. >>> >>> Main support needed from ICANN staff: >>> - Elaboration on legal implications on incorporation of NCSG and what it >>> will mean for ICANN. >>> - Advice on alternative sources of fundraising and opening a bank >>> account in the name of NCSG. >>> - Recommendation on how to best set up the Operational Procedures and >>> ways of working with ICANN finance to support NCSG and constituency >>> initiatives and activities. >>> - Provision of clarity on how community comments are reflected in >>> current and future ICANN operational and financial plans. >>> >>> We only have 2 weeks before the meeting. I hope this message, finds you >>> well, thanks. >>> >>> Thato Mfikwe. >>> >>> _______________________________________________ >> NCSG-FC mailing list >> NCSG-FC at lists.ncsg.is >> https://lists.ncsg.is/mailman/listinfo/ncsg-fc >> > -- *Bruna Martins dos Santos * Skype ID: bruna.martinsantos @boomartins -------------- next part -------------- An HTML attachment was scrubbed... URL: From remmyn at gmail.com Thu Feb 21 01:26:46 2019 From: remmyn at gmail.com (Remmy Nweke) Date: Thu, 21 Feb 2019 00:26:46 +0100 Subject: [NCSG-FC] [Ext] ICANN64 FC meeting preparations In-Reply-To: References: <5jyfwu2xk66oqy1s1u7a9dwe.1550696024335@email.android.com> <6e8404b1-94e0-6187-caa0-4565afe3c94e@mail.utoronto.ca> Message-ID: Hi dear Bruna Without holding brief for Thato the issue of inviting ICANN to share some insights on their expectations was not new and was shared in our Panama meeting with both C's chair and report then to our immediate communities and we had no objection as far as I can recall. And was also to help NCSG have a direction on ICANN tasks of demand on FC. So it's not new. It's unfortunate that the only thing people see in FC is about travels, forgetting FC actually has to wear the NCSG cap to populate it to relevant communities with aim of fundraising. Much of these Stephanie pointed out in earlier submissions as a big chores, conversely, brand marketing for sponsorship deserves full option which include face to face in relevant events. FC did not have a specific direction on who submits ABR or not and be that as it may, it was never intended in bad faith knowing fully well its an open document/process and holding it against anyone is discouraging if not dehumnising. Agreed mistakes were made along the line including use of NCSG chair name which may have been done by the iCANN secretariat. Without mistakes it beome impossible especially where an ocean of communication gap exist to learn. I am sure you must have seen communications on having FC reps in the Excom. Why not? So that those reps will have a feel or body language where things are going and ask relevant questions and also take direction for smooth co-existence. Though not very surprised that auditors everywhere are not appreciated, hence the assignment/mandate of FC goes beyond mere auditing. This I had pointed out earlier needs to be revisited and FC devolved into auditors, financial Secretariat and fundraising committee if we so desire and want things worked out. The complexity of these trio is what is making things a bit muddled up and if we must make progress, FC must have some level of autonomy for effective auditing, beginning with the review of our NCSG charter. And finally our leadership and membership inability to appreciate these facts based on unharmonised charter and on what FC roles are and mandates should be, will keep us with same circle unless we just want o'Yes members in FC as reps. We can't have a twin and favour one and expect the other one not to shout, otherwise it goes into oblivion. Best of the day Remmy On Wed, 20 Feb 2019, 11:30 p.m. Bruna Martins dos Santos < bruna.mrtns at gmail.com wrote: > Hey Thato, > > I sincerely don't know how to deal with so many FC incidents. You have > been claiming for the so-called 'independence' but all I have seen so far > is a huge disregard for NSCG and its constituencies. So far you have added > stuff to your Operating procedures that were not agreed with neither > suggested by membership (such as the attempt of granting travel slots to > the FC), submitted ABRs that involved the SG and its Constituencies > activities without even notifying the leadership teams and now we have this > invitation for staff to join the FC meeting in Kobe without, once again, > consulting with membership - even despite the fact that on the thread about > NCSG bank account several members considered that asking staff for advice > at such stage (of the FC) would not be advisable. Sincerely it has been > really hard trying to work with the FC when I know that despite of the > advice that we might add to any discussions will be simply ignored. > > With regards to 'announcements for FC members replacement' I guess there > is a little misunderstanding on your behalf here. All NCSG/NCUC/NPOC > leadership positions have terms, even the appointed ones. And you might > recall that back in Barcelona, when I became NCUC chair, we announced that > the calls for NCUC appointees to all NCSG committees would be done at the > beginning of this year. So this is not an attempt to shut down any > committee, but simply NCUC complying with its operating procedures. If you > have any interest in continuing at this position you should apply to be > once again the NCUC appointee to the FC, and the EC will deliberate on this > - I dont have a say in votings unless we have a tie. > > Other than coming back and forth with such discussions, I think the FC > could be doing a little inreaching to membership. I am pretty sure that the > FC members are all capable of doing these discussions and I would > personally like to see you being involved with the ICANN Strategic Plan for > Fiscal Years 2021 ? 2025 and maybe even being the penholders of this > comment. Or even asking the mailing lists about what discussions they would > like to see at the FC meeting in Kobe. > > Best, > Bruna > > Em qua, 20 de fev de 2019 ?s 18:26, Stephanie Perrin < > stephanie.perrin at mail.utoronto.ca> escreveu: > >> I think you must have meant this for Bruna, Thato. I am not the head of >> the NCUC, nor of NPOC. the heads of those constituencies are in charge of >> managing the selection of their members of the Finance Cttee, not me. >> ccing Bruna so she can respond. Other responses in line. >> >> Stephanie >> On 2019-02-20 15:53, thatomfikwe wrote: >> >> Hi, >> >> >> When things are happening in parallel, with announcements for FC members >> replacement, makes the entire planning process for the Kobe meeting a >> mission. >> >> It would have been better if such announcements were made after ICANN64, >> they put the FC in a difficult position and the Kobe meeting is planned to >> revive the FC not create uncertainty and uncomfortable situations with >> members who will be leading deliberations. Not sure if such actions were >> well thought of or well planned. >> >> see Bruna and Joan >> >> >> >> I am not exactly sure how we are going to proceed despite serveral >> attempts to hold a meeting with members before Kobe in order to discuss the >> planned agenda in detail and emerging issues. >> >> Do you have any idea how busy council is, and the epdp, and the WHOIS >> review cttee, and the comments process in general? We are running ragged. >> WE need more members to staff the working groups. >> >> >> ICANN staff is just an email away, the Charter requires the FC to work >> with ICANN finance so if the committee is to be effective then it needs to >> establish or revive critical connections that will ensure that NCSG and its >> constituencies are fairly supported. >> >> First we determine our own policy positions. Do we want paid >> memberships? Do we want to establish an entity, if so what? These are not >> issues to discuss with staff, they would not be authorized to express an >> opinion, nor should they. >> >> >> Regarding the strong position of the community, what issues are they >> arguing? Do you think they are valid and what were the reposnes of members >> during that time? >> >> not sure what this question is addressing >> >> >> If you carefully review comments, they.were centered around >> - the bank account and incorporation of NCSG. This is currently being >> dealt with and in progress, to also be further discussed and decided upon >> - the role of the FC, many disagree with a lot of what is stipulated on >> the Charter, whereas the Charter uses simple language >> >> Indeed, I cannot figure out for the life of me what the drafters of the >> Charter had in mind. Establishing an entity has serious financial >> repercussions. I have no idea where the money for that would come from. >> Fund raising is difficult at the best of times, to support us at >> ICANN....likely to be quite a chore. >> >> >> When we review we need to be objective, even though it might seem like >> the vocal in the mailing list are the majority. If the FC is designed to >> have no autonomy then its efforts to correct mistakes of the past will >> always go unnoticed and unrecognised. >> >> what specific mistakes are you talking about? >> >> >> >> >> Thato Mfikwe. >> >> Sent from my Samsung Galaxy smartphone. >> -------- Original message -------- >> From: Stephanie Perrin >> >> Date: 20/02/2019 21:59 (GMT+02:00) >> To: Thato Mfikwe >> Cc: Maryam Bakoshi >> Subject: Re: [Ext] ICANN64 FC meeting preparations >> >> The event where the FC Chair, without informing his colleagues on Council >> or the PC, invited senior ICANN staff to one of the first FC meetings. >> Nobody was prepared. Most of us were unable to attend the last minute >> meeting. Surprises are rarely appreciated, and noone knew the conditions >> under which staff had been invited. If you check back in the email >> archives you will be able to see the grumbling that ensued after that >> meeting. Senior people are exceptionally busy at ICANN meetings....we >> don't invite them unless we have consensus that we are ready to meet them. >> >> We are by nature a consultative group. The FC should always be >> consulted, so there is an open record for members to consult. Many members >> have strongly held views on the FC and its mandate, and check the email >> archives. If there is nothing there, it is insufficiently transparent, at >> least in my view. I believe that is a commonly held view. >> >> Stephanie >> >> >> On 2019-02-20 13:51, Thato Mfikwe wrote: >> >> Hi Sephanie, >> >> What was an embarrasment? >> >> Thato Mfikwe. >> >> On Wed, Feb 20, 2019 at 8:40 PM Stephanie Perrin < >> stephanie.perrin at mail.utoronto.ca> wrote: >> >>> Personally, I do not think we are ready to meet with ICANN Finance >>> staff. However, it appears the request has gone. We have already gone >>> through this when Ed was chairing the Finance Committee, and it was an >>> embarrassment in my opinion. >>> >>> >>> Cheers Stephanie >>> On 2019-02-20 03:27, Maryam Bakoshi wrote: >>> >>> Hi Thato, >>> >>> Good morning I hope this email meets you well. I have forwarded this >>> request to Mary Wong, ICANN Staff. >>> >>> I am also cc?ing Stephanie, so she is in the loop. >>> >>> ? >>> Many thanks, >>> >>> >>> *Maryam Bakoshi* | SO/AC Collaboration Services Sr. Coordinator >>> *ICANN* | Internet Corporation for Assigned Names and Numbers >>> *S*: Maryam.bakoshi.icann | *T*: ?+44 7846 471777? >>> >>> On 20 Feb 2019, at 00:25, Thato Mfikwe wrote: >>> >>> Hi Maryam, >>> >>> Is it possible that we request the presence of one of ICANN Finance >>> staff and ICANN legal in the FC meeting in Kobe which will be taking place >>> on Wednesday, 15h15 - 16h45. >>> >>> Main support needed from ICANN staff: >>> - Elaboration on legal implications on incorporation of NCSG and what it >>> will mean for ICANN. >>> - Advice on alternative sources of fundraising and opening a bank >>> account in the name of NCSG. >>> - Recommendation on how to best set up the Operational Procedures and >>> ways of working with ICANN finance to support NCSG and constituency >>> initiatives and activities. >>> - Provision of clarity on how community comments are reflected in >>> current and future ICANN operational and financial plans. >>> >>> We only have 2 weeks before the meeting. I hope this message, finds you >>> well, thanks. >>> >>> Thato Mfikwe. >>> >>> > > -- > *Bruna Martins dos Santos * > > Skype ID: bruna.martinsantos > @boomartins > _______________________________________________ > NCSG-FC mailing list > NCSG-FC at lists.ncsg.is > https://lists.ncsg.is/mailman/listinfo/ncsg-fc > -------------- next part -------------- An HTML attachment was scrubbed... URL: From thatomfikwe at gmail.com Thu Feb 21 02:00:56 2019 From: thatomfikwe at gmail.com (thatomfikwe) Date: Thu, 21 Feb 2019 02:00:56 +0200 Subject: [NCSG-FC] [Ext] ICANN64 FC meeting preparations Message-ID: <7p1j5d4dsu4sh4h09lsa1x51.1550707256664@email.android.com> Bruna, As the FC we need to agree on the meeting agenda so that it does not become my agenda when it goes to the mailing list. If not.interested in the meeting, please state so that other members can continue in the meanwhile. The operational procedures intergrated community input and FC inputs. I did.not put my personal opinion on the OP, feel free to comment on the doc as opposed to continue lashing. This doc still has to go to the NCSG EC. There is nothing wrong with the FC participating in meeting in order to establish itself and gain presence and confidence within the community. What is the real reason the FC need not attend F2F onsite meetings? Travel slots should be open to all committees and members and of course active and committee members must receive a significant portion. If this is not fair enough then I do not know what resolve the travel slots issue which is not just a FC issue but a community issue.? Fundraising and resource mobilisation is important, the FC understands what its duties but it seems like there are serious barrier within the committee as it is fighting with itself. Lately there has been a lot of toungue lashing on the FC. Which I consider disrespectful, we are not small children, nobody is better than the other, we all leaders in our own personal & different capacities. I try to maintain respect for all members of NCSG but if respect is not returned..then what? Leaders are normally in control of their emotions that is why they find it easy to lead diverse people. The charter needs review, if not the FC issues and problems will not come to an end. @Bruna, clearly there is no confidence right now in my participation within this committee, so what does the Ncuc EC really propose regarding this matter? I do not even see how I can reapply if the situation is as bad as you describe as the Chair. Its is pretty obvious what your position on this matter is. Your statements are very confusing because you later mention that I must consider being a penholder for the budget, yet you are telling me about my sins. Initially you said my term expired as NCUC Rep then you said I must continue with the meeting, please, I am not a robot, you can remote control me. The NCUC EC needs to make a decision whether I continue until further update as opposed to dancing to the music as it plays within the FC. Personal preferences are always supercedeed by community interest and organisational goals in a civil society environment. Thato Mfikwe. Sent from my Samsung Galaxy smartphone.-------- Original message --------From: Bruna Martins dos Santos Date: 21/02/2019 00:30 (GMT+02:00) To: Stephanie Perrin Cc: thatomfikwe , Maryam Bakoshi , ncsg-fc at lists.ncsg.is Subject: Re: [Ext] ICANN64 FC meeting preparations Hey Thato,? I sincerely don't know how to deal with so many FC incidents. You have been claiming for the so-called 'independence' but all I have seen so far is a huge disregard for NSCG and its constituencies. So far you have added stuff to your Operating procedures that were not agreed with neither suggested by membership (such as the attempt of granting travel slots to the FC), submitted ABRs that involved the SG and its Constituencies activities without even notifying the leadership teams and now we have this invitation for staff to join the FC meeting in Kobe without, once again, consulting with membership - even despite the fact that on the thread about NCSG bank account several members considered that asking staff for advice at such stage (of the FC) would not be advisable. Sincerely it has been really hard trying to work with the FC when I know that despite of the advice that we might add to any discussions will be simply ignored.? With regards to 'announcements for FC members replacement' I guess there is a little misunderstanding on your behalf here. All NCSG/NCUC/NPOC leadership positions have terms, even the appointed ones. And you might recall that back in Barcelona, when I became NCUC chair, we announced that the calls for NCUC appointees to all NCSG committees would be done at the beginning of this year. So this is not an attempt to shut down any committee, but simply NCUC complying with its operating procedures. If you have any interest in continuing at this position you should apply to be once again the NCUC appointee to the FC, and the EC will deliberate on this - I dont have a say in votings unless we have a tie.? Other than coming back and forth with such discussions, I think the FC could be doing a little inreaching to membership. I am pretty sure that the FC members are all capable of doing these discussions and I would personally like to see you being involved with the?ICANN Strategic Plan for Fiscal Years 2021 ? 2025 and maybe even being the penholders of this comment. Or even asking the mailing lists about what discussions they would like to see at the FC meeting in Kobe.? Best,?Bruna? Em qua, 20 de fev de 2019 ?s 18:26, Stephanie Perrin escreveu: I think you must have meant this for Bruna, Thato.? I am not the head of the NCUC, nor of NPOC.? the heads of those constituencies are in charge of managing the selection of their members of the Finance Cttee, not me.? ccing Bruna so she can respond.? Other responses in line. Stephanie On 2019-02-20 15:53, thatomfikwe wrote: Hi, When things are happening in parallel, with announcements for FC members replacement, makes the entire planning process for the Kobe meeting a mission. It would have been better if such announcements were made after ICANN64, they put the FC in a difficult position and the Kobe meeting is planned to revive the FC not create uncertainty and uncomfortable situations with members who will be leading deliberations. Not sure if such actions were well thought of or well planned. see Bruna and Joan I am not exactly sure how we are going to proceed despite serveral attempts to hold a meeting with members before Kobe in order to discuss the planned agenda in detail and emerging issues. Do you have any idea how busy council is, and the epdp, and the WHOIS review cttee, and the comments process in general?? We are running ragged.? WE need more members to staff the working groups. ICANN staff is just an email away, the Charter requires the FC to work with ICANN finance so if the committee is to be effective then it needs to establish or revive critical connections that will ensure that NCSG and its constituencies are fairly supported. First we determine our own policy positions.? Do we want paid memberships?? Do we want to establish an entity, if so what?? These are not issues to discuss with staff, they would not be authorized to express an opinion, nor should they. Regarding the strong position of the community, what issues are they arguing? Do you think they are valid and what were the reposnes of members during that time? not sure what this question is addressing If you carefully review comments, they.were centered around? - the bank account and incorporation of NCSG. This is currently being dealt with and in progress, to also be further discussed and decided upon - the role of the FC, many disagree with a lot of what is stipulated on the Charter, whereas the Charter uses simple language Indeed, I cannot figure out for the life of me what the drafters of the Charter had in mind.? Establishing an entity has serious financial repercussions.? I have no idea where the money for that would come from.? Fund raising is difficult at the best of times, to support us at ICANN....likely to be quite a chore. When we review we need to be objective, even though it might seem like the vocal in the mailing list are the majority. If the FC is designed to have no autonomy then its efforts to correct mistakes of the past will always go unnoticed and unrecognised. what specific mistakes are you talking about? Thato Mfikwe. Sent from my Samsung Galaxy smartphone. -------- Original message -------- From: Stephanie Perrin Date: 20/02/2019 21:59 (GMT+02:00) To: Thato Mfikwe Cc: Maryam Bakoshi Subject: Re: [Ext] ICANN64 FC meeting preparations The event where the FC Chair, without informing his colleagues on Council or the PC, invited senior ICANN staff to one of the first FC meetings.? Nobody was prepared.? Most of us were unable to attend the last minute meeting.? Surprises are rarely appreciated, and noone knew the conditions under which staff had been invited.?? If you check back in the email archives you will be able to see the grumbling that ensued after that meeting.? Senior people are exceptionally busy at ICANN meetings....we don't invite them unless we have consensus that we are ready to meet them. We are by nature a consultative group.? The FC should always be consulted, so there is an open record for members to consult.? Many members have strongly held views on the FC and its mandate, and check the email archives. If there is nothing there, it is insufficiently transparent, at least in my view.? I believe that is a commonly held view. Stephanie On 2019-02-20 13:51, Thato Mfikwe wrote: Hi Sephanie, What was an embarrasment? Thato Mfikwe. On Wed, Feb 20, 2019 at 8:40 PM Stephanie Perrin wrote: Personally, I do not think we are ready to meet with ICANN Finance staff. However, it appears the request has gone.? We have already gone through this when Ed was chairing the Finance Committee, and it was an embarrassment in my opinion. Cheers Stephanie On 2019-02-20 03:27, Maryam Bakoshi wrote: Hi Thato, Good morning I hope this email meets you well. I have forwarded this request to Mary Wong, ICANN Staff.? I am also cc?ing Stephanie, so she is in the loop.? ? Many thanks, Maryam Bakoshi?| SO/AC Collaboration Services Sr. Coordinator? ICANN?| Internet Corporation for Assigned Names and Numbers? S: Maryam.bakoshi.icann |?T:??+44 7846 471777? On 20 Feb 2019, at 00:25, Thato Mfikwe wrote: Hi Maryam, Is it possible that we request the presence of one of ICANN Finance staff and ICANN legal in the FC meeting in Kobe which will be taking place on Wednesday, 15h15 - 16h45. Main support needed from ICANN staff: - Elaboration on legal implications on incorporation of NCSG and what it will mean for ICANN. - Advice on alternative sources of fundraising and opening a bank account in the name of NCSG. - Recommendation on how to best set up the Operational Procedures and ways of working with ICANN finance to support NCSG and constituency initiatives and activities. - Provision of clarity on how community comments are reflected in current and future ICANN operational and financial plans. We only have 2 weeks before the meeting. I hope this message, finds you well, thanks. Thato Mfikwe. -- Bruna Martins dos Santos? Skype ID: bruna.martinsantos @boomartins -------------- next part -------------- An HTML attachment was scrubbed... URL: From bruna.mrtns at gmail.com Thu Feb 21 03:49:42 2019 From: bruna.mrtns at gmail.com (Bruna Martins dos Santos) Date: Wed, 20 Feb 2019 22:49:42 -0300 Subject: [NCSG-FC] [Ext] ICANN64 FC meeting preparations In-Reply-To: <7p1j5d4dsu4sh4h09lsa1x51.1550707256664@email.android.com> References: <7p1j5d4dsu4sh4h09lsa1x51.1550707256664@email.android.com> Message-ID: Dear Thato and Remmy, I agree with you both that we cannot continue with so many disagreements, it takes far too much time from all of us (especially when I have the NCUC Agenda for the Kobe meeting to finalize). The reason why we opened the call for NCUC Appointee to the Finance committee was solely based on the end of Thato's term. I might have my concerns with some recent concerns regarding the FC but I havent disclosed them in details to the NCUC EC. Thato, I also believe your comment on the lack of confidence in your participation at this commitee is not very accurate. I have tried to chatting with you in order to understand how could I help you and the FC from the NCUC perspective but there seems to be some sort of resistance to me - or on the fact that I am a female colleague based on the fact that you questioned my lack of 'control' for my emotions. Once again, the reason why I am on this list (as an observer) is based on the fact that I do want to contribute to the FC work. And when I advised you to reapply for the position I really meant it, @Thato Mfikwe . When I mentioned that I would have liked to see you both engaged with the comment is due to the fact that I consider you both apt for the job and the merit of the comment pretty much aligned with the FC activities. Maybe by doing this kind of work we can get you more fine tuned with the community and work our ways into empowering the FC - which is something I believe you both also want. I just dont think this empowerment will come from the FC acting without any community consultation and claiming that there was not a clear orientation on the matter. Lastly, I would once again stress that we need to work together and learn to respect opposite opinions, not simply lash at people and invest in petty attacks such as implying that I am not in control of my emotions. Being a woman working on the tech environment I should have gotten used to such implications by now, but it still offends me - especially when we are a group of people meaning to do the same work and simply not managing to understand that we are all saying the same things in different ways. Best, Bruna Em qua, 20 de fev de 2019 ?s 21:07, thatomfikwe escreveu: > Bruna, > > As the FC we need to agree on the meeting agenda so that it does not > become my agenda when it goes to the mailing list. If not.interested in the > meeting, please state so that other members can continue in the meanwhile. > > The operational procedures intergrated community input and FC inputs. I > did.not put my personal opinion on the OP, feel free to comment on the doc > as opposed to continue lashing. This doc still has to go to the NCSG EC. > > There is nothing wrong with the FC participating in meeting in order to > establish itself and gain presence and confidence within the community. > What is the real reason the FC need not attend F2F onsite meetings? > > Travel slots should be open to all committees and members and of course > active and committee members must receive a significant portion. If this is > not fair enough then I do not know what resolve the travel slots issue > which is not just a FC issue but a community issue. > > Fundraising and resource mobilisation is important, the FC understands > what its duties but it seems like there are serious barrier within the > committee as it is fighting with itself. > > Lately there has been a lot of toungue lashing on the FC. Which I consider > disrespectful, we are not small children, nobody is better than the other, > we all leaders in our own personal & different capacities. I try to > maintain respect for all members of NCSG but if respect is not > returned..then what? > > Leaders are normally in control of their emotions that is why they find it > easy to lead diverse people. > > The charter needs review, if not the FC issues and problems will not come > to an end. > > @Bruna, clearly there is no confidence right now in my participation > within this committee, so what does the Ncuc EC really propose regarding > this matter? > > I do not even see how I can reapply if the situation is as bad as you > describe as the Chair. Its is pretty obvious what your position on this > matter is. > > Your statements are very confusing because you later mention that I must > consider being a penholder for the budget, yet you are telling me about my > sins. > > Initially you said my term expired as NCUC Rep then you said I must > continue with the meeting, please, I am not a robot, you can remote control > me. The NCUC EC needs to make a decision whether I continue until further > update as opposed to dancing to the music as it plays within the FC. > > Personal preferences are always supercedeed by community interest and > organisational goals in a civil society environment. > > > Thato Mfikwe. > > Sent from my Samsung Galaxy smartphone. > -------- Original message -------- > From: Bruna Martins dos Santos > Date: 21/02/2019 00:30 (GMT+02:00) > To: Stephanie Perrin > Cc: thatomfikwe , Maryam Bakoshi < > maryam.bakoshi at icann.org>, ncsg-fc at lists.ncsg.is > Subject: Re: [Ext] ICANN64 FC meeting preparations > > Hey Thato, > > I sincerely don't know how to deal with so many FC incidents. You have > been claiming for the so-called 'independence' but all I have seen so far > is a huge disregard for NSCG and its constituencies. So far you have added > stuff to your Operating procedures that were not agreed with neither > suggested by membership (such as the attempt of granting travel slots to > the FC), submitted ABRs that involved the SG and its Constituencies > activities without even notifying the leadership teams and now we have this > invitation for staff to join the FC meeting in Kobe without, once again, > consulting with membership - even despite the fact that on the thread about > NCSG bank account several members considered that asking staff for advice > at such stage (of the FC) would not be advisable. Sincerely it has been > really hard trying to work with the FC when I know that despite of the > advice that we might add to any discussions will be simply ignored. > > With regards to 'announcements for FC members replacement' I guess there > is a little misunderstanding on your behalf here. All NCSG/NCUC/NPOC > leadership positions have terms, even the appointed ones. And you might > recall that back in Barcelona, when I became NCUC chair, we announced that > the calls for NCUC appointees to all NCSG committees would be done at the > beginning of this year. So this is not an attempt to shut down any > committee, but simply NCUC complying with its operating procedures. If you > have any interest in continuing at this position you should apply to be > once again the NCUC appointee to the FC, and the EC will deliberate on this > - I dont have a say in votings unless we have a tie. > > Other than coming back and forth with such discussions, I think the FC > could be doing a little inreaching to membership. I am pretty sure that the > FC members are all capable of doing these discussions and I would > personally like to see you being involved with the ICANN Strategic Plan for > Fiscal Years 2021 ? 2025 and maybe even being the penholders of this > comment. Or even asking the mailing lists about what discussions they would > like to see at the FC meeting in Kobe. > > Best, > Bruna > > Em qua, 20 de fev de 2019 ?s 18:26, Stephanie Perrin < > stephanie.perrin at mail.utoronto.ca> escreveu: > >> I think you must have meant this for Bruna, Thato. I am not the head of >> the NCUC, nor of NPOC. the heads of those constituencies are in charge of >> managing the selection of their members of the Finance Cttee, not me. >> ccing Bruna so she can respond. Other responses in line. >> >> Stephanie >> On 2019-02-20 15:53, thatomfikwe wrote: >> >> Hi, >> >> >> When things are happening in parallel, with announcements for FC members >> replacement, makes the entire planning process for the Kobe meeting a >> mission. >> >> It would have been better if such announcements were made after ICANN64, >> they put the FC in a difficult position and the Kobe meeting is planned to >> revive the FC not create uncertainty and uncomfortable situations with >> members who will be leading deliberations. Not sure if such actions were >> well thought of or well planned. >> >> see Bruna and Joan >> >> >> >> I am not exactly sure how we are going to proceed despite serveral >> attempts to hold a meeting with members before Kobe in order to discuss the >> planned agenda in detail and emerging issues. >> >> Do you have any idea how busy council is, and the epdp, and the WHOIS >> review cttee, and the comments process in general? We are running ragged. >> WE need more members to staff the working groups. >> >> >> ICANN staff is just an email away, the Charter requires the FC to work >> with ICANN finance so if the committee is to be effective then it needs to >> establish or revive critical connections that will ensure that NCSG and its >> constituencies are fairly supported. >> >> First we determine our own policy positions. Do we want paid >> memberships? Do we want to establish an entity, if so what? These are not >> issues to discuss with staff, they would not be authorized to express an >> opinion, nor should they. >> >> >> Regarding the strong position of the community, what issues are they >> arguing? Do you think they are valid and what were the reposnes of members >> during that time? >> >> not sure what this question is addressing >> >> >> If you carefully review comments, they.were centered around >> - the bank account and incorporation of NCSG. This is currently being >> dealt with and in progress, to also be further discussed and decided upon >> - the role of the FC, many disagree with a lot of what is stipulated on >> the Charter, whereas the Charter uses simple language >> >> Indeed, I cannot figure out for the life of me what the drafters of the >> Charter had in mind. Establishing an entity has serious financial >> repercussions. I have no idea where the money for that would come from. >> Fund raising is difficult at the best of times, to support us at >> ICANN....likely to be quite a chore. >> >> >> When we review we need to be objective, even though it might seem like >> the vocal in the mailing list are the majority. If the FC is designed to >> have no autonomy then its efforts to correct mistakes of the past will >> always go unnoticed and unrecognised. >> >> what specific mistakes are you talking about? >> >> >> >> >> Thato Mfikwe. >> >> Sent from my Samsung Galaxy smartphone. >> -------- Original message -------- >> From: Stephanie Perrin >> >> Date: 20/02/2019 21:59 (GMT+02:00) >> To: Thato Mfikwe >> Cc: Maryam Bakoshi >> Subject: Re: [Ext] ICANN64 FC meeting preparations >> >> The event where the FC Chair, without informing his colleagues on Council >> or the PC, invited senior ICANN staff to one of the first FC meetings. >> Nobody was prepared. Most of us were unable to attend the last minute >> meeting. Surprises are rarely appreciated, and noone knew the conditions >> under which staff had been invited. If you check back in the email >> archives you will be able to see the grumbling that ensued after that >> meeting. Senior people are exceptionally busy at ICANN meetings....we >> don't invite them unless we have consensus that we are ready to meet them. >> >> We are by nature a consultative group. The FC should always be >> consulted, so there is an open record for members to consult. Many members >> have strongly held views on the FC and its mandate, and check the email >> archives. If there is nothing there, it is insufficiently transparent, at >> least in my view. I believe that is a commonly held view. >> >> Stephanie >> >> >> On 2019-02-20 13:51, Thato Mfikwe wrote: >> >> Hi Sephanie, >> >> What was an embarrasment? >> >> Thato Mfikwe. >> >> On Wed, Feb 20, 2019 at 8:40 PM Stephanie Perrin < >> stephanie.perrin at mail.utoronto.ca> wrote: >> >>> Personally, I do not think we are ready to meet with ICANN Finance >>> staff. However, it appears the request has gone. We have already gone >>> through this when Ed was chairing the Finance Committee, and it was an >>> embarrassment in my opinion. >>> >>> >>> Cheers Stephanie >>> On 2019-02-20 03:27, Maryam Bakoshi wrote: >>> >>> Hi Thato, >>> >>> Good morning I hope this email meets you well. I have forwarded this >>> request to Mary Wong, ICANN Staff. >>> >>> I am also cc?ing Stephanie, so she is in the loop. >>> >>> ? >>> Many thanks, >>> >>> >>> *Maryam Bakoshi* | SO/AC Collaboration Services Sr. Coordinator >>> *ICANN* | Internet Corporation for Assigned Names and Numbers >>> *S*: Maryam.bakoshi.icann | *T*: ?+44 7846 471777? >>> >>> On 20 Feb 2019, at 00:25, Thato Mfikwe wrote: >>> >>> Hi Maryam, >>> >>> Is it possible that we request the presence of one of ICANN Finance >>> staff and ICANN legal in the FC meeting in Kobe which will be taking place >>> on Wednesday, 15h15 - 16h45. >>> >>> Main support needed from ICANN staff: >>> - Elaboration on legal implications on incorporation of NCSG and what it >>> will mean for ICANN. >>> - Advice on alternative sources of fundraising and opening a bank >>> account in the name of NCSG. >>> - Recommendation on how to best set up the Operational Procedures and >>> ways of working with ICANN finance to support NCSG and constituency >>> initiatives and activities. >>> - Provision of clarity on how community comments are reflected in >>> current and future ICANN operational and financial plans. >>> >>> We only have 2 weeks before the meeting. I hope this message, finds you >>> well, thanks. >>> >>> Thato Mfikwe. >>> >>> > > -- > *Bruna Martins dos Santos * > > Skype ID: bruna.martinsantos > @boomartins > -- *Bruna Martins dos Santos * Skype ID: bruna.martinsantos @boomartins -------------- next part -------------- An HTML attachment was scrubbed... URL: From stephanie.perrin at mail.utoronto.ca Thu Feb 21 07:30:32 2019 From: stephanie.perrin at mail.utoronto.ca (Stephanie Perrin) Date: Thu, 21 Feb 2019 05:30:32 +0000 Subject: [NCSG-FC] [Ext] ICANN64 FC meeting preparations In-Reply-To: References: <5jyfwu2xk66oqy1s1u7a9dwe.1550696024335@email.android.com> <6e8404b1-94e0-6187-caa0-4565afe3c94e@mail.utoronto.ca> Message-ID: I can only speak for myself here folks, but I think it would really help me understand the ongoing work of the FC if I could read the plan. Where is the plan? Here are a few sample questions, on a basic skeleton. Incorporation of NCSG * what are the goals of the FC in terms of NCSG's structure? * do we need to be a legal entity to do the work we have been doing at ICANN? * If not, why do it? What are the risks and benefits of being a legal entity? Fundraising strategy * what exactly do we need money for? * do we have a current inventory of all the existing funding we receive? * Why would funders give us money? * Which jurisdictions would they come from? * would it be better to have local funders or thematic funders contribute to some of our members separately, rather than give to an NCSG entity? * are membership fees part of this funding strategy? If so, do we have an idea of the membership fees? * do we need the FC members, if they are going to be auditors, to have those credentials? Budget * at the moment we do not prepare an NCSG budget, at least I am unaware of it. I have only participated in NCSG for 5-6 years, I do not recall seeing one. What are the plans, who would do it, how would it be approved. * at the moment we do not appear to be doing oversight of the funds approved for travel requests. Should that be in an annual public financial report? * How would an NCSG FC assume oversight of NPOC and NCUC spending? Not clear in the Charter, unless I am misreading it. There is no central NCSG control Communications and transparency * Who is the FC accountable to? How does it communicate to that responsible party? * Does the FC have the authority to give direction to Maryam? In other words, does she support the FC independently, or is that supposed to happen through the NCSG EC? * do we have an agenda for the Kobe face to face meeting? will it be open to all stakeholders, or closed to NCSG members? These are just a few questions I have. I do not quite understand what Remmy is saying below, and am simply trying to put a few questions down to kickstart a strategic discussion. Stephanie Perrin NCSG Chair On 2019-02-20 17:31, Remmy Nweke wrote: Dear FC Sure the week has been busy. I have noticed in the NCUC call for FC representative that there is a discrepancy of NCUC charter and that of NCSG on FC on modalities of getting new members For the NCSG the chair of constituencies are the observers which is not the case with NCUC quoted charter thereof. Like I have maintained, it's better we resolve this discrepancy among others in charter as they come before further engagement so as to avoid engagement that will leave people on the street instead of the house and going round the house. Regards Remmy On Wed, 20 Feb 2019, 10:26 p.m. Stephanie Perrin wrote: I think you must have meant this for Bruna, Thato. I am not the head of the NCUC, nor of NPOC. the heads of those constituencies are in charge of managing the selection of their members of the Finance Cttee, not me. ccing Bruna so she can respond. Other responses in line. Stephanie On 2019-02-20 15:53, thatomfikwe wrote: Hi, When things are happening in parallel, with announcements for FC members replacement, makes the entire planning process for the Kobe meeting a mission. It would have been better if such announcements were made after ICANN64, they put the FC in a difficult position and the Kobe meeting is planned to revive the FC not create uncertainty and uncomfortable situations with members who will be leading deliberations. Not sure if such actions were well thought of or well planned. see Bruna and Joan I am not exactly sure how we are going to proceed despite serveral attempts to hold a meeting with members before Kobe in order to discuss the planned agenda in detail and emerging issues. Do you have any idea how busy council is, and the epdp, and the WHOIS review cttee, and the comments process in general? We are running ragged. WE need more members to staff the working groups. ICANN staff is just an email away, the Charter requires the FC to work with ICANN finance so if the committee is to be effective then it needs to establish or revive critical connections that will ensure that NCSG and its constituencies are fairly supported. First we determine our own policy positions. Do we want paid memberships? Do we want to establish an entity, if so what? These are not issues to discuss with staff, they would not be authorized to express an opinion, nor should they. Regarding the strong position of the community, what issues are they arguing? Do you think they are valid and what were the reposnes of members during that time? not sure what this question is addressing If you carefully review comments, they.were centered around - the bank account and incorporation of NCSG. This is currently being dealt with and in progress, to also be further discussed and decided upon - the role of the FC, many disagree with a lot of what is stipulated on the Charter, whereas the Charter uses simple language Indeed, I cannot figure out for the life of me what the drafters of the Charter had in mind. Establishing an entity has serious financial repercussions. I have no idea where the money for that would come from. Fund raising is difficult at the best of times, to support us at ICANN....likely to be quite a chore. When we review we need to be objective, even though it might seem like the vocal in the mailing list are the majority. If the FC is designed to have no autonomy then its efforts to correct mistakes of the past will always go unnoticed and unrecognised. what specific mistakes are you talking about? Thato Mfikwe. Sent from my Samsung Galaxy smartphone. -------- Original message -------- From: Stephanie Perrin Date: 20/02/2019 21:59 (GMT+02:00) To: Thato Mfikwe Cc: Maryam Bakoshi Subject: Re: [Ext] ICANN64 FC meeting preparations The event where the FC Chair, without informing his colleagues on Council or the PC, invited senior ICANN staff to one of the first FC meetings. Nobody was prepared. Most of us were unable to attend the last minute meeting. Surprises are rarely appreciated, and noone knew the conditions under which staff had been invited. If you check back in the email archives you will be able to see the grumbling that ensued after that meeting. Senior people are exceptionally busy at ICANN meetings....we don't invite them unless we have consensus that we are ready to meet them. We are by nature a consultative group. The FC should always be consulted, so there is an open record for members to consult. Many members have strongly held views on the FC and its mandate, and check the email archives. If there is nothing there, it is insufficiently transparent, at least in my view. I believe that is a commonly held view. Stephanie On 2019-02-20 13:51, Thato Mfikwe wrote: Hi Sephanie, What was an embarrasment? Thato Mfikwe. On Wed, Feb 20, 2019 at 8:40 PM Stephanie Perrin > wrote: Personally, I do not think we are ready to meet with ICANN Finance staff. However, it appears the request has gone. We have already gone through this when Ed was chairing the Finance Committee, and it was an embarrassment in my opinion. Cheers Stephanie On 2019-02-20 03:27, Maryam Bakoshi wrote: Hi Thato, Good morning I hope this email meets you well. I have forwarded this request to Mary Wong, ICANN Staff. I am also cc?ing Stephanie, so she is in the loop. ? Many thanks, Maryam Bakoshi | SO/AC Collaboration Services Sr. Coordinator ICANN | Internet Corporation for Assigned Names and Numbers S: Maryam.bakoshi.icann | T: ?+44 7846 471777? On 20 Feb 2019, at 00:25, Thato Mfikwe > wrote: Hi Maryam, Is it possible that we request the presence of one of ICANN Finance staff and ICANN legal in the FC meeting in Kobe which will be taking place on Wednesday, 15h15 - 16h45. Main support needed from ICANN staff: - Elaboration on legal implications on incorporation of NCSG and what it will mean for ICANN. - Advice on alternative sources of fundraising and opening a bank account in the name of NCSG. - Recommendation on how to best set up the Operational Procedures and ways of working with ICANN finance to support NCSG and constituency initiatives and activities. - Provision of clarity on how community comments are reflected in current and future ICANN operational and financial plans. We only have 2 weeks before the meeting. I hope this message, finds you well, thanks. Thato Mfikwe. _______________________________________________ NCSG-FC mailing list NCSG-FC at lists.ncsg.is https://lists.ncsg.is/mailman/listinfo/ncsg-fc On Wed, 20 Feb 2019, 10:26 p.m. Stephanie Perrin wrote: I think you must have meant this for Bruna, Thato. I am not the head of the NCUC, nor of NPOC. the heads of those constituencies are in charge of managing the selection of their members of the Finance Cttee, not me. ccing Bruna so she can respond. Other responses in line. Stephanie On 2019-02-20 15:53, thatomfikwe wrote: Hi, When things are happening in parallel, with announcements for FC members replacement, makes the entire planning process for the Kobe meeting a mission. It would have been better if such announcements were made after ICANN64, they put the FC in a difficult position and the Kobe meeting is planned to revive the FC not create uncertainty and uncomfortable situations with members who will be leading deliberations. Not sure if such actions were well thought of or well planned. see Bruna and Joan I am not exactly sure how we are going to proceed despite serveral attempts to hold a meeting with members before Kobe in order to discuss the planned agenda in detail and emerging issues. Do you have any idea how busy council is, and the epdp, and the WHOIS review cttee, and the comments process in general? We are running ragged. WE need more members to staff the working groups. ICANN staff is just an email away, the Charter requires the FC to work with ICANN finance so if the committee is to be effective then it needs to establish or revive critical connections that will ensure that NCSG and its constituencies are fairly supported. First we determine our own policy positions. Do we want paid memberships? Do we want to establish an entity, if so what? These are not issues to discuss with staff, they would not be authorized to express an opinion, nor should they. Regarding the strong position of the community, what issues are they arguing? Do you think they are valid and what were the reposnes of members during that time? not sure what this question is addressing If you carefully review comments, they.were centered around - the bank account and incorporation of NCSG. This is currently being dealt with and in progress, to also be further discussed and decided upon - the role of the FC, many disagree with a lot of what is stipulated on the Charter, whereas the Charter uses simple language Indeed, I cannot figure out for the life of me what the drafters of the Charter had in mind. Establishing an entity has serious financial repercussions. I have no idea where the money for that would come from. Fund raising is difficult at the best of times, to support us at ICANN....likely to be quite a chore. When we review we need to be objective, even though it might seem like the vocal in the mailing list are the majority. If the FC is designed to have no autonomy then its efforts to correct mistakes of the past will always go unnoticed and unrecognised. what specific mistakes are you talking about? Thato Mfikwe. Sent from my Samsung Galaxy smartphone. -------- Original message -------- From: Stephanie Perrin Date: 20/02/2019 21:59 (GMT+02:00) To: Thato Mfikwe Cc: Maryam Bakoshi Subject: Re: [Ext] ICANN64 FC meeting preparations The event where the FC Chair, without informing his colleagues on Council or the PC, invited senior ICANN staff to one of the first FC meetings. Nobody was prepared. Most of us were unable to attend the last minute meeting. Surprises are rarely appreciated, and noone knew the conditions under which staff had been invited. If you check back in the email archives you will be able to see the grumbling that ensued after that meeting. Senior people are exceptionally busy at ICANN meetings....we don't invite them unless we have consensus that we are ready to meet them. We are by nature a consultative group. The FC should always be consulted, so there is an open record for members to consult. Many members have strongly held views on the FC and its mandate, and check the email archives. If there is nothing there, it is insufficiently transparent, at least in my view. I believe that is a commonly held view. Stephanie On 2019-02-20 13:51, Thato Mfikwe wrote: Hi Sephanie, What was an embarrasment? Thato Mfikwe. On Wed, Feb 20, 2019 at 8:40 PM Stephanie Perrin > wrote: Personally, I do not think we are ready to meet with ICANN Finance staff. However, it appears the request has gone. We have already gone through this when Ed was chairing the Finance Committee, and it was an embarrassment in my opinion. Cheers Stephanie On 2019-02-20 03:27, Maryam Bakoshi wrote: Hi Thato, Good morning I hope this email meets you well. I have forwarded this request to Mary Wong, ICANN Staff. I am also cc?ing Stephanie, so she is in the loop. ? Many thanks, Maryam Bakoshi | SO/AC Collaboration Services Sr. Coordinator ICANN | Internet Corporation for Assigned Names and Numbers S: Maryam.bakoshi.icann | T: ?+44 7846 471777? On 20 Feb 2019, at 00:25, Thato Mfikwe > wrote: Hi Maryam, Is it possible that we request the presence of one of ICANN Finance staff and ICANN legal in the FC meeting in Kobe which will be taking place on Wednesday, 15h15 - 16h45. Main support needed from ICANN staff: - Elaboration on legal implications on incorporation of NCSG and what it will mean for ICANN. - Advice on alternative sources of fundraising and opening a bank account in the name of NCSG. - Recommendation on how to best set up the Operational Procedures and ways of working with ICANN finance to support NCSG and constituency initiatives and activities. - Provision of clarity on how community comments are reflected in current and future ICANN operational and financial plans. We only have 2 weeks before the meeting. I hope this message, finds you well, thanks. Thato Mfikwe. _______________________________________________ NCSG-FC mailing list NCSG-FC at lists.ncsg.is https://lists.ncsg.is/mailman/listinfo/ncsg-fc _______________________________________________ NCSG-FC mailing list NCSG-FC at lists.ncsg.is https://lists.ncsg.is/mailman/listinfo/ncsg-fc -------------- next part -------------- An HTML attachment was scrubbed... URL: From remmyn at gmail.com Thu Feb 21 15:14:10 2019 From: remmyn at gmail.com (Remmy Nweke) Date: Thu, 21 Feb 2019 14:14:10 +0100 Subject: [NCSG-FC] [Ext] ICANN64 FC meeting preparations In-Reply-To: References: <5jyfwu2xk66oqy1s1u7a9dwe.1550696024335@email.android.com> <6e8404b1-94e0-6187-caa0-4565afe3c94e@mail.utoronto.ca> Message-ID: > > Dear Stephanie > > *Thanks for the questions. I think it?s a bold step in resolving whatever > quagmire we are currently in as FC with hope it will avail us more > understanding. I will try to respond to them from my prism inline below.* > > I can only speak for myself here folks, but I think it would really help > me understand the ongoing work of the FC if I could read the plan. Where > is the plan? Here are a few sample questions, on a basic skeleton. > > *Incorporation of NCSG* > > ? what are the goals of the FC in terms of NCSG's structure? > > *The FC goals are driven by the NCSG Charter which include but not limited > to entrenching:* > > *(a) ** responsible fund raising mechanism in place, * > > *(b)**setting voluntary contribution levels for members, * > > *(c) **determining procedures for the distribution of funds, and * > > *(d)**for monitoring the utilization of funds. * > > *(e) **The Treasurer function. * > > *In addition, FC tends to among others:* > > ? *Develop and deploy a fund-??raising plan for the NCSG;* > > ? *Work with the ICANN staff to determine levels of support > available to the NCSG;* > > ? *Work with ICANN finance officers to insure the NCSG and its > Constituencies receive fair and equivalent financial support from ICANN;* > > ? *Accounting for any funds received by the NCSG from any source. > This accounting will include the following:* > > *??* *All funds raised by voluntary membership fees or otherwise must be > held in a separate NCSG account.* > > *?? **Proper controls must be implemented.* > > *?? **Regarding Expenditures:* > > ? *All expenditures under 500 Euro may be made on the authority of > the NCSG Treasurer* > > ? *All expenditures over 500 Euro must be approved by the > NCSG-??FC* > > *?? **Financial reports must be prepared annually and be made public.* > > ? *Provide internal conflict resolution process regarding funds.* > > ? *Provide the oversight of the Treasurer function.* > > ? *Fulfill any other accounting, auditing or other prescribed financial > requirements as set by the ICANN Board of Directors for organizations > within the ICANN structure* > > ? *Document methods and procedures used for accounting, reporting and > budget creation. Such documentation is subject to review by the NCSG-?**?* > *EC.* > > ? do we need to be a legal entity to do the work we have been doing at > ICANN? > > *My understanding this is that currently some of the Cs, in fact both > Constituencies have already become legal entities and has the capability of > receiving fund if need be and there may be NO need to engage in another > process considering our diversity and very short tenure of offices. Thus, > recommended that we use what we have to get what we need. That is using any > of the Cs now to open an SPV ? Special Purpose Vehicle account, just like > ISOC did in setting up PIR to serve a special purpose until such a time, > the footing is clearer and scope warrants stand-alone legal entity.* > > ? If not, why do it? What are the risks and benefits of being a legal > entity? > > *As for the risks of being a separate legal entity by NCSG, for now, as > ICANN offshoot for non-Commercial, we need to do the registration in the > United States and any other country as may be agreed upon, which has a > process including setting up the BoT ? Board of Trustees which involves > residency etc very often. This will also entail another level or layer of > advisory team outside the NCSG EC, hence my earlier suggestion for us to > use what we have to get what we want via SPV.* > > *SPV account actually is to ensure that every external fund inflow resides > in a place as may be agreed by both Cs and NCSG EC with an MoU, so that we > do not fall into issues when the current leadership of any chosen account > holder elapses and avail NCSG full control of such account under FC as > mandated in the charter at all times.* > > *Fundraising strategy* > > ? what exactly do we need money for? > > *We need money for outreach for membership drive and showcase of what NCSG > family is, and has been doing, stand for and support NCSG community and > individual work including but not limited to distinct and independent > research by NPOC | NCUC or NCSG, as may become necessary for internal use > and support our position, on the side line of policy development and > building capacity of our members across financial transparency and policy > engagement and development, among others. Especially where ICANN support > cannot cover immediately; As you know most ICANN supports are tied to > regions, which does not preclude that some other regions at the same time > do not need support within the remits of outlines above. For instance, > ICANN can support global IGF, what of the regional IGFs etc or national IG > events. These are revolving outreach programmes.* > > ? do we have a current inventory of all the existing funding we receive? > > *The only one known to me/FC is from PIR ? Public Interest Registry, this > has to be expanded with the outreach targeted at Donors beyond PIR and > across regions.* > > ? Why would funders give us money? > > *For the interest of non-commercial purposes and those who want more > inclusive internet eco-system despite diversity and in tune with NCSG goals > and objectives (Mission) to ensure their voices are heard and they > participate actively against all odds envisioned in commercial stakes.* > > ? Which jurisdictions would they come from? > > *Funding could come from a global purpose and largely regional as > explained earlier which are tied to specific regions and that is one area > FC intend to target too. Like the CIPESA Internet Freedom Forum has a > session on funding and donors session. Just a few FC is targeting all > things equal for this year.* > > ? would it be better to have local funders or thematic funders > contribute to some of our members separately, rather than give to an NCSG > entity? > > *For now, both ways are fine, but for purposes of this, NCSG charter was > not specific on this and if we must have local funders or via thematic > funding to some members. Its worthy of exploring but then, FC should be > looking at it from the point of purse that is available to support members, > knowing fully well that funders require at least organistional endorsement > to pathway with their funds, a clout some of our upcoming members and small > membership organizations may not have. One can confidently say that NCSG is > the umbrella body of non-commercial users.* > > ? are membership fees part of this funding strategy? If so, do we have > an idea of the membership fees? > > *For me, with my experience, membership fees will be a clog, considering > that in some countries, especially in Africa, where I am currently serving > as the Vice President, African Civil Society on the Information Society > (ACSIS), charges on dollar fee surpasses some of the annual dues > affordable, which does not make sense to be making money for eTransaction > operators. While some have restriction occasioned to their regional > policies. For instance, we access paypal in Nigeria in terms of usage if > preloaded, but cannot receive fund via paypal due to government policy.* > > *For NPOC charter ?**NPOC will not collect dues, fees, or subscriptions > from its members.?* > > ? do we need the FC members, if they are going to be auditors, to have > those credentials? > > *Credentials matters and I will not place that over and above industry > experience linked to finance/audit management. We may not get strict > auditors because of the kind of work we do (voluntary, except we are ready > to start paying auditors per say); but people who are willing to learn > could be another area, definitely not devoid of experience such as managing > an NGO could be an ideal, among others.* > > *Budget* > > ? at the moment we do not prepare an NCSG budget, at least I am unaware > of it. I have only participated in NCSG for 5-6 years, I do not recall > seeing one. What are the plans, who would do it, how would it be approved. > > *Well, you are very right. I have not seen one myself too. This is one of > the streamlining for accountability that current FC envisaged to entrench > and its not going to work if Cs are not cooperating. Another instance is > that Cs need to prepare this, invariably FC can advice if need be as you > cannot prepare budget and still audit same. This will be achieved by > ensuring that each Cs either through the Financial Secretary or Secretariat > prepares their budget and send to NCSG FC, even if its for the records, > because they have their individual C exco to approve spending. NCSG Excom > needs a copy too to enable it also prepare own budget leveraging possibly > from what the Cs may have submitted to ensure they do not run across > purposes but rather driving strength from Cs.* > > *And based on this, FC can also submit its own budget lines likewise the > Policy Committee (PC) since both are the legally recognized sub-entities in > the charter based on activities to be executed within the year under review > in collaboration with NCSG EC. * > > *We can create capacity building on budgeting for ICANN as annual > refresher course to keep leadership of Cs and NCSG abreast of development > and feedback on any challenges using pre-ICANN sessions.* > > *You can tag the Committees budget as operational budgets while that of Cs > as capital and we can take up from there. This will make it easy for ABR > where necessary too to fill in the gap of engagements.* > > *These will be merged to ensure everyone is extending a helping hand to > another based on equal footing.* > > *We can develop this via a budget template either in existence or fresh > template, so as to ease harmonization of the budget session eventually.* > > ? at the moment we do not appear to be doing oversight of the funds > approved for travel requests. Should that be in an annual public financial > report? > > *Yes, very correct and its part of the challenges. Yes, we may be members > of NCSG, but these have to be submitted afterwards, either quarterly or > annually as may be agreed upon, but yearly is mandatory. These are some of > the understanding required to co-exist in this space. The oversight does > not mean FC non-approval as long as its contained in the formal budget > approved/submitted for the year, but to take note and make comments > thereafter on judicious or otherwise use of the said funds to improve > future applications. * > > *One of it is that Cs may give scholarships/fellowships to an ICANN public > meeting, how will FC know if such scholarships were judiciously expended to > the letter if not by monitoring the processes to the letter as well and may > be interfacing with scholarship awardees at venue to know areas of > dissatisfaction so as to improve on processes. * > > *There is need to also have its own session accommodated in such a meeting > so as to kill two birds with a stone and create awareness, earn more public > trust and openness, in order to provide background to FC reports eventually > on how funds received were used either to ICANN.org or funders for future > engagements and sustained funding or affiliation as most funders will > request feedback of funds.* > > ? How would an NCSG FC assume oversight of NPOC and NCUC spending? Not > clear in the Charter, unless I am misreading it. There is no central NCSG > control. > > *It behoves on the leadership of NPOC and NCUC to trust FC enough and send > or share information as deem fit and as may be required or demanded. Part > of the oversight is physical monitoring of activities both at ICANN and > outside where such a fund is being expended as long as the community > funding and activities are involve. This will put the FC representatives in > good standing to defend any claim, allegations or query that may arise > thereof from ICANN.org or funders, thereby offering better insight when > necessary.* > > *Communications and transparency* > > ? Who is the FC accountable to? How does it communicate to that > responsible party? > > *Based on our NCSG charter which sets up the FC, communication to > community is key but in terms of accountable, its ICANN.org and funders, > which stated inter alia in Section 2.6: * > > ? *?Accounting for any funds received by the NCSG from any source.* > > ? *Financial reports must be prepared annually and be made public.* > > ? *Fulfill any other accounting, auditing or other prescribed > financial requirements as set by the ICANN Board of Directors for > organizations within the ICANN structure.* > > ? *Document methods and procedures used for accounting, reporting > and budget creation. Such documentation is subject to review by the > NCSG-??EC.?* > > > > *With the aforementioned, FC reports to ICANN.org and funders whereas its > annual report must be made public, which is the community and by extension > our respective Cs in terms of debriefing (feedback), at Cs Exco sessions or > as may be required.* > > > > *NB: Of course where good communication exists as it should, one expects > that NCSG EC and Cs will have the privilege of the content prior to/soon > after sending it out to ICANN.org or funders, since it will be coming from > them anyways.* > > ? Does the FC have the authority to give direction to Maryam? In other > words, does she support the FC independently, or is that supposed to happen > through the NCSG EC? > > *I think that Maryam and other ICANN support staff are here to help us > achieve our various assignments, goals and mandates, and as such could take > a direction to assist any given committee as long as they are > constitutionally or legally constituted. Whether the direction is an > authority resides with the chair or person giving the direction, so as to > take full responsibility of the action when it matters. Therefore, every > ICANN staff supports every community including committees independently. > Theirs is facilitation.* > > *As I have explained based on the charter, FC being the supposed auditor > now should assume some level of autonomy but under good understanding keeps > NCSG EC briefed, that is why communication, trust and understanding are > key, but I do not think that is the way some of us understand it hence the > challenge in communication. And that is why its vital to include FC Reps in > NCSG EC and their respective Cs, even at observer level, as they are not > ?supposed? to be heard at such meetings outside advisory.* > > ? do we have an agenda for the Kobe face to face meeting? will it be > open to all stakeholders, or closed to NCSG members? > > *Yes, of course. I am aware, there is an agenda for Kobe and so all other > meetings will be open for all stakeholders and is part of the planned > outreach series to bridge the gap between FC and ICANN finance as well as > NCSG community specifically, as listed above.* > > These are just a few questions I have. I do not quite understand what > Remmy is saying below, and am simply trying to put a few questions down to > kickstart a strategic discussion. > > *Thanks for putting the questions, definitely not a few and I hope my > "few" responses will be helpful in charting the way forward.* > > *Thanks again* > > Remmy Nweke > -------------- next part -------------- An HTML attachment was scrubbed... URL: From thatomfikwe at gmail.com Thu Feb 21 16:36:05 2019 From: thatomfikwe at gmail.com (Thato Mfikwe) Date: Thu, 21 Feb 2019 16:36:05 +0200 Subject: [NCSG-FC] [Ext] ICANN64 FC meeting preparations In-Reply-To: References: <7p1j5d4dsu4sh4h09lsa1x51.1550707256664@email.android.com> Message-ID: Hey Bruna, This conversation has no business with gender, the pejudice and gender card is not developmental. We engaging each other as FC members, if you have difficulty dealing with the opposite gender, then I am not sure how I can help. Personally, in my past and current professional life, I worked with women and have been led by them before, disagreements and resistance are two different terms based on perception and eperience. This is actually the first time, such a prejudice insinuation has been made in my name. I control my emotions to uphold respect, even if I do not agree with proceedings. I tend to listen to understand not react in potential disagreements or arguements, that is what I meant in a more detailed sense. Most of the suggestions made are already documented in the FC action plan , another challenge in moving forward with the action plan is capacity to deliver with very few members, the new FC will also need capacity and support to fully implement the FC action plan. Thato Mfikwe. On Thu, Feb 21, 2019 at 3:49 AM Bruna Martins dos Santos < bruna.mrtns at gmail.com> wrote: > Dear Thato and Remmy, > > I agree with you both that we cannot continue with so many disagreements, > it takes far too much time from all of us (especially when I have the NCUC > Agenda for the Kobe meeting to finalize). > > The reason why we opened the call for NCUC Appointee to the Finance > committee was solely based on the end of Thato's term. I might have my > concerns with some recent concerns regarding the FC but I havent disclosed > them in details to the NCUC EC. Thato, I also believe your comment on the > lack of confidence in your participation at this commitee is not very > accurate. I have tried to chatting with you in order to understand how > could I help you and the FC from the NCUC perspective but there seems to be > some sort of resistance to me - or on the fact that I am a female colleague > based on the fact that you questioned my lack of 'control' for my emotions. > > Once again, the reason why I am on this list (as an observer) is based on > the fact that I do want to contribute to the FC work. And when I advised > you to reapply for the position I really meant it, @Thato Mfikwe > . When I mentioned that I would have liked to see > you both engaged with the comment is due to the fact that I consider you > both apt for the job and the merit of the comment pretty much aligned with > the FC activities. Maybe by doing this kind of work we can get you more > fine tuned with the community and work our ways into empowering the FC - > which is something I believe you both also want. I just dont think this > empowerment will come from the FC acting without any community consultation > and claiming that there was not a clear orientation on the matter. > > Lastly, I would once again stress that we need to work together and learn > to respect opposite opinions, not simply lash at people and invest in petty > attacks such as implying that I am not in control of my emotions. Being a > woman working on the tech environment I should have gotten used to such > implications by now, but it still offends me - especially when we are a > group of people meaning to do the same work and simply not managing to > understand that we are all saying the same things in different ways. > > Best, > Bruna > > Em qua, 20 de fev de 2019 ?s 21:07, thatomfikwe > escreveu: > >> Bruna, >> >> As the FC we need to agree on the meeting agenda so that it does not >> become my agenda when it goes to the mailing list. If not.interested in the >> meeting, please state so that other members can continue in the meanwhile. >> >> The operational procedures intergrated community input and FC inputs. I >> did.not put my personal opinion on the OP, feel free to comment on the doc >> as opposed to continue lashing. This doc still has to go to the NCSG EC. >> >> There is nothing wrong with the FC participating in meeting in order to >> establish itself and gain presence and confidence within the community. >> What is the real reason the FC need not attend F2F onsite meetings? >> >> Travel slots should be open to all committees and members and of course >> active and committee members must receive a significant portion. If this is >> not fair enough then I do not know what resolve the travel slots issue >> which is not just a FC issue but a community issue. >> >> Fundraising and resource mobilisation is important, the FC understands >> what its duties but it seems like there are serious barrier within the >> committee as it is fighting with itself. >> >> Lately there has been a lot of toungue lashing on the FC. Which I >> consider disrespectful, we are not small children, nobody is better than >> the other, we all leaders in our own personal & different capacities. I try >> to maintain respect for all members of NCSG but if respect is not >> returned..then what? >> >> Leaders are normally in control of their emotions that is why they find >> it easy to lead diverse people. >> >> The charter needs review, if not the FC issues and problems will not come >> to an end. >> >> @Bruna, clearly there is no confidence right now in my participation >> within this committee, so what does the Ncuc EC really propose regarding >> this matter? >> >> I do not even see how I can reapply if the situation is as bad as you >> describe as the Chair. Its is pretty obvious what your position on this >> matter is. >> >> Your statements are very confusing because you later mention that I must >> consider being a penholder for the budget, yet you are telling me about my >> sins. >> >> Initially you said my term expired as NCUC Rep then you said I must >> continue with the meeting, please, I am not a robot, you can remote control >> me. The NCUC EC needs to make a decision whether I continue until further >> update as opposed to dancing to the music as it plays within the FC. >> >> Personal preferences are always supercedeed by community interest and >> organisational goals in a civil society environment. >> >> >> Thato Mfikwe. >> >> Sent from my Samsung Galaxy smartphone. >> -------- Original message -------- >> From: Bruna Martins dos Santos >> Date: 21/02/2019 00:30 (GMT+02:00) >> To: Stephanie Perrin >> Cc: thatomfikwe , Maryam Bakoshi < >> maryam.bakoshi at icann.org>, ncsg-fc at lists.ncsg.is >> Subject: Re: [Ext] ICANN64 FC meeting preparations >> >> Hey Thato, >> >> I sincerely don't know how to deal with so many FC incidents. You have >> been claiming for the so-called 'independence' but all I have seen so far >> is a huge disregard for NSCG and its constituencies. So far you have added >> stuff to your Operating procedures that were not agreed with neither >> suggested by membership (such as the attempt of granting travel slots to >> the FC), submitted ABRs that involved the SG and its Constituencies >> activities without even notifying the leadership teams and now we have this >> invitation for staff to join the FC meeting in Kobe without, once again, >> consulting with membership - even despite the fact that on the thread about >> NCSG bank account several members considered that asking staff for advice >> at such stage (of the FC) would not be advisable. Sincerely it has been >> really hard trying to work with the FC when I know that despite of the >> advice that we might add to any discussions will be simply ignored. >> >> With regards to 'announcements for FC members replacement' I guess there >> is a little misunderstanding on your behalf here. All NCSG/NCUC/NPOC >> leadership positions have terms, even the appointed ones. And you might >> recall that back in Barcelona, when I became NCUC chair, we announced that >> the calls for NCUC appointees to all NCSG committees would be done at the >> beginning of this year. So this is not an attempt to shut down any >> committee, but simply NCUC complying with its operating procedures. If you >> have any interest in continuing at this position you should apply to be >> once again the NCUC appointee to the FC, and the EC will deliberate on this >> - I dont have a say in votings unless we have a tie. >> >> Other than coming back and forth with such discussions, I think the FC >> could be doing a little inreaching to membership. I am pretty sure that the >> FC members are all capable of doing these discussions and I would >> personally like to see you being involved with the ICANN Strategic Plan for >> Fiscal Years 2021 ? 2025 and maybe even being the penholders of this >> comment. Or even asking the mailing lists about what discussions they would >> like to see at the FC meeting in Kobe. >> >> Best, >> Bruna >> >> Em qua, 20 de fev de 2019 ?s 18:26, Stephanie Perrin < >> stephanie.perrin at mail.utoronto.ca> escreveu: >> >>> I think you must have meant this for Bruna, Thato. I am not the head of >>> the NCUC, nor of NPOC. the heads of those constituencies are in charge of >>> managing the selection of their members of the Finance Cttee, not me. >>> ccing Bruna so she can respond. Other responses in line. >>> >>> Stephanie >>> On 2019-02-20 15:53, thatomfikwe wrote: >>> >>> Hi, >>> >>> >>> When things are happening in parallel, with announcements for FC members >>> replacement, makes the entire planning process for the Kobe meeting a >>> mission. >>> >>> It would have been better if such announcements were made after ICANN64, >>> they put the FC in a difficult position and the Kobe meeting is planned to >>> revive the FC not create uncertainty and uncomfortable situations with >>> members who will be leading deliberations. Not sure if such actions were >>> well thought of or well planned. >>> >>> see Bruna and Joan >>> >>> >>> >>> I am not exactly sure how we are going to proceed despite serveral >>> attempts to hold a meeting with members before Kobe in order to discuss the >>> planned agenda in detail and emerging issues. >>> >>> Do you have any idea how busy council is, and the epdp, and the WHOIS >>> review cttee, and the comments process in general? We are running ragged. >>> WE need more members to staff the working groups. >>> >>> >>> ICANN staff is just an email away, the Charter requires the FC to work >>> with ICANN finance so if the committee is to be effective then it needs to >>> establish or revive critical connections that will ensure that NCSG and its >>> constituencies are fairly supported. >>> >>> First we determine our own policy positions. Do we want paid >>> memberships? Do we want to establish an entity, if so what? These are not >>> issues to discuss with staff, they would not be authorized to express an >>> opinion, nor should they. >>> >>> >>> Regarding the strong position of the community, what issues are they >>> arguing? Do you think they are valid and what were the reposnes of members >>> during that time? >>> >>> not sure what this question is addressing >>> >>> >>> If you carefully review comments, they.were centered around >>> - the bank account and incorporation of NCSG. This is currently being >>> dealt with and in progress, to also be further discussed and decided upon >>> - the role of the FC, many disagree with a lot of what is stipulated on >>> the Charter, whereas the Charter uses simple language >>> >>> Indeed, I cannot figure out for the life of me what the drafters of the >>> Charter had in mind. Establishing an entity has serious financial >>> repercussions. I have no idea where the money for that would come from. >>> Fund raising is difficult at the best of times, to support us at >>> ICANN....likely to be quite a chore. >>> >>> >>> When we review we need to be objective, even though it might seem like >>> the vocal in the mailing list are the majority. If the FC is designed to >>> have no autonomy then its efforts to correct mistakes of the past will >>> always go unnoticed and unrecognised. >>> >>> what specific mistakes are you talking about? >>> >>> >>> >>> >>> Thato Mfikwe. >>> >>> Sent from my Samsung Galaxy smartphone. >>> -------- Original message -------- >>> From: Stephanie Perrin >>> >>> Date: 20/02/2019 21:59 (GMT+02:00) >>> To: Thato Mfikwe >>> Cc: Maryam Bakoshi >>> Subject: Re: [Ext] ICANN64 FC meeting preparations >>> >>> The event where the FC Chair, without informing his colleagues on >>> Council or the PC, invited senior ICANN staff to one of the first FC >>> meetings. Nobody was prepared. Most of us were unable to attend the last >>> minute meeting. Surprises are rarely appreciated, and noone knew the >>> conditions under which staff had been invited. If you check back in the >>> email archives you will be able to see the grumbling that ensued after that >>> meeting. Senior people are exceptionally busy at ICANN meetings....we >>> don't invite them unless we have consensus that we are ready to meet them. >>> >>> We are by nature a consultative group. The FC should always be >>> consulted, so there is an open record for members to consult. Many members >>> have strongly held views on the FC and its mandate, and check the email >>> archives. If there is nothing there, it is insufficiently transparent, at >>> least in my view. I believe that is a commonly held view. >>> >>> Stephanie >>> >>> >>> On 2019-02-20 13:51, Thato Mfikwe wrote: >>> >>> Hi Sephanie, >>> >>> What was an embarrasment? >>> >>> Thato Mfikwe. >>> >>> On Wed, Feb 20, 2019 at 8:40 PM Stephanie Perrin < >>> stephanie.perrin at mail.utoronto.ca> wrote: >>> >>>> Personally, I do not think we are ready to meet with ICANN Finance >>>> staff. However, it appears the request has gone. We have already gone >>>> through this when Ed was chairing the Finance Committee, and it was an >>>> embarrassment in my opinion. >>>> >>>> >>>> Cheers Stephanie >>>> On 2019-02-20 03:27, Maryam Bakoshi wrote: >>>> >>>> Hi Thato, >>>> >>>> Good morning I hope this email meets you well. I have forwarded this >>>> request to Mary Wong, ICANN Staff. >>>> >>>> I am also cc?ing Stephanie, so she is in the loop. >>>> >>>> ? >>>> Many thanks, >>>> >>>> >>>> *Maryam Bakoshi* | SO/AC Collaboration Services Sr. Coordinator >>>> *ICANN* | Internet Corporation for Assigned Names and Numbers >>>> *S*: Maryam.bakoshi.icann | *T*: ?+44 7846 471777? >>>> >>>> On 20 Feb 2019, at 00:25, Thato Mfikwe wrote: >>>> >>>> Hi Maryam, >>>> >>>> Is it possible that we request the presence of one of ICANN Finance >>>> staff and ICANN legal in the FC meeting in Kobe which will be taking place >>>> on Wednesday, 15h15 - 16h45. >>>> >>>> Main support needed from ICANN staff: >>>> - Elaboration on legal implications on incorporation of NCSG and what >>>> it will mean for ICANN. >>>> - Advice on alternative sources of fundraising and opening a bank >>>> account in the name of NCSG. >>>> - Recommendation on how to best set up the Operational Procedures and >>>> ways of working with ICANN finance to support NCSG and constituency >>>> initiatives and activities. >>>> - Provision of clarity on how community comments are reflected in >>>> current and future ICANN operational and financial plans. >>>> >>>> We only have 2 weeks before the meeting. I hope this message, finds you >>>> well, thanks. >>>> >>>> Thato Mfikwe. >>>> >>>> >> >> -- >> *Bruna Martins dos Santos * >> >> Skype ID: bruna.martinsantos >> @boomartins >> > > > -- > *Bruna Martins dos Santos * > > Skype ID: bruna.martinsantos > @boomartins > -------------- next part -------------- An HTML attachment was scrubbed... URL: From stephanie.perrin at mail.utoronto.ca Thu Feb 21 16:48:11 2019 From: stephanie.perrin at mail.utoronto.ca (Stephanie Perrin) Date: Thu, 21 Feb 2019 14:48:11 +0000 Subject: [NCSG-FC] [Ext] ICANN64 FC meeting preparations In-Reply-To: References: <5jyfwu2xk66oqy1s1u7a9dwe.1550696024335@email.android.com> <6e8404b1-94e0-6187-caa0-4565afe3c94e@mail.utoronto.ca> Message-ID: Thanks Remmy, this is useful. Lets keep up the effort to address these substantive issues! Stephanie On 2019-02-21 08:14, Remmy Nweke wrote: Dear Stephanie Thanks for the questions. I think it?s a bold step in resolving whatever quagmire we are currently in as FC with hope it will avail us more understanding. I will try to respond to them from my prism inline below. I can only speak for myself here folks, but I think it would really help me understand the ongoing work of the FC if I could read the plan. Where is the plan? Here are a few sample questions, on a basic skeleton. Incorporation of NCSG ? what are the goals of the FC in terms of NCSG's structure? The FC goals are driven by the NCSG Charter which include but not limited to entrenching: (a) responsible fund raising mechanism in place, (b)setting voluntary contribution levels for members, (c) determining procedures for the distribution of funds, and (d)for monitoring the utilization of funds. (e) The Treasurer function. In addition, FC tends to among others: ? Develop and deploy a fund-??raising plan for the NCSG; ? Work with the ICANN staff to determine levels of support available to the NCSG; ? Work with ICANN finance officers to insure the NCSG and its Constituencies receive fair and equivalent financial support from ICANN; ? Accounting for any funds received by the NCSG from any source. This accounting will include the following: ?? All funds raised by voluntary membership fees or otherwise must be held in a separate NCSG account. ?? Proper controls must be implemented. ?? Regarding Expenditures: ? All expenditures under 500 Euro may be made on the authority of the NCSG Treasurer ? All expenditures over 500 Euro must be approved by the NCSG-??FC ?? Financial reports must be prepared annually and be made public. ? Provide internal conflict resolution process regarding funds. ? Provide the oversight of the Treasurer function. ? Fulfill any other accounting, auditing or other prescribed financial requirements as set by the ICANN Board of Directors for organizations within the ICANN structure ? Document methods and procedures used for accounting, reporting and budget creation. Such documentation is subject to review by the NCSG-??EC. ? do we need to be a legal entity to do the work we have been doing at ICANN? My understanding this is that currently some of the Cs, in fact both Constituencies have already become legal entities and has the capability of receiving fund if need be and there may be NO need to engage in another process considering our diversity and very short tenure of offices. Thus, recommended that we use what we have to get what we need. That is using any of the Cs now to open an SPV ? Special Purpose Vehicle account, just like ISOC did in setting up PIR to serve a special purpose until such a time, the footing is clearer and scope warrants stand-alone legal entity. ? If not, why do it? What are the risks and benefits of being a legal entity? As for the risks of being a separate legal entity by NCSG, for now, as ICANN offshoot for non-Commercial, we need to do the registration in the United States and any other country as may be agreed upon, which has a process including setting up the BoT ? Board of Trustees which involves residency etc very often. This will also entail another level or layer of advisory team outside the NCSG EC, hence my earlier suggestion for us to use what we have to get what we want via SPV. SPV account actually is to ensure that every external fund inflow resides in a place as may be agreed by both Cs and NCSG EC with an MoU, so that we do not fall into issues when the current leadership of any chosen account holder elapses and avail NCSG full control of such account under FC as mandated in the charter at all times. Fundraising strategy ? what exactly do we need money for? We need money for outreach for membership drive and showcase of what NCSG family is, and has been doing, stand for and support NCSG community and individual work including but not limited to distinct and independent research by NPOC | NCUC or NCSG, as may become necessary for internal use and support our position, on the side line of policy development and building capacity of our members across financial transparency and policy engagement and development, among others. Especially where ICANN support cannot cover immediately; As you know most ICANN supports are tied to regions, which does not preclude that some other regions at the same time do not need support within the remits of outlines above. For instance, ICANN can support global IGF, what of the regional IGFs etc or national IG events. These are revolving outreach programmes. ? do we have a current inventory of all the existing funding we receive? The only one known to me/FC is from PIR ? Public Interest Registry, this has to be expanded with the outreach targeted at Donors beyond PIR and across regions. ? Why would funders give us money? For the interest of non-commercial purposes and those who want more inclusive internet eco-system despite diversity and in tune with NCSG goals and objectives (Mission) to ensure their voices are heard and they participate actively against all odds envisioned in commercial stakes. ? Which jurisdictions would they come from? Funding could come from a global purpose and largely regional as explained earlier which are tied to specific regions and that is one area FC intend to target too. Like the CIPESA Internet Freedom Forum has a session on funding and donors session. Just a few FC is targeting all things equal for this year. ? would it be better to have local funders or thematic funders contribute to some of our members separately, rather than give to an NCSG entity? For now, both ways are fine, but for purposes of this, NCSG charter was not specific on this and if we must have local funders or via thematic funding to some members. Its worthy of exploring but then, FC should be looking at it from the point of purse that is available to support members, knowing fully well that funders require at least organistional endorsement to pathway with their funds, a clout some of our upcoming members and small membership organizations may not have. One can confidently say that NCSG is the umbrella body of non-commercial users. ? are membership fees part of this funding strategy? If so, do we have an idea of the membership fees? For me, with my experience, membership fees will be a clog, considering that in some countries, especially in Africa, where I am currently serving as the Vice President, African Civil Society on the Information Society (ACSIS), charges on dollar fee surpasses some of the annual dues affordable, which does not make sense to be making money for eTransaction operators. While some have restriction occasioned to their regional policies. For instance, we access paypal in Nigeria in terms of usage if preloaded, but cannot receive fund via paypal due to government policy. For NPOC charter ?NPOC will not collect dues, fees, or subscriptions from its members.? ? do we need the FC members, if they are going to be auditors, to have those credentials? Credentials matters and I will not place that over and above industry experience linked to finance/audit management. We may not get strict auditors because of the kind of work we do (voluntary, except we are ready to start paying auditors per say); but people who are willing to learn could be another area, definitely not devoid of experience such as managing an NGO could be an ideal, among others. Budget ? at the moment we do not prepare an NCSG budget, at least I am unaware of it. I have only participated in NCSG for 5-6 years, I do not recall seeing one. What are the plans, who would do it, how would it be approved. Well, you are very right. I have not seen one myself too. This is one of the streamlining for accountability that current FC envisaged to entrench and its not going to work if Cs are not cooperating. Another instance is that Cs need to prepare this, invariably FC can advice if need be as you cannot prepare budget and still audit same. This will be achieved by ensuring that each Cs either through the Financial Secretary or Secretariat prepares their budget and send to NCSG FC, even if its for the records, because they have their individual C exco to approve spending. NCSG Excom needs a copy too to enable it also prepare own budget leveraging possibly from what the Cs may have submitted to ensure they do not run across purposes but rather driving strength from Cs. And based on this, FC can also submit its own budget lines likewise the Policy Committee (PC) since both are the legally recognized sub-entities in the charter based on activities to be executed within the year under review in collaboration with NCSG EC. We can create capacity building on budgeting for ICANN as annual refresher course to keep leadership of Cs and NCSG abreast of development and feedback on any challenges using pre-ICANN sessions. You can tag the Committees budget as operational budgets while that of Cs as capital and we can take up from there. This will make it easy for ABR where necessary too to fill in the gap of engagements. These will be merged to ensure everyone is extending a helping hand to another based on equal footing. We can develop this via a budget template either in existence or fresh template, so as to ease harmonization of the budget session eventually. ? at the moment we do not appear to be doing oversight of the funds approved for travel requests. Should that be in an annual public financial report? Yes, very correct and its part of the challenges. Yes, we may be members of NCSG, but these have to be submitted afterwards, either quarterly or annually as may be agreed upon, but yearly is mandatory. These are some of the understanding required to co-exist in this space. The oversight does not mean FC non-approval as long as its contained in the formal budget approved/submitted for the year, but to take note and make comments thereafter on judicious or otherwise use of the said funds to improve future applications. One of it is that Cs may give scholarships/fellowships to an ICANN public meeting, how will FC know if such scholarships were judiciously expended to the letter if not by monitoring the processes to the letter as well and may be interfacing with scholarship awardees at venue to know areas of dissatisfaction so as to improve on processes. There is need to also have its own session accommodated in such a meeting so as to kill two birds with a stone and create awareness, earn more public trust and openness, in order to provide background to FC reports eventually on how funds received were used either to ICANN.org or funders for future engagements and sustained funding or affiliation as most funders will request feedback of funds. ? How would an NCSG FC assume oversight of NPOC and NCUC spending? Not clear in the Charter, unless I am misreading it. There is no central NCSG control. It behoves on the leadership of NPOC and NCUC to trust FC enough and send or share information as deem fit and as may be required or demanded. Part of the oversight is physical monitoring of activities both at ICANN and outside where such a fund is being expended as long as the community funding and activities are involve. This will put the FC representatives in good standing to defend any claim, allegations or query that may arise thereof from ICANN.org or funders, thereby offering better insight when necessary. Communications and transparency ? Who is the FC accountable to? How does it communicate to that responsible party? Based on our NCSG charter which sets up the FC, communication to community is key but in terms of accountable, its ICANN.org and funders, which stated inter alia in Section 2.6: ? ?Accounting for any funds received by the NCSG from any source. ? Financial reports must be prepared annually and be made public. ? Fulfill any other accounting, auditing or other prescribed financial requirements as set by the ICANN Board of Directors for organizations within the ICANN structure. ? Document methods and procedures used for accounting, reporting and budget creation. Such documentation is subject to review by the NCSG-??EC.? With the aforementioned, FC reports to ICANN.org and funders whereas its annual report must be made public, which is the community and by extension our respective Cs in terms of debriefing (feedback), at Cs Exco sessions or as may be required. NB: Of course where good communication exists as it should, one expects that NCSG EC and Cs will have the privilege of the content prior to/soon after sending it out to ICANN.org or funders, since it will be coming from them anyways. ? Does the FC have the authority to give direction to Maryam? In other words, does she support the FC independently, or is that supposed to happen through the NCSG EC? I think that Maryam and other ICANN support staff are here to help us achieve our various assignments, goals and mandates, and as such could take a direction to assist any given committee as long as they are constitutionally or legally constituted. Whether the direction is an authority resides with the chair or person giving the direction, so as to take full responsibility of the action when it matters. Therefore, every ICANN staff supports every community including committees independently. Theirs is facilitation. As I have explained based on the charter, FC being the supposed auditor now should assume some level of autonomy but under good understanding keeps NCSG EC briefed, that is why communication, trust and understanding are key, but I do not think that is the way some of us understand it hence the challenge in communication. And that is why its vital to include FC Reps in NCSG EC and their respective Cs, even at observer level, as they are not ?supposed? to be heard at such meetings outside advisory. ? do we have an agenda for the Kobe face to face meeting? will it be open to all stakeholders, or closed to NCSG members? Yes, of course. I am aware, there is an agenda for Kobe and so all other meetings will be open for all stakeholders and is part of the planned outreach series to bridge the gap between FC and ICANN finance as well as NCSG community specifically, as listed above. These are just a few questions I have. I do not quite understand what Remmy is saying below, and am simply trying to put a few questions down to kickstart a strategic discussion. Thanks for putting the questions, definitely not a few and I hope my "few" responses will be helpful in charting the way forward. Thanks again Remmy Nweke _______________________________________________ NCSG-FC mailing list NCSG-FC at lists.ncsg.is https://lists.ncsg.is/mailman/listinfo/ncsg-fc -------------- next part -------------- An HTML attachment was scrubbed... URL: From thatomfikwe at gmail.com Thu Feb 21 17:48:37 2019 From: thatomfikwe at gmail.com (Thato Mfikwe) Date: Thu, 21 Feb 2019 17:48:37 +0200 Subject: [NCSG-FC] ICANN64 Meeting plenary Message-ID: Hi all, *1. This is final call for iput on the ICANN64 FC meeting agenda (90 minutes), please make your input so that I can circulate in the mailing list by Monday 25 February for community input.* Proposed Agenda a. Introduction and background on the Finance Committee (5 min) Justification: This will ensure participants are on the same page and with the same understanding as the meeting progresses. b. Overview of the NCSG Charter and the Draft FC OP (10 min) Justification: Review of the Charter and OP contention areas (responsibilities, the accounting, auditing and providing oversight function, bank account and incopropration implications or use of constituency bank accounts (SPV), how the FC works with constituencies and financial reporting ) c. Q & A (10 min) d. Harmonising of the OP with the NCSG Charter based on the overview (10 min) Justification: Obtaining community input and building synergy between the NCSG Charter and FC OP e. Open floor and inputs (15 min) f. NCSG priorities, needs and wants - planning forward (5 min) Justification: Collection of ideas from members regarding their priorities, needs and wants g. Open floor (15 min) h.Fundraising and levelraging on ICANN finances - initiating a fundraising plan (5 min) Justification: Exploring different avenue for fundraising for NCSG i. Open floor and Q & A (10 min) j. Call for volunteers for different focus areas and closure - building internal capacity (5 min) *2. Should the be an oversight somewhere, please make recommendation.* *3. Please also make input in terms of resource people who will be needed to ease proceedings of this meeting and can also provide answers. I still maintain that we need ICANN finance, so that we are able to discuss ways on how the FC can leverage on ICANN finances and improve on the ABR submission process.* Thanks. Thato Mfikwe. -------------- next part -------------- An HTML attachment was scrubbed... URL: From remmyn at gmail.com Thu Feb 21 18:16:25 2019 From: remmyn at gmail.com (Remmy Nweke) Date: Thu, 21 Feb 2019 17:16:25 +0100 Subject: [NCSG-FC] [Ext] ICANN64 FC meeting preparations In-Reply-To: References: <5jyfwu2xk66oqy1s1u7a9dwe.1550696024335@email.android.com> <6e8404b1-94e0-6187-caa0-4565afe3c94e@mail.utoronto.ca> Message-ID: Thanks Stephanie and for finding that class work useful. ? @Thato and Bruna May I appeal for a cease fire on any other trend. As you can see @Stephanie has raised some fundamental questions, which is the way I think we should go, even if we do not accomplish everything, we have started on the right step. I expect us to ask more questions and attempt will be made to provide an answer. There is no bank of knowledge anywhere but collectively we can make FC of our dreams working. I will also request Thato to ensure he reapplies for NCUC FC since that is the case. Reason being that we have started making progress by talking now and definitely will arrive on ways forward and experience as his is required to channel these efforts and build NCSG FC we shall all be proud of, despite differences. And definitely once e new person comes we may need the orientation all over again. May be afterwards, we may have to develop collectively educational programme for FC members 101. I will personally want all of us to be part of the history that reposition NCSG FC, supported it to take its root firmly for good and stop any perceived competition or personal biases, which may be widening our communication gap rather than closing.. Key take is that we need to understand each other more by communicating, asking questions and hopefully get answers that may be satisfactory eventually. NCSG Charter may be reviewed, but I will appeal for further attempt in implementation so that when we do review, say by end of the year, there will other areas to discover for correction during review. In fact when all the current leadership emerged, I was hopeful we have an understanding fellows who will move FC forward and I would not like to be disappointed. Have a good evening people. Remmy Nweke ____ REMMY NWEKE, mNGE, Lead Strategist/Group Executive Editor, DigitalSENSE Africa Media [*Multiple-award winning medium*] (DigitalSENSE Business News ; ITREALMS , NaijaAgroNet ) Block F1, Shop 133 Moyosore Aboderin Plaza, Bolade Junction, Oshodi-Lagos M: 234-8033592762, 8023122558, 8051000475, T: @ITRealms Author: A Decade of ICT Reportage in Nigeria *2019 Nigeria DigitalSENSE Forum on IG4D & Nigeria IPv6 Roundtable * JOIN us!! *Vice President, African Civil Society on the Information Society (ACSIS ) *NPOC FC Rep @ICANN Non-Commercial Stakeholders Group (NCSG)* _________________________________________________________________ *Confidentiality Notice:* The information in this document and attachments are confidential and may also be privileged information. It is intended only for the use of the named recipient. Remmy Nweke does not accept legal responsibility for the contents of this e-mail. If you are not the intended recipient, please notify me immediately, then delete this document and do not disclose the contents of this document to any other person, nor make any copies. Violators may face court persecution. On Thu, Feb 21, 2019 at 3:48 PM Stephanie Perrin < stephanie.perrin at mail.utoronto.ca> wrote: > Thanks Remmy, this is useful. Lets keep up the effort to address these > substantive issues! > > Stephanie > On 2019-02-21 08:14, Remmy Nweke wrote: > > Dear Stephanie >> >> *Thanks for the questions. I think it?s a bold step in resolving whatever >> quagmire we are currently in as FC with hope it will avail us more >> understanding. I will try to respond to them from my prism inline below.* >> >> I can only speak for myself here folks, but I think it would really help >> me understand the ongoing work of the FC if I could read the plan. Where >> is the plan? Here are a few sample questions, on a basic skeleton. >> >> *Incorporation of NCSG* >> >> ? what are the goals of the FC in terms of NCSG's structure? >> >> *The FC goals are driven by the NCSG Charter which include but not >> limited to entrenching:* >> >> *(a) ** responsible fund raising mechanism in place, * >> >> *(b)**setting voluntary contribution levels for members, * >> >> *(c) **determining procedures for the distribution of funds, and * >> >> *(d)**for monitoring the utilization of funds. * >> >> *(e) **The Treasurer function. * >> >> *In addition, FC tends to among others:* >> >> ? *Develop and deploy a fund-??raising plan for the NCSG;* >> >> ? *Work with the ICANN staff to determine levels of support >> available to the NCSG;* >> >> ? *Work with ICANN finance officers to insure the NCSG and its >> Constituencies receive fair and equivalent financial support from ICANN;* >> >> ? *Accounting for any funds received by the NCSG from any source. >> This accounting will include the following:* >> >> *??* *All funds raised by voluntary membership fees or otherwise must >> be held in a separate NCSG account.* >> >> *?? **Proper controls must be implemented.* >> >> *?? **Regarding Expenditures:* >> >> ? *All expenditures under 500 Euro may be made on the authority of >> the NCSG Treasurer* >> >> ? *All expenditures over 500 Euro must be approved by the >> NCSG-??FC* >> >> *?? **Financial reports must be prepared annually and be made public.* >> >> ? *Provide internal conflict resolution process regarding funds.* >> >> ? *Provide the oversight of the Treasurer function.* >> >> ? *Fulfill any other accounting, auditing or other prescribed financial >> requirements as set by the ICANN Board of Directors for organizations >> within the ICANN structure* >> >> ? *Document methods and procedures used for accounting, reporting and >> budget creation. Such documentation is subject to review by the NCSG-?* >> *?**EC.* >> >> ? do we need to be a legal entity to do the work we have been doing at >> ICANN? >> >> *My understanding this is that currently some of the Cs, in fact both >> Constituencies have already become legal entities and has the capability of >> receiving fund if need be and there may be NO need to engage in another >> process considering our diversity and very short tenure of offices. Thus, >> recommended that we use what we have to get what we need. That is using any >> of the Cs now to open an SPV ? Special Purpose Vehicle account, just like >> ISOC did in setting up PIR to serve a special purpose until such a time, >> the footing is clearer and scope warrants stand-alone legal entity.* >> >> ? If not, why do it? What are the risks and benefits of being a legal >> entity? >> >> *As for the risks of being a separate legal entity by NCSG, for now, as >> ICANN offshoot for non-Commercial, we need to do the registration in the >> United States and any other country as may be agreed upon, which has a >> process including setting up the BoT ? Board of Trustees which involves >> residency etc very often. This will also entail another level or layer of >> advisory team outside the NCSG EC, hence my earlier suggestion for us to >> use what we have to get what we want via SPV.* >> >> *SPV account actually is to ensure that every external fund inflow >> resides in a place as may be agreed by both Cs and NCSG EC with an MoU, so >> that we do not fall into issues when the current leadership of any chosen >> account holder elapses and avail NCSG full control of such account under FC >> as mandated in the charter at all times.* >> >> *Fundraising strategy* >> >> ? what exactly do we need money for? >> >> *We need money for outreach for membership drive and showcase of what >> NCSG family is, and has been doing, stand for and support NCSG community >> and individual work including but not limited to distinct and independent >> research by NPOC | NCUC or NCSG, as may become necessary for internal use >> and support our position, on the side line of policy development and >> building capacity of our members across financial transparency and policy >> engagement and development, among others. Especially where ICANN support >> cannot cover immediately; As you know most ICANN supports are tied to >> regions, which does not preclude that some other regions at the same time >> do not need support within the remits of outlines above. For instance, >> ICANN can support global IGF, what of the regional IGFs etc or national IG >> events. These are revolving outreach programmes.* >> >> ? do we have a current inventory of all the existing funding we receive? >> >> *The only one known to me/FC is from PIR ? Public Interest Registry, this >> has to be expanded with the outreach targeted at Donors beyond PIR and >> across regions.* >> >> ? Why would funders give us money? >> >> *For the interest of non-commercial purposes and those who want more >> inclusive internet eco-system despite diversity and in tune with NCSG goals >> and objectives (Mission) to ensure their voices are heard and they >> participate actively against all odds envisioned in commercial stakes.* >> >> ? Which jurisdictions would they come from? >> >> *Funding could come from a global purpose and largely regional as >> explained earlier which are tied to specific regions and that is one area >> FC intend to target too. Like the CIPESA Internet Freedom Forum has a >> session on funding and donors session. Just a few FC is targeting all >> things equal for this year.* >> >> ? would it be better to have local funders or thematic funders >> contribute to some of our members separately, rather than give to an NCSG >> entity? >> >> *For now, both ways are fine, but for purposes of this, NCSG charter was >> not specific on this and if we must have local funders or via thematic >> funding to some members. Its worthy of exploring but then, FC should be >> looking at it from the point of purse that is available to support members, >> knowing fully well that funders require at least organistional endorsement >> to pathway with their funds, a clout some of our upcoming members and small >> membership organizations may not have. One can confidently say that NCSG is >> the umbrella body of non-commercial users.* >> >> ? are membership fees part of this funding strategy? If so, do we have >> an idea of the membership fees? >> >> *For me, with my experience, membership fees will be a clog, considering >> that in some countries, especially in Africa, where I am currently serving >> as the Vice President, African Civil Society on the Information Society >> (ACSIS), charges on dollar fee surpasses some of the annual dues >> affordable, which does not make sense to be making money for eTransaction >> operators. While some have restriction occasioned to their regional >> policies. For instance, we access paypal in Nigeria in terms of usage if >> preloaded, but cannot receive fund via paypal due to government policy.* >> >> *For NPOC charter ?**NPOC will not collect dues, fees, or subscriptions >> from its members.?* >> >> ? do we need the FC members, if they are going to be auditors, to have >> those credentials? >> >> *Credentials matters and I will not place that over and above industry >> experience linked to finance/audit management. We may not get strict >> auditors because of the kind of work we do (voluntary, except we are ready >> to start paying auditors per say); but people who are willing to learn >> could be another area, definitely not devoid of experience such as managing >> an NGO could be an ideal, among others.* >> >> *Budget* >> >> ? at the moment we do not prepare an NCSG budget, at least I am unaware >> of it. I have only participated in NCSG for 5-6 years, I do not recall >> seeing one. What are the plans, who would do it, how would it be approved. >> >> *Well, you are very right. I have not seen one myself too. This is one of >> the streamlining for accountability that current FC envisaged to entrench >> and its not going to work if Cs are not cooperating. Another instance is >> that Cs need to prepare this, invariably FC can advice if need be as you >> cannot prepare budget and still audit same. This will be achieved by >> ensuring that each Cs either through the Financial Secretary or Secretariat >> prepares their budget and send to NCSG FC, even if its for the records, >> because they have their individual C exco to approve spending. NCSG Excom >> needs a copy too to enable it also prepare own budget leveraging possibly >> from what the Cs may have submitted to ensure they do not run across >> purposes but rather driving strength from Cs.* >> >> *And based on this, FC can also submit its own budget lines likewise the >> Policy Committee (PC) since both are the legally recognized sub-entities in >> the charter based on activities to be executed within the year under review >> in collaboration with NCSG EC. * >> >> *We can create capacity building on budgeting for ICANN as annual >> refresher course to keep leadership of Cs and NCSG abreast of development >> and feedback on any challenges using pre-ICANN sessions.* >> >> *You can tag the Committees budget as operational budgets while that of >> Cs as capital and we can take up from there. This will make it easy for ABR >> where necessary too to fill in the gap of engagements.* >> >> *These will be merged to ensure everyone is extending a helping hand to >> another based on equal footing.* >> >> *We can develop this via a budget template either in existence or fresh >> template, so as to ease harmonization of the budget session eventually.* >> >> ? at the moment we do not appear to be doing oversight of the funds >> approved for travel requests. Should that be in an annual public financial >> report? >> >> *Yes, very correct and its part of the challenges. Yes, we may be members >> of NCSG, but these have to be submitted afterwards, either quarterly or >> annually as may be agreed upon, but yearly is mandatory. These are some of >> the understanding required to co-exist in this space. The oversight does >> not mean FC non-approval as long as its contained in the formal budget >> approved/submitted for the year, but to take note and make comments >> thereafter on judicious or otherwise use of the said funds to improve >> future applications. * >> >> *One of it is that Cs may give scholarships/fellowships to an ICANN >> public meeting, how will FC know if such scholarships were judiciously >> expended to the letter if not by monitoring the processes to the letter as >> well and may be interfacing with scholarship awardees at venue to know >> areas of dissatisfaction so as to improve on processes. * >> >> *There is need to also have its own session accommodated in such a >> meeting so as to kill two birds with a stone and create awareness, earn >> more public trust and openness, in order to provide background to FC >> reports eventually on how funds received were used either to ICANN.org or >> funders for future engagements and sustained funding or affiliation as most >> funders will request feedback of funds.* >> >> ? How would an NCSG FC assume oversight of NPOC and NCUC spending? Not >> clear in the Charter, unless I am misreading it. There is no central NCSG >> control. >> >> *It behoves on the leadership of NPOC and NCUC to trust FC enough and >> send or share information as deem fit and as may be required or demanded. >> Part of the oversight is physical monitoring of activities both at ICANN >> and outside where such a fund is being expended as long as the community >> funding and activities are involve. This will put the FC representatives in >> good standing to defend any claim, allegations or query that may arise >> thereof from ICANN.org or funders, thereby offering better insight when >> necessary.* >> >> *Communications and transparency* >> >> ? Who is the FC accountable to? How does it communicate to that >> responsible party? >> >> *Based on our NCSG charter which sets up the FC, communication to >> community is key but in terms of accountable, its ICANN.org and funders, >> which stated inter alia in Section 2.6: * >> >> ? *?Accounting for any funds received by the NCSG from any >> source.* >> >> ? *Financial reports must be prepared annually and be made >> public.* >> >> ? *Fulfill any other accounting, auditing or other prescribed >> financial requirements as set by the ICANN Board of Directors for >> organizations within the ICANN structure.* >> >> ? *Document methods and procedures used for accounting, reporting >> and budget creation. Such documentation is subject to review by the >> NCSG-??EC.?* >> >> >> >> *With the aforementioned, FC reports to ICANN.org and funders whereas its >> annual report must be made public, which is the community and by extension >> our respective Cs in terms of debriefing (feedback), at Cs Exco sessions or >> as may be required.* >> >> >> >> *NB: Of course where good communication exists as it should, one expects >> that NCSG EC and Cs will have the privilege of the content prior to/soon >> after sending it out to ICANN.org or funders, since it will be coming from >> them anyways.* >> >> ? Does the FC have the authority to give direction to Maryam? In other >> words, does she support the FC independently, or is that supposed to happen >> through the NCSG EC? >> >> *I think that Maryam and other ICANN support staff are here to help us >> achieve our various assignments, goals and mandates, and as such could take >> a direction to assist any given committee as long as they are >> constitutionally or legally constituted. Whether the direction is an >> authority resides with the chair or person giving the direction, so as to >> take full responsibility of the action when it matters. Therefore, every >> ICANN staff supports every community including committees independently. >> Theirs is facilitation.* >> >> *As I have explained based on the charter, FC being the supposed auditor >> now should assume some level of autonomy but under good understanding keeps >> NCSG EC briefed, that is why communication, trust and understanding are >> key, but I do not think that is the way some of us understand it hence the >> challenge in communication. And that is why its vital to include FC Reps in >> NCSG EC and their respective Cs, even at observer level, as they are not >> ?supposed? to be heard at such meetings outside advisory.* >> >> ? do we have an agenda for the Kobe face to face meeting? will it be >> open to all stakeholders, or closed to NCSG members? >> >> *Yes, of course. I am aware, there is an agenda for Kobe and so all other >> meetings will be open for all stakeholders and is part of the planned >> outreach series to bridge the gap between FC and ICANN finance as well as >> NCSG community specifically, as listed above.* >> >> These are just a few questions I have. I do not quite understand what >> Remmy is saying below, and am simply trying to put a few questions down to >> kickstart a strategic discussion. >> >> *Thanks for putting the questions, definitely not a few and I hope my >> "few" responses will be helpful in charting the way forward.* >> >> *Thanks again* >> >> Remmy Nweke >> > > _______________________________________________ > NCSG-FC mailing listNCSG-FC at lists.ncsg.ishttps://lists.ncsg.is/mailman/listinfo/ncsg-fc > > _______________________________________________ > NCSG-FC mailing list > NCSG-FC at lists.ncsg.is > https://lists.ncsg.is/mailman/listinfo/ncsg-fc > -------------- next part -------------- An HTML attachment was scrubbed... URL: From remmyn at gmail.com Fri Feb 22 01:47:02 2019 From: remmyn at gmail.com (Remmy Nweke) Date: Fri, 22 Feb 2019 00:47:02 +0100 Subject: [NCSG-FC] ICANN64 Meeting plenary In-Reply-To: References: Message-ID: Thanks Thato It should have been very helpful If I was to be there to assist in some physically. However, there will be need for online participation. There is need also to have an ICANN staff preferably from Finance speak to some of the issues, especially in responsibility and expectations from an FC. Equally a few minutes remarks by NCSG chair will not be out of place as well as Cs chair. May be NCSG 3minutes, C chairs 2minutes each. They will still speak to issues as intervention arises. Good luck. Remmy ____ REMMY NWEKE, mNGE, Lead Strategist/Group Executive Editor, DigitalSENSE Africa Media [*Multiple-award winning medium*] (DigitalSENSE Business News ; ITREALMS , NaijaAgroNet ) Block F1, Shop 133 Moyosore Aboderin Plaza, Bolade Junction, Oshodi-Lagos M: 234-8033592762, 8023122558, 8051000475, T: @ITRealms Author: A Decade of ICT Reportage in Nigeria *2019 Nigeria DigitalSENSE Forum on IG4D & Nigeria IPv6 Roundtable * JOIN us!! *Vice President, African Civil Society on the Information Society (ACSIS ) *NPOC FC Rep @ICANN Non-Commercial Stakeholders Group (NCSG)* _________________________________________________________________ *Confidentiality Notice:* The information in this document and attachments are confidential and may also be privileged information. It is intended only for the use of the named recipient. Remmy Nweke does not accept legal responsibility for the contents of this e-mail. If you are not the intended recipient, please notify me immediately, then delete this document and do not disclose the contents of this document to any other person, nor make any copies. Violators may face court persecution. On Thu, Feb 21, 2019 at 4:48 PM Thato Mfikwe wrote: > Hi all, > > *1. This is final call for iput on the ICANN64 FC meeting agenda (90 > minutes), please make your input so that I can circulate in the mailing > list by Monday 25 February for community input.* > > Proposed Agenda > a. Introduction and background on the Finance Committee (5 min) > Justification: This will ensure participants are on the same page and with > the same understanding as the meeting progresses. > > b. Overview of the NCSG Charter and the Draft FC OP (10 min) > Justification: Review of the Charter and OP contention areas > (responsibilities, the accounting, auditing and providing oversight > function, bank account and incopropration implications or use of > constituency bank accounts (SPV), how the FC works with constituencies and > financial reporting ) > > c. Q & A (10 min) > > d. Harmonising of the OP with the NCSG Charter based on the overview (10 > min) > Justification: Obtaining community input and building synergy between the > NCSG Charter and FC OP > > e. Open floor and inputs (15 min) > > f. NCSG priorities, needs and wants - planning forward (5 min) > Justification: Collection of ideas from members regarding their > priorities, needs and wants > > g. Open floor (15 min) > > h.Fundraising and levelraging on ICANN finances - initiating a fundraising > plan (5 min) > Justification: Exploring different avenue for fundraising for NCSG > > i. Open floor and Q & A (10 min) > > j. Call for volunteers for different focus areas and closure - building > internal capacity (5 min) > > > *2. Should the be an oversight somewhere, please make recommendation.* > > *3. Please also make input in terms of resource people who will be needed > to ease proceedings of this meeting and can also provide answers. I still > maintain that we need ICANN finance, so that we are able to discuss ways on > how the FC can leverage on ICANN finances and improve on the ABR submission > process.* > > Thanks. > > Thato Mfikwe. > > _______________________________________________ > NCSG-FC mailing list > NCSG-FC at lists.ncsg.is > https://lists.ncsg.is/mailman/listinfo/ncsg-fc > -------------- next part -------------- An HTML attachment was scrubbed... URL: From stephanie.perrin at mail.utoronto.ca Fri Feb 22 02:01:40 2019 From: stephanie.perrin at mail.utoronto.ca (Stephanie Perrin) Date: Fri, 22 Feb 2019 00:01:40 +0000 Subject: [NCSG-FC] ICANN64 Meeting plenary In-Reply-To: References: Message-ID: <451cb70a-6ca7-6e3d-3a3f-315d75eca556@mail.utoronto.ca> Have you inquired of other Stakeholder Groups, how they handle their finances? What role does ICANN play? I would suspect none. It is not their place. Stephanie On 2019-02-21 18:47, Remmy Nweke wrote: Thanks Thato It should have been very helpful If I was to be there to assist in some physically. However, there will be need for online participation. There is need also to have an ICANN staff preferably from Finance speak to some of the issues, especially in responsibility and expectations from an FC. Equally a few minutes remarks by NCSG chair will not be out of place as well as Cs chair. May be NCSG 3minutes, C chairs 2minutes each. They will still speak to issues as intervention arises. Good luck. Remmy ____ REMMY NWEKE, mNGE, Lead Strategist/Group Executive Editor, DigitalSENSE Africa Media [Multiple-award winning medium] (DigitalSENSE Business News; ITREALMS, NaijaAgroNet) Block F1, Shop 133 Moyosore Aboderin Plaza, Bolade Junction, Oshodi-Lagos M: 234-8033592762, 8023122558, 8051000475, T: @ITRealms Author: A Decade of ICT Reportage in Nigeria 2019 Nigeria DigitalSENSE Forum on IG4D & Nigeria IPv6 Roundtable JOIN us!! *Vice President, African Civil Society on the Information Society (ACSIS) NPOC FC Rep @ICANN Non-Commercial Stakeholders Group (NCSG) _________________________________________________________________ *Confidentiality Notice:* The information in this document and attachments are confidential and may also be privileged information. It is intended only for the use of the named recipient. Remmy Nweke does not accept legal responsibility for the contents of this e-mail. If you are not the intended recipient, please notify me immediately, then delete this document and do not disclose the contents of this document to any other person, nor make any copies. Violators may face court persecution. On Thu, Feb 21, 2019 at 4:48 PM Thato Mfikwe > wrote: Hi all, 1. This is final call for iput on the ICANN64 FC meeting agenda (90 minutes), please make your input so that I can circulate in the mailing list by Monday 25 February for community input. Proposed Agenda a. Introduction and background on the Finance Committee (5 min) Justification: This will ensure participants are on the same page and with the same understanding as the meeting progresses. b. Overview of the NCSG Charter and the Draft FC OP (10 min) Justification: Review of the Charter and OP contention areas (responsibilities, the accounting, auditing and providing oversight function, bank account and incopropration implications or use of constituency bank accounts (SPV), how the FC works with constituencies and financial reporting ) c. Q & A (10 min) d. Harmonising of the OP with the NCSG Charter based on the overview (10 min) Justification: Obtaining community input and building synergy between the NCSG Charter and FC OP e. Open floor and inputs (15 min) f. NCSG priorities, needs and wants - planning forward (5 min) Justification: Collection of ideas from members regarding their priorities, needs and wants g. Open floor (15 min) h.Fundraising and levelraging on ICANN finances - initiating a fundraising plan (5 min) Justification: Exploring different avenue for fundraising for NCSG i. Open floor and Q & A (10 min) j. Call for volunteers for different focus areas and closure - building internal capacity (5 min) 2. Should the be an oversight somewhere, please make recommendation. 3. Please also make input in terms of resource people who will be needed to ease proceedings of this meeting and can also provide answers. I still maintain that we need ICANN finance, so that we are able to discuss ways on how the FC can leverage on ICANN finances and improve on the ABR submission process. Thanks. Thato Mfikwe. _______________________________________________ NCSG-FC mailing list NCSG-FC at lists.ncsg.is https://lists.ncsg.is/mailman/listinfo/ncsg-fc _______________________________________________ NCSG-FC mailing list NCSG-FC at lists.ncsg.is https://lists.ncsg.is/mailman/listinfo/ncsg-fc -------------- next part -------------- An HTML attachment was scrubbed... URL: From remmyn at gmail.com Fri Feb 22 03:33:39 2019 From: remmyn at gmail.com (Remmy Nweke) Date: Fri, 22 Feb 2019 02:33:39 +0100 Subject: [NCSG-FC] ICANN64 Meeting plenary In-Reply-To: <451cb70a-6ca7-6e3d-3a3f-315d75eca556@mail.utoronto.ca> References: <451cb70a-6ca7-6e3d-3a3f-315d75eca556@mail.utoronto.ca> Message-ID: Sorry Stephanie to come in here. Others may choose to ignore it but I think there is a role based on our NCSG charter guidelines especially on report back on how money or funds given to stakeholders group or received from all sources are expended. In financial management it's usually a precondition for another round of support which I think ICANN.org is not strict about otherwise they should be making the demands. May be because there are individual reports very often and I know Maryam team emphasis on this too as precondition. Regards Remmy On Fri, 22 Feb 2019, 1:01 a.m. Stephanie Perrin < stephanie.perrin at mail.utoronto.ca wrote: > Have you inquired of other Stakeholder Groups, how they handle their > finances? What role does ICANN play? > > I would suspect none. It is not their place. > > Stephanie > On 2019-02-21 18:47, Remmy Nweke wrote: > > Thanks Thato > It should have been very helpful If I was to be there to assist in some > physically. > > However, there will be need for online participation. > > There is need also to have an ICANN staff preferably from Finance speak to > some of the issues, especially in responsibility and expectations from an > FC. > > Equally a few minutes remarks by NCSG chair will not be out of place as > well as Cs chair. May be NCSG 3minutes, C chairs 2minutes each. They will > still speak to issues as intervention arises. > > Good luck. > Remmy > ____ > REMMY NWEKE, mNGE, > Lead Strategist/Group Executive Editor, > DigitalSENSE Africa Media [*Multiple-award winning medium*] > (DigitalSENSE Business News > ; ITREALMS > , NaijaAgroNet > ) > Block F1, Shop 133 Moyosore Aboderin Plaza, Bolade Junction, Oshodi-Lagos > M: 234-8033592762, 8023122558, 8051000475, T: @ITRealms > > Author: A Decade of ICT Reportage in Nigeria > > > *2019 Nigeria DigitalSENSE Forum on IG4D & Nigeria IPv6 Roundtable > * > JOIN us!! > > *Vice President, African Civil Society on the Information Society (ACSIS > ) > > *NPOC FC Rep @ICANN Non-Commercial Stakeholders Group (NCSG)* > > _________________________________________________________________ > *Confidentiality Notice:* The information in this document and attachments > are confidential and may also be privileged information. It is intended > only for the use of the named recipient. Remmy Nweke does not accept legal > responsibility for the contents of this e-mail. If you are not the intended > recipient, please notify me immediately, then delete this document and do > not disclose the contents of this document to any other person, nor make > any copies. Violators may face court persecution. > > > > On Thu, Feb 21, 2019 at 4:48 PM Thato Mfikwe > wrote: > >> Hi all, >> >> *1. This is final call for iput on the ICANN64 FC meeting agenda (90 >> minutes), please make your input so that I can circulate in the mailing >> list by Monday 25 February for community input.* >> >> Proposed Agenda >> a. Introduction and background on the Finance Committee (5 min) >> Justification: This will ensure participants are on the same page and >> with the same understanding as the meeting progresses. >> >> b. Overview of the NCSG Charter and the Draft FC OP (10 min) >> Justification: Review of the Charter and OP contention areas >> (responsibilities, the accounting, auditing and providing oversight >> function, bank account and incopropration implications or use of >> constituency bank accounts (SPV), how the FC works with constituencies and >> financial reporting ) >> >> c. Q & A (10 min) >> >> d. Harmonising of the OP with the NCSG Charter based on the overview (10 >> min) >> Justification: Obtaining community input and building synergy between the >> NCSG Charter and FC OP >> >> e. Open floor and inputs (15 min) >> >> f. NCSG priorities, needs and wants - planning forward (5 min) >> Justification: Collection of ideas from members regarding their >> priorities, needs and wants >> >> g. Open floor (15 min) >> >> h.Fundraising and levelraging on ICANN finances - initiating a >> fundraising plan (5 min) >> Justification: Exploring different avenue for fundraising for NCSG >> >> i. Open floor and Q & A (10 min) >> >> j. Call for volunteers for different focus areas and closure - building >> internal capacity (5 min) >> >> >> *2. Should the be an oversight somewhere, please make recommendation. * >> >> *3. Please also make input in terms of resource people who will be needed >> to ease proceedings of this meeting and can also provide answers. I still >> maintain that we need ICANN finance, so that we are able to discuss ways on >> how the FC can leverage on ICANN finances and improve on the ABR submission >> process.* >> >> Thanks. >> >> Thato Mfikwe. >> >> _______________________________________________ >> NCSG-FC mailing list >> NCSG-FC at lists.ncsg.is >> https://lists.ncsg.is/mailman/listinfo/ncsg-fc >> > > _______________________________________________ > NCSG-FC mailing listNCSG-FC at lists.ncsg.ishttps://lists.ncsg.is/mailman/listinfo/ncsg-fc > > _______________________________________________ > NCSG-FC mailing list > NCSG-FC at lists.ncsg.is > https://lists.ncsg.is/mailman/listinfo/ncsg-fc > -------------- next part -------------- An HTML attachment was scrubbed... URL: From rafik.dammak at gmail.com Fri Feb 22 05:09:47 2019 From: rafik.dammak at gmail.com (Rafik Dammak) Date: Fri, 22 Feb 2019 12:09:47 +0900 Subject: [NCSG-FC] ICANN64 Meeting plenary In-Reply-To: References: <451cb70a-6ca7-6e3d-3a3f-315d75eca556@mail.utoronto.ca> Message-ID: Hi. ICANN Finance doesn't get involved on SG/C finance and refuse to manage bank accounts (in particular for those collecting membership fees) on their behalf for liability reasons. when ICANN give any in-kind or financial support, it already control the whole process i.e. procurement, hiring external resources, travel arrangement etc. In other cases like for membership system, it ask SG/C to pay first then it reimburse. As organization, it mitigates risks and doesn't let community to be involved on the process other making request through ABRs etc. it is the same for PDP WGs ( I am aware of as I am involved for EPDP) ICANN Finance team looks usually to discuss about ICANN budget and operating plan not about internal finance of SG/C. Best, Rafik Le ven. 22 f?vr. 2019 ? 10:34, Remmy Nweke a ?crit : > Sorry Stephanie to come in here. > Others may choose to ignore it but I think there is a role based on our > NCSG charter guidelines especially on report back on how money or funds > given to stakeholders group or received from all sources are expended. > In financial management it's usually a precondition for another round of > support which I think ICANN.org is not strict about otherwise they should > be making the demands. > May be because there are individual reports very often and I know Maryam > team emphasis on this too as precondition. > Regards > Remmy > > On Fri, 22 Feb 2019, 1:01 a.m. Stephanie Perrin < > stephanie.perrin at mail.utoronto.ca wrote: > >> Have you inquired of other Stakeholder Groups, how they handle their >> finances? What role does ICANN play? >> >> I would suspect none. It is not their place. >> >> Stephanie >> On 2019-02-21 18:47, Remmy Nweke wrote: >> >> Thanks Thato >> It should have been very helpful If I was to be there to assist in some >> physically. >> >> However, there will be need for online participation. >> >> There is need also to have an ICANN staff preferably from Finance speak >> to some of the issues, especially in responsibility and expectations from >> an FC. >> >> Equally a few minutes remarks by NCSG chair will not be out of place as >> well as Cs chair. May be NCSG 3minutes, C chairs 2minutes each. They will >> still speak to issues as intervention arises. >> >> Good luck. >> Remmy >> ____ >> REMMY NWEKE, mNGE, >> Lead Strategist/Group Executive Editor, >> DigitalSENSE Africa Media [*Multiple-award winning medium*] >> (DigitalSENSE Business News >> ; ITREALMS >> , NaijaAgroNet >> ) >> Block F1, Shop 133 Moyosore Aboderin Plaza, Bolade Junction, Oshodi-Lagos >> M: 234-8033592762, 8023122558, 8051000475, T: @ITRealms >> >> Author: A Decade of ICT Reportage in Nigeria >> >> >> *2019 Nigeria DigitalSENSE Forum on IG4D & Nigeria IPv6 Roundtable >> * >> JOIN us!! >> >> *Vice President, African Civil Society on the Information Society (ACSIS >> ) >> >> *NPOC FC Rep @ICANN Non-Commercial Stakeholders Group (NCSG)* >> >> _________________________________________________________________ >> *Confidentiality Notice:* The information in this document and >> attachments are confidential and may also be privileged information. It is >> intended only for the use of the named recipient. Remmy Nweke does not >> accept legal responsibility for the contents of this e-mail. If you are not >> the intended recipient, please notify me immediately, then delete this >> document and do not disclose the contents of this document to any other >> person, nor make any copies. Violators may face court persecution. >> >> >> >> On Thu, Feb 21, 2019 at 4:48 PM Thato Mfikwe >> wrote: >> >>> Hi all, >>> >>> *1. This is final call for iput on the ICANN64 FC meeting agenda (90 >>> minutes), please make your input so that I can circulate in the mailing >>> list by Monday 25 February for community input.* >>> >>> Proposed Agenda >>> a. Introduction and background on the Finance Committee (5 min) >>> Justification: This will ensure participants are on the same page and >>> with the same understanding as the meeting progresses. >>> >>> b. Overview of the NCSG Charter and the Draft FC OP (10 min) >>> Justification: Review of the Charter and OP contention areas >>> (responsibilities, the accounting, auditing and providing oversight >>> function, bank account and incopropration implications or use of >>> constituency bank accounts (SPV), how the FC works with constituencies and >>> financial reporting ) >>> >>> c. Q & A (10 min) >>> >>> d. Harmonising of the OP with the NCSG Charter based on the overview (10 >>> min) >>> Justification: Obtaining community input and building synergy between >>> the NCSG Charter and FC OP >>> >>> e. Open floor and inputs (15 min) >>> >>> f. NCSG priorities, needs and wants - planning forward (5 min) >>> Justification: Collection of ideas from members regarding their >>> priorities, needs and wants >>> >>> g. Open floor (15 min) >>> >>> h.Fundraising and levelraging on ICANN finances - initiating a >>> fundraising plan (5 min) >>> Justification: Exploring different avenue for fundraising for NCSG >>> >>> i. Open floor and Q & A (10 min) >>> >>> j. Call for volunteers for different focus areas and closure - building >>> internal capacity (5 min) >>> >>> >>> *2. Should the be an oversight somewhere, please make recommendation. * >>> >>> *3. Please also make input in terms of resource people who will be >>> needed to ease proceedings of this meeting and can also provide answers. I >>> still maintain that we need ICANN finance, so that we are able to discuss >>> ways on how the FC can leverage on ICANN finances and improve on the ABR >>> submission process.* >>> >>> Thanks. >>> >>> Thato Mfikwe. >>> >>> _______________________________________________ >>> NCSG-FC mailing list >>> NCSG-FC at lists.ncsg.is >>> https://lists.ncsg.is/mailman/listinfo/ncsg-fc >>> >> >> _______________________________________________ >> NCSG-FC mailing listNCSG-FC at lists.ncsg.ishttps://lists.ncsg.is/mailman/listinfo/ncsg-fc >> >> _______________________________________________ >> NCSG-FC mailing list >> NCSG-FC at lists.ncsg.is >> https://lists.ncsg.is/mailman/listinfo/ncsg-fc >> > _______________________________________________ > NCSG-FC mailing list > NCSG-FC at lists.ncsg.is > https://lists.ncsg.is/mailman/listinfo/ncsg-fc > -------------- next part -------------- An HTML attachment was scrubbed... URL: From thatomfikwe at gmail.com Fri Feb 22 19:03:46 2019 From: thatomfikwe at gmail.com (Thato Mfikwe) Date: Fri, 22 Feb 2019 19:03:46 +0200 Subject: [NCSG-FC] ICANN64 Meeting plenary In-Reply-To: <451cb70a-6ca7-6e3d-3a3f-315d75eca556@mail.utoronto.ca> References: <451cb70a-6ca7-6e3d-3a3f-315d75eca556@mail.utoronto.ca> Message-ID: Hi Stephanie, There is limited information on different community Finance committees and how they work but I have asked AFRALO to share how they manage their finances, will share once I obtain a response and the role played by ICANN Finance in that respect. I think NCSG will be first to adopt FC operational procedures but am not really sure, thanks. Thato Mfikwe. On Fri, Feb 22, 2019 at 2:01 AM Stephanie Perrin < stephanie.perrin at mail.utoronto.ca> wrote: > Have you inquired of other Stakeholder Groups, how they handle their > finances? What role does ICANN play? > > I would suspect none. It is not their place. > > Stephanie > On 2019-02-21 18:47, Remmy Nweke wrote: > > Thanks Thato > It should have been very helpful If I was to be there to assist in some > physically. > > However, there will be need for online participation. > > There is need also to have an ICANN staff preferably from Finance speak to > some of the issues, especially in responsibility and expectations from an > FC. > > Equally a few minutes remarks by NCSG chair will not be out of place as > well as Cs chair. May be NCSG 3minutes, C chairs 2minutes each. They will > still speak to issues as intervention arises. > > Good luck. > Remmy > ____ > REMMY NWEKE, mNGE, > Lead Strategist/Group Executive Editor, > DigitalSENSE Africa Media [*Multiple-award winning medium*] > (DigitalSENSE Business News > ; ITREALMS > , NaijaAgroNet > ) > Block F1, Shop 133 Moyosore Aboderin Plaza, Bolade Junction, Oshodi-Lagos > M: 234-8033592762, 8023122558, 8051000475, T: @ITRealms > > Author: A Decade of ICT Reportage in Nigeria > > > *2019 Nigeria DigitalSENSE Forum on IG4D & Nigeria IPv6 Roundtable > * > JOIN us!! > > *Vice President, African Civil Society on the Information Society (ACSIS > ) > > *NPOC FC Rep @ICANN Non-Commercial Stakeholders Group (NCSG)* > > _________________________________________________________________ > *Confidentiality Notice:* The information in this document and attachments > are confidential and may also be privileged information. It is intended > only for the use of the named recipient. Remmy Nweke does not accept legal > responsibility for the contents of this e-mail. If you are not the intended > recipient, please notify me immediately, then delete this document and do > not disclose the contents of this document to any other person, nor make > any copies. Violators may face court persecution. > > > > On Thu, Feb 21, 2019 at 4:48 PM Thato Mfikwe > wrote: > >> Hi all, >> >> *1. This is final call for iput on the ICANN64 FC meeting agenda (90 >> minutes), please make your input so that I can circulate in the mailing >> list by Monday 25 February for community input.* >> >> Proposed Agenda >> a. Introduction and background on the Finance Committee (5 min) >> Justification: This will ensure participants are on the same page and >> with the same understanding as the meeting progresses. >> >> b. Overview of the NCSG Charter and the Draft FC OP (10 min) >> Justification: Review of the Charter and OP contention areas >> (responsibilities, the accounting, auditing and providing oversight >> function, bank account and incopropration implications or use of >> constituency bank accounts (SPV), how the FC works with constituencies and >> financial reporting ) >> >> c. Q & A (10 min) >> >> d. Harmonising of the OP with the NCSG Charter based on the overview (10 >> min) >> Justification: Obtaining community input and building synergy between the >> NCSG Charter and FC OP >> >> e. Open floor and inputs (15 min) >> >> f. NCSG priorities, needs and wants - planning forward (5 min) >> Justification: Collection of ideas from members regarding their >> priorities, needs and wants >> >> g. Open floor (15 min) >> >> h.Fundraising and levelraging on ICANN finances - initiating a >> fundraising plan (5 min) >> Justification: Exploring different avenue for fundraising for NCSG >> >> i. Open floor and Q & A (10 min) >> >> j. Call for volunteers for different focus areas and closure - building >> internal capacity (5 min) >> >> >> *2. Should the be an oversight somewhere, please make recommendation. * >> >> *3. Please also make input in terms of resource people who will be needed >> to ease proceedings of this meeting and can also provide answers. I still >> maintain that we need ICANN finance, so that we are able to discuss ways on >> how the FC can leverage on ICANN finances and improve on the ABR submission >> process.* >> >> Thanks. >> >> Thato Mfikwe. >> >> _______________________________________________ >> NCSG-FC mailing list >> NCSG-FC at lists.ncsg.is >> https://lists.ncsg.is/mailman/listinfo/ncsg-fc >> > > _______________________________________________ > NCSG-FC mailing listNCSG-FC at lists.ncsg.ishttps://lists.ncsg.is/mailman/listinfo/ncsg-fc > > _______________________________________________ > NCSG-FC mailing list > NCSG-FC at lists.ncsg.is > https://lists.ncsg.is/mailman/listinfo/ncsg-fc > -------------- next part -------------- An HTML attachment was scrubbed... URL: From stephanie.perrin at mail.utoronto.ca Fri Feb 22 19:16:01 2019 From: stephanie.perrin at mail.utoronto.ca (Stephanie Perrin) Date: Fri, 22 Feb 2019 17:16:01 +0000 Subject: [NCSG-FC] ICANN64 Meeting plenary In-Reply-To: References: <451cb70a-6ca7-6e3d-3a3f-315d75eca556@mail.utoronto.ca> Message-ID: <92749187-1210-7b92-8556-33d3855c6326@mail.utoronto.ca> I will ask all the chairs (e.g. Rrs, Rys, BC, IPC, ISPC.) I am pretty confident that you will find they all have finance committees, as they charge substantial fees to join. However, these entities are independent of ICANN. The RALOS are a rather different kettle of fish, as ALAC has a lot more funding that we have and is set up quite differently than the GNSO stakeholder groups. Stephanie On 2019-02-22 12:03, Thato Mfikwe wrote: Hi Stephanie, There is limited information on different community Finance committees and how they work but I have asked AFRALO to share how they manage their finances, will share once I obtain a response and the role played by ICANN Finance in that respect. I think NCSG will be first to adopt FC operational procedures but am not really sure, thanks. Thato Mfikwe. On Fri, Feb 22, 2019 at 2:01 AM Stephanie Perrin > wrote: Have you inquired of other Stakeholder Groups, how they handle their finances? What role does ICANN play? I would suspect none. It is not their place. Stephanie On 2019-02-21 18:47, Remmy Nweke wrote: Thanks Thato It should have been very helpful If I was to be there to assist in some physically. However, there will be need for online participation. There is need also to have an ICANN staff preferably from Finance speak to some of the issues, especially in responsibility and expectations from an FC. Equally a few minutes remarks by NCSG chair will not be out of place as well as Cs chair. May be NCSG 3minutes, C chairs 2minutes each. They will still speak to issues as intervention arises. Good luck. Remmy ____ REMMY NWEKE, mNGE, Lead Strategist/Group Executive Editor, DigitalSENSE Africa Media [Multiple-award winning medium] (DigitalSENSE Business News; ITREALMS, NaijaAgroNet) Block F1, Shop 133 Moyosore Aboderin Plaza, Bolade Junction, Oshodi-Lagos M: 234-8033592762, 8023122558, 8051000475, T: @ITRealms Author: A Decade of ICT Reportage in Nigeria 2019 Nigeria DigitalSENSE Forum on IG4D & Nigeria IPv6 Roundtable JOIN us!! *Vice President, African Civil Society on the Information Society (ACSIS) NPOC FC Rep @ICANN Non-Commercial Stakeholders Group (NCSG) _________________________________________________________________ *Confidentiality Notice:* The information in this document and attachments are confidential and may also be privileged information. It is intended only for the use of the named recipient. Remmy Nweke does not accept legal responsibility for the contents of this e-mail. If you are not the intended recipient, please notify me immediately, then delete this document and do not disclose the contents of this document to any other person, nor make any copies. Violators may face court persecution. On Thu, Feb 21, 2019 at 4:48 PM Thato Mfikwe > wrote: Hi all, 1. This is final call for iput on the ICANN64 FC meeting agenda (90 minutes), please make your input so that I can circulate in the mailing list by Monday 25 February for community input. Proposed Agenda a. Introduction and background on the Finance Committee (5 min) Justification: This will ensure participants are on the same page and with the same understanding as the meeting progresses. b. Overview of the NCSG Charter and the Draft FC OP (10 min) Justification: Review of the Charter and OP contention areas (responsibilities, the accounting, auditing and providing oversight function, bank account and incopropration implications or use of constituency bank accounts (SPV), how the FC works with constituencies and financial reporting ) c. Q & A (10 min) d. Harmonising of the OP with the NCSG Charter based on the overview (10 min) Justification: Obtaining community input and building synergy between the NCSG Charter and FC OP e. Open floor and inputs (15 min) f. NCSG priorities, needs and wants - planning forward (5 min) Justification: Collection of ideas from members regarding their priorities, needs and wants g. Open floor (15 min) h.Fundraising and levelraging on ICANN finances - initiating a fundraising plan (5 min) Justification: Exploring different avenue for fundraising for NCSG i. Open floor and Q & A (10 min) j. Call for volunteers for different focus areas and closure - building internal capacity (5 min) 2. Should the be an oversight somewhere, please make recommendation. 3. Please also make input in terms of resource people who will be needed to ease proceedings of this meeting and can also provide answers. I still maintain that we need ICANN finance, so that we are able to discuss ways on how the FC can leverage on ICANN finances and improve on the ABR submission process. Thanks. Thato Mfikwe. _______________________________________________ NCSG-FC mailing list NCSG-FC at lists.ncsg.is https://lists.ncsg.is/mailman/listinfo/ncsg-fc _______________________________________________ NCSG-FC mailing list NCSG-FC at lists.ncsg.is https://lists.ncsg.is/mailman/listinfo/ncsg-fc _______________________________________________ NCSG-FC mailing list NCSG-FC at lists.ncsg.is https://lists.ncsg.is/mailman/listinfo/ncsg-fc _______________________________________________ NCSG-FC mailing list NCSG-FC at lists.ncsg.is https://lists.ncsg.is/mailman/listinfo/ncsg-fc -------------- next part -------------- An HTML attachment was scrubbed... URL: From thatomfikwe at gmail.com Sat Feb 23 00:26:39 2019 From: thatomfikwe at gmail.com (Thato Mfikwe) Date: Sat, 23 Feb 2019 00:26:39 +0200 Subject: [NCSG-FC] ICANN64 Meeting plenary In-Reply-To: References: <451cb70a-6ca7-6e3d-3a3f-315d75eca556@mail.utoronto.ca> Message-ID: Hi Rafik, In regard to ICANN finance, you will note that with declined ABRs in previuos FYs, there was room for improvement and further engagement of various ICANN teams like the communication, GSE and in order to obtain access to support requested as opposed to fund allocations themselves. For the FC, it would be benefitial to understand this process. It would laso be interesting to find out how budgets accomodate community activities and how communities can play a role in realising ICANN strategic objectives, or instance: - Strengthen the inclusivity and openness of ICANN?s multistakeholder model by improving and sustaining diverse representation and active, effective participation and collaboration with GSE on outreach efforts and in local and regional IGFs The main reason for inviting ICANN finance was centered around finding the best way to ensure that NCSG and constituencies are adequately supported, as stated in the NCSG charter, as this is never clear when ICANN budgets and plans are published. I am not expecting ICANN to manage our bank account but provide advice on how this can be best managed and remmber that the FC activities must adhere to ICANN bylaws, so if there are deviations, we need to be made aware of such or ensure adherence. Thato Mfikwe. On Fri, Feb 22, 2019 at 5:10 AM Rafik Dammak wrote: > Hi. > > ICANN Finance doesn't get involved on SG/C finance and refuse to manage > bank accounts (in particular for those collecting membership fees) on their > behalf for liability reasons. > > when ICANN give any in-kind or financial support, it already control the > whole process i.e. procurement, hiring external resources, travel > arrangement etc. In other cases like for membership system, it ask SG/C to > pay first then it reimburse. As organization, it mitigates risks and > doesn't let community to be involved on the process other making request > through ABRs etc. it is the same for PDP WGs ( I am aware of as I am > involved for EPDP) > > ICANN Finance team looks usually to discuss about ICANN budget and > operating plan not about internal finance of SG/C. > > Best, > > Rafik > > Le ven. 22 f?vr. 2019 ? 10:34, Remmy Nweke a ?crit : > >> Sorry Stephanie to come in here. >> Others may choose to ignore it but I think there is a role based on our >> NCSG charter guidelines especially on report back on how money or funds >> given to stakeholders group or received from all sources are expended. >> In financial management it's usually a precondition for another round of >> support which I think ICANN.org is not strict about otherwise they should >> be making the demands. >> May be because there are individual reports very often and I know Maryam >> team emphasis on this too as precondition. >> Regards >> Remmy >> >> On Fri, 22 Feb 2019, 1:01 a.m. Stephanie Perrin < >> stephanie.perrin at mail.utoronto.ca wrote: >> >>> Have you inquired of other Stakeholder Groups, how they handle their >>> finances? What role does ICANN play? >>> >>> I would suspect none. It is not their place. >>> >>> Stephanie >>> On 2019-02-21 18:47, Remmy Nweke wrote: >>> >>> Thanks Thato >>> It should have been very helpful If I was to be there to assist in some >>> physically. >>> >>> However, there will be need for online participation. >>> >>> There is need also to have an ICANN staff preferably from Finance speak >>> to some of the issues, especially in responsibility and expectations from >>> an FC. >>> >>> Equally a few minutes remarks by NCSG chair will not be out of place as >>> well as Cs chair. May be NCSG 3minutes, C chairs 2minutes each. They will >>> still speak to issues as intervention arises. >>> >>> Good luck. >>> Remmy >>> ____ >>> REMMY NWEKE, mNGE, >>> Lead Strategist/Group Executive Editor, >>> DigitalSENSE Africa Media [*Multiple-award winning medium*] >>> (DigitalSENSE Business News >>> ; ITREALMS >>> , NaijaAgroNet >>> ) >>> Block F1, Shop 133 Moyosore Aboderin Plaza, Bolade Junction, Oshodi-Lagos >>> M: 234-8033592762, 8023122558, 8051000475, T: @ITRealms >>> >>> Author: A Decade of ICT Reportage in Nigeria >>> >>> >>> *2019 Nigeria DigitalSENSE Forum on IG4D & Nigeria IPv6 Roundtable >>> * >>> JOIN us!! >>> >>> *Vice President, African Civil Society on the Information Society (ACSIS >>> ) >>> >>> *NPOC FC Rep @ICANN Non-Commercial Stakeholders Group (NCSG)* >>> >>> _________________________________________________________________ >>> *Confidentiality Notice:* The information in this document and >>> attachments are confidential and may also be privileged information. It is >>> intended only for the use of the named recipient. Remmy Nweke does not >>> accept legal responsibility for the contents of this e-mail. If you are not >>> the intended recipient, please notify me immediately, then delete this >>> document and do not disclose the contents of this document to any other >>> person, nor make any copies. Violators may face court persecution. >>> >>> >>> >>> On Thu, Feb 21, 2019 at 4:48 PM Thato Mfikwe >>> wrote: >>> >>>> Hi all, >>>> >>>> *1. This is final call for iput on the ICANN64 FC meeting agenda (90 >>>> minutes), please make your input so that I can circulate in the mailing >>>> list by Monday 25 February for community input.* >>>> >>>> Proposed Agenda >>>> a. Introduction and background on the Finance Committee (5 min) >>>> Justification: This will ensure participants are on the same page and >>>> with the same understanding as the meeting progresses. >>>> >>>> b. Overview of the NCSG Charter and the Draft FC OP (10 min) >>>> Justification: Review of the Charter and OP contention areas >>>> (responsibilities, the accounting, auditing and providing oversight >>>> function, bank account and incopropration implications or use of >>>> constituency bank accounts (SPV), how the FC works with constituencies and >>>> financial reporting ) >>>> >>>> c. Q & A (10 min) >>>> >>>> d. Harmonising of the OP with the NCSG Charter based on the overview >>>> (10 min) >>>> Justification: Obtaining community input and building synergy between >>>> the NCSG Charter and FC OP >>>> >>>> e. Open floor and inputs (15 min) >>>> >>>> f. NCSG priorities, needs and wants - planning forward (5 min) >>>> Justification: Collection of ideas from members regarding their >>>> priorities, needs and wants >>>> >>>> g. Open floor (15 min) >>>> >>>> h.Fundraising and levelraging on ICANN finances - initiating a >>>> fundraising plan (5 min) >>>> Justification: Exploring different avenue for fundraising for NCSG >>>> >>>> i. Open floor and Q & A (10 min) >>>> >>>> j. Call for volunteers for different focus areas and closure - building >>>> internal capacity (5 min) >>>> >>>> >>>> *2. Should the be an oversight somewhere, please make recommendation. * >>>> >>>> *3. Please also make input in terms of resource people who will be >>>> needed to ease proceedings of this meeting and can also provide answers. I >>>> still maintain that we need ICANN finance, so that we are able to discuss >>>> ways on how the FC can leverage on ICANN finances and improve on the ABR >>>> submission process.* >>>> >>>> Thanks. >>>> >>>> Thato Mfikwe. >>>> >>>> _______________________________________________ >>>> NCSG-FC mailing list >>>> NCSG-FC at lists.ncsg.is >>>> https://lists.ncsg.is/mailman/listinfo/ncsg-fc >>>> >>> >>> _______________________________________________ >>> NCSG-FC mailing listNCSG-FC at lists.ncsg.ishttps://lists.ncsg.is/mailman/listinfo/ncsg-fc >>> >>> _______________________________________________ >>> NCSG-FC mailing list >>> NCSG-FC at lists.ncsg.is >>> https://lists.ncsg.is/mailman/listinfo/ncsg-fc >>> >> _______________________________________________ >> NCSG-FC mailing list >> NCSG-FC at lists.ncsg.is >> https://lists.ncsg.is/mailman/listinfo/ncsg-fc >> > _______________________________________________ > NCSG-FC mailing list > NCSG-FC at lists.ncsg.is > https://lists.ncsg.is/mailman/listinfo/ncsg-fc > -------------- next part -------------- An HTML attachment was scrubbed... URL: From rafik.dammak at gmail.com Sat Feb 23 00:45:47 2019 From: rafik.dammak at gmail.com (Rafik Dammak) Date: Sat, 23 Feb 2019 07:45:47 +0900 Subject: [NCSG-FC] ICANN64 Meeting plenary In-Reply-To: References: <451cb70a-6ca7-6e3d-3a3f-315d75eca556@mail.utoronto.ca> Message-ID: > I am not expecting ICANN to manage our bank account but provide advice on > how this can be best managed and remmber that the FC activities must adhere > to ICANN bylaws, so if there are deviations, we need to be made aware of > such or ensure adherence. > sorry that is not ICANN Finance team role or remit. ICANN Bylaws says nothing about SG/C finance or expectations. I think my point is clear, ICANN org and Finance team in particular has nothing to do with how NCSG manages its finance. Accountability is ensured by NCSG membership first. Best, Rafik > On Fri, Feb 22, 2019 at 5:10 AM Rafik Dammak > wrote: > >> Hi. >> >> ICANN Finance doesn't get involved on SG/C finance and refuse to manage >> bank accounts (in particular for those collecting membership fees) on their >> behalf for liability reasons. >> >> when ICANN give any in-kind or financial support, it already control the >> whole process i.e. procurement, hiring external resources, travel >> arrangement etc. In other cases like for membership system, it ask SG/C to >> pay first then it reimburse. As organization, it mitigates risks and >> doesn't let community to be involved on the process other making request >> through ABRs etc. it is the same for PDP WGs ( I am aware of as I am >> involved for EPDP) >> >> ICANN Finance team looks usually to discuss about ICANN budget and >> operating plan not about internal finance of SG/C. >> >> Best, >> >> Rafik >> >> Le ven. 22 f?vr. 2019 ? 10:34, Remmy Nweke a ?crit : >> >>> Sorry Stephanie to come in here. >>> Others may choose to ignore it but I think there is a role based on our >>> NCSG charter guidelines especially on report back on how money or funds >>> given to stakeholders group or received from all sources are expended. >>> In financial management it's usually a precondition for another round of >>> support which I think ICANN.org is not strict about otherwise they should >>> be making the demands. >>> May be because there are individual reports very often and I know Maryam >>> team emphasis on this too as precondition. >>> Regards >>> Remmy >>> >>> On Fri, 22 Feb 2019, 1:01 a.m. Stephanie Perrin < >>> stephanie.perrin at mail.utoronto.ca wrote: >>> >>>> Have you inquired of other Stakeholder Groups, how they handle their >>>> finances? What role does ICANN play? >>>> >>>> I would suspect none. It is not their place. >>>> >>>> Stephanie >>>> On 2019-02-21 18:47, Remmy Nweke wrote: >>>> >>>> Thanks Thato >>>> It should have been very helpful If I was to be there to assist in some >>>> physically. >>>> >>>> However, there will be need for online participation. >>>> >>>> There is need also to have an ICANN staff preferably from Finance speak >>>> to some of the issues, especially in responsibility and expectations from >>>> an FC. >>>> >>>> Equally a few minutes remarks by NCSG chair will not be out of place as >>>> well as Cs chair. May be NCSG 3minutes, C chairs 2minutes each. They will >>>> still speak to issues as intervention arises. >>>> >>>> Good luck. >>>> Remmy >>>> ____ >>>> REMMY NWEKE, mNGE, >>>> Lead Strategist/Group Executive Editor, >>>> DigitalSENSE Africa Media [*Multiple-award winning medium*] >>>> (DigitalSENSE Business News >>>> ; ITREALMS >>>> , NaijaAgroNet >>>> ) >>>> Block F1, Shop 133 Moyosore Aboderin Plaza, Bolade Junction, >>>> Oshodi-Lagos >>>> M: 234-8033592762, 8023122558, 8051000475, T: @ITRealms >>>> >>>> Author: A Decade of ICT Reportage in Nigeria >>>> >>>> >>>> *2019 Nigeria DigitalSENSE Forum on IG4D & Nigeria IPv6 Roundtable >>>> * >>>> JOIN us!! >>>> >>>> *Vice President, African Civil Society on the Information Society >>>> (ACSIS ) >>>> >>>> *NPOC FC Rep @ICANN Non-Commercial Stakeholders Group (NCSG)* >>>> >>>> _________________________________________________________________ >>>> *Confidentiality Notice:* The information in this document and >>>> attachments are confidential and may also be privileged information. It is >>>> intended only for the use of the named recipient. Remmy Nweke does not >>>> accept legal responsibility for the contents of this e-mail. If you are not >>>> the intended recipient, please notify me immediately, then delete this >>>> document and do not disclose the contents of this document to any other >>>> person, nor make any copies. Violators may face court persecution. >>>> >>>> >>>> >>>> On Thu, Feb 21, 2019 at 4:48 PM Thato Mfikwe >>>> wrote: >>>> >>>>> Hi all, >>>>> >>>>> *1. This is final call for iput on the ICANN64 FC meeting agenda (90 >>>>> minutes), please make your input so that I can circulate in the mailing >>>>> list by Monday 25 February for community input.* >>>>> >>>>> Proposed Agenda >>>>> a. Introduction and background on the Finance Committee (5 min) >>>>> Justification: This will ensure participants are on the same page and >>>>> with the same understanding as the meeting progresses. >>>>> >>>>> b. Overview of the NCSG Charter and the Draft FC OP (10 min) >>>>> Justification: Review of the Charter and OP contention areas >>>>> (responsibilities, the accounting, auditing and providing oversight >>>>> function, bank account and incopropration implications or use of >>>>> constituency bank accounts (SPV), how the FC works with constituencies and >>>>> financial reporting ) >>>>> >>>>> c. Q & A (10 min) >>>>> >>>>> d. Harmonising of the OP with the NCSG Charter based on the overview >>>>> (10 min) >>>>> Justification: Obtaining community input and building synergy between >>>>> the NCSG Charter and FC OP >>>>> >>>>> e. Open floor and inputs (15 min) >>>>> >>>>> f. NCSG priorities, needs and wants - planning forward (5 min) >>>>> Justification: Collection of ideas from members regarding their >>>>> priorities, needs and wants >>>>> >>>>> g. Open floor (15 min) >>>>> >>>>> h.Fundraising and levelraging on ICANN finances - initiating a >>>>> fundraising plan (5 min) >>>>> Justification: Exploring different avenue for fundraising for NCSG >>>>> >>>>> i. Open floor and Q & A (10 min) >>>>> >>>>> j. Call for volunteers for different focus areas and closure - >>>>> building internal capacity (5 min) >>>>> >>>>> >>>>> *2. Should the be an oversight somewhere, please make recommendation. * >>>>> >>>>> *3. Please also make input in terms of resource people who will be >>>>> needed to ease proceedings of this meeting and can also provide answers. I >>>>> still maintain that we need ICANN finance, so that we are able to discuss >>>>> ways on how the FC can leverage on ICANN finances and improve on the ABR >>>>> submission process.* >>>>> >>>>> Thanks. >>>>> >>>>> Thato Mfikwe. >>>>> >>>>> _______________________________________________ >>>>> NCSG-FC mailing list >>>>> NCSG-FC at lists.ncsg.is >>>>> https://lists.ncsg.is/mailman/listinfo/ncsg-fc >>>>> >>>> >>>> _______________________________________________ >>>> NCSG-FC mailing listNCSG-FC at lists.ncsg.ishttps://lists.ncsg.is/mailman/listinfo/ncsg-fc >>>> >>>> _______________________________________________ >>>> NCSG-FC mailing list >>>> NCSG-FC at lists.ncsg.is >>>> https://lists.ncsg.is/mailman/listinfo/ncsg-fc >>>> >>> _______________________________________________ >>> NCSG-FC mailing list >>> NCSG-FC at lists.ncsg.is >>> https://lists.ncsg.is/mailman/listinfo/ncsg-fc >>> >> _______________________________________________ >> NCSG-FC mailing list >> NCSG-FC at lists.ncsg.is >> https://lists.ncsg.is/mailman/listinfo/ncsg-fc >> > _______________________________________________ > NCSG-FC mailing list > NCSG-FC at lists.ncsg.is > https://lists.ncsg.is/mailman/listinfo/ncsg-fc > -------------- next part -------------- An HTML attachment was scrubbed... URL: From thatomfikwe at gmail.com Sat Feb 23 01:04:14 2019 From: thatomfikwe at gmail.com (Thato Mfikwe) Date: Sat, 23 Feb 2019 01:04:14 +0200 Subject: [NCSG-FC] URGENT: Adoption of FC Operational Procedures Message-ID: Hi Stephanie and all, Can you please kindly and urgently review the *2nd version of the FC Draft OP *, I would like to ask Stephanie to forward this draft, if agreed, to the NCSG EC for review and comment, on Monday or once adopted. The sooner we are able to get the EC input, the easier it will be to finalise and adopt this document. The objections and contention points that will emerge from this submission will form discussion points during the FC Kobe meeting. Please also note that this document tried to balance the inputs, suggestions and comments of the Finance committee with that of the community, should you deem necessary to make further comment, please do so ASAP. I wish that the adoption of the FC OP be finalised by end of April 2019 and obtain feedback from the EC by 4 March latest. I also understand your busy schedules and apologies for the needed pressure, thanks in advance. Thato Mfikwe. -------------- next part -------------- An HTML attachment was scrubbed... URL: From thatomfikwe at gmail.com Sat Feb 23 01:14:15 2019 From: thatomfikwe at gmail.com (Thato Mfikwe) Date: Sat, 23 Feb 2019 01:14:15 +0200 Subject: [NCSG-FC] ICANN64 Meeting plenary In-Reply-To: References: <451cb70a-6ca7-6e3d-3a3f-315d75eca556@mail.utoronto.ca> Message-ID: Does ICANN finance also have nothing to do with the other 3 reasons as listed? If so, what other role do you think ICANN finance can play to support communities besides ABRs and budgets? Thato Mfikwe. On Sat, Feb 23, 2019 at 12:46 AM Rafik Dammak wrote: > > >> I am not expecting ICANN to manage our bank account but provide advice on >> how this can be best managed and remmber that the FC activities must adhere >> to ICANN bylaws, so if there are deviations, we need to be made aware of >> such or ensure adherence. >> > > > sorry that is not ICANN Finance team role or remit. ICANN Bylaws says > nothing about SG/C finance or expectations. > > I think my point is clear, ICANN org and Finance team in particular has > nothing to do with how NCSG manages its finance. Accountability is ensured > by NCSG membership first. > > Best, > > Rafik > > >> On Fri, Feb 22, 2019 at 5:10 AM Rafik Dammak >> wrote: >> >>> Hi. >>> >>> ICANN Finance doesn't get involved on SG/C finance and refuse to manage >>> bank accounts (in particular for those collecting membership fees) on their >>> behalf for liability reasons. >>> >>> when ICANN give any in-kind or financial support, it already control the >>> whole process i.e. procurement, hiring external resources, travel >>> arrangement etc. In other cases like for membership system, it ask SG/C to >>> pay first then it reimburse. As organization, it mitigates risks and >>> doesn't let community to be involved on the process other making request >>> through ABRs etc. it is the same for PDP WGs ( I am aware of as I am >>> involved for EPDP) >>> >>> ICANN Finance team looks usually to discuss about ICANN budget and >>> operating plan not about internal finance of SG/C. >>> >>> Best, >>> >>> Rafik >>> >>> Le ven. 22 f?vr. 2019 ? 10:34, Remmy Nweke a ?crit : >>> >>>> Sorry Stephanie to come in here. >>>> Others may choose to ignore it but I think there is a role based on our >>>> NCSG charter guidelines especially on report back on how money or funds >>>> given to stakeholders group or received from all sources are expended. >>>> In financial management it's usually a precondition for another round >>>> of support which I think ICANN.org is not strict about otherwise they >>>> should be making the demands. >>>> May be because there are individual reports very often and I know >>>> Maryam team emphasis on this too as precondition. >>>> Regards >>>> Remmy >>>> >>>> On Fri, 22 Feb 2019, 1:01 a.m. Stephanie Perrin < >>>> stephanie.perrin at mail.utoronto.ca wrote: >>>> >>>>> Have you inquired of other Stakeholder Groups, how they handle their >>>>> finances? What role does ICANN play? >>>>> >>>>> I would suspect none. It is not their place. >>>>> >>>>> Stephanie >>>>> On 2019-02-21 18:47, Remmy Nweke wrote: >>>>> >>>>> Thanks Thato >>>>> It should have been very helpful If I was to be there to assist in >>>>> some physically. >>>>> >>>>> However, there will be need for online participation. >>>>> >>>>> There is need also to have an ICANN staff preferably from Finance >>>>> speak to some of the issues, especially in responsibility and expectations >>>>> from an FC. >>>>> >>>>> Equally a few minutes remarks by NCSG chair will not be out of place >>>>> as well as Cs chair. May be NCSG 3minutes, C chairs 2minutes each. They >>>>> will still speak to issues as intervention arises. >>>>> >>>>> Good luck. >>>>> Remmy >>>>> ____ >>>>> REMMY NWEKE, mNGE, >>>>> Lead Strategist/Group Executive Editor, >>>>> DigitalSENSE Africa Media [*Multiple-award winning medium*] >>>>> (DigitalSENSE Business News >>>>> ; ITREALMS >>>>> , NaijaAgroNet >>>>> ) >>>>> Block F1, Shop 133 Moyosore Aboderin Plaza, Bolade Junction, >>>>> Oshodi-Lagos >>>>> M: 234-8033592762, 8023122558, 8051000475, T: @ITRealms >>>>> >>>>> Author: A Decade of ICT Reportage in Nigeria >>>>> >>>>> >>>>> *2019 Nigeria DigitalSENSE Forum on IG4D & Nigeria IPv6 Roundtable >>>>> * >>>>> JOIN us!! >>>>> >>>>> *Vice President, African Civil Society on the Information Society >>>>> (ACSIS ) >>>>> >>>>> *NPOC FC Rep @ICANN Non-Commercial Stakeholders Group (NCSG)* >>>>> >>>>> _________________________________________________________________ >>>>> *Confidentiality Notice:* The information in this document and >>>>> attachments are confidential and may also be privileged information. It is >>>>> intended only for the use of the named recipient. Remmy Nweke does not >>>>> accept legal responsibility for the contents of this e-mail. If you are not >>>>> the intended recipient, please notify me immediately, then delete this >>>>> document and do not disclose the contents of this document to any other >>>>> person, nor make any copies. Violators may face court persecution. >>>>> >>>>> >>>>> >>>>> On Thu, Feb 21, 2019 at 4:48 PM Thato Mfikwe >>>>> wrote: >>>>> >>>>>> Hi all, >>>>>> >>>>>> *1. This is final call for iput on the ICANN64 FC meeting agenda (90 >>>>>> minutes), please make your input so that I can circulate in the mailing >>>>>> list by Monday 25 February for community input.* >>>>>> >>>>>> Proposed Agenda >>>>>> a. Introduction and background on the Finance Committee (5 min) >>>>>> Justification: This will ensure participants are on the same page and >>>>>> with the same understanding as the meeting progresses. >>>>>> >>>>>> b. Overview of the NCSG Charter and the Draft FC OP (10 min) >>>>>> Justification: Review of the Charter and OP contention areas >>>>>> (responsibilities, the accounting, auditing and providing oversight >>>>>> function, bank account and incopropration implications or use of >>>>>> constituency bank accounts (SPV), how the FC works with constituencies and >>>>>> financial reporting ) >>>>>> >>>>>> c. Q & A (10 min) >>>>>> >>>>>> d. Harmonising of the OP with the NCSG Charter based on the overview >>>>>> (10 min) >>>>>> Justification: Obtaining community input and building synergy between >>>>>> the NCSG Charter and FC OP >>>>>> >>>>>> e. Open floor and inputs (15 min) >>>>>> >>>>>> f. NCSG priorities, needs and wants - planning forward (5 min) >>>>>> Justification: Collection of ideas from members regarding their >>>>>> priorities, needs and wants >>>>>> >>>>>> g. Open floor (15 min) >>>>>> >>>>>> h.Fundraising and levelraging on ICANN finances - initiating a >>>>>> fundraising plan (5 min) >>>>>> Justification: Exploring different avenue for fundraising for NCSG >>>>>> >>>>>> i. Open floor and Q & A (10 min) >>>>>> >>>>>> j. Call for volunteers for different focus areas and closure - >>>>>> building internal capacity (5 min) >>>>>> >>>>>> >>>>>> *2. Should the be an oversight somewhere, please make recommendation. >>>>>> * >>>>>> >>>>>> *3. Please also make input in terms of resource people who will be >>>>>> needed to ease proceedings of this meeting and can also provide answers. I >>>>>> still maintain that we need ICANN finance, so that we are able to discuss >>>>>> ways on how the FC can leverage on ICANN finances and improve on the ABR >>>>>> submission process.* >>>>>> >>>>>> Thanks. >>>>>> >>>>>> Thato Mfikwe. >>>>>> >>>>>> _______________________________________________ >>>>>> NCSG-FC mailing list >>>>>> NCSG-FC at lists.ncsg.is >>>>>> https://lists.ncsg.is/mailman/listinfo/ncsg-fc >>>>>> >>>>> >>>>> _______________________________________________ >>>>> NCSG-FC mailing listNCSG-FC at lists.ncsg.ishttps://lists.ncsg.is/mailman/listinfo/ncsg-fc >>>>> >>>>> _______________________________________________ >>>>> NCSG-FC mailing list >>>>> NCSG-FC at lists.ncsg.is >>>>> https://lists.ncsg.is/mailman/listinfo/ncsg-fc >>>>> >>>> _______________________________________________ >>>> NCSG-FC mailing list >>>> NCSG-FC at lists.ncsg.is >>>> https://lists.ncsg.is/mailman/listinfo/ncsg-fc >>>> >>> _______________________________________________ >>> NCSG-FC mailing list >>> NCSG-FC at lists.ncsg.is >>> https://lists.ncsg.is/mailman/listinfo/ncsg-fc >>> >> _______________________________________________ >> NCSG-FC mailing list >> NCSG-FC at lists.ncsg.is >> https://lists.ncsg.is/mailman/listinfo/ncsg-fc >> > _______________________________________________ > NCSG-FC mailing list > NCSG-FC at lists.ncsg.is > https://lists.ncsg.is/mailman/listinfo/ncsg-fc > -------------- next part -------------- An HTML attachment was scrubbed... URL: From rafik.dammak at gmail.com Sat Feb 23 01:27:57 2019 From: rafik.dammak at gmail.com (Rafik Dammak) Date: Sat, 23 Feb 2019 08:27:57 +0900 Subject: [NCSG-FC] ICANN64 Meeting plenary In-Reply-To: References: <451cb70a-6ca7-6e3d-3a3f-315d75eca556@mail.utoronto.ca> Message-ID: Hi, ICANN Finance team primary role and goal is ICANN own finance through budget, operating plan, reserve etc. ABRs are as its name says additional budget requests to what already in the budget for supporting community work. no, I don't see any other role for finance team. I can understand engagement related to ICANN budget operating plan for FY20 as that impact gTLD PDPs (which our main focus and that is why we are involved) and ABRs but not about NCSG finance. Best, Rafik Le sam. 23 f?vr. 2019 ? 08:14, Thato Mfikwe a ?crit : > Does ICANN finance also have nothing to do with the other 3 reasons as > listed? If so, what other role do you think ICANN finance can play to > support communities besides ABRs and budgets? > > Thato Mfikwe. > > On Sat, Feb 23, 2019 at 12:46 AM Rafik Dammak > wrote: > >> >> >>> I am not expecting ICANN to manage our bank account but provide advice >>> on how this can be best managed and remmber that the FC activities must >>> adhere to ICANN bylaws, so if there are deviations, we need to be made >>> aware of such or ensure adherence. >>> >> >> >> sorry that is not ICANN Finance team role or remit. ICANN Bylaws says >> nothing about SG/C finance or expectations. >> >> I think my point is clear, ICANN org and Finance team in particular has >> nothing to do with how NCSG manages its finance. Accountability is ensured >> by NCSG membership first. >> >> Best, >> >> Rafik >> >> >>> On Fri, Feb 22, 2019 at 5:10 AM Rafik Dammak >>> wrote: >>> >>>> Hi. >>>> >>>> ICANN Finance doesn't get involved on SG/C finance and refuse to manage >>>> bank accounts (in particular for those collecting membership fees) on their >>>> behalf for liability reasons. >>>> >>>> when ICANN give any in-kind or financial support, it already control >>>> the whole process i.e. procurement, hiring external resources, travel >>>> arrangement etc. In other cases like for membership system, it ask SG/C to >>>> pay first then it reimburse. As organization, it mitigates risks and >>>> doesn't let community to be involved on the process other making request >>>> through ABRs etc. it is the same for PDP WGs ( I am aware of as I am >>>> involved for EPDP) >>>> >>>> ICANN Finance team looks usually to discuss about ICANN budget and >>>> operating plan not about internal finance of SG/C. >>>> >>>> Best, >>>> >>>> Rafik >>>> >>>> Le ven. 22 f?vr. 2019 ? 10:34, Remmy Nweke a ?crit : >>>> >>>>> Sorry Stephanie to come in here. >>>>> Others may choose to ignore it but I think there is a role based on >>>>> our NCSG charter guidelines especially on report back on how money or funds >>>>> given to stakeholders group or received from all sources are expended. >>>>> In financial management it's usually a precondition for another round >>>>> of support which I think ICANN.org is not strict about otherwise they >>>>> should be making the demands. >>>>> May be because there are individual reports very often and I know >>>>> Maryam team emphasis on this too as precondition. >>>>> Regards >>>>> Remmy >>>>> >>>>> On Fri, 22 Feb 2019, 1:01 a.m. Stephanie Perrin < >>>>> stephanie.perrin at mail.utoronto.ca wrote: >>>>> >>>>>> Have you inquired of other Stakeholder Groups, how they handle their >>>>>> finances? What role does ICANN play? >>>>>> >>>>>> I would suspect none. It is not their place. >>>>>> >>>>>> Stephanie >>>>>> On 2019-02-21 18:47, Remmy Nweke wrote: >>>>>> >>>>>> Thanks Thato >>>>>> It should have been very helpful If I was to be there to assist in >>>>>> some physically. >>>>>> >>>>>> However, there will be need for online participation. >>>>>> >>>>>> There is need also to have an ICANN staff preferably from Finance >>>>>> speak to some of the issues, especially in responsibility and expectations >>>>>> from an FC. >>>>>> >>>>>> Equally a few minutes remarks by NCSG chair will not be out of place >>>>>> as well as Cs chair. May be NCSG 3minutes, C chairs 2minutes each. They >>>>>> will still speak to issues as intervention arises. >>>>>> >>>>>> Good luck. >>>>>> Remmy >>>>>> ____ >>>>>> REMMY NWEKE, mNGE, >>>>>> Lead Strategist/Group Executive Editor, >>>>>> DigitalSENSE Africa Media [*Multiple-award winning medium*] >>>>>> (DigitalSENSE Business News >>>>>> ; ITREALMS >>>>>> , NaijaAgroNet >>>>>> ) >>>>>> Block F1, Shop 133 Moyosore Aboderin Plaza, Bolade Junction, >>>>>> Oshodi-Lagos >>>>>> M: 234-8033592762, 8023122558, 8051000475, T: @ITRealms >>>>>> >>>>>> Author: A Decade of ICT Reportage in Nigeria >>>>>> >>>>>> >>>>>> *2019 Nigeria DigitalSENSE Forum on IG4D & Nigeria IPv6 Roundtable >>>>>> * >>>>>> JOIN us!! >>>>>> >>>>>> *Vice President, African Civil Society on the Information Society >>>>>> (ACSIS ) >>>>>> >>>>>> *NPOC FC Rep @ICANN Non-Commercial Stakeholders Group (NCSG)* >>>>>> >>>>>> _________________________________________________________________ >>>>>> *Confidentiality Notice:* The information in this document and >>>>>> attachments are confidential and may also be privileged information. It is >>>>>> intended only for the use of the named recipient. Remmy Nweke does not >>>>>> accept legal responsibility for the contents of this e-mail. If you are not >>>>>> the intended recipient, please notify me immediately, then delete this >>>>>> document and do not disclose the contents of this document to any other >>>>>> person, nor make any copies. Violators may face court persecution. >>>>>> >>>>>> >>>>>> >>>>>> On Thu, Feb 21, 2019 at 4:48 PM Thato Mfikwe >>>>>> wrote: >>>>>> >>>>>>> Hi all, >>>>>>> >>>>>>> *1. This is final call for iput on the ICANN64 FC meeting agenda (90 >>>>>>> minutes), please make your input so that I can circulate in the mailing >>>>>>> list by Monday 25 February for community input.* >>>>>>> >>>>>>> Proposed Agenda >>>>>>> a. Introduction and background on the Finance Committee (5 min) >>>>>>> Justification: This will ensure participants are on the same page >>>>>>> and with the same understanding as the meeting progresses. >>>>>>> >>>>>>> b. Overview of the NCSG Charter and the Draft FC OP (10 min) >>>>>>> Justification: Review of the Charter and OP contention areas >>>>>>> (responsibilities, the accounting, auditing and providing oversight >>>>>>> function, bank account and incopropration implications or use of >>>>>>> constituency bank accounts (SPV), how the FC works with constituencies and >>>>>>> financial reporting ) >>>>>>> >>>>>>> c. Q & A (10 min) >>>>>>> >>>>>>> d. Harmonising of the OP with the NCSG Charter based on the overview >>>>>>> (10 min) >>>>>>> Justification: Obtaining community input and building synergy >>>>>>> between the NCSG Charter and FC OP >>>>>>> >>>>>>> e. Open floor and inputs (15 min) >>>>>>> >>>>>>> f. NCSG priorities, needs and wants - planning forward (5 min) >>>>>>> Justification: Collection of ideas from members regarding their >>>>>>> priorities, needs and wants >>>>>>> >>>>>>> g. Open floor (15 min) >>>>>>> >>>>>>> h.Fundraising and levelraging on ICANN finances - initiating a >>>>>>> fundraising plan (5 min) >>>>>>> Justification: Exploring different avenue for fundraising for NCSG >>>>>>> >>>>>>> i. Open floor and Q & A (10 min) >>>>>>> >>>>>>> j. Call for volunteers for different focus areas and closure - >>>>>>> building internal capacity (5 min) >>>>>>> >>>>>>> >>>>>>> *2. Should the be an oversight somewhere, please make >>>>>>> recommendation. * >>>>>>> >>>>>>> *3. Please also make input in terms of resource people who will be >>>>>>> needed to ease proceedings of this meeting and can also provide answers. I >>>>>>> still maintain that we need ICANN finance, so that we are able to discuss >>>>>>> ways on how the FC can leverage on ICANN finances and improve on the ABR >>>>>>> submission process.* >>>>>>> >>>>>>> Thanks. >>>>>>> >>>>>>> Thato Mfikwe. >>>>>>> >>>>>>> _______________________________________________ >>>>>>> NCSG-FC mailing list >>>>>>> NCSG-FC at lists.ncsg.is >>>>>>> https://lists.ncsg.is/mailman/listinfo/ncsg-fc >>>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> NCSG-FC mailing listNCSG-FC at lists.ncsg.ishttps://lists.ncsg.is/mailman/listinfo/ncsg-fc >>>>>> >>>>>> _______________________________________________ >>>>>> NCSG-FC mailing list >>>>>> NCSG-FC at lists.ncsg.is >>>>>> https://lists.ncsg.is/mailman/listinfo/ncsg-fc >>>>>> >>>>> _______________________________________________ >>>>> NCSG-FC mailing list >>>>> NCSG-FC at lists.ncsg.is >>>>> https://lists.ncsg.is/mailman/listinfo/ncsg-fc >>>>> >>>> _______________________________________________ >>>> NCSG-FC mailing list >>>> NCSG-FC at lists.ncsg.is >>>> https://lists.ncsg.is/mailman/listinfo/ncsg-fc >>>> >>> _______________________________________________ >>> NCSG-FC mailing list >>> NCSG-FC at lists.ncsg.is >>> https://lists.ncsg.is/mailman/listinfo/ncsg-fc >>> >> _______________________________________________ >> NCSG-FC mailing list >> NCSG-FC at lists.ncsg.is >> https://lists.ncsg.is/mailman/listinfo/ncsg-fc >> > _______________________________________________ > NCSG-FC mailing list > NCSG-FC at lists.ncsg.is > https://lists.ncsg.is/mailman/listinfo/ncsg-fc > -------------- next part -------------- An HTML attachment was scrubbed... URL: From stephanie.perrin at mail.utoronto.ca Sat Feb 23 03:06:51 2019 From: stephanie.perrin at mail.utoronto.ca (Stephanie Perrin) Date: Sat, 23 Feb 2019 01:06:51 +0000 Subject: [NCSG-FC] URGENT: Adoption of FC Operational Procedures In-Reply-To: References: Message-ID: <1c5f7bd4-6c4e-8c3e-bb6e-f92be4bd3506@mail.utoronto.ca> I am sorry, I cannot do that at the moment, there are too many urgent priorities prior to Kobe. We have to set our meeting agendas and Board questions. Everyone is flat out at this point. Would you like ten minutes on the NCSG meeting agenda to discuss progress of the FC? I think that would be appropriate. You could also ask for comments from the PC, by sending the proposed procedures there. cheers Stephanie On 2019-02-22 18:04, Thato Mfikwe wrote: Hi Stephanie and all, Can you please kindly and urgently review the 2nd version of the FC Draft OP, I would like to ask Stephanie to forward this draft, if agreed, to the NCSG EC for review and comment, on Monday or once adopted. The sooner we are able to get the EC input, the easier it will be to finalise and adopt this document. The objections and contention points that will emerge from this submission will form discussion points during the FC Kobe meeting. Please also note that this document tried to balance the inputs, suggestions and comments of the Finance committee with that of the community, should you deem necessary to make further comment, please do so ASAP. I wish that the adoption of the FC OP be finalised by end of April 2019 and obtain feedback from the EC by 4 March latest. I also understand your busy schedules and apologies for the needed pressure, thanks in advance. Thato Mfikwe. -------------- next part -------------- An HTML attachment was scrubbed... URL: From stephanie.perrin at mail.utoronto.ca Sat Feb 23 20:32:07 2019 From: stephanie.perrin at mail.utoronto.ca (Stephanie Perrin) Date: Sat, 23 Feb 2019 18:32:07 +0000 Subject: [NCSG-FC] URGENT: Adoption of FC Operational Procedures In-Reply-To: References: Message-ID: Although I did say I cannot review them over the weekend Thato, I have indeed looked at the operating procedures. I think they need a lot of work. They are not ready for the NCSG EC. Here is a very short list of my feedback; as I said, I cannot really go into detail until after Kobe but I am putting half an hour on the agenda of the NCSG meeting for a discussion of our goals for the FC. * There has not been an active FC since the Charter was developed. We should therefore revisit the Charter to see if if still matches reality, after 9 years. We agree, for instance, that the membership is too small. * The Op procedures lack a logical structure. They should refer to the Charter, not quote it. There is repetition of goals (for pages). If we need definitions, they need to be in the appendix. Every one of them needs to be checked. * Sections currently have sub categories that do not fit within the section title. * We need crystal clarity about whose money we are monitoring....ICANN is responsible for accountability re its travel funding (e.g. for councillors, executives, etc). Rafik has pointed this out recently on the list, but it is an extremely important distinction. * We need a discussion on fundraising and membership fees....prior to drafting operating procedures. * We need a discussion on creating an entity for NCSG before a fundraising strategy is developed. * there are details in there about amounts of funding that require approval....but how will that approval be achieved? how did you arrive at those amounts? * What are the policy considerations behind funding decisions, and how will those decisions be made? If, for instance, the GNSO council members decided they needed to bring a subject matter expert to a given meeting to speak on a topic, could the FC veto that decision? the parameters of the authority of the FC have been neither discussed in plenary, nor described in this document, and this is important. I think this is enough for now. Much work still needs to be done on this document in my view, and on the very nature of the FC and its responsibilities. Fortunately, we have no money at the moment so there is no urgency to this. We have the time to do this correctly, let us do so. Stephanie Hi Stephanie and all, Can you please kindly and urgently review the 2nd version of the FC Draft OP, I would like to ask Stephanie to forward this draft, if agreed, to the NCSG EC for review and comment, on Monday or once adopted. The sooner we are able to get the EC input, the easier it will be to finalise and adopt this document. The objections and contention points that will emerge from this submission will form discussion points during the FC Kobe meeting. Please also note that this document tried to balance the inputs, suggestions and comments of the Finance committee with that of the community, should you deem necessary to make further comment, please do so ASAP. I wish that the adoption of the FC OP be finalised by end of April 2019 and obtain feedback from the EC by 4 March latest. I also understand your busy schedules and apologies for the needed pressure, thanks in advance. Thato Mfikwe. -------------- next part -------------- An HTML attachment was scrubbed... URL: From rbeauregardlacroix at gmail.com Sat Feb 23 21:20:03 2019 From: rbeauregardlacroix at gmail.com (=?UTF-8?Q?Rapha=C3=ABl_Beauregard=2DLacroix?=) Date: Sat, 23 Feb 2019 14:20:03 -0500 Subject: [NCSG-FC] URGENT: Adoption of FC Operational Procedures In-Reply-To: References: Message-ID: All, I also support Stephanie in that. It is good you have drafted those Thato as they provide a starting point *but* there are more fundamental issues that need to be addressed before we get to "fine tuning" operational procedures of the FC. I will not be in Kobe but I look forward to the results of these discussion points that Stephanie brings up here. Have a nice weekend, On Sat, Feb 23, 2019 at 1:32 PM Stephanie Perrin < stephanie.perrin at mail.utoronto.ca> wrote: > Although I did say I cannot review them over the weekend Thato, I have > indeed looked at the operating procedures. I think they need a lot of > work. They are not ready for the NCSG EC. Here is a very short list of my > feedback; as I said, I cannot really go into detail until after Kobe but I > am putting half an hour on the agenda of the NCSG meeting for a discussion > of our goals for the FC. > > - There has not been an active FC since the Charter was developed. We > should therefore revisit the Charter to see if if still matches reality, > after 9 years. We agree, for instance, that the membership is too small. > - The Op procedures lack a logical structure. They should refer to > the Charter, not quote it. There is repetition of goals (for pages). If > we need definitions, they need to be in the appendix. Every one of them > needs to be checked. > - Sections currently have sub categories that do not fit within the > section title. > - We need crystal clarity about whose money we are monitoring....ICANN > is responsible for accountability re its travel funding (e.g. for > councillors, executives, etc). Rafik has pointed this out recently on the > list, but it is an extremely important distinction. > - We need a discussion on fundraising and membership fees....prior to > drafting operating procedures. > - We need a discussion on creating an entity for NCSG before a > fundraising strategy is developed. > - there are details in there about amounts of funding that require > approval....but how will that approval be achieved? how did you arrive at > those amounts? > - What are the policy considerations behind funding decisions, and how > will those decisions be made? If, for instance, the GNSO council members > decided they needed to bring a subject matter expert to a given meeting to > speak on a topic, could the FC veto that decision? the parameters of the > authority of the FC have been neither discussed in plenary, nor described > in this document, and this is important. > > I think this is enough for now. Much work still needs to be done on this > document in my view, and on the very nature of the FC and its > responsibilities. Fortunately, we have no money at the moment so there is > no urgency to this. We have the time to do this correctly, let us do so. > > Stephanie > > Hi Stephanie and all, > > Can you please kindly and urgently review the *2nd version of the FC > Draft OP > *, > I would like to ask Stephanie to forward this draft, if agreed, to the NCSG > EC for review and comment, on Monday or once adopted. The sooner we are > able to get the EC input, the easier it will be to finalise and adopt this > document. > > The objections and contention points that will emerge from this submission > will form discussion points during the FC Kobe meeting. > > Please also note that this document tried to balance the inputs, > suggestions and comments of the Finance committee with that of the > community, should you deem necessary to make further comment, please do so > ASAP. I wish that the adoption of the FC OP be finalised by end of April > 2019 and obtain feedback from the EC by 4 March latest. I also understand > your busy schedules and apologies for the needed pressure, thanks in > advance. > > Thato Mfikwe. > > _______________________________________________ > NCSG-FC mailing list > NCSG-FC at lists.ncsg.is > https://lists.ncsg.is/mailman/listinfo/ncsg-fc > -------------- next part -------------- An HTML attachment was scrubbed... URL: From rbeauregardlacroix at gmail.com Tue Feb 26 23:02:20 2019 From: rbeauregardlacroix at gmail.com (=?UTF-8?Q?Rapha=C3=ABl_Beauregard=2DLacroix?=) Date: Tue, 26 Feb 2019 16:02:20 -0500 Subject: [NCSG-FC] Today's meeting with Wapix Message-ID: Dear all, Just had a call with Wapix regarding outstanding issues with our members database, with Josh who is project manager and Jordan whom he is currently onboarding; I presume she will take over once the currently outstanding issues are dealt with. The service provided by Wapix has been uneven to say the least, and we've had quite a few technical problems with CIVI (which is the CRM we use; think of it like Wordpress) and with that bane of a front end we use at the EC to evaluate and approve new members. I understand that there have been problems for a while, much before I was even around ;) Given these recurrent problems, it was thought we could switch over to CIVIcase, which is a specific implementation of CIVI which would offer most of the functionalities we need in a more streamlined way. The downside of that, is that it would certainly require *more *development blocks than what we have paid for now, meaning more money out of our pockets. Hence what Josh suggested is that we deal with outstanding issues in a more individual manner, using the development time already accrued. There's a handful of such issues, which range from display problems in the front to the upgrade to a newer version of CIVI. As for communications generally, we'll be dealing directly with him for what's currently outstanding and once this is done I understand he might pass the puck to Jordan. Hence Tapani: you can CC me when you contact Wapix, and feel free to forward me anything you get regarding CIVI (and Farzaneh, if she wants to, although I doubt it by now;)) Updating CIVI to the newer version is indeed part of the "outstanding" issues. So EC people, let me know what you think of the plan. TLDR: either we go for a more integral rehaul with the near-certainty of additional costs (and high uncertainty in terms of the actual amount of those costs,) or we opt for a more modest option of "just" dealing with whatever is outstanding for now, for which the plan is to use development time we currently have "in bank" with them (that is, time which has already been paid for) As for others, this is more a FYI than anything else! Depending on our decision, I will then be in touch with Josh for implementation and I will report back as things move forward. Have a nice day, Raphael -------------- next part -------------- An HTML attachment was scrubbed... URL: