After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 537372 - (ipernity-export) Export to www.ipernity.com
(ipernity-export)
Export to www.ipernity.com
Status: RESOLVED WONTFIX
Product: f-spot
Classification: Other
Component: General
0.4.x
Other All
: Normal enhancement
: ---
Assigned To: F-spot maintainers
F-spot maintainers
gnome[unmaintained]
Depends on:
Blocks:
 
 
Reported: 2008-06-09 10:07 UTC by voyeg3r
Modified: 2018-07-12 00:10 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Patch adding ipernity export support to F-Spot (SVN rev. 4681) (30.78 KB, patch)
2008-12-31 16:50 UTC, Matthias Benkard
needs-work Details | Review

Description voyeg3r 2008-06-09 10:07:13 UTC
And import from all
Comment 1 Maxxer 2008-06-09 10:54:56 UTC
do you have a link to upload api specifications, if exists?
Comment 2 Nils Pickert 2008-09-06 12:28:19 UTC
The API is not yet published. However they have some flickr-compatibility layer in their API, which Carsten Schurig used to crate an initial patch for f-spot. You can find it on his ipernity-page here: http://www.ipernity.com/blog/c.schurig/12956 or directly at http://foto-cs.de/blog/downloads/f-spot_ipernity.diff.bz2

According to the Ipernity people, the API will be finished soon, they have done around 80%. 
Comment 3 Nils Pickert 2008-11-14 19:40:42 UTC
The api has been released and is documented under http://www.ipernity.com/help/api

There are also two groups for API development and API usage.
Comment 4 Matthias Benkard 2008-12-31 16:50:04 UTC
Created attachment 125585 [details] [review]
Patch adding ipernity export support to F-Spot (SVN rev. 4681)

What's worse?  (1) A quick and simple adaptation of flickrnet to the Flickr-compatible, apparently undocumented API whose status I have no idea about, or (2) a couple of ugly hacks making F-Spot aware of the official ipernity API?  There are various patches for (1) floating about, while I've implemented (2).

Note: The API key and secret contained in the attached patch are preliminary and FOR TESTING ONLY.  I do not intend to pay a “financial contribution” to ipernity for causing them “significant cost” as the Terms and Conditions want me to.
Comment 5 Ruben Vermeersch 2010-06-24 14:47:48 UTC
Comment on attachment 125585 [details] [review]
Patch adding ipernity export support to F-Spot (SVN rev. 4681)

Maintenance update: In the past we've been less than stellar in reviewing patches. As such we have a pile of patches in bugzilla which are outdated and don't apply anymore. Am currently marking all of these as "needs-work". My apologies for this.

Since I've become a maintainer of the project, I've set the personal rule of quickly reviewing all patches, to avoid that this happens again. If you (or anyone) wants to go through the trouble of updating this patch, please talk to us to figure out if it fits in the F-Spot long term roadmap.

Should you, in the future, notice a patch lingering around for too long, please notify us immediately and we'll look into it, to avoid situations like these from happening again.

You can filter these mails by searching for ###F-OLDPATCHCLEANUP###
Comment 6 André Klapper 2018-07-12 00:10:14 UTC
F-Spot has moved to https://github.com/f-spot/f-spot/issues

If this Bugzilla ticket is still valid in a recent version of F-Spot, please feel free to post this topic as a ticket in the F-Spot project on GitHub.

Closing this report as WONTFIX as part of Bugzilla Housekeeping as we are planning to shut down GNOME Bugzilla in favor of GNOME Gitlab.