Last modified: 2014-07-10 19:17:24 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T69344, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 67344 - Add mochila_images.s3.amazonaws.com to the wgCopyUploadsDomains whitelist
Add mochila_images.s3.amazonaws.com to the wgCopyUploadsDomains whitelist
Status: RESOLVED FIXED
Product: Wikimedia
Classification: Unclassified
Site requests (Other open bugs)
wmf-deployment
All All
: Unprioritized normal (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-07-01 01:19 UTC by Ayaita
Modified: 2014-07-10 19:17 UTC (History)
7 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Ayaita 2014-07-01 01:19:52 UTC
please add the following domain(s) to the wgCopyUploadsDomains whitelist:

This is an example: 

https://www.dropbox.com/sh/qziqxh4fs2id69d/AACf_EBbByO6-GeoZbfRotr3a/10_LagoAlajuela.jpg
Comment 1 This, that and the other (TTO) 2014-07-01 03:09:24 UTC
What? Dropbox? We're not going to add that. What exactly do you want this for?
Comment 2 Ayaita 2014-07-01 03:29:09 UTC
Why do you want to know if you are already saying you are not adding it?

I am not a super tech savvy user and don't know what you mean by "what? Dropbox?" 

I am trying to use the GWToolset to mass upload pictures to Commons.  We don't have the pictures online and the only alternative we found was to upload them to a dropbox folder.  Then, when using the GWToolset we noticed the white list of domains and this led me to make this request, as suggested here:
http://gwtoolset.wmflabs.org/wiki/Special:GWToolset
Comment 3 jeremyb 2014-07-01 03:34:37 UTC
You'll need to find some other place to upload to. A good option may be an amazon s3 bucket. It needs a dedicated domain name that no other user can upload content to.

Or else why even bother maintaining a whitelist at all? Dropbox would defeat the purpose.
Comment 4 jeremyb 2014-07-01 03:39:42 UTC
Anyway, also answer the other question. What is this for?

Ate you uploading on behalf of an organization? Which one?

What is the source of these images? Did you take them yourself?
Comment 5 Ayaita 2014-07-01 03:45:34 UTC
It's an institutional project, and the pictures are from different institutions that have released them with CC-BY and CC-BY-SA. We are still working on the templates but it's more or less described here:
https://commons.wikimedia.org/wiki/Commons:AlmanaqueAzul
Comment 6 Ayaita 2014-07-01 03:48:06 UTC
Once I use the s3 bucket, do I need to fill another bug report to add the domain from s3bucket to the white list?
Comment 7 jeremyb 2014-07-01 03:50:01 UTC
Just comment on this bug with the bucket's name/domain.
Comment 8 Ayaita 2014-07-01 03:55:27 UTC
thanks, will do
Comment 9 This, that and the other (TTO) 2014-07-01 05:47:07 UTC
(In reply to Ayaita from comment #2)
> Why do you want to know if you are already saying you are not adding it?

I wanted to know so I would be able to suggest an alternative. I see that Jeremy has already done that.

> I am not a super tech savvy user and don't know what you mean by "what?
> Dropbox?" 

Dropbox is a filesharing service usable by anyone. (I was assuming you knew this, since you included a Dropbox URL in the bug description.) Anyone can upload there, so it makes no sense to add it to our whitelist.
Comment 10 Ayaita 2014-07-01 06:18:04 UTC
(In reply to This, that and the other from comment #9)
> (In reply to Ayaita from comment #2)
> > Why do you want to know if you are already saying you are not adding it?
> 
> I wanted to know so I would be able to suggest an alternative. I see that
> Jeremy has already done that.

It was not clear that your "what? dropbox?" answer meant that. Please be more aware of different type of users next time, 

> 
> > I am not a super tech savvy user and don't know what you mean by "what?
> > Dropbox?" 
> 
> Dropbox is a filesharing service usable by anyone. (I was assuming you knew
> this, since you included a Dropbox URL in the bug description.) Anyone can
> upload there, so it makes no sense to add it to our whitelist.

You were assuming things and I assumed things too.  See, in that whitelist Flickr is listed, and to me, Flickr is a filesharing service usable by anyone.
Comment 11 jeremyb 2014-07-01 07:15:56 UTC
(In reply to Ayaita from comment #10)
> See, in that whitelist
> Flickr is listed, and to me, Flickr is a filesharing service usable by
> anyone.

AIUI, there is one shared whitelist for multiple uses.

IIRC, Flickr was on that list long before there was a GWToolset. (I think for a while Flickr was the only member of the list) Flickr is much different from Dropbox for 2 reasons (in general, not specifically in relation to GWToolset):

* there are no arbitrary file uploads; files must be one of a few limited types of media (right?) and the site provides methods for recording various metadata on a per-file basis (including license)
* we have processes specifically for dealing with Flickr including a bot that follows up on Flickr uploads soon after upload and verifies that the metadata at Flickr matches the file description page. AFAIK, no such comparison would be possible with dropbox; there would be nothing to compare against.

GWToolsat may also have some hardcoded special casing for Flickr, I'm not sure.
Comment 12 Ayaita 2014-07-04 16:25:06 UTC
Hi, we finally uploaded the pictures to S3 bucket, this is an example URL:

http://s3.amazonaws.com/mochila_images/02050019.jpg

The bucket's name is: 
mochila_imagenes_import_1  

I appreciate if this can be added to the GWToolset whitelist.
Comment 13 jeremyb 2014-07-04 16:34:51 UTC
(In reply to Ayaita from comment #12)
> http://s3.amazonaws.com/mochila_images/02050019.jpg

So you can use:
http://mochila_images.s3.amazonaws.com/02050019.jpg

> The bucket's name is: 
> mochila_imagenes_import_1

So, now I'm confused. Is it mochila_images or mochila_imagenes_import_1 ?
Comment 14 Ayaita 2014-07-04 17:19:18 UTC
(In reply to jeremyb from comment #13)
> (In reply to Ayaita from comment #12)
> > http://s3.amazonaws.com/mochila_images/02050019.jpg
> 
> So you can use:
> http://mochila_images.s3.amazonaws.com/02050019.jpg
> 
> > The bucket's name is: 
> > mochila_imagenes_import_1
> 
> So, now I'm confused. Is it mochila_images or mochila_imagenes_import_1 ?

I'm sorry, my bad. 

mochila_imagenes_import_1 is the name of the main bucket.  Inside it, we created two buckets of images (and plan to add more later to better control different groups of images):
mochila_images
mochila_images2

The example url sent before is inside mochila_images 

I hope this clarifies the request.
Comment 15 Ayaita 2014-07-09 14:30:00 UTC
Is there any other question about this? I really need to proceed with our image upload. 

Please tell me if you need anything else to add our url from amazon s3 to the white list.
Comment 16 Gerrit Notification Bot 2014-07-09 22:16:06 UTC
Change 145144 had a related patch set uploaded by Steinsplitter:
Adding mochila_images.s3.amazonaws.com and mochila_images2.s3.amazonaws.com temporary to wgCopyUploadsDomains for GWToolset upload.

https://gerrit.wikimedia.org/r/145144
Comment 17 Gerrit Notification Bot 2014-07-09 22:20:52 UTC
Change 145144 abandoned by Ori.livneh:
Adding mochila_images.s3.amazonaws.com and mochila_images2.s3.amazonaws.com temporary to wgCopyUploadsDomains for GWToolset upload.

https://gerrit.wikimedia.org/r/145144
Comment 18 Gerrit Notification Bot 2014-07-10 11:45:55 UTC
Change 145273 had a related patch set uploaded by Steinsplitter:
Adding new domains to wgCopyUploadsDomains.

https://gerrit.wikimedia.org/r/145273
Comment 19 Gerrit Notification Bot 2014-07-10 18:16:49 UTC
Change 145273 merged by jenkins-bot:
Adding new domains to wgCopyUploadsDomains.

https://gerrit.wikimedia.org/r/145273

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links