You are here: Home > Participate > RIPE Community > Task Forces > RIPE Accountability Task Force > Accountability Task Force Recommendations

Accountability Task Force Recommendations

In 2019, the RIPE Accountability Task Force published its final report, following its review of the RIPE community. In the report were 15 recommendations, highlighting things that the RIPE community might want to examine and consider whether further action was needed.

This page is intended to document the RIPE community's work as it considers these recommendations and record any actions or decisions that are taken as a result. It is important to note that the task force viewed these recommendations as things for the community to look at in more detail - it did not necessarily expect that all of them would result in action.

 

Pending:   Completed:  

Recommendation/Outcome

Status

Recommendation
1. Consider whether any formalised commitments are needed from the RIPE NCC (that it will implement policy, follow relevant community directions, etc).

 

Recommendation
2. Consider whether the RIPE Chair should be asked to disclose financial details associated with performing RIPE Chair duties and who covers these.

Outcome
The RIPE Chair provided this information (slide 11) during the RIPE Community Plenary session at RIPE 79.

 

Recommendation
3. Consider reviewing whether current informal safeguards are enough to prevent bad actors from passing a policy proposal without the wider community having an opportunity to comment (not a great risk in the task force’s view).

 

Recommendation
4. Consider including an explanation at the top of obsoleted RIPE Documents when there is no replacement document that it refers to. Possibly create a new “Archived” status for documents that are no longer current, but not exactly obsolete.

 

Recommendation
5. The community should consider whether more can be done to distinguish between the different types of RIPE Documents and whether consistency can be applied to the metadata for these documents moving forward.

 

Recommendation
6. The task force believes that the community needs to make progress on finalising the RIPE Chair replacement procedure.

Outcome
A new RIPE Document describes the replacement procedure and consensus on this was announced in August 2019.

  

Recommendation
7. Consider whether the RIPE Chair should report back to the community after representing RIPE in other forums.

Outcome
The RIPE Chair gave an update (slide 6) in the RIPE Community Plenary at RIPE 79 on other forums he had attended. He also aims to increase reporting more generally.

  

Recommendation
8. Consider aligning the process for selecting working group chairs across the community.

  

Recommendation
9. Consider having more of a standardised process for informing new WG Chairs about relevant RIPE Documents and their responsibilities.

  

Recommendation
10. Consider developing a “crash course” for new chairs that covers things like how to effectively chair a session or determine consensus.

  

Recommendation
11. Consider developing general information for newcomers to explain how to participate in working groups, task forces and BoFs and how the community functions more generally (the RIPE NCC could be tasked to produce this content)

  

Recommendation
12. Consider providing an overview of what the Working Group Chair Collective does and what it is responsible for.

  

Recommendation
13. The RIPE Document that defines task forces is obsolete, and the working description on ripe.net no longer seems fit for purpose. Consider updating this with the description provided in ripe-464, which has been accepted by the RIPE community.

  

Recommendation
14. Develop documentation around the plenary and what its powers are. Also consider doing more to record closing plenary decisions which are not minuted currently.

  

Recommendation
15. Consider putting in place some kind of semi-regular review of the RIPE community’s accountability.

  

 

RIPE Forum

The RIPE Forum is an additional way to participate in RIPE community mailing list discussions using a web-based interface rather than an email client.

Check out the forum