F-Spot

Meeting 0601

Where

IRC: #f-spot (irc://irc.gnome.org/#f-spot)

When

Mon July 31 at 20:30 UTC

New York:  16:30
Paris: 22:30
Melbourne: 6:30 (the next day, Tues Aug 1)

IRC Log

Full IRC Log

Summary of meeting below

First, I would like to thank everyone for participating and making this meeting a good first meeting. It looks like we have some good things going now :)

Is there some way we can get code committed more efficiently?

• Small clear cut fixes should be reviewed by a few people, and if everything is ok (after a few persons have confirmed it), change status on the patch to "accepted commit now". This indicates that this patch can be committed without further inputs or comments.
• Larger patches should be reviewed by as many as possible to enhance it, and remove all obvious faults.

  After this, it has to be reviewed by Core developers and active patchers/testers and before it can be committed.

How would this review procedure look like?

• General review procedure
  1. Do the patch follow the guidelines (guidelines (http://www.mono-project.com/Coding_Guidelines) and old review (http://mail.gnome.org/archives/f-spot-list/2005-October/msg00044.html))
  2. Scan patch for obvious problem
  3. Apply patch
  4. Test that patch fixes problem
  5. Read patch more carefully
  6. Check to make sure that any changes might break existing functionality
  7. Think if the patch is really the right way to solve the problem
• Enhancement requests that we do not see happening.
  1. Do not close them with WONTFIX, but lower priority, and explain to submitter why. Re-evaluate the enhancement request later (12 months or so) if needed.

Overall direction of the project.

• Larry pointed to the following wiki page. http://f-spot.org/Goals

  During the discussion that followed, a number of items were found missing (duplication, plugin, email resize etc).

  bmon also mentioned that we are missing a Mission Statement, to give a general view of F-Spot.

Short-term plans.

• Larry stated his immediate plans are (apart from vacation)
  1. Improve importing
  2. add unit tests to images
  3. refactor image loaders
  4. clean up editing
• Next short term goal?
  1. The Query tag patch

     Although a number of different patches were mentioned, like loseless cropping,

• Comments/Feedback of the first (un-official) goal (bug #342137 XMP imports)
  1. Looking good so far. Larry will have a review of it as well in the next day or so. Possible ready for commit very soon, although might need to add a little more structure to the XMP so you can tell where it came from (XMP sidecar, XMP embedded, IPTC, EXIF etc..) Sidecar is not needed after importing the data in it.

Anything else that anyone can come up with.

• Moderator status for IRC channel? Who, how etc?
  1. Larry have Moderator status, and the Title for the IRC chatroom was set.

• With which interval should we have the meetings? (presuming we will have more :))
  1. Two weeks interval, and same time. Difficult to get a good time for everyone.

• Suggestion: Lets aim to release when Gnome is releasing?
  1. We will try to have some regular releases, but no real code freeze though.

• CVS vs SVN.
  1. A majority is in favor of trying to get SVN as soon as possible, even it if means moving away from Gnome cvs. Especially since we can migrate back again later when Gnome have move to SVN.

• Calling for next meeting
  1. bmon will co-ordinate this and send out the invitation.

• Call for help to reach goal #2
  1. sde will send out the mail

Action Points

1. MoM - bengt
2. Call for next meeting - bmon
3. Next goal mail - sde

Bugzilla Status

Bugs

• Blocker - 1 bug (345005 - Need information)
• Critical - 13 bugs (8 normal, 5 high)
• Major - 8 bugs (2 need, 1 new, 5 unconfirmed)
• Normal - 100 bugs (19 new, 75 unconfirmed, 4 need, 2 ass)
• Minor - 32 bugs (5 new, 1 need, 26 uncon)
• Trivial - 10 bugs

Total 164 bugs

Enhancement Requests

• Enhancements - 160 enhancements requests

Existing patches

• 56 bugs (30 enh, 2 maj, 18 nor, 5 min, 1 tri)