Low hanging fruit

Connor Imes rocket2dmn at ubuntu.com
Sat May 9 14:21:26 UTC 2009


Dougie Richardson wrote:
> Hi Nathan,
>
> 2009/5/9 Nathan Handler <nhandler at ubuntu.com>:
>   
>> On Sat, May 9, 2009 at 1:02 PM, Dougie Richardson
>> <dougierichardson at ubuntu.com> wrote:
>>     
>>> FWIW I don't think bitesize is clearer as the phrase low hanging fruit
>>> is used quite widely, bitesize implies small rather than achievable.
>>> For example this bug [1] looks like a small change but it isn't.
>>>       
>> bitesize means "This bug is easy to fix and suitable for new
>> contributors.". The bug you linked to really is not hard to fix. The
>> issue was that we were not sure what the proper solution was, so some
>> questions had to be asked. I think the tag should be used to denote
>> bugs that are technically easy to fix. This does not necessarily mean
>> that the fix is a quick five minute patch. It very well might require
>> talking to several team members and members of other teams in order to
>> get accurate information. However, I do not feel that the amount of
>> work involved is necessarily the same as the difficulty level of the
>> bug.
>>     
>
> That's exactly my point, this isn't about picking out difficulty
> levels of bugs but about picking out suitable bugs for new
> contributers to build their confidence with.
>
>   
I would agree that we should use existing LP tags if applicable, rather 
than creating new ones that fulfill the same function.  I think the 
bitesize tag is exactly what we are looking for here.  The term may not 
seem as obvious as "lowhangingfruit" but it is what the rest of the 
community uses, and we should educate new contributors in doing things 
the Ubuntu way.

I added the bitesize tag to the bug mentioned earlier.  You could simply 
change the link to [1]:

[1] 
https://bugs.launchpad.net/ubuntu/+source/ubuntu-docs/+bugs?field.tag=bitesize

-Connor




More information about the ubuntu-doc mailing list