Marco Schmidt

Website Redesign Simplifies Policy Proposal Discussions

Marco Schmidt

4 min read

0 You have liked this article 0 times.
0

When re-designing www.ripe.net, we paid extra attention to how we can improve the interface for the Policy Development Process (PDP). This open and transparent process determines RIPE Policies, which govern the distribution and use of nearly all Internet resources in the RIPE NCC service region. Our aim was to make it easier to review policies and proposals and encourage participation in policy discussions. This post explains these improvements in more detail.


RIPE Documents

All RIPE Documents - including RIPE Policies - can now easily be reviewed as they evolve. A widget on the right side of the policy page shows all the previous versions of a document (below, "Updates"). If you are viewing an obsolete document, the widget shows the documents that obsoleted it ("Updated by").

AS Assignment Policy Figure 1: Previous versions of a RIPE document can be seen on the right side

Clicking on one of the RIPE Document numbers brings you to that specific version of the document.

Did you notice the little “double-page” symbol after each document number? Look again:

Updated by

Figure 2: Feature to compare different versions of a document

During the website redesign, we implemented an automatic tool to allow easy comparison between different versions of the same document. This makes it much easier to see changes between the document versions. In the following example, a word has been replaced in Section 3 and a new Section 4 has been added.

Returning ASes Figure 3: Showing the differences in two versions of a document

The more iterations there are between two compared versions of a document, the more content is likely to have been changed. The tool also compares HTML content, so even minor changes such as extra spacing are shown as differences.

Each RIPE Document now has an ASCII file attached to it. This was done in response to requests from the community to provide plain-text versions of our documents.

Besides this functionality, we also gave all RIPE Documents a new style, with a larger font and slightly looser spacing, to increase their readability.

Policy Proposals

The main focus of our work on the policy proposals was to improve usability. After receiving comments that it was not clear how to respond to a policy proposal, we included a clear access link from each proposal to the relevant working group.

Next to the policy text, we added a “Get Involved” widget that provides a one-click solution to subscribe to the relevant working group, review the archives and join the discussion.

Policy Text Figure 4: "Get involved" widget next to a policy proposal

Just below that, we added a “Contact” widget for people who would like to contact me directly. If you have a question on the development process, if you want support for your own proposal or if you need information about previous proposals and discussions, you can use this widget to contact me.

The widget includes my Twitter details in case you prefer to get the latest PDP updates this way.

Contact Figure 5: "Contact" widget

We also worked on the visual clarity of the policy proposal pages to make it easier to see when a proposal has been accepted or withdrawn.

  Policy Status Figure 6: Green bar showing status of policy document

We think these improvements will make it easier to review RIPE Policies and policy proposals. In this way, we hope the new design will encourage participation in the Policy Development Process. We look forward to seeing more of you getting involved in RIPE Policy discussions.

We also welcome any suggestions for further improvements on our website. Simply send an email to pdo@ripe.net .

0 You have liked this article 0 times.
0

You may also like

View more

About the author

Marco Schmidt Based in Amsterdam, Netherlands

Marco Schmidt is the RIPE NCC’s Policy Development Officer. In this role, he supports and drives the RIPE (community) Policy Development Processes (PDP), both externally and internally. He also supports the implementation of accepted policies into RIPE NCC procedures and workflow. Marco initially joined the RIPE NCC as an IP Resource Analyst (IPRA) for the Registration Services department, where he worked for five years. Within that role, he gained valuable experience in evaluating IPv4, IPv6 and Autonomous System Number requests while providing support to the RIPE NCC membership.

Comments 0