Decentralizing the Python members #268
Conversation
README.md
Outdated
| @@ -4,6 +4,24 @@ | |||
| [gitter-image]: https://badges.gitter.im/open-telemetry/opentelemetry-python.svg | |||
| [gitter-url]: https://gitter.im/open-telemetry/opentelemetry-python?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge | |||
|
|
|||
| We hold regular meetings. See details at [community page](https://github.com/open-telemetry/community#python-sdk). | |||
There was a problem hiding this comment.
Seems like we could move this out of the community repo too.
There was a problem hiding this comment.
mmm, shouldn't that be "python SIG" instead of "python SDK"?
There was a problem hiding this comment.
It should, but "SDK" had a different meaning when that doc was first written. We can fix that here by just moving the content into this doc.
There was a problem hiding this comment.
I go back and forth. It's a little nice to see all the meetings in one list. It's not always evident what meetings do or do not occur.
There was a problem hiding this comment.
I agree with @toumorokoshi. I like seeing a list of all meetings and details in one place. With that being said, we can change python-sdk to python-sig in the community repo.
There was a problem hiding this comment.
We could put it in both places. It seems a bit ridiculous to direct people to the community repo when we could just say "every thursday at 8AM PT" here.
open-telemetry/community#233 also says we ought to move the meeting schedule here:
Similarly, the SIG information (schedule of meetings, etc.) can be also moved from the README in this repo to the READMEs in the respective repos. This repo will only have the links to information.
README.md
Outdated
| @@ -4,6 +4,24 @@ | |||
| [gitter-image]: https://badges.gitter.im/open-telemetry/opentelemetry-python.svg | |||
| [gitter-url]: https://gitter.im/open-telemetry/opentelemetry-python?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge | |||
|
|
|||
| We hold regular meetings. See details at [community page](https://github.com/open-telemetry/community#python-sdk). | |||
There was a problem hiding this comment.
I go back and forth. It's a little nice to see all the meetings in one list. It's not always evident what meetings do or do not occur.
|
@c24t The javascript and .NET repositories both have this information in their READMEs. I feel like it's good to be consistent. With that being said, you're right about the awkward placement at the top of the repo. I'll put this in the "contributing" section in the README just like what js is doing. |
README.md
Outdated
| @@ -77,6 +77,24 @@ for a complete example. | |||
|
|
|||
| See [CONTRIBUTING.md](CONTRIBUTING.md) | |||
|
|
|||
| We hold regular meetings. See details at [community page](https://github.com/open-telemetry/community#python-sdk). | |||
There was a problem hiding this comment.
Here's what I would write here to replace the content on the community page:
We meet weekly on Thursday at 8AM PT. The meeting is subject to change depending on contributors' availability. Check the OpenTelemetry community calendar for specific dates.
Meetings take place via Zoom video conference: https://zoom.us/j/6729396170.
Meeting notes are available as a public Google doc. For edit access, get in touch on Gitter.
Part of open-telemetry/community#233