Opened 13 years ago
Last modified 4 years ago
#229 closed enhancement
import from flickr -> mediagoblin — at Version 11
Reported by: | Caleb Davis | Owned by: | |
---|---|---|---|
Priority: | trivial | Milestone: | |
Component: | programming | Keywords: | |
Cc: | Parent Tickets: |
Description (last modified by )
What does the glorious future hold for sucking the life out of existing centralized saas and then breathing it into free alternatives? Okay, specifically, how do we handle this use case: - Hey, I just heard about MediaGoblin, and I'd like to try it out, but all my stuff is in Flickr. What's the easiest way to move things over?
Change History (11)
comment:2 by , 13 years ago
well, there's this one - `http://bugs.foocorp.net/issues/293 <http://bugs.foocorp.net/issues/293>`_
comment:5 by , 13 years ago
Yes, I think Elrond is right on with how we should approach this. I think API support will be one of the parts of the holy trinity of big features we kick off after 0.1.0 (along with multimedia, federation) ;)
comment:6 by , 13 years ago
Priority: | Normal → Low |
---|
This looks quite Low Priority to me, really. Of course, if someone volunteers, it's great. and to be honest, this sounds like something for the "Feature Ideas" wiki page.
comment:7 by , 13 years ago
I tried to flesh out some of the basics of this feature in the wiki (good idea, Elrond). `http://wiki.mediagoblin.org/Feature\_Ideas/Flickr\_Import <http://wiki.mediagoblin.org/Feature_Ideas/Flickr_Import>`_ Let's edit that page when relevant to get the idea formalized.
comment:8 by , 13 years ago
The original url for this bug was http://bugs.foocorp.net/issues/539 .
Relations:
#27: blocked
comment:9 by , 13 years ago
I hacked together an import tool using phantomjs. It has quite a few problems, the ones I know about are documented in the README.
code: https://gitorious.org/phantomjs-mediagoblin-flickr-import/
comment:10 by , 12 years ago
Type: | defect → enhancement |
---|
comment:11 by , 12 years ago
Description: | modified (diff) |
---|---|
Milestone: | → 0.4.0 |
Some options:
- We could test the above mentioned tool and link to it on the docs or wiki. That would partially close this bug.
- We have an API by now. So in theory someone could write a (maybe cleaner) desktop tool to do the job. I am unsure, whether we can bring this forward without someone knowing the flickr api (or libraries for it) better.
I am putting this on the 0.4.0 queue, so that we decide on how to continue with this.