Reviewing RIPE Accountability

Slides:



Advertisements
Similar presentations
Staff Performance- functionality overview The ‘Personnel Details’ tab will be Personnel as it currently stands Professional Details has been given its.
Advertisements

Proclamation 2015 Orientation November 06, :30 p.m. Administration Board Room.
PDO Activities Emilio Madaio Policy Development Officer RIPE NCC RIPE Oct - 4 Nov 2011, Vienna.
PDP Improvements Update & Discussion. | 2 Background  Ten proposed improvements aimed to streamline and enhance the GNSO PDP Ten proposed improvements.
Victoria L. Ravenscroft Senior Policy Analyst Reliability Planning and Performance Analysis Information Sharing Policy Update March 25-26, 2014 Standing.
Filiz Yilmaz IGF 2006, Athens RIPE Policy History Focusing on IPv4 Filiz Yilmaz Policy Development Officer
1 RMS TAC Update April 3, Test Plan Flight Dates It is the practice of RMS to approved the dates for future testing flights. This enables new.
Health Big Data Discussion Privacy and Security Workgroup Deven McGraw, Chair Stanley Crosley, Co-chair June 8, 2015.
IEEE PCIC Standards Working Group Officers’ Workshop IEEE-SA Public Review Overview for Sponsor Chairs, Working Group Chairs and Ballot Designees Pat Roder.
Put name of kaizen event here
Filiz Yilmaz, ASO AC Chair
Submitting and reviewing promotion applications in Vibe
New gTLD Auction Proceeds CCWG Status Update
2017/8 NomCom Review: Status Update
Security SIG in MTS 05th November 2013 DEG/MTS RISK-BASED SECURITY TESTING Fraunhofer FOKUS.
International Defence Enterprise Architecture Specification (IDEAS)
The NICE Citizens Council and the role of social value judgements
GAC Operating Principles
Reliability Assessment Committee
RIPE Accountability Task Force Update – RIPE 75
Reliability Assessment Guidebook (RAG): Status Report
Negotiating Your Local Targets and Understanding Perkins Core Indicator Annual and Trend Reports November 9, 2017.
Accountability Court Certification and Peer Review
Reliability Assessment Guidebook (RAG): Status Report
IAASB-IESBA Coordination
Standards Development: An Overview
IEEE Task Group G Status Update
Structure of the Code Don Thomson, Task Force Chair IESBA Meeting
Internal Audit Life Cycle
Potential Milestones A timeline to finish in one year
IAASB-IESBA Coordination
CTAERN/DOE System Level Counselor Coordinator Profile Entry Initiative
Task Force 3: Electrolyte leakage
AIXM CCB meeting EUROCONTROL HQ, Brussels
IESBA Meeting New York September 17-20, 2018
The Community Project Silver Spring International Middle School
Architecture Data Exchange Experiments Military Utility Demonstration
International Defence Enterprise Architecture Specification (IDEAS)
SVP Connecticut Values Retreat Session – November 7th
Initial Thoughts on GAC Operating Principles Evolution
RIPE Accountability Task Force
Critical Element: Implementation Plan
Development of energy balance statistics
Rule 21 Working Group 2 IN-PERSON WORKSHOP August 29, 2018
2019 Local School District Charter Application Process
Structure of the Code Don Thomson, Task Force Chair IESBA CAG Meeting
Critical Element: PBIS Team
NERC Reliability Standards Development Plan
Finance & Planning Committee of the San Francisco Health Commission
RIPE Accountability Task Force – RIPE 76
CTAERN/DOE System Level Counselor Coordinator Profile Entry Initiative
Next Steps Advisory group debrief call Circulate meeting summary
NERC Reliability Standards Development Plan
Progress Report GRE TF AVSR
What are the RIPE Community’s Values?
Evaluating Progress Towards Achieving Targets Identified in the Communication on Halting the Loss of Biodiversity to 2010 and Beyond Member State Contribution.
Facilitated/Presented by:
Parliamentary Committees
Goal 1.5 Evaluation Documents Faculty and Staff
The ETSI Standardisation Process
GAC Travel Support Rules Update
Update of PWG Process and IP Policy
CCWG-Accountability ICANN56 26 June 2016
Performance Management Effective Evaluations
On Site Management Meeting 7.
Progress Report GRE TF AVSR
IRS Circular 230 Required Notice--IRS regulations require that we inform you that to the extent this communication contains any statement regarding federal.
Information Sharing Policy Update March 25-26, 2014
Marine Environment and Water Industry
SAE Standards Works Training Module - Useful Tabs
Presentation transcript:

Reviewing RIPE Accountability Filiz Yilmaz / William Sylvester RIPE74, Budapest, May 2017

We Think That RIPE is Accountable Open, transparent, bottom-up Established processes and procedures But… Not everything is documented There may be gaps or “unknown unknowns” We need to be able to demonstrate our accountability to outside observers And onboard Newcomers efficiently too

RIPE Accountability Task Force Formed at RIPE 73 (October 2016) to examine the accountability of the RIPE community 14 community members, plus support from RIPE NCC staff https://www.ripe.net/participate/ripe/tf/ripe- accountability-task-force/

Current Status Part I Draft scope published We want to finalise this with your consent Last call until 12 May 2017 Discussions & communication taking place at ripe-list@ripe.net

Draft Scope (1) Review existing RIPE community structures, documentation and processes to evaluate whether they are accountable and in alignment with RIPE values Assemble a list of existing RIPE community structures or processes Identify potential gaps where RIPE accountability could be improved or strengthened

Draft Scope (2) Publish recommendations for the RIPE community Identify areas where communications efforts or materials may be required The scope of the task force is limited to an examination of the RIPE community.

Current Status Part II Mapping out RIPE accountability areas E.g what “powers” does a WG Chair have? Finding where documentation exists/where there are gaps

Mapping out RIPE accountability areas Came up with a list of areas to consider Review is underway F2F mtg here today at RIPE74 during lunch time Open to observers via Webex: https://ripencc.webex.com/ripencc/j.php?MTID=m961b d4ae6c27ceecdf58e61f8621452f Sample snap-shot of the current working document on next slide

Partial view from TF’s working document

Next Steps Publish the mapping document for Community review Move ahead with the next steps: Identification of gaps Recommendations to fill them in Ex: This area is not documented or not documented well. TF recommends Community considers improving documentation on it. Publish Final report Disband the Task Force

Current Status – Recent discussions on list Support on scope as it is currently Come up with a timeline Was hard to guestimate so far with a moving scope Once we lock up the “scope”, we will be able to publish one Come up with a work plan See above, yes, now we can with a locked up scope Don’t come up with any new procedures. We never intended to. Addressed on the list and in the updated scope’s wording.

We want to hear from you Do you support the draft scope? Is the approach acceptable? Is this transparent to you? So can the TF move ahead with its work?

Questions?