<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;
mso-ligatures:none;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link=blue vlink=purple style='word-wrap:break-word'><div class=WordSection1><p class=MsoNormal>Thanks Olga.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Regarding the invoice, unless our financial officer needs something else, then it looks good to me as an invoice.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>One question comes to mind…what is Dusan’s responsibilities at this point? He has completed the redesign and cleaned up the operational components of the site, and it is now ready to port to its new home. I presume we need for him to be involved with that step? Also, has he completed any documentation regarding the technical components of the site that will be handed over to Tapani?<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Officially, perhaps we can say that we approve payment once the site is ported and any necessary documentation handed over (i.e., Tapani is satisfied that he has what he needs. In practice, I hope that Dusan can commit to answering basic questions about the site should any issue arise. <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>From what I saw on the e-mail list, we have consensus from the regional reps and the NCUC chair to port the web site as discussed yesterday. The only missing piece may be the financial arrangements for the hosting, which I believe Benjamin will discuss and clarify with Milton once we have some figures from Tapani and clarification regarding the reimbursement of hosting costs from ICANN org. <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Regarding the content of the site, it looked very good to me, although updates will shortly be necessary.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>One question, though, is that I see images of people on the site. Since this is a public site, does anyone know if we need to have consent from the individuals in the images?<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I agree with Benjamin that we should retain the existing site as a backup, but I do not see any reason to delay getting the new site up and running. I would like to suggest that we use our next EC meeting to agree on the steps to maintain the pages.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Ken<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b>From:</b> Olga Kyryliuk <olga_kyryliuk@ukr.net> <br><b>Sent:</b> Wednesday, August 2, 2023 9:16 AM<br><b>To:</b> Benjamin Akinmoyeje <benakin@gmail.com><br><b>Cc:</b> Ken Herman <ken@kherman.com>; Benjamin Akinmoyeje <benakin@gmail.com>; Amin Hacha <aminhacha@gmail.com>; Andrea Glandon <andrea.glandon@icann.org>; Exec. Comm <ncuc-ec@lists.ncuc.org>; Tapani Tarvainen <ncsg@tapani.tarvainen.info>; David Morar <davidcristianmorar@gmail.com><br><b>Subject:</b> Re[2]: [NCUC-EC] E-Team Engagement<o:p></o:p></p></div></div><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal>I also agree that we do not need to add more hosting options but better proceed with what we’ve already agreed about. There is no significant difference in hosting. We just prolong acting on reached decision by putting new ideas on the table.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Invoice was sent that same day when we had a call to the EC mailing list.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Best,<o:p></o:p></p></div><div><p class=MsoNormal>Olga<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal><i><span style='font-size:10.5pt'>2 серпня 2023 р. о 11:25:23, від "Benjamin Akinmoyeje" <<a href="mailto:benakin@gmail.com">benakin@gmail.com</a>>: </span></i><o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in'><p class=MsoNormal>> <o:p></o:p></p><div><p class=MsoNormal>Dear Tapani, Ken, Amin and all,<o:p></o:p></p><div><p class=MsoNormal>Thank you for your enormous contributions to moving this agenda forward.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>I agree that we acknowledge Amin's request and we help include their contributions.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>NCUC has a handful of logistical updates to do however in the interim can we align to the technical issues? We have identified all we need to get the website online technically....it will be great to go with that.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>My concern is to ensure we do not lose any content and that we keep the trail of everything we do.<o:p></o:p></p></div><div><p class=MsoNormal>I will suggest we keep a backup of existing content and if anything goes wrong we can revert to the previous content.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Do we have the invoice from Olga now?<o:p></o:p></p></div><div><p class=MsoNormal>Are OK with documentation to support future management of the NCUC website?<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>I believe everyone is clear with the next steps and support from Tapani.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>I believe the ECs are OK with the work done on the website.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Kind regards,<o:p></o:p></p></div><div><p class=MsoNormal>Benjamin <o:p></o:p></p></div></div><p class=MsoNormal><o:p> </o:p></p><div><div><p class=MsoNormal>On Tue, Aug 1, 2023 at 3:06 PM Tapani Tarvainen <<a href="mailto:ncsg@tapani.tarvainen.info">ncsg@tapani.tarvainen.info</a>> wrote:<o:p></o:p></p></div><blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in'><p class=MsoNormal>Hi Amin, all,<br><br>First about the GDPR: there's no formal difference between France and<br>Italy. I don't know if there are practical ones (like, how effective<br>their DPAs are), but I don't think there'd be any that'd be important<br>for NCUC. Likewise for differences between companies, I don't expect<br>there to be any that really matter, if they're both EU-based.<br><br>There are differences between companies based in EU and outside<br>of it, however, but given the rather limited amount of personal<br>data processing NCUC does I think it'd be mainly symbolic (which<br>doesn't mean it's irrelevant, but I'll leave it up to the EC).<br><br>Anyway, yes there are cheaper options than NCUC's current hosting<br>provider (Gandi), but I don't think the difference really matters,<br>especially as (if) ICANN picks the tab. Sticking with Gandi would make<br>administration easier as long as the old VM stays there.<br><br>Second, I'm not sure why we'd want to change the domain. The owner of<br><a href="http://ncuc.org" target="_blank">ncuc.org</a> is not the hosting company but The Internet Governance<br>Project of Georgia Tech, in effect Milton Mueller and Brenden Kuerbis.<br><br>Unless I'm mistaken, NCUC could not own a domain name anyway unless<br>it's first incorporated somewhere, and that would not be trivial.<br><br>As a side note, NCUC's bank account is also legally not NCUC's but<br>Milton's, for the same reason. Should he be run over by a bus or<br>something, NCUC would not find it easy to access the funds.<br><br>Best,<br><br>Tapani<br><br>On Tue, Aug 01, 2023 at 10:09:52AM +0200, Amin Hacha (<a href="mailto:aminhacha@gmail.com" target="_blank">aminhacha@gmail.com</a>) wrote:<br>> <br>> Greetings all.<br>> Starting, I want to express my appreciation to Olga for her valuable time<br>> and efforts.<br>> <br>> Thanks, Ken for the meeting brief.<br>> <br>> I would like to bring attention to some points that were discussed and not<br>> mentioned in the meeting brief, as well as provide further suggestions on<br>> specific matters.<br>> <br>> Firstly, during the meeting, I expressed that me and David, we are ready to<br>> volunteer to handle and make the forthcoming update, especially since we<br>> had several meetings discussing that with Benjamin ( during ICANN 76 and<br>> 77). Also, Benjamin mentioned our readiness during the meeting. Kindly if<br>> possible add that to the meeting brief.<br>> And for future reference, I kindly request that my name be mentioned<br>> specifically when referring to the individual who offered free hosting,<br>> rather than written as "a member of the e-team."<br>> <br>> Regarding the hosting company based in France and the implications of the<br>> General Data Protection Regulation (GDPR), as mentioned by Tipani, I<br>> recommend gathering more detailed information through Tipani before<br>> reaching a final decision. Since I am currently located in Italy, I am not<br>> well-versed in the French hosting company's approach to GDPR compliance.<br>> <br>> Furthermore, I have an inquiry concerning the domain name for NCUC. Are we<br>> planning to buy a new domain name, or will we continue using the existing<br>> one?<br>> If to buy a new domain, I propose that NCUC acquires the domain<br>> independently to mitigate any potential future issues with the domain's<br>> current owner ( the hosting company).<br>> <br>> In today's market, many reputable global companies offer domain names with<br>> unlimited hosting capacity and provide free assistance at affordable<br>> prices. For example, <a href="http://www.ipage.com" target="_blank">www.ipage.com</a> offers a hosting package for three years<br>> at just 2 USD per month, with the domain name included free of charge for<br>> the first year, followed by a yearly fee of approximately 15 USD. with 24/7<br>> assistance. This option has been well-tested and trusted.<br>> in this case, it is not difficult to upload the new design as it seems done<br>> thru WordPress.<br>> <br>> Thank you for your attention to these matters.<br>> Enjoy your summertime.<br>> Best regards,<br>> Amine<br>> <br>> On Mon, Jul 31, 2023 at 6:19 PM Ken Herman <<a href="mailto:ken@kherman.com" target="_blank">ken@kherman.com</a>> wrote:<br>> <br>> > Hello all.<br>> ><br>> ><br>> ><br>> > Thanks for everyone’s contribution.<br>> ><br>> ><br>> ><br>> > The link below is my brief summary of today’s discussion. Please edit in<br>> > places where I might have missed key points.<br>> ><br>> ><br>> ><br>> ><br>> > <a href="https://docs.google.com/document/d/1aeBwOPClnTiNzr6LLcY0K9Ha_JrRmWTXLqa585_fOYw/edit?usp=sharing" target="_blank">https://docs.google.com/document/d/1aeBwOPClnTiNzr6LLcY0K9Ha_JrRmWTXLqa585_fOYw/edit?usp=sharing</a><br>> ><br>> ><br>> ><br>> > Ken<br>> ><br>> ><br>> ><br>> > *From:* NCUC-EC <<a href="mailto:ncuc-ec-bounces@lists.ncuc.org" target="_blank">ncuc-ec-bounces@lists.ncuc.org</a>> *On Behalf Of *Benjamin<br>> > Akinmoyeje<br>> > *Sent:* Saturday, July 29, 2023 3:12 PM<br>> > *To:* Tapani Tarvainen <<a href="mailto:ncsg@tapani.tarvainen.info" target="_blank">ncsg@tapani.tarvainen.info</a>>; Amin Hacha <<br>> > <a href="mailto:aminhacha@gmail.com" target="_blank">aminhacha@gmail.com</a>>; Andrea Glandon <<a href="mailto:andrea.glandon@icann.org" target="_blank">andrea.glandon@icann.org</a>>; David<br>> > Morar <<a href="mailto:davidcristianmorar@gmail.com" target="_blank">davidcristianmorar@gmail.com</a>>; Olga Kyryliuk <<a href="mailto:olga_kyryliuk@ukr.net" target="_blank">olga_kyryliuk@ukr.net</a>>;<br>> > Exec. Comm <<a href="mailto:ncuc-ec@lists.ncuc.org" target="_blank">ncuc-ec@lists.ncuc.org</a>><br>> > *Subject:* Re: [NCUC-EC] E-Team Engagement<br>> ><br>> ><br>> ><br>> > Dear Andrea,<br>> ><br>> > Good day to you and I hope you are doing well.<br>> ><br>> ><br>> ><br>> > Please can you help create a Zoom meeting for us the eTeam and Olga to<br>> > meet.<br>> ><br>> ><br>> ><br>> > Please it would be great if you can invite everyone on this mail trail.<br>> ><br>> ><br>> ><br>> > The date and time of the meeting is July 31, 2023, and by 6 pm Kyiv time.<br>> ><br>> ><br>> ><br>> > Kind regards,<br>> ><br>> > Benjamin<br>> ><br>> ><br>> ><br>> > On Fri, Jul 28, 2023 at 4:07 PM Tapani Tarvainen <<br>> > <a href="mailto:ncsg@tapani.tarvainen.info" target="_blank">ncsg@tapani.tarvainen.info</a>> wrote:<br>> ><br>> > I can do July 31 at that time. Probably could arrange the latter<br>> > options as well but would have to look at specific times.<br>> ><br>> > Tapani<br>> ><br>> > On Fri, Jul 28, 2023 at 08:44:21AM +0000, Benjamin Akinmoyeje (<br>> > <a href="mailto:benakin@gmail.com" target="_blank">benakin@gmail.com</a>) wrote:<br>> > ><br>> > > Dear eTeam,<br>> > > Good day to you.<br>> > ><br>> > > Please here is the time availability I got from Olga<br>> > ><br>> > > “So if you want a call, let’s make smth quick for 30 minutes max with EC<br>> > > inviting Tapani who can explain what is the challenge on his side. I can<br>> > > make it for a call on 31 July after 6 pm (Kyiv time, UTC+3), 3 August<br>> > after<br>> > > 4 pm and 5 August any time at the moment.”<br>> > ><br>> > ><br>> > > I will recommend July 31st please<br>> > ><br>> > ><br>> > > Looking forward to hear from you.<br>> > ><br>> > > Kind regards,<br>> > > Benjamin<br>> > ><br>> > > On Thu, 13 Jul 2023 at 2:16 PM, Tapani Tarvainen <<br>> > <a href="mailto:ncsg@tapani.tarvainen.info" target="_blank">ncsg@tapani.tarvainen.info</a>><br>> > > wrote:<br>> > ><br>> > > > So, a brief summary of the situation as I see it:<br>> > > ><br>> > > > Olga and her friend Dusan have designed a new website, which you can<br>> > > > see at <a href="http://www2.ncuc.org" target="_blank">www2.ncuc.org</a>. Contentwise it's no more up-to-date than the<br>> > > > old one, but it should be easy to update (the old one isn't as you<br>> > > > presumably know, I won't go into the reasons for that now).<br>> > > ><br>> > > > The first decision would be if the new design is good enough<br>> > > > to move forward with. (I think it is.)<br>> > > ><br>> > > > There are some compatibility issues with the current VPN where<br>> > > > it now is. They are not trivial to solve because the old mailing<br>> > > > list software (<a href="http://lists.ncuc.org" target="_blank">lists.ncuc.org</a>) needs different (older) versions<br>> > > > of some stuff, and we don't want to break the mailing lists.<br>> > > ><br>> > > > Easiest solution from my perspective here is getting another VPN and<br>> > > > separate the mailing list and website to their own VPNs. This will<br>> > > > cost something to the order of $10/month.<br>> > > ><br>> > > > So that's the second decision. I can set up a new VPN in<br>> > > > a few minuts once you confirm someone will pay for it.<br>> > > ><br>> > > > Once that's up and the new wordpress setup is there, it's contents<br>> > > > would need to be updated. Not all that much new content is needed,<br>> > > > most important is to make sure that whatever is there is current,<br>> > > > notably EC and other committee memberships. Some subsections are also<br>> > > > completely empty now, but could be populated simply by copying content<br>> > > > from the old site.<br>> > > ><br>> > > > Publication of the new site could be done in two ways:<br>> > > ><br>> > > > (1) keep it in a temporary location (www2 or whatever) until the<br>> > > > contents are more or less up to date and then change the URL to<br>> > > > <a href="http://www.ncuc.org" target="_blank">www.ncuc.org</a> and announce it to the world.<br>> > > ><br>> > > > (2) switch URL immediately, that is make <a href="http://www.ncuc.org" target="_blank">www.ncuc.org</a> point to<br>> > > > the new design even while incomplete and update it there.<br>> > > ><br>> > > > Difference between those is mainly in the optics as it were, how<br>> > > > things look like while it's being worked on. The first would be<br>> > > > prettier, more glamorous so to speak, but if nobody then takes up the<br>> > > > content work it could hang in a limbo for a long time.<br>> > > ><br>> > > > That's the third decision.<br>> > > ><br>> > > > But what that leads to is continued maintenance of the site,<br>> > > > both content (Wordpress) and back end.<br>> > > ><br>> > > > Pretty much everybody should be able to learn what it takes to to edit<br>> > > > WP content in a matter of minutes, although some care (and<br>> > > > documentation!) would be needed to keep the site consistent in what's<br>> > > > where. But you'd need several people doing that enough that they don't<br>> > > > forget how it works.<br>> > > ><br>> > > > So the fourth decision is, who'd be doing that.<br>> > > ><br>> > > > The back end I can manage for now, but at least in the long run it<br>> > > > would be necessary to have a backup sysadmin in case I'm run over<br>> > > > by a bus or die of old age or something, and for that you'd need<br>> > > > someone with Linux sysadmin skills. There are also options for<br>> > > > managed hosting where that'd be somewhat easier, at extra cost<br>> > > > (of course), which might make sense at some point.<br>> > > ><br>> > > > Deciding on that isn't as urgent, but for the record it's one<br>> > > > more question to decide on at some point.<br>> > > ><br>> > > > OK, it wasn't all that brief... but I think I got most of<br>> > > > the issues covered.<br>> > > ><br>> > > > --<br>> > > > Tapani Tarvainen<br>> > > ><br>> ><br>> > --<br>> > Tapani Tarvainen<br>> ><br>> ><br><br>-- <br>Tapani Tarvainen<o:p></o:p></p></blockquote></div></blockquote></div></body></html>