瀏覽代碼

Docs: Extended the reporting issues guide with the content from CONTRIBUTING.md.

Aleksander Nowodzinski 7 年之前
父節點
當前提交
3142ec6132
共有 1 個文件被更改,包括 7 次插入0 次删除
  1. 7 0
      docs/builds/guides/support/reporting-issues.md

+ 7 - 0
docs/builds/guides/support/reporting-issues.md

@@ -26,4 +26,11 @@ All issues should be reported in the [CKEditor 5 repositories](https://github.co
 
 Issues related to builds are usually caused by issues in the CKEditor 5 Framework components and plugins included in the build. You may report issues directly into the repositories that you think are related to them (like plugins) but, if you are unsure, the [`ckeditor5` issues page](https://github.com/ckeditor/ckeditor5/issues) should be used as the fallback place for any issue. The CKEditor 5 team will then move the issue to the right place or give you further instructions, if necessary.
 
+Things to keep in mind:
+
+* Search for existing issues before starting a new one. This helps our team to have the backlog in order.
+* Be concise and informative, making it easy for our team to understand the problem.
+* Do not use the issues pages for asking for help. The project has other {@link framework/guides/support/getting-support communication channels} for that purpose.
+* Feel free to jump into discussions around issues, exposing your opinion!
+
 Issues with third-party plugins should be reported directly to their developers.