Starting this week we’ll be publishing a monthly newsletter to all of our contacts. Click here for a preview of our first edition
Each newsletter will feature a “News” section where we discuss the latest news from the Open edX world.
Please use this thread to share any info that could be worthy of adding to that section for an upcoming newsletter. Each month we’ll share our ideas for the upcoming newsletter and we’ll ask for your input.
For reference, here are the news for the first edition:
The 10th Open edX release will be called Juniper and is now around the corner. The Release Candidate 1 has been cut this week and the release working group is now targeting May 21st for the release.
LTI 1.3 is being worked on by us and edX. In addition to the privacy and security benefits, LTI 1.3 has a more straightforward upgrade path than other versions and the full support and endorsement of major platform providers.
Nice!
The first edition of the newsletter looks amazing!
I’ll just throw random ideas here for the next ones:
Feature our blog posts
Take active discussions from the community group or discuss.openedx.org, write a brief intro and invite the audience to participate.
Link some tutorials/courses on improving and making course content
Check in with a few clients which we done custom work for and feature that work and it’s impact on the learners? (from simple things such as the custom auth for Lumerical to the big projects like LabXChange, HMS, and Yonkers)
Also, not exactly in the scope of the newsletter, but we might want to make a marketing campaign to launch the new Ocim user console (after we finish fixing all the bugs though ). I’ll ping about this on the epic when it’s time.
We are compiling our May newsletter and wanted to check in on some of the the latest news from the Open edX world. What have you been reading this month? Any exciting industry updates?
For easy reference, what we included in the April newsletter is noted above in @gabriel’s note.
I am preparing our June newsletter and wanted to check in on some of the the latest news. There’s a few nice topics that we can share this month. I thought I’d go with:
Details about edX projects we’re working on
Juniper release
Launch of the core committers program
Featured blog posts
Any additional suggestions? Or maybe suggestions for next month? Thanks!
We’ll have the video updated by Nordik, given the feedback provided in the thread, so it won’t be ready in time for the July newsletter. It would be a good candidate for the August newsletter though.
Maybe add a point giving an update on the core committers program? @braden would you be willing to write a couple of sentences for that update, including stats about our own participation to the program?
@gabriel Another point that could be worth mentioning in the newsletter is the fact that Open edX has re-affirmed a decision to cut more predictable 6 month releases (cf threads on forum - including a recent post from Ned proposing dates for the cut and release of Koa).
The time has come once again! This month will be short, since there was 2-3 weeks of Holidays where things were slower. Here’s what I had planned on publishing in our upcoming newsletter:
Mention the fact that we have opened our forum to the public, and link to it (we should also add a link from our website, actually?)
Ask the readers to submit their own items for the next newsletter - which could be done in the current thread, since it is public
Ask for feedback & suggestions about OpenCraft in general? Our services, what they are happy with, what we could do better… We could invite readers to reply directly to the email?
@adolfo You might also have a few points, about the different working groups for example?
And another suggestion - it would be worth posting the news section from the newsletter in a blog post, each month? It’s a really useful bit by itself, it would give people visiting our site an overview of it.
And we could also encourage people to subscribe to the newsletter there – by mentioning that this is sent every month as part of the newsletter, and include a call to action in that blog post, pointing to the newsletter registration.
Good idea. I’ll be glad to contribute a couple of paragraphs on the built-test-release and community groups. @gabriel, how does this usually work? Would I write directly on the draft?