As part of our effort to increase our contributions to the Open edX Blog, I would like us to prepare a series of blog posts about the edX Blended Projects we have been working on in the past year.
I thought I’d ask epic owners for Blended projects to prepare a blog post about their respective projects. Furthermore, I think we should enlist someone from edX (who is/was involved in the project) to help co-write each article, and publish it as a joint effort. I think we can publish about projects that are both completed and still in progress.
I’ve offered Ned a tech talk about the LTI project in the community meetup once this project is delivered. And I’m in to write a blog post for the ORA changes.
Thanks for getting back @giovannicimolin. Can you please create a ticket for the ORA blog post, and add me as 2nd reviewer? For LTI, that’s also great! Maybe we can also schedule a short blog post to summarize the project and provide a link to the recording of your talk?
@gabriel Are you also referring to the SQL grader XBlock? (SE-2957). I haven’t seen it referred to as „blended project“ before. We could write about it though it’s a small change we did, and it doesn’t reach as many people as the other projects in the „blended projects“ list.
Or maybe you wanted to ping @Agrendalath instead, since he owns some projects in that list.
You’re right; I was referring to SE-2957 but indeed this wasn’t really a blended dev project. But yes, we should definitely write about it in a blog post
I created SE-4299, could you check the epic/account?
How do we synchronize with edX to write about this? Since the request seems to come from us, do we need to ask for permission?
I’d prefer to let some time pass because the code is being reviewed this+next sprint.
Note that the changes we did are small, and this XBlock is very specific (it’s the type of block that you would only need in courses about SQL).
Sorry as well @gabriel, forum pings don’t show up in my inbox with the filters I setup when we first started using it. I’ve adjusted these since the forum has become quite a bit more important now.
I’m open to contributing here for BD-27 certainly, though I’m not sure how it would best fit in. CC2OLX is more self-contained than some of the other blended projects, as it’s a standalone tool.
Though we could still write a blog post describing the tool, it’s origins and development if that would be appealing?
@gabriel, I was off. I think it’s a good idea, and I’m up to writing such a post once BD-14 is delivered. Thing is, the project is currently paused, and will only be restarted on Q3 this year: it’ll be a little while.
On the other hand, I believe Kyle and/or Marco will enjoy contributing to the post, so there’s that.
@daniel thanks for creating a ticket, the account is the right one. It would be good to reach out to Mike yes, and ask if he can either co-author the post, or at least review it and give it the . And sure, it’s fine to wait a few weeks. We could aim to publish this in May?
And IMO it’s fine to do this even if the changes are small/specific. The post doesn’t need to be super long, and it can be very technical if you like it that way. Up to you! If it’s very technical, Open edX may choose not to publish it on their blog, but then we’ll publish it on our blog only, and that’s ok.
@josh yep, that would be great! It’s fine if this project is more self-contained; a summary like you described sounds good. Can you create ticket(s) to do this? Doesn’t need to be right away, but maybe start by reaching out to people edX to see if someone wants to co-author, or at least review your work?
My apologies @adolfo, I should have checked! Sounds good, and thanks for creating a ticket. I’ll follow-up with you on this later this year.
Ah yep, I created the ticket (BB-4057) but didn’t ping back here.
I put it under the account for BD-27 for now, but should we move the account to marketing?
I think it’s a good idea, and I’m up to writing such a post once BD-14 is delivered. Thing is, the project is currently paused, and will only be restarted on Q3 this year: it’ll be a little while.
. And sure, it’s fine to wait a few weeks. We could aim to publish this in May?