Filiz,

I agree with Brian.

Cheers,

--
Shane

At 2017-05-05 09:16:15 +0100
Brian Nisbet <[email protected]> wrote:

> I think the updates are positive and I look forward to seeing the work
> of the Task Force.
> 
> Thanks,
> 
> Brian
> 
> Brian Nisbet
> Network Operations Manager
> HEAnet CLG, Ireland's National Education and Research Network
> 1st Floor, 5 George's Dock, IFSC, Dublin D01 X8N7, Ireland
> +35316609040 [email protected] www.heanet.ie
> Registered in Ireland, No. 275301. CRA No. 20036270
> 
> On 04/05/2017 12:59, Filiz Yilmaz wrote:
> > 
> > Dear colleagues, 
> > 
> > The RIPE Accountability Task Force has updated the draft scope based on
> > community feedback (below). We are now seeking your approval on the
> > updated version. 
> > 
> > In this latest vesion, we have changed the second bullet point from:
> > "Document existing RIPE community structures or processes." to "Assemble
> > a list of existing RIPE community structures or processes." This better
> > reflects the stock-taking activity that we intend to perform. 
> > 
> > With this, we believe that we have addressed the community's concerns,
> > and we would like to get your blessing by the end of RIPE 74. We would
> > like to avoid wordsmithing this any further and are considering this
> > "last call" for comments. Please share any comments or statements of
> > support on this mailing list before Friday, 12 May. 
> > 
> > We will also be giving a brief update on the scope and work of the task
> > force at RIPE 74 in Tuesday's Plenary at 9am. There will be plenty of
> > time for comments from the floor, so please attend and give us your
> > feedback. 
> > 
> > 
> > Kind regards
> > RIPE Accountability Task Force Chairs
> > Filiz Yilmaz & William Sylvester 
> > 
> > ====
> > 
> > *Updated Draft Scope*
> > ____
> > The RIPE Accountability Task Force agreed to:
> > 
> >   * 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 
> >   * 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.  
> 
> 

Attachment: pgpCnATz4zq37.pgp
Description: OpenPGP digitale handtekening

Reply via email to