Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update maintainers/approvers #107

Merged
merged 5 commits into from
Jun 12, 2020
Merged

Update maintainers/approvers #107

merged 5 commits into from
Jun 12, 2020

Conversation

reyang
Copy link
Member

@reyang reyang commented Jun 12, 2020

  • Updated the maintainers/approvers.
  • Aligned the doc structure with other SDK repo which is aligned with the overall guidance.
  • Fixed all the obvious GFM issues.
  • Changed the wording from C/C++ to C++ based on our decision that we're not going to provide C interface in this repo.

I will update the community repo after this PR.

CONTRIBUTING.md Outdated

Select an example of interest from the <a href="https://github.com/open-telemetry/opentelemetry-cpp/tree/master/examples"> examples folder </a>. Inside each example directory is a `BUILD` file containing instructions for Bazel. Find the binary name of your example by inspecting the contents of this `BUILD` file.
Select an example of interest from the [examples folder](https://github.com/open-telemetry/opentelemetry-cpp/tree/master/examples). Inside each example directory is a `BUILD` file containing instructions for Bazel. Find the binary name of your example by inspecting the contents of this `BUILD` file.
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It seems we are now very inconsistent with 1 space vs. 2 spaces.
Wish to get more perspectives before I try to make them consistent.

I personally vote for just having 1 space since it is easier to maintain.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

1 space looks good. Some Markdown editors (e.g. MS Word, for example) tend to insert double-space or even a space that's not 0x20 :)

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sweet, changed all the 2 spaces to 1 space.

@reyang reyang merged commit b395e1a into master Jun 12, 2020
@reyang reyang deleted the reyang/owner-and-doc-update branch June 12, 2020 17:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants