-
Notifications
You must be signed in to change notification settings - Fork 2
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
[DEPR]: xqueue and xqueue-watcher #214
Comments
Hello! We use xqueue and xqueue-watcher in our on-campus instance of open edX. Our faculty won't be able to devote time to rewriting their problems for a new system until next summer, so we request that the deprecation be postponed until the 2024-12 named release. |
We have updated the acceptance date to October 2024 to accommodate migrations off xqueue problems that need to happen. |
@pdpinch would you be interested in being the owner for this ticket and helping to push it forward? We're trying to ensure that all active deprecation tickets have owners. |
@dianakhuang and @pdpinch I will be the owner for this with the goal of landing it for Sumac. An open question we had was whether MIT was using XQueue in any of the deployments they directly manage. |
@jristau1984 Our belief is that 2U are ready for this to DEPR to be finalized, please confirm that I have that right. This has been open for a minute, and we'd like to land it for Sumac to get if off the board. |
@e0d is the goal to have this accepted by Oct 10 (a ten week comment period)? or would you rather have a 2-week comment period, with Oct 10 being the earliest removal date? either way, as it's been a year since this was communicated, can you put quick update in that thread, x-post it again to #open-edx-proposals, and then mark this as Communicated ? |
I've updated the acceptance date to be August 15th. So everyone should comment ASAP. As Kyle notes, this has been for about a year. |
@e0d - We have the same belief as you about 2U's use of xq, but I have tasked the team to confirm that belief before your Aug 15 target date. Thanks! |
MIT has four active courses on edx.org using xqueue graders. |
@shellyu Can you share which courses and when they run through? |
Additionally, MIT is still using xqueue in our on-campus instance. |
MIT's courses on edx.org: Last I heard there was at least one other edx partner using xqueue, so if edx signed off on this and missed our four courses, they may want to review other partners who might not see this DEPR. |
@NotoriousMKD Are there any plans to migrate off of XQueue for oncampus grading? I was under the impression there was a move to migrate to TurnItIn, for example. |
@e0d we were considering other tools at one point, but plans to migrate off of xqueue for on-campus use are on hold. |
A few more comments and questions that have come up since last we discussed this deprecation
|
Thanks @NotoriousMKD and @pdpinch this is helpful input. As you probably know, we're trying to rationalize the maintenance of the software platform. Prior input suggested XQueue was a good candidate for deprecation. However, we don't want to remove a feature that is important and will circle back and discuss other approaches. |
Proposal Date
2023-08-08
Target Ticket Acceptance Date
2024-08-15
Earliest Open edX Named Release Without This Functionality
Sumac release, October 2024
Rationale
xqueue is an application for managing queued tasks in edx-platform LMS. It primarily supports two use cases, one of which has already been deprecated:
Certificate creation was already deprecated and removed when the edx-certificates repository was archived as part of DEPR-155.
Grading of student-submitted code, for which there are two well-known clients:
xqueue-watcher is an xqueue client for running and evaluating student-submitted code.
Maintaining and updating two different applications to serve one uncommon use case is not the best user of resources – in particular when there are many more-functional alternatives that are under active development.
Removal
Replacement
Deprecation
No response
Migration
No response
Additional Info
No response
The text was updated successfully, but these errors were encountered: