**What do we want to solve?**
At the moment, there is a lot of bad experiences where communities are not engaged the best way. But we also know good experiences. We all want to prevent all bad experiences which can happen during a development process, and make both users and development teams happy. Users have expectations that we should respect, but developers have the same.
The idea is to create "10 tips" guide of good relations between users and developers, in both ways. This should be a pillar on the relations we create.
**How can we do that?**
[*] in November, CL define a plan
[*] in December, internal consultation of CE members and engineering to gather their good and bad experience when they engage communities, and gather feedback about how communities work (philosophy, culture, involvement, how do they deal with change...)
[*] in January, at Dev Submit, discuss about how development teams engage communities, collect feedback and interact (80 minutes long discussion - Thursday@11:30am)
[] in January, later, involve users
[] Later, publish "10 tips" as global principles.
"10 tips" defines a global idea: have a short, comprehensive and easy to remind text. Ideally with 10 items max.
**Existing resources**:
* https://outreach.wikimedia.org/wiki/Best_practices_for_reaching_out_to_projects_in_multiple_languages
* https://meta.wikimedia.org/wiki/Best_practices_for_working_with_community_members
* https://www.mediawiki.org/wiki/Community_Engagement_%28Product%29/Collaboration_process/Draft
* ...