shotwell

It's an important feature but you should make this as generic as possible at the beginning

so what is purpose of this issue? do we copy aperture ui (never seen by me) or is it possible to set the requirements for photo versioning here?

There's no plan to copy Aperture - we want to make what is most useful for Shotwell users. This feature is still under discussion and suggestions are welcome.

sorry to discuss it here instead going to the mailing list...

could you provide any links where this is being discussed? is there anything accepted in terms of requirements?

The only place this is being discussed is on this ticket. :) Nothing has been accepted yet. Any suggestions are welcome - you might want to start by adding the same comments you made on #5275.

I often have my camera set to continuous release and shoot a few photos that are almost identical. I would appreciate the ability of "stacking" these.

Even better would be if shotwell used timestamps and fuzzy image comparison (something along the lines of the imagemagick compare operator) to automatically group such images (though I don't think automatic grouping should be the default behavior).

Maybe a not too hard to implement first step towards photo stacking would be the ability for a user to manually stack images of his choice.

"Automagic" grouping through analysis of filenames, exif metadata or fuzzy comparison seems like an ambitious and delicate thing to get right, and it would probably be quite difficult to get it right in a way that satisfies a large part of Shotwell's userbase. It would require long discussions, trial and error, and would probably end up with a bunch of options to override the default. I'm not even sure the most precise tuning of parameters would work for me every time.

UI-wise, I'd be happy to start with something basic such as sub-nodes under events, combined with any form of visual or textual clue that differentiates the original raw or jpeg masters from their modified results. These two could be set manually by the user as a first implementation step, as I can see two pretty opposite use cases : single master and multiple refined editions ; and multiple master (for HDR/tonemapping) and single or multiple refined result.