Skip to content

Commit 042ac63

Browse files
committed
docs: translated contributing/issues into ja
1 parent 2291fd8 commit 042ac63

File tree

1 file changed

+94
-0
lines changed

1 file changed

+94
-0
lines changed
+94
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,94 @@
1+
---
2+
title: イシュー
3+
description: 既存イシューの修正方法、またはバグ、セキュリティ、潜在的な改善の報告方法
4+
weight: 10
5+
_issues: https://github.com/open-telemetry/opentelemetry.io/issues
6+
_issue: https://github.com/open-telemetry/opentelemetry.io/issues?q=is%3Aissue+is%3Aopen+sort%3Aupdated-desc+label%3A
7+
default_lang_commit: 01d3e2eee9798dfa7c4a36425621849a2a37e489
8+
cSpell:ignore: prepopulated
9+
---
10+
11+
## 既存のイシューの修正
12+
13+
OTel を改善するための最も良い方法の 1 つは、既存のイシューを修正することです。
14+
15+
1. [issues]({{% param _issues %}}) のリストを参照してください。
16+
2. 作業したいイシューを選択してください。短時間で修正できるものが理想です。
17+
18+
<!-- prettier-ignore -->
19+
<a name="first-issue"></a>
20+
{{% alert title="最初のコントリビュートですか?" %}}
21+
22+
以下のラベルのイシューを選択してください。
23+
24+
- [Good first issue]
25+
- [Help wanted]
26+
27+
<!-- prettier-ignore -->
28+
> **NOTE**: メンターシップやオンボーディングプロセスの一部でない限り、私たちは、[OpenTelemetry organization][org] にまだコントリビュートしたことがない人に**イシューをアサインしません**
29+
{.mt-3}
30+
31+
<!-- prettier-ignore -->
32+
[good first issue]: {{% param _issue %}}%22good+first+issue%22
33+
[help wanted]: {{% param _issue %}}%3A%22help+wanted%22
34+
[org]: https://github.com/open-telemetry
35+
36+
{{% /alert %}}
37+
38+
3. イシューにコメントがある場合、内容を読んでください。
39+
4. このイシューがまだ関係あるかをメンテナーに尋ね、明らかにしたい質問がある場合はイシューにコメントを投稿して質問してください。
40+
5. この旨のコメントを追加して、問題に取り組む意向を共有してください。
41+
6. イシューの修正に取り組みましょう。問題が発生した場合は、メンテナーに知らせてください。
42+
7. 準備ができれば、[プルリクエストを通じてあなたの作業を提出してください](../pull-requests)
43+
44+
## イシューの報告
45+
46+
エラーに気が付いたり既存の内容に改善を提案したい場合は、イシューを開いてください。
47+
48+
1. Click the **Create documentation issue** link on any document. This redirects
49+
you to a GitHub issue page prepopulated with some headers.
50+
2. Describe the issue or suggestion for improvement. Provide as many details as
51+
you can.
52+
3. Click **Submit new issue**.
53+
54+
After submitting, check in on your issue occasionally or turn on GitHub
55+
notifications. It might take a few days until maintainers and approvers respond.
56+
Reviewers and other community members might ask questions before they can take
57+
action on your issue.
58+
59+
## Suggesting new content or features
60+
61+
If you have an idea for new content or a feature, but you aren't sure where it
62+
should go, you can still file an issue. You can also report bugs and security
63+
vulnerabilities.
64+
65+
1. Go to
66+
[GitHub](https://github.com/open-telemetry/opentelemetry.io/issues/new/) and
67+
select **New issue** inside the **Issues** tab.
68+
69+
1. Select the type of issue that best applies to your request or doubt.
70+
71+
1. Fill out the template.
72+
73+
1. Submit the issue.
74+
75+
### How to file great issues
76+
77+
Keep the following in mind when filing an issue:
78+
79+
- Provide a clear issue description. Describe what specifically is missing, out
80+
of date, wrong, or needs improvement.
81+
- Explain the specific impact the issue has on users.
82+
- Limit the scope of a given issue to a reasonable unit of work. For problems
83+
with a large scope, break them down into smaller issues. For example, "Fix the
84+
security docs" is too broad, but "Add details to the 'Restricting network
85+
access' topic" is specific enough to be actionable.
86+
- Search the existing issues to see if there's anything related or similar to
87+
the new issue.
88+
- If the new issue relates to another issue or pull request, refer to it either
89+
by its full URL or by the issue or pull request number prefixed with a `#`
90+
character. For example, `Introduced by #987654`.
91+
- Follow the
92+
[Code of Conduct](https://github.com/open-telemetry/community/blob/main/code-of-conduct.md).
93+
Respect your fellow contributors. For example, "The docs are terrible" is not
94+
helpful or polite feedback.

0 commit comments

Comments
 (0)