Hi John, My advice for you is to pull Geary from our git repository and make sure you can build it on your own machine. You can find information about that on our wiki: http://redmine.yorba.org/projects/geary/wiki#Building-38-Running
From there, there's two paths you could consider. First is to run Geary and get to know the app. I recommend using it as your daily email client. Dogfooding is the best way to familiarize yourself with any program. This might give you some inspiration about what you'd like to change -- an itch to scratch, so to speak. Don't think too big, something small. Then, check our bug database to see if it's already ticketed: http://redmine.yorba.org/projects/geary/issues If not, submit a ticket. If it is ticketed, make a comment on the ticket that you'd like to attack it. What's important is to let us know you want to work on it. We might have some ideas already what we want a feature or fix to look like, or where it should belong in the code. Better to have a little coordination first, before coding. The other approach is to simply walk the ticket list looking for something to pick off. Again, let us know if you find something so we're aware you're working on it. Hope this gives you the advice you need to jump in! -- Jim On Tue, Oct 9, 2012 at 6:44 AM, John Kim <[email protected]> wrote: Hi Yorba team and contributers, I'm John and I am very interested in contributing to the geary project. But like most starts, I'm stumped on where and how to begin. The vision of a light yet simple mail app is absolutely enticing. What's the most recommended ide for the project? How should I get started? Thanks. Have a great day. John Kim _______________________________________________ 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
