-
Notifications
You must be signed in to change notification settings - Fork 18
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
Community driven periodic OSDC Newsletter #1
Comments
The newsletter approach feels like a really great idea to go with. |
@shermix That's a nice inclusion too. Curated and recommended reads worth your time . . . which don't come under current happenings ig |
Is there any way to make the newsletter collaborative? Or will there be a maintainer who handles framing and sending it periodically? Any plans regarding it? |
@sidntrivedi012 I believe the collaboration would be standard through github issue/pr/comments like how blogs are added to osdc/blog. Anyone would be free to drop in recommendations through comments or reviews. Regarding handling the framing, I believe it would be great if for each period a particular member volunteer to handle and frame it, this way it wouldn't be a burden to a single person as well diversify the content in each period. These are just my initial plans. I'm open to suggestions. |
We talk and discuss about a lot of stuff in the community chat or meetups but many of us tend to miss out on it due to various reasons like too many things to follow up, time constraints etc. This newsletter would act as a medium to compile and share various information regarding the various happenings in and around FOSS and OSDC. The newsletter doesn't necessarily need to be constrained to regular information but can be used to highlight various achievements by various community members.
Some of the things which may be included in the newsletter include
This list is not exhaustive. If you have any suggestion please comment down below, I will be happy to discuss and include more stuff here.
The text was updated successfully, but these errors were encountered: