-
Notifications
You must be signed in to change notification settings - Fork 255
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
project onboarding: Developer Experience SIG #2189
Comments
Thanks @svrnm ! |
Do each of these just require opening a community repo issue? Aside from finding a meeting time. Which I guess I'll just use a regular doodle for. |
We can work on them here if possible but some might require a dedicated issue, eg the teams&repo setup |
Created https://github.com/orgs/open-telemetry/projects/105/ @svrnm how do I make get it public? |
@open-telemetry/technical-committee @austinlparker @trask can one of you set the project board shared above to public? Thanks |
@tsloughter you should be able to make it public yourself now, can you double check (cc @danielgblanco) |
@svrnm are you able to create a repo? We need one for hosting/tracking discussions. I hope to update sig.yml soon but waiting participants final opinion on meeting time. |
No, I can not, we need to raise an issue for that (repo management), see #2191 for an example. I can create that for you, or you just go ahead and do it
Sure! You could add it already without meeting hours, depending on how long it will take for that to be finalized The slack channel still needs to be renamed? |
Yea, still waiting on a slack channel rename. I'll poke people about that today. |
I've created the EU meeting as well as [email protected]. |
Created the NA meeting |
Created repository and teams. |
thanks all, last thing missing is to also update the project file at https://github.com/open-telemetry/community/blob/main/projects/developer_experience.md |
With #2144 merge, the Developer Experience SIG can be onboarded, here are the TODOs to get them started:
@tsloughter @austinlparker @tedsuo @lmolkova @dmathieu @julianocosta89 @martinjt @samsp-msft @stevejgordon
The text was updated successfully, but these errors were encountered: