RIPE Accountability Task Force: Updated Draft Scope and Presentation at RIPE 74
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.
Filiz, 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 brian.nisbet@heanet.ie 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.
Filiz, I agree with Brian. Cheers, -- Shane At 2017-05-05 09:16:15 +0100 Brian Nisbet <brian.nisbet@heanet.ie> 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 brian.nisbet@heanet.ie 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.
Filiz, task force members, Thank you for changing from 'document' to 'assemble a list'. That is much clearer and partly addresses a major concern. A number of real concerns remain with the current draft. Therefore I will make three specific proposals to improve it in the following message. This is not 'wordsmithing' but a matter of substance. I do not particularly enjoy having to have this conversation. During a sabbatical year other activities appear much more gratifying. Best Daniel
Colleagues, Below I make three concrete proposals for the charter. More than 25 years of experience with RIPE and similar organisations suggests to me that this charter still needs work. This still is a charter for a 'formalisation working group' rather than a 'task force'. A 'working group' because the definition of the tasks is very broad and there is no end-date. 'Formalisation' because the whole arrangement and context suggests formalisation as an inevitable outcome. We should make it very very clear that we are not starting an endless process that will inevitably lead to more process and formalisation. Process and formalisation is not automatically and universally a good thing. Formalisation does have drawbacks and risks. Formalisation is not a prerequisite for fairness, openness and transparency . Formalisation is often opposed to pragmatism and bottom-up consensus driven community work. Since 'nothing has happened' if it is not on the mailing list, please comment here on these three specific proposals. Thank you! ---- Proposal 1 Ideally a task force charter states a rather narrowly defined task and also lists expected results, such as specific documents. In order to avoid spending more time and energy arguing over this I suggest, as a compromise, to add the following language: "The task force will publish and maintain a work plan. For each document under development the work plan will show when drafts will be published and how and when community consensus will be achieved on the final result." This allows the task force to organise its work and at the same time it helps to conduct the work transparently and with track-able goals. ---- Proposal 2 Ideally a task force charter contains when and how the task force will finish. In order to avoid spending more time and energy arguing over this I suggest, by way of compromise, to add the following sentence: "This charter will be reviewed by the community no later than the second RIPE meeting in 2018." This avoids setting up an endless task force and provides the opportunity to modify or add tasks based on the work already completed. ---- Proposal 3 In order to clarify that there is definitely no intent to propose new procedures and formalisms right away, I propose to add the following sentence after "Publish recommendations for the RIPE community." "The task force will not propose or recommend specific new procedures or formalisms." This makes the charter explicitly reflect the intention of the task force as stated by Filiz earlier in this discussion. Such tasks very well be added later once we have considered all alternatives and have established community consensus to develop specific procedures or formalisms. Since 'nothing has happened' if it is not on the mailing list, please comment here on these specific proposals. Thank you! Daniel (Supporting the RIPE Community since 1989)
On 08/05/2017 11:02, Daniel Karrenberg wrote:
---- Proposal 1
Ideally a task force charter states a rather narrowly defined task and also lists expected results, such as specific documents. In order to avoid spending more time and energy arguing over this I suggest, as a compromise, to add the following language:
"The task force will publish and maintain a work plan. For each document under development the work plan will show when drafts will be published and how and when community consensus will be achieved on the final result."
This allows the task force to organise its work and at the same time it helps to conduct the work transparently and with track-able goals.
I'm in full agreement with this proposal. If this is a Task Force (and I believe it should be) then it must have a well defined goal.
---- Proposal 2
Ideally a task force charter contains when and how the task force will finish. In order to avoid spending more time and energy arguing over this I suggest, by way of compromise, to add the following sentence:
"This charter will be reviewed by the community no later than the second RIPE meeting in 2018."
This avoids setting up an endless task force and provides the opportunity to modify or add tasks based on the work already completed. Again... agreed. Task forces have well defined self destruct dates.
---- Proposal 3
In order to clarify that there is definitely no intent to propose new procedures and formalisms right away, I propose to add the following sentence after "Publish recommendations for the RIPE community."
"The task force will not propose or recommend specific new procedures or formalisms."
This makes the charter explicitly reflect the intention of the task force as stated by Filiz earlier in this discussion. Such tasks very well be added later once we have considered all alternatives and have established community consensus to develop specific procedures or formalisms.
I have no problems with this proposal, although I feel that the TF has already addressed this issue. There can be no harm in having it explicitly stated in the charter. Nigel
participants (5)
-
Brian Nisbet -
Daniel Karrenberg -
Filiz Yilmaz -
Nigel Titley -
Shane Kerr