Skip to content

Commit 5c85274

Browse files
authored
Merge pull request #418 from kenhys/fix-found-a-bug
Update contributing
2 parents be2cd59 + 9e2fbf6 commit 5c85274

File tree

1 file changed

+9
-9
lines changed

1 file changed

+9
-9
lines changed

views/contributing.erb

Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -19,13 +19,13 @@
1919
</p>
2020
<h3>Got a question or problem?</h3>
2121
<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.
2323
</p>
2424
<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>.
2626
</p>
2727
<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:
2929
<ul>
3030
<li>installed xxx plugin but it doesn't work. Why?</li>
3131
<li>Fluentd starts but logs are not sent to xxx. Am I wrong?</li>
@@ -34,23 +34,23 @@
3434
</p>
3535
<p>
3636
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.
3838
</p>
3939
<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.
4141
</p>
4242
<h3>Found a bug?</h3>
4343
<p>
4444
If you find a bug of Fluentd or a mistake in the documentation, you can help us by
4545
submitting an issue to Fluentd. Even better you can submit a Pull Request with a fix.
4646
</p>
4747
<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>
5050
</ul>
5151
<p>
5252
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.
5454
</p>
5555

5656
<h3>Patch Guidelines</h3>
@@ -59,7 +59,7 @@
5959
<ul>
6060
<li>Write tests</li>
6161
<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>
6363
</ul>
6464
</p>
6565
<p>

0 commit comments

Comments
 (0)