From aba85855ee519e343eefa38106a00532ee063557 Mon Sep 17 00:00:00 2001 From: Shivshankar-Reddy Date: Tue, 15 Oct 2024 18:19:45 +0000 Subject: [PATCH] Update contributing file Signed-off-by: Shivshankar-Reddy --- CONTRIBUTING.md | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index cc807a79b6..5e2a712133 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -79,10 +79,9 @@ you need to ensure that the contribution is in accordance with the DCO. 1. If it is a major feature or a semantical change, please don't start coding straight away: if your feature is not a conceptual fit you'll lose a lot of -time writing the code without any reason. Start by posting in the mailing list -and creating an issue at Github with the description of, exactly, what you want -to accomplish and why. Use cases are important for features to be accepted. -Here you can see if there is consensus about your idea. +time writing the code without any reason. Start by creating an issue at Github with the +description of, exactly, what you want to accomplish and why. Use cases are important for +features to be accepted. Here you can see if there is consensus about your idea. 2. If in step 1 you get an acknowledgment from the project leaders, use the following procedure to submit a patch: