sean roberts wrote:
> Being successful at your first patch for most people means that their
> first effort is different than an a regular patch.
>
> Identifying abandoned work more quickly is good. It doesn't help the
> first timer.
>
> Tagging low hanging fruit for first timers I like. I'm
Excerpts from sean roberts's message of 2015-11-30 07:57:54 -0800:
> How about:
> First timers assign a bug to a mentor and the mentor takes responsibility
> for the first timer learning from the bug to completion.
That would mean the learning process is different from what we want the
regular
How about:
First timers assign a bug to a mentor and the mentor takes responsibility
for the first timer learning from the bug to completion.
Per project, a few people volunteer themselves as mentors. As easy as
responding to [project][mentor] emails.
On Monday, November 30, 2015, Sean Dague
Being successful at your first patch for most people means that their first
effort is different than an a regular patch.
Identifying abandoned work more quickly is good. It doesn't help the first
timer.
Tagging low hanging fruit for first timers I like. I'm recommending we add
a mentor as part
Doug Hellmann wrote:
> Excerpts from Shamail's message of 2015-11-26 02:07:55 +0500:
>>
>>> On Nov 26, 2015, at 1:42 AM, Doug Hellmann wrote:
>>>
>>> OK, reserving bugs for new contributors does reduce the number of
>>> people contending for them, but it doesn't eliminate
On 11/26/2015 10:40 AM, Thierry Carrez wrote:
Doug Hellmann wrote:
Excerpts from Shamail's message of 2015-11-26 02:07:55 +0500:
On Nov 26, 2015, at 1:42 AM, Doug Hellmann wrote:
OK, reserving bugs for new contributors does reduce the number of
people contending
> On Nov 26, 2015, at 4:19 PM, Rossella Sblendido wrote:
>
> I'd like to help. Neutron could be one of the pilot project. I will mention
> that in the next Neutron team meeting :)
Thank you! If one, or more, projects pilot this concept... We could share the
results at
This is an awesome idea!!!
On 11/25/15 16:15, Shamail Tahir wrote:
Hi everyone,
Andrew Mitry recently shared a medium post[1] by Kent C. Dobbs which
discusses how one open-source project is encouraging contributions by
new open-source contributors through a combination of a special tag
Excerpts from Shamail Tahir's message of 2015-11-25 09:15:54 -0500:
> Hi everyone,
>
> Andrew Mitry recently shared a medium post[1] by Kent C. Dobbs which
> discusses how one open-source project is encouraging contributions by new
> open-source contributors through a combination of a special tag
Have a tag for first time contributor is a great idea.
On the other hand we should not take out the "low hanging fruit" tag. I
contribute to OpenStack on my spare time and in my current situation I can
only work on the low hanging fruits. If the first time tag is replacing
the low hanging fruit
Hi,
> On Nov 25, 2015, at 10:51 PM, Anthony Chow wrote:
>
> Have a tag for first time contributor is a great idea.
>
> On the other hand we should not take out the "low hanging fruit" tag. I
> contribute to OpenStack on my spare time and in my current situation I can
> On Nov 26, 2015, at 1:42 AM, Doug Hellmann wrote:
>
> OK, reserving bugs for new contributors does reduce the number of
> people contending for them, but it doesn't eliminate the need to
> figure out if someone else is already working on a bug before you
> start.
Hi,
> On Nov 25, 2015, at 11:05 PM, Doug Hellmann wrote:
>
> Excerpts from Shamail Tahir's message of 2015-11-25 09:15:54 -0500:
>> Hi everyone,
>>
>> Andrew Mitry recently shared a medium post[1] by Kent C. Dobbs which
>> discusses how one open-source project is
Excerpts from Shamail's message of 2015-11-26 01:22:48 +0500:
> Hi,
>
> > On Nov 25, 2015, at 11:05 PM, Doug Hellmann wrote:
> >
> > Excerpts from Shamail Tahir's message of 2015-11-25 09:15:54 -0500:
> >> Hi everyone,
> >>
> >> Andrew Mitry recently shared a medium
Excerpts from Shamail's message of 2015-11-26 02:07:55 +0500:
>
> > On Nov 26, 2015, at 1:42 AM, Doug Hellmann wrote:
> >
> > OK, reserving bugs for new contributors does reduce the number of
> > people contending for them, but it doesn't eliminate the need to
> > figure
Hi everyone,
Andrew Mitry recently shared a medium post[1] by Kent C. Dobbs which
discusses how one open-source project is encouraging contributions by new
open-source contributors through a combination of a special tag (which is
associated with work that is needed but can only be completed by
16 matches
Mail list logo