-
Notifications
You must be signed in to change notification settings - Fork 182
Conversation
Would like to help @tedsuo! Thx for kicking this off. |
Same here! Thanks for the kick off.
|
Hi I'm interested in shaping the documentation of the general API and the C/C++ and Python implementations. |
I'm interested in contributing. |
Cannot currently commit to membership but happy to review changes and comment/submit things. Been working on the Jaeger C++ docs and trying to ask clarifying questions on the opentracing c++ docs. |
I'm interested in contributing. |
Awesome! I'll leave this issue open till the end of the week, and begin organizing on Monday. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM aside from my one comment here.
project_organization.md
Outdated
@@ -55,6 +55,27 @@ OTIAB members have the following primary responsibilities: | |||
- Provide feedback about possible priorities and/or specific proposals from the OTSC | |||
- Represent OpenTracing’s interests within their own organizations | |||
|
|||
## Documentation Working Group | |||
|
|||
The OpenTracing community is growing rapidly, moving from a tight-knit group of early adopters to a larger group of developers. In order to support this transition, the Documentation Working Group is tasked with codifying the existing knowledge base into proper documentation which can be easily accessed via the OpenTracing website. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Seems like the "documentation working group" is something that will always exist (i.e., it's not transitional). This paragraph feels like a great thing for the PR description, but for this actual .md
file I'd rather just describe what the doc working group is without referring to the point in time when this paragraph happened to be added to the .md
file. E.g., maybe rewrite to be just the following:
The Documentation Working Group codifies and maintains the existing knowledge base as proper documentation which can be easily discovered via the OpenTracing website.
?
I've merged this PR, and the working group is now created! I've invited everyone who responded in this issue to the working group gitter channel, and created a document for brainstorming an agenda. We will discuss meeting formats on gitter and schedule an initial working group session. Gitter Channel: Agenda Proposals: Cheers, |
Documentation Working Group
The OpenTracing community is growing rapidly, moving from a tight-knit group of early adopters to a larger group of developers. In order to support this transition, the Documentation Working Group is tasked with codifying the existing knowledge base into proper documentation which can be easily accessed via the OpenTracing website.
Documentation Projects
Responsibilities
Initial agenda for Working Group sessions
Initial Membership
If you are interested in joining this Working Group, please let @tedsuo know or reply below.