precisions about the open design process

diff --git a/Contribute-to-design.md b/Contribute-to-design.md
index 770fefebc092486a369db0e254f8433027a50da4..9a0d03262677707684988aebe3fdc0546b352262 100644 (file)
--- a/Contribute-to-design.md
+++ b/Contribute-to-design.md
@@ -1,7 +1,6 @@
 <!-- This guide is heavily inspired by GitLab's own contributing guide for its design team. Kudos to them! -->
 
-Thank you for your interest in contributing to PeerTube's design. This guide details how
-to contribute in a way that is efficient for everyone.
+Thank you for your interest in contributing to PeerTube's design. Our team is building a software product, but we don't forget the core concept of that product still is to interact with people. Here's how you can help them better get along.
 
 ---
 
@@ -38,11 +37,16 @@ The project is still low on resources and no dedicated design team has been esta
 
 We care about [Open Source Design](http://opensourcedesign.net/goals/), and Open Design in general. Making the design process open is an important thing for us, as interfaces too can greatly impact the resulting software, in bad or good.
 
+It implies putting your files in the open and iterating to modify it with others until consensus. More specifically, it means dividing a given design problem in manageable parts, and track them [in public](issue-link) for us to help :smiley:.
+
+You might want to read some more here, although these are just hints:
+- http://opendesignkit.org/process/
+
 ### Suggested workflow
 
 1. See what you think about is being tackled by others on the [issue tracker](issue-link)
 1. Think of using pen & paper. High-end software isn't the goal. Design is.
-1. [Fork this project][fork-link] to your personal namespace. Or don't: it's just a suggested skeleton project to help you get started and structure your proposal.
+<!-- 1. [Fork this project][fork-link] to your personal namespace. Or don't: it's just a suggested skeleton project to help you get started and structure your proposal. -->
 1. Create a repository from your fork.
    - Be very descriptive of the changes you've made. The reviewer will have to manually merge them, which means they have to be aware of even the smallest changes as they could be easy to miss.
 1. Create an issue on [PeerTube's repository](issue-link).