Hello Everybody,
You are welcome to look over a draft of a new definition of the Numbered
Work Item process. This new version keeps the existing process largely
the same with some procedural tweaks here and there and also improves
the readability of the text.
Let us know what you think about this proposed change, good or bad. We'd
like to make it official in about three weeks.
NEW DRAFT Text:
–––––
RIPE Database Working Group Numbered Work Items
In order to facilitate discussion about issues and solutions, as well
as report on the progress made with solution implementation, the RIPE
Database Working Group employs a process using Numbered Work Items
(NWIs). Please note that this does not replace the Policy Development
Process. Instead it is used for smaller work items and helps to
facilitate the communication between the DB WG and the RIPE NCC.
Kickstart:
Anyone can contact the RIPE DB WG co-chairs and present a proposal or
a problem statement. Alternatively this can also be sent to the WG
mailing list directly. If there is interest in this work item, the
Database WG co-chairs will ask the RIPE NCC to assign a number to this
work item and include it on the list of numbered work items (NWIs).
Problem definition:
After an NWI is created, the proposal or problem statement will be
discussed in the WG. This can mean further specifying the problem
statement and including example cases of the problem to clarify the
scope. After two to three weeks the WG co-chairs will determine of
there is a consensus and will either post a clearly defined problem
statement to the list, or if there is no agreement on a problem
statement, the NWI will be closed.
Solution definition:
Anyone, including RIPE NCC staff, can propose solutions to a work
item's problem statement. The RIPE NCC will also provide an
implementation analysis that can include feasibility, expected
workload, proposed solutions, impact on other work items etc. In this
phase, the RIPE NCC together with the RIPE DB WG co-chairs will also
determine if the NWI might have an impact on an existing policy or if
the NWI might in fact lead to a change in policy or a new policy. In
this case, the WG co-chairs are advised to use the more formal Policy
Development Process (PDP) instead of the NWI process.
Implementation:
Once the WG agrees on the proposed solution, the RIPE NCC can start
implementing it, keeping the WG up to date about the timeframe,
milestones, documentation etc. The RIPE NCC will also update the entry
of the NWI on the table of NWIs accordingly.
Finished:
The project ends when the change has been deployed in the production
environment.
Cancelled:
The project can also end when the working group decides to cancel it.
The RIPE NCC will update the list of NWIs on a regular basis to
reflect the status of each NWI.
–––––
EXISTING Text for your convenience
–––––
In order to facilitate an ordered discussion about issues and solutions,
as well as report on the progress made with solution implementation,
the RIPE Database Working Group employs the following process
using Numbered Work Items (NWIs):
Kickstart:
To kickstart the process, any db-wg participant can email the chairs
with a snippet of text (a rough problem statement) and formally ask
the chairs to make it a work item. The chairs can then say “yes”, and
assign it a number, or “no”. If a number is assigned, the work item
will be routed through the following three phases:
Phase 1: Problem Definition
In this phase we will work as a group on formulating an exact problem
definition: text goes back and forth in the working group, example
cases of the problem are provided. In a timeframe of two to three
weeks the chairs declare consensus on the problem statement of the NWI.
Phase 1 output: A clearly defined problem statement, or a conclusion
if we cannot agree upon a problem statement definition. If the latter
is true, the NWI cannot proceed to Phase 2.
Phase 2: Solution Definition
Solution finding: People can propose solutions to a work item's problem
statement. Solutions can come from RIPE NCC staff or from any working
group member. The RIPE NCC may offer an implementation analysis
on proposed solutions or aspects of solutions.
For the NWI to move to Phase 3, the RIPE NCC has to provide the working
group with a summary of their understanding of the solution, and the
chairs declare consensus on the group's acceptance of this summary.
Phase 3: Development and Deployment Phase
The RIPE NCC writes the code, sets timelines and milestones
and documents the transitions/migration plan if applicable.
Finish:
The project ends when the change has been deployed in the production
environment.
Cancelled:
The project can also end when the working group decides to cancel it.
Every month the RIPE NCC will update this page with an overview of all
open NWIs, a brief summary of each, who is taking action and what that
action is.
–––––
I express my gratitude to all those who worked on this draft, and everybody
who took the time to offer their feedback.
Kind regards,
Peter and David
-----
To unsubscribe from this mailing list or change your subscription options,
please visit: https://mailman.ripe.net/mailman3/lists/db-wg.ripe.net/
As we have migrated to Mailman 3, you will need to create an account with the email matching your subscription before you can change your settings.
More details at: https://www.ripe.net/membership/mail/mailman-3-migration/
