-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
[Discussion]: Possible improvements to the upload queue management #5589
Comments
Great Idea ✨ to create a discussion channel |
After a lot of debugging and uploading a decent amount of pictures on Commons, this is the flow I observed (posting here for everyone's benefit) : (Just so everyone understands the reference, STATE_QUEUED means, the item will have a ‘Queued’ tag and STATE_IN_PROGRESS means, the item will have a non-started progress bar animation)
There are some issues with the pause and resume buttons as well, but since they are not a part of the given task, it would be better to discuss them here. (i) I suggest to set the state to STATE_IN_PROGRESS only when the item is currently being uploaded, that is to skip step 2 and go to step 3 directly. By, doing this, only the current item being uploaded will have a progress bar and the rest will have a Queued or Failed or Paused tag. This will create a standard upload flow, wherein only the item currently getting uploaded will have a progress bar and other items will have a 'Queued (N)' tag or 'Paused' or 'Failed' tag. Below, I have attached a rough flowchart of what an ideal flow should be, according to me : Suggestions and feedback regarding the above flow are more than welcome :) |
As discussed here, this issue aims to discuss the potential enhancements which can be made to the current upload queue management. If you have any questions about how the app should behave regarding the upload queue, please feel free to ask them here. By doing so, the maintainers won't have to answer the same questions repeatedly.
The text was updated successfully, but these errors were encountered: