Dear Colleagues,

As I mentioned during the Council call, on Friday I had a discussion with ICANN Org people regarding the new ccNSO website. As promised, here is a short summary.

You have probably noticed that there is a huge amount of information created, shared and stored by ICANN Org and SOACs (including ccNSO, of course). Currently, the management of that information, including search capabilities, is far from being optimal. As you may know, the Information Transparency Initiative (ITI) started by ICANN in 2018 is focused on improving access to and findability of ICANN's published information through the implementation of a document management system (DMS). ITI began with content on https://www.icann.org. The plan is to complete it by March. Other websites (including the websites of SOACs) will be built following the same principles and design. ICANN team will start to work on the ccNSO website in May.

So, the timeline looks something like this:

- March: ICANN team will give us a list of things they need from us to start working on our website.

- May: ICANN team starts working.

- In an undetermined point in future: our website is ready.

What we need to do:

- March: add the work on the ccNSO website to our work plan for this year.

- As soon as possible: organise ourselves to make sure we are ready to provide all the necessary information and feed-back. I believe this is something for the new Outreach and Involvement Standing committee, don’t you think? After our March meeting I will no longer be the chair of the ccNSO Council, but if you allow me to participate in this work, I will gladly do it (I started my career as a webmaster a long time ago in a galaxy far, far away).

- May: provide feedback to the questions we receive in March to make sure that ICANN team can start working.

- May-…: provide timely feed-back.

Additionally, ICANN team will look into possibility to provide:

- Information on the current visitor statistics for our website (it would help us to understand what people are looking for);

- Ticketing system we could use to report all the bugs, ask for improvements/features, and monitor the progress.

I believe that’s about it. I can only add some variations of Murphy’s law:

- If it seems too good to be true, it probably is;

- Everything takes longer than you think;

- There is always one more bug;

- There’s never time to do it right, but there’s always time to do it over;

- If everything seems to be going well, you have obviously overlooked something.

Kind regards,

]{atrina