Changes

<div style="clear:both;"></div>

<div style="clear:both;"></div>

<div style="width:49.5%;float:left;">

<div style="width:49.5%;float:left;">

<div style="background:#61A376; font-family:sans-serif;font-size:100%;font-weight:bold;text-align:left;color:#F2EFEA;height: 1.5em;margin:.2em 0 .1em 0; padding:.5em .25em .5em .75em;border-radius:5px;">Featured Article, July 1, 2022</div>

<div style="background:#61A376; font-family:sans-serif;font-size:100%;font-weight:bold;text-align:left;color:#F2EFEA;height: 1.5em;margin:.2em 0 .1em 0; padding:.5em .25em .5em .75em;border-radius:5px;">Featured Article, July 5, 2022</div>

<div style="padding:.5em 0 0 0;width:95.5%;">   

<div style="padding:.5em 0 0 0;width:95.5%;">   

'''[[CARNet|Croatian Academic and Research Network]]''' (CARNet) is the registry operator for the .hr ccTLD for Croatia. Initially a Ministry of Science and Technology project, it was spun off as a separate institution in 1995 by the Croatian government to administer the ccTLD. The University Computing Center of the University of Zagreb provided administrative and technical support to the registry until 2010 when CARNet took over most of the work.

The '''[[First GNSO Organizational Review]]''' (GNSO1) was initiated in 2007, with the implementation of improvements continuing throughout 2012. It resulted in major changes in the structure and organization of the [[GNSO]], including the division of the constituent groups into contracted and non-contracted houses. The resulting final report concluded with five key recommendations:

* Formalize a working group model to become the focal point for policy development and enhance the PDP by making it more inclusive, representative, and – ultimately – more effective and efficient.

* Revise the PDP to make it more effective and responsive to ICANN’s policy development needs, bringing it in line with the time and effort actually required to develop policy, and making it consistent with ICANN’s existing contracts (including, but not limited to, clarifying the appropriate scope of GNSO “consensus policy” development).

* Move the GNSO Council away from being a legislative body heavily focused on voting towards becoming a smaller, more focused strategic entity, composed of four broad stakeholder groups, with strengthened management and oversight of the policy development process, the elimination of weighted voting and the imposition of term limits.

* Improve GNSO coordination with other ICANN bodies.

</div>

</div>

</div>

</div>