On Monday, May 11, 2015 at 5:13:36 AM UTC+8, RjOllos wrote: > > On Sat, May 9, 2015 at 9:59 PM, Walty Yeung <wal...@gmail.com > <javascript:>> wrote: > >> hi, >> >> I have been using trac for 5+ years now, and I really love the simple and >> yet powerful design of whole thing. >> >> I have modified the source code of trac myself, to add some more tools >> for the use of our company (internally). >> >> and now I would like contribute back to the Trac project. I have read the >> wiki of http://trac.edgewall.org/wiki/HowToContribute, and briefly >> checked the coding style, unit test, and patch submitting mechanism. >> >> and my question is, is the bite-sized tasks ( >> http://trac.edgewall.org/query?status=new&status=assigned&status=reopened&keywords=~bitesized&group=component&order=priority) >> >> still the optimal entry point of contribution now? I asked only because I >> saw most of the tickets there are actually pretty old, and I am not sure if >> they are actually outdated now, however, I don't mind to start with the >> minor changes at all. >> >> thanks. >> > > Hello Walty, > > We would be very happy to have you contribute. Thank you for getting > started by seeking out and reading the right documents. > > Bite-sized tickets are a good place to get started so that we can bring > you up to speed on how we develop Trac, including things that may not have > (yet) been documented. You are right that the bite-sized tasks are not up > to date. We haven't done a good job lately of marking tickets as > bite-sized. I'll plan to review and mark tickets as bite-size in the next > several days. > > In the meantime, you could find some very relevant tickets to work on by > surveying the tickets assigned to next-stable-1.0.x and next-dev-1.1.x: > http://trac.edgewall.org/milestone/next-stable-1.0.x > http://trac.edgewall.org/milestone/next-dev-1.1.x > > Those are tickets we've determined should be fixed on the maintenance > branch for 1.0 or the development branch for 1.2. We certainly won't get to > all of them by the time 1.2 is released, so we would sure appreciate help > in knocking out some of those. > > We are currently preparing the next release, hoping to finish today. After > that we will dive into developing for the next milestones. I've found that > a good way to learn is to checkout the changes that other devs post for > review, code review the changes and run the tests. It always helps to have > the tests executed on one more platform. When I started working on the > project I found at least a half-dozen issues with the tests that were due > to my developing on a platform with a different configuration than the > other devs. > > - Ryan > >
hi ryan, thanks for your detailed instructions. two quick questions, just to make sure I did fully understand the suggestions: 1. Where could I get the changes of review? should I read the timeline page (http://trac.edgewall.org/timeline)? Or is there some other places I could read the reviews? 2. I currently checked out the trunk version of trac, and set up a development environment in my mac. So, would u suggest to set up virtualbox of ubuntu and windows to do a through testing before submitting the patches? Or I could do that a little bit later? thanks have a nice day walty -- You received this message because you are subscribed to the Google Groups "Trac Development" group. To unsubscribe from this group and stop receiving emails from it, send an email to trac-dev+unsubscr...@googlegroups.com. To post to this group, send email to trac-dev@googlegroups.com. Visit this group at http://groups.google.com/group/trac-dev. For more options, visit https://groups.google.com/d/optout.
