I was reading an article about the growth rate in developer contributions to libreoffice compared to openoffice, and a signficant amount of the growth was attributed to them having an 'easyhacks' list of tasks, bugs, etc.
These range from a) provide stack traces for bug reports that don't have stack traces b) confirm whether a 'bug' reported by a static analysis (clang) is valid to tasks that require more in depth knowledge of the source http://wiki.documentfoundation.org/Development/Easy_Hacks_by_required_Skill basically it looks like they autogenerate these pages from the bugtracker using a set of tags (easytask, interesting, the skill required) http://wiki.documentfoundation.org/Development/Easy_Hacks_Bugzilla_Whiteboard_Status perhaps we could do something similar? There are also a ton of small feature requests that are worth doing (ie see the wishlist for gsoc); but which core devs don't necessarily have time for. LetterRip _______________________________________________ Bf-committers mailing list Bf-committers@blender.org http://lists.blender.org/mailman/listinfo/bf-committers
