There are some categories of "simple" tasks in my mind. Of course, things may become complex when you really dive into details. - Simple UI changes, eg. modify UI string or change the size to avoid truncation, or color change, or a little more complex, to change the default settings...maybe someone has different opinion - Defects already fixed in another stream, eg. in Symphony stream. Again, you may find some easy things become complex when you come to the code...but at least, you have some ready solution to refer to, and migrate the code. - Inspired by Andrea, work with experienced developers on the same features but help on simple tasks, eg. some ongoing items development in 4.0. You can call for input from 4.0 developers. I believe they will be happy if others can help. Of course, better the volunteers can really help so that we do not waste the time. One easy defect to start will help to find out the ones. - Extension Development (depends on the complexity of the extensions) - (thinking on more...)
Helen 2013/1/10 Andrea Pescetti <[email protected]> > Rob Weir wrote: > >> https://issues.apache.org/ooo/**buglist.cgi?f1=cf_fix_** >> difficulty&list_id=41193&o1=**equals&resolution=---&query_** >> format=advanced&v1=easy<https://issues.apache.org/ooo/buglist.cgi?f1=cf_fix_difficulty&list_id=41193&o1=equals&resolution=---&query_format=advanced&v1=easy> >> >> We agreed to use the "difficulty" field in Bugzilla for this, to >> indicate which bugs are most suitable for new volunteers. So I need >> your help to get a bunch of issues that are suitable for new >> volunteers. Ideally we'd have 30 or more classified as "easy". >> > > And ideally people who mark a bug/enhancement as "easy" would be people > who know how to fix it, but are simply busy with other tasks. They should > add a comment saying they are available to mentor the developer who chooses > to fix that bug: this would help a lot in getting new developers. > > Regards, > Andrea. >
