[Bf-committers] 'easy hacks' list
ideasman42 at gmail.com
Thu Mar 8 18:52:27 CET 2012
Would be great to have though we have bad track record of anything
that looks like a todo/task list becoming a wish-list.
Our simple todo list is really only simple for existing devs who are
familier with the code:
Criteria for this could be...
* existing core devs should be confidant they could do an an afternoon
without running into big problems.
* things we are sure can be accepted if written to acceptable quality.
* not generator work.
Perhaps disclaimer at the top to only add items if you're a developer
who knows some task is in fact easy (users should check with devs
first before adding items).
Or have a section with approved items and a second section with tasks
for review - users can add to - and devs can check if there easy
enough to qualify or remove.
On Fri, Mar 9, 2012 at 4:09 AM, Tom M <letterrip at gmail.com> wrote:
> 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
> basically it looks like they autogenerate these pages from the
> bugtracker using a set of tags (easytask, interesting, the skill
> 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.
> Bf-committers mailing list
> Bf-committers at blender.org
More information about the Bf-committers