Bug 17376

Summary:	Request to start a new specification project (thumbnail management spec)
Product:	Specifications	Reporter:	Philip Van Hoof <pvanhoof>
Component:	General	Assignee:	Allison Lortie (desrt) <desrt>
Status:	RESOLVED INVALID	QA Contact:
Severity:	normal
Priority:	medium	CC:	brian, bugzilla, chrislord.net, faure, hans, kevin.krammer, madcat, marcandre.lureau, rob.taylor, vuntz, zeuthen
Version:	unspecified
Hardware:	Other
OS:	All
Whiteboard:
i915 platform:		i915 features:
Bug Depends on:	17383
Bug Blocks:

Description Philip Van Hoof 2008-08-31 02:13:00 UTC

Hi there,

This is an official request to start a new specification project titled:

"A specification for requesting thumbnails"

This specification will depend on the thumbnail-spec [1], if anything it will extend it, it doesn't try to replace it.

The specification will be about writing up a DBus API, guidelines and expected behaviour for a thumbnailer. A thumbnailer will be (is) a service (provider by a standalone daemon or by any other infrastructure of the desktop) that will receive requests for thumbnail creation from various desktop applications that want to display and consume thumbnails. The specification will also address moves and deletes of the thumbnail-able content.

A first discussion seemed to result in overall positive reactions from both GNOME and the KDE developers:

http://lists.freedesktop.org/archives/xdg/2008-August/009834.html

ps. I have put everybody who contributed to this discussion in CC of this bug.

I have (will) sent separate E-mails to jens@gnome.org, jmillikin@gmail.com and olivier@lx.student.wau.nl because those E-mail addresses didn't match anything on this bugzilla.

-- footnotes 

[1] http://jens.triq.net/thumbnail-spec/index.html

Comment 1 Vincent Untz 2008-08-31 13:36:19 UTC

Would you mind using a common spec repository for this spec? (it's not there yet, but it will eventually)

Note that it probably makes sense to come with a first draft.

Comment 2 Philip Van Hoof 2008-09-01 00:50:13 UTC

No problem for me using a common repository. I don't think I have a username/password for FDO's repositories yet though.

I will try to sketch a first draft. Discussions are still ongoing but I already have an rough idea of what it will look like indeed.

Comment 3 Philip Van Hoof 2008-09-01 05:17:17 UTC

Note: Not "a thumbnailer" but "thumbnail management" appears to be the best name for what is being proposed.

Comment 4 Philip Van Hoof 2008-09-01 06:03:25 UTC

Here's a first draft:

http://live.gnome.org/ThumbnailerSpec

Comment 5 Philip Van Hoof 2008-09-03 07:17:55 UTC

This E-mail is related to this request:

http://lists.freedesktop.org/archives/xdg/2008-September/009857.html

Comment 6 Philip Van Hoof 2008-09-07 02:02:24 UTC

Changing the title to something a little bit less drastic

Comment 7 Philip Van Hoof 2008-09-24 13:27:17 UTC

You can find a working prototype of this specification here

https://stage.maemo.org/svn/maemo/projects/haf/branches/hildon-thumbnail/daemonize/

Comment 8 Benjamin Close 2008-10-08 07:16:47 UTC

Vince can you shed any light on the common spec repo?

Comment 9 Vincent Untz 2010-02-08 09:22:58 UTC

(In reply to comment #8)
> Vince can you shed any light on the common spec repo?

I learnt last week that we have a git repo now. I hope to start filling it soon (but probably not this week -- I need to play with importing various cvs repos in one git project, with history).

So maybe assign the bug to me, or move it to the specifications product?

Comment 10 Tollef Fog Heen 2010-02-08 09:26:03 UTC

Moved and reassigned.

Comment 11 David Faure 2014-04-01 20:22:08 UTC

Does anything still need to be done about this? i.e. is it intended to put the spec into the xdg-specs git repo?

Comment 12 Vincent Untz 2015-09-18 09:41:44 UTC

Sorry for the noise, reassigning to new (since 2 years) maintainers (Ryan & David).

Comment 13 Daniel Stone 2019-02-16 12:14:18 UTC

Seems to no longer be a thing?

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.