Page MenuHomePhabricator

Server-side upload request for Koavf
Closed, DeclinedPublicRequest

Description

Please upload the following file(s) to Wikimedia Commons:

My username is koavf. Thank you.

Please upload https://archive.org/details/the-black-watch_1929, as the film entered the public domain today.

Replaces T382853.

Event Timeline

The current max file size is 5GB (T191804).

Then this may need to be a child bug to a parent that is about increasing the max upload size so it can just be put on a list of files that could/would/should be uploaded when the max size is increased.

The current max file size is 5GB (T191804).

Then this may need to be a child bug to a parent that is about increasing the max upload size so it can just be put on a list of files that could/would/should be uploaded when the max size is increased.

Perhaps this task should be declined. It is unlikely we will increase the upload size further in the next 5-10 years, and i don't think it really makes sense to have server-side upload tasks just be waiting around in limbo that long.

The current max file size is 5GB (T191804).

Then this may need to be a child bug to a parent that is about increasing the max upload size so it can just be put on a list of files that could/would/should be uploaded when the max size is increased.

Perhaps this task should be declined. It is unlikely we will increase the upload size further in the next 5-10 years, and i don't think it really makes sense to have server-side upload tasks just be waiting around in limbo that long.

How does it not make sense? A to-do list can have items on it indefinitely and does it make *more* sense to make the same bug <var>x</var> years from now?

Personally i believe that such lists of files to upload when the limit increases should instead be on commons. There is probably thousands of such files, and their url might change in the next decade. Not to mention that this process might not even be the correct process in a decade's time (One certainly hopes in a decade upload by url would be stable enough that the upload would be done directly on commons).

I think it would be better to create a list on commons of all the very large files waiting to be imported. It would make it easier to sort through and maintain then potentially having thousands of tasks for files that we likely aren't going to be able to upload any time soon. Having all these tasks on phab that cannot be actioned on makes it difficult to see what work needs to be done in the present.

Personally i believe that such lists of files to upload when the limit increases should instead be on commons. There is probably thousands of such files, and their url might change in the next decade. Not to mention that this process might not even be the correct process in a decade's time (One certainly hopes in a decade upload by url would be stable enough that the upload would be done directly on commons).

I think it would be better to create a list on commons of all the very large files waiting to be imported. It would make it easier to sort through and maintain then potentially having thousands of tasks for files that we likely aren't going to be able to upload any time soon. Having all these tasks on phab that cannot be actioned on makes it difficult to see what work needs to be done in the present.

That sounds reasonable to me. Thanks.