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.

Sign up for GitHub

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

Jump to bottom

Improve contributing guide to clarify the workflow on issues #1948

Open
tigrannajaryan opened this issue Sep 21, 2021 · 0 comments
Open

Improve contributing guide to clarify the workflow on issues #1948

tigrannajaryan opened this issue Sep 21, 2021 · 0 comments
Labels
needs discussion Need more information before all suitable labels can be applied spec:miscellaneous For issues that don't match any other spec label

Comments

@tigrannajaryan
Copy link
Member

We need to make it clear how the spec issues are worked on. The contributing guide currently is silent about it. We auto-assign issues to TC members but it is not clear what are the expected next steps after that.

See the comment here that raises this problem: open-telemetry/community#837 (comment)

I posted some preliminary thoughts on how we can approach this here: open-telemetry/community#837 (comment)
@tigrannajaryan tigrannajaryan added the spec:miscellaneous For issues that don't match any other spec label label Sep 21, 2021
@tigrannajaryan tigrannajaryan mentioned this issue Sep 21, 2021
Closed
@tigrannajaryan tigrannajaryan added the needs discussion Need more information before all suitable labels can be applied label Sep 21, 2021
@tigrannajaryan tigrannajaryan mentioned this issue Sep 24, 2021
Closed
@SergeyKanzhelev SergeyKanzhelev removed their assignment Feb 18, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
needs discussion Need more information before all suitable labels can be applied spec:miscellaneous For issues that don't match any other spec label
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@tigrannajaryan @SergeyKanzhelev