[Accountability-tf] Acountability TF Call Monday 12 February @ 14:00 UTC+1

Dear task force members,

As I mentioned in my other email, we have a call scheduled for this 
Monday (12 February) at 2pm.

Athina and I have looked at the draft document we sent around on Monday 
to see what areas could benefit the most from TF input. We have come up 
with three areas below that we could discuss on the call (the sections 
in the document they relate to are in brackets).

We've also included a few thoughts and questions of our own that may 
help to guide the discussion, but obviously there will be plenty more to 
discuss for each topic.

Cheers

Antony


***

Agenda/Topics to Discuss


*1. Consensus (2.1.1 & 2.1.1.1)*

(Moving towards finalising Malcolm's document)

-The role of Chair needs in determinig consensus - determining whether 
an objection is valid or not

-How does the chair evaluate whether an objection coming from a large 
number of participants can be rejected vs expresses the community's 
will? Are there any generally respected values they can use in this 
assessment?

-When does "Silence is consensus" apply? Is there a minimum of 
participation required for consensus to be legitimate?

-How does the chair act when there is an implied agreement that's not 
necessarily expressed by the community?

-What are the differences between RIPE and the IETF's understanding of 
consensus.

*2. Capture (1.3.1)*

-How do? RIPE structures prevent capture
+People selected according to community processes. Constant support from 
community needed for Chair to remain in their role - power can be 
revoked at any time - community won't hesitate to remove a chair if 
necssary.
+Limited concentration of power in any one role (mostly administrative 
function).
+Formal appeal process (in the PDP) - against the policy and not the chair.

-How likely is capture given existing procedures?

-What is the role of 1) community values, and 2) participants in 
preventing capture

-What is the role of consensus in avoiding capture

*3. Documentation in RIPE (1.1, 1.2)*

-What is the role of documentation in RIPE?
-When does something need to be documented and to what degree? Who 
decides? Proactive vs reactive documentation

-What isn't documented that needs to be?