[Shotwell] Shotwell - Thoughts on work-flow and extensions

[Bruno Girin]

On Tue, 2010-05-25 at 11:37 -0700, Adam Dingle wrote:
[snip]
> 
> > I would be very interested in contributing to Shotwell development first
> > by helping fix bugs and hopefully later contributing new features. What
> > easy bugs would people recommend I look at to get started?
> >    
> 
> We'd be happy to have your help.  In our ticket database, if a ticket 
> has no owner that means that nobody is actively working on it.  So feel 
> free to work on any of these tickets.  If you do start working on a 
> ticket, please set yourself to be the owner so we won't step on each 
> other's feet.  We're currently hoping to fix all tickets at high 
> priority for 0.6, which may be ambitious.
> 
> Here are some possibly easy bugs/features at high priority:
> 
> #1919       Ctrl + mouse wheel to zoom in Photos view
> #1934       allow Add Tags/Modify Tags in full-window mode
> #1952       remove Display Borders preference
> #1959       Rename Photo causes soft assertion
> #1965       import dialog nits
> 
> And here are some possibly easy bugs/features at medium priority:
> 
> #853       Control+Shift+Click
> #1110       send pictures via email
> #1304       display shadow around each photo
> #1321       icons in Publish dialog dropdown
> #1845       Indent and ellipsize filenames in Import Complete dialog
> #1858       Cursor disappear when not in use during fullscreen mode
> #1954       show exposure bias in Extended Information

OK, I'll have a look. What's the complete process to work on those? My
assumption is:
      * Set myself as the owner of the ticket
      * Work on the trunk code
      * Create a patch
      * Upload the patch to Trac
      * Someone else reviews the patch before merging it into trunk

Is that correct? And is there an IRC channel where I can ask questions
about the code or should this be done on this list?

Bruno