From 08b081acecdca2afdd89da7cd087f53cf21a7aae Mon Sep 17 00:00:00 2001 From: zimbatm Date: Wed, 15 Feb 2017 18:36:15 +0000 Subject: [PATCH] First stab at defining the buddy responsibilities --- rfcs/0000-rfc-process.md | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/rfcs/0000-rfc-process.md b/rfcs/0000-rfc-process.md index 22c7aac..f7aab03 100644 --- a/rfcs/0000-rfc-process.md +++ b/rfcs/0000-rfc-process.md @@ -94,6 +94,15 @@ rubber stamp, and in particular still does not mean the feature will ultimately be merged; it does mean that in principle all the major stakeholders have agreed to the feature and are amenable to merging it. +### Role of the "buddy" + +To goal for assigning a "buddy" to the RFC is multifold. The main +responsability is to make himself available for to the author to move the RFC +along. It means keep a closer connection with him, talk and help resolve +ongoing issues and add credence to the proposal. The buddy doesn't necessarily +have to agree with all the points of the RFC but should generally be satisfied +that the proposed additions are a good thing for the community. + # Drawbacks [drawbacks]: #drawbacks