You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+14Lines changed: 14 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -21,6 +21,20 @@ for general information about the project.
21
21
After making any changes to .proto files make sure to generate all
22
22
implementation by running `make gen-all`.
23
23
24
+
## Style-Guide
25
+
26
+
OpenTelemetry follows the [protocol buffer style guide](https://protobuf.dev/programming-guides/style/) with the following clarifications:
27
+
28
+
- All Messages and fields should be documented via comments.
29
+
- Field comments should document purpose or behavior with active verbs, or
30
+
a simple definition noun phrase (similar to a dictionary entry).
31
+
- valid: "Represents ..."
32
+
valid: "Additional attributes that describe the scope."
33
+
- not-valid: "used to represent..."
34
+
- Message and field comments may reference the field or message by name.
35
+
- valid: "AnyValue ..."
36
+
- valid: "The value ..."
37
+
24
38
## Further Help
25
39
26
40
If you have any questions or need assistance while contributing, feel free to reach out to the [`#otel-specification`](https://cloud-native.slack.com/archives/C01N7PP1THC) Slack channel.
0 commit comments