|
19 | 19 | </p> |
20 | 20 | <h3>Got a question or problem?</h3> |
21 | 21 | <p> |
22 | | - Resources of <a href="http://www.fluentd.org">Official site and <a href="http://docs.fluentd.org">Fluentd documentation</a> may help you. |
| 22 | + Resources of <a href="https://www.fluentd.org">Official site and <a href="https://docs.fluentd.org">Fluentd documentation</a> may help you. |
23 | 23 | </p> |
24 | 24 | <p> |
25 | | - If you have further questions about Fluentd and plugins, please direct these to <a href="https://github.com/fluent/fluentd/discussions">Forum</a>. |
| 25 | + If you have further questions about Fluentd and plugins, please direct these to <a href="https://github.com/fluent/fluentd/discussions/categories/q-a">Q & A category in GitHub Discussions</a>. |
26 | 26 | </p> |
27 | 27 | <p> |
28 | | - Don't use Github issue for asking questions. Here are examples: |
| 28 | + Don't use GitHub issue for asking questions. Here are examples: |
29 | 29 | <ul> |
30 | 30 | <li>installed xxx plugin but it doesn't work. Why?</li> |
31 | 31 | <li>Fluentd starts but logs are not sent to xxx. Am I wrong?</li> |
|
34 | 34 | </p> |
35 | 35 | <p> |
36 | 36 | We may close such questions to keep clear repository for developers and users. |
37 | | - Github issue is mainly for submitting a bug report or feature request. See below. |
| 37 | + GitHub issue is mainly for submitting a bug report or feature request. See below. |
38 | 38 | </p> |
39 | 39 | <p> |
40 | | - If you can't judge your case is a bug or not, use mailing list or slack first. |
| 40 | + If you can't judge your case is a bug or not, use slack first. |
41 | 41 | </p> |
42 | 42 | <h3>Found a bug?</h3> |
43 | 43 | <p> |
44 | 44 | If you find a bug of Fluentd or a mistake in the documentation, you can help us by |
45 | 45 | submitting an issue to Fluentd. Even better you can submit a Pull Request with a fix. |
46 | 46 | </p> |
47 | 47 | <ul> |
48 | | - <li><b>Fluentd</b>: Use <a href="https://github.com/fluent/fluentd">Fluentd</a> repository. Fill issue template.</li> |
49 | | - <li><b>Documentation</b>: Use <a href="https://github.com/fluent/fluentd-docs-gitbook">Fluentd-Docs</a> repository.</li> |
| 48 | + <li><b>Fluentd</b>: Use <a href="https://github.com/fluent/fluentd">Fluentd</a> repository. Fill <a href="https://github.com/fluent/fluentd/issues/new?template=bug_report.yml">issue template</a>.</li> |
| 49 | + <li><b>Documentation</b>: Use <a href="https://github.com/fluent/fluentd-docs-gitbook">Fluentd-Docs</a> repository. Fill <a href="https://github.com/fluent/fluentd-docs-gitbook/issues/new?template=bug_report.yml">issue template</a>.</li> |
50 | 50 | </ul> |
51 | 51 | <p> |
52 | 52 | If you find a bug of 3rd party plugins, please submit an issue to each plugin repository. |
53 | | - And use <a href="https://github.com/fluent-plugins-nursery/fluent-package-builder">fluent-package-builder</a> repository for td-agent releated issues. |
| 53 | + And use <a href="https://github.com/fluent-plugins-nursery/fluent-package-builder">fluent-package-builder</a> repository for fluent-package releated issues. |
54 | 54 | </p> |
55 | 55 |
|
56 | 56 | <h3>Patch Guidelines</h3> |
|
59 | 59 | <ul> |
60 | 60 | <li>Write tests</li> |
61 | 61 | <li>Run tests before send Pull Request by <i>bundle exec rake test</i></li> |
62 | | - <li>Write a <a href="http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html">good commit message</a></li> |
| 62 | + <li>Write a <a href="https://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html">good commit message</a></li> |
63 | 63 | </ul> |
64 | 64 | </p> |
65 | 65 | <p> |
|
0 commit comments