From 707902e574af6f866e7a1996dbd96682e2ece2cc Mon Sep 17 00:00:00 2001 From: "Yann Esposito (Yogsototh)" Date: Thu, 26 Nov 2020 10:23:03 +0100 Subject: [PATCH] journal/2020-11-26--10-11-23Z--meta_rfc_for_dev_team.org --- journal/2020-11-26--10-11-23Z--meta_rfc_for_dev_team.org | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/journal/2020-11-26--10-11-23Z--meta_rfc_for_dev_team.org b/journal/2020-11-26--10-11-23Z--meta_rfc_for_dev_team.org index ccd374c9..f39d39a4 100644 --- a/journal/2020-11-26--10-11-23Z--meta_rfc_for_dev_team.org +++ b/journal/2020-11-26--10-11-23Z--meta_rfc_for_dev_team.org @@ -25,4 +25,7 @@ We are dependent on =github= issue tracker for essential knowledge for our team. * Solution We should have a document that keep track of our RFCs. -I would propose to have a document +So if an RFC is about coding conventions, we should probably amend the +=CONTRIBUTING.org= file with a link to the RFC issue. + +Before calling that RFC, we used the label /Epic/ for issues