Hi Robert,

You've been picking off some really juicy tickets. Great to hear you're ready for more!

Search is being developed here, and we're not quite ready to throw a third body onto the problem. We are working from a feature branch (feature/search), so you can easily monitor progress. I suspect once we land all the plumbing (which may or may not be the same time we merge with master) we'll be ready to open up the work to more hands.

Offline mode is something I'd like to spend more time architecting before diving in. Also, I'm working on a rework of the IMAP layer (#5224) that will have a direct effect on how offline mode will be implemented, so I need more time before we can start on it.

Inline replies would be a huge feature to land. I can appreciate that this isn't a big deal for you, but I know many people are waiting for it. It's also a feature that, in my mind, "seals" Geary's conversation-based interface and makes it stand out against existing Linux mail clients. In the same vein, moving the composer window into the main window (http://redmine.yorba.org/issues/4554) would be great as well and make Geary seem more like a "uniform" application.

Another one that doesn't seem like much but is actually a real sticking point is to indicate the unread message count in the folder list (http://redmine.yorba.org/issues/3694). If you want to pick up on Charles' branch or start from scratch, I'll leave up to you. As Charles' indicated in his notes, there's more work to be done in the Engine to gather and store unread message counts. I'd be happy to help you there.

Those are my nominees. Feel free to ask more questions here or on the tickets themselves.

Thanks!

-- Jim

On Tue, May 14, 2013 at 10:30 PM, Robert Schroll <[email protected]> wrote:
Hi all,

With #5642 finished, I've cleared out my current to-do list for Geary. There's a few directions I might go next, so I thought I'd check to see which would be the most productive. There are two missing features that keep me from using Geary full time. I don't know if I should work on those, or if it would be better to attack some smaller issues to free up others to work on them.

The first missing feature is search, and it looks like that's already being taken care of. If there's some part of that I could help with, please let me know. Otherwise, I'll stay out of the way on this.

The second missing feature is offline mode (#3767). I suspect this is also a fairly large project, since everything that might query the server has to be told what to do when the server isn't available. If there's some sort of a plan here that would make sense for me to work on, I'm willing. But I'm not the person to make that plan if it doesn't exist.

There are two somewhat smaller, or at least more well-defined, areas that might be more productive for me. First, there are several bugs related to identifying more things as attachments (attached emails, attachments in attached emails, inline parts). While I'm not familiar with this part of the code, there does seem to be a density of targets that could make it worthwhile for me to learn.

The other project would be inline replies (#4554). This interests me less, but it does touch on two areas (conversation view and composer) that I know pretty well. Since this is targeted for 0.5, I'm guessing that this isn't much of a priority at the moment, but I would be happy to work on it.

There's also numerous smaller bugs that I might make some progress on. I don't know what the schedule for 0.4 looks like, but if you'd prefer bugfixing to new features at this time, please say so.

So let me know which of these is most desired, or if there's something I haven't considered that would be helpful. I won't promise to follow your recommendation, but I will weigh it when considering what to do next.

Thanks,
Robert

P.S. Two Redmine questions:

1) Some bugs I watch because I want to know what's happening with them, while others I watch because I might want to work on them. But I have to try to remember which is which when look through to find one to work on. Are there any tricks for tagging bugs so that I can get a list just of bugs I might want to work on?

2) The Redmine comment box is absurdly wide. Every time I make a comment, I have to start by scrolling to the right and then dragging the corner back to the left to give it a reasonable width. Is there anything you can do on the backend to fix this? Thanks.

_______________________________________________
Geary mailing list
[email protected]
http://lists.yorba.org/cgi-bin/mailman/listinfo/geary
_______________________________________________
Geary mailing list
[email protected]
http://lists.yorba.org/cgi-bin/mailman/listinfo/geary

Reply via email to