Document new contributing process (#119)

* document new contributing process

Signed-off-by: Calum Murray <cmurray@redhat.com>

* Update CONTRIBUTING.md

Co-authored-by: Ali Ok <aliok@redhat.com>

---------

Signed-off-by: Calum Murray <cmurray@redhat.com>
Co-authored-by: Ali Ok <aliok@redhat.com>

CONTRIBUTING.md

@@ -35,9 +35,8 @@ detailing the change that needs to be made, after the designs you made have been
 like if you wanted to work on an issue titled "re-design website buttons".
 1. First, you would assign the issue to yourself by commenting `/assign` on the issue
 2. Next, you would work on an initial draft of the design.
-3. Once you have a design you are happy with or that you want feedback on, you will leave a comment on the issue with the artefacts from the design (e.g. a PNG output of the 
-button design from Figma)
-4. The design leads for the working group will leave feedback on the design, and possible ask you to make some changes with comments on the issue.
-5. Once the design leads are happy with your design, they will let you know on the issue. 
-6. Now, you will go to the repository for the website (knative/docs), and open an issue with the final design asking someone to update the buttons accordingly. If your
+3. Once you have a design you are happy with or that you want feedback on, you will open a Pull Request to this repository with the artifacts included.
+4. The design leads or other contributors in the working group will leave feedback on the design, and possible ask you to make some changes.
+5. At the bi-weekly working group meeting, everyone at the meeting will work together to make a final decision on the design. If the group agrees on the changes, it will be merged into the repo.
+6. Now, you can go to the repository for the website (knative/docs), and open an issue with the final design asking someone to update the buttons accordingly. If your
 change is not for the website and you are not sure which repository it should go to, please ask the WG tech lead for help.