[Shotwell] Features for Shotwell 0.6

[Martin Olsson]

Adam Dingle wrote:
> Now that Shotwell 0.5 is out the door, we're already beginning to plan for
> Shotwell 0.6.  We're interested in input from you, the Shotwell community,
> about the features you'd most like to see.  If you could choose only a small
> number of features for the next release, which would they be?  Your ideas
> are welcome - thanks!

In this order, as many as possible without compromising quality:

* NEF/CRW support
* A basic screensaver that shows images from your Shotwell photo collection
* Enhance the screensaver so that it does this: http://www.photojoy.com/gallery/gallery.aspx?type_id=4&id=11213
* Video playback/seeking
* Export album to static HTML website; to local folder, SFTP, SSH and FTP (resident geek owns hosting and sets it up, family member just clicks Publish)
* Export to Gallery ( http://gallery.menalto.com/ )
* Ability to attach tags during import (i.e. if I shot photos during an 8 day vacation they are currently split into several date-based events which is fine but it's a bit annoying having to go into each separate day from my vacation, then select all and add the tag).
* Photo specific printing, i.e. ability to select X photos and group them Y per page, ability to choose how the photos are rotated on the paper.
* Currently you can easily navigate to "Photos from December 2005" using the events tree, but in a semi professional photo workflow you'd often to the same for other metadata such as specific DSLR lenses or GPS data. Sometimes these are also combined (i.e. I want to see all the shoots from my 50mm fixed lens taken in India).
* Upload video to youtube.
* Super simple editor for still image slideshow videos (user selects duration for each still, selects transition effects, selects background music, possibly adds some caption texts)
* Support Adobe DNG and RAW formats from minor camera manufacturers.

Also as a parallel to all of this:
* Automated UI sanity tests, unittests, code coverage and performance regression tests
  - Helps new devs get started.
  - Extends product lifetime by helping non-core devs maintain the project and its quality, years after it's "pioneer glory" days fade away (i.e when many yorba devs focus on Lombard instead or whatever).
  - It's hard to catch up if you have a huge backlog of untested features.
  - Ensures package sanity on each specific target platform before shipping
    (i.e. Debian will add the "make check" to their debuild etc ensuring that stuff
    like the issues Lucid had earlier are detected before reaching end users)
  - In reality no human notices a series of small perf regressions that happen
    over time so the only way to deliver great perf is to have tests for it;
    i.e. use "sync" and "/proc/sys/vm/drop_caches" followed by a normal import
    for example.


		Martin