Docs: Add community section to readme #2305
Conversation
Signed-off-by: Kyle J. Davis <[email protected]>
|
|
||
| If you're interested in contributing, thank you! | ||
| - [Join on Meetup](https://www.meetup.com/bottlerocket-community/) to hear about the latest Bottlerocket (virtual/in-person) events and community meetings. The [next community meeting is August 24, 2022](https://www.meetup.com/bottlerocket-community/events/287425423/). |
There was a problem hiding this comment.
Do we want to include specific dates here? That would mean we need to make sure to regularly update the README.
I think it may be better to just drop the last sentence, or state something about seeing the Meetup page for upcoming meeting details.
There was a problem hiding this comment.
How about a link to a COMMUNITY-MEETINGS.md file (containing a table of all past and planned community meetings?)
Or a GitHub Discussions thread made for announcing the community meetings?
There was a problem hiding this comment.
I like the idea of a Discussion thread. That increases the ways someone might discover our community meeting. And someone could follow that for any other updates we would want to post related to community meetings.
There was a problem hiding this comment.
Great question @stmcginnis. Typically, I wouldn't add short lived information to a readme, however this is a stop gap to advertise the current community meeting given that the repo is our only stable URL at the moment.
Long term, we have a website in-process and that's where this kind of information would go after it's established.
Given that I'm going to be directing a lot of folks from upcoming events to this repo, I wanted to make sure there is a link directly to the next community meeting.
Signed-off-by: Kyle J. Davis [email protected]
Issue number: N/a
Description of changes: Small refactor of
Contact Ussection and addition ofParticipate in the Communityto add note about meetup.Testing done: eyeballs 👀
Terms of contribution:
By submitting this pull request, I agree that this contribution is dual-licensed under the terms of both the Apache License, version 2.0, and the MIT license.