Re: Guidelines for new contributors

[Timothy Chen]

Hi Vinod,

All of this is in Diana's WIP newbie guide, we should have a draft
published soon to the dev/user list.

Tim

On Tue, Sep 1, 2015 at 10:46 AM, Vinod Kone  wrote:
> Hi folks,
>
> I've seen a bunch of new contributors and contributions pop up lately
> (awesome!), so wanted to take some time to provide some guidelines to
> newbies as its been a bit chaotic. Hopefully this will be part of the
> newbie doc that Tim and Diana are working on.
>
> *Shepherds*: It is really important to find a shepherd *before* you assign
> a ticket to yourself and definitely before you submit a review. Sometimes
> working with a shepherd or discussing on the ticket will reveal its
> priority for the project at the current time. Look at the maintainers
>  file to get an
> idea for who to ask to be a shepherd.
>
> *Reviews*: Please only submit a review *after* you have come to agreement
> with your shepherd on the proposed solution. Make sure to add your shepherd
> as a "reviewer" (among others) in the review. I'll be updating the review
> bot to flag reviews that do not have reviewers. This will ensure that your
> reviews get attention.
>
> *Finding tickets*: If you are fairly new, it's best to pick tickets labeled
> "newbie". After that, it's best to work on projects that are important for
> the next release. See the tracking ticket for the release to figure out the
> high priority projects or ask the release manager to guide you. You are
> more likely to find shepherds and reviewers, when you work on projects that
> are important for the next release.
>
> Please remember that shepherds and reviewers are extremely busy, so any
> upfront work you can do to streamline the review process, will reduce their
> burden and increase the chance of your reviews getting committed.
>
> Hope this helps and looking forward to all your contributions,
>
> Vinod

Guidelines for new contributors

[Vinod Kone]

Hi folks,

I've seen a bunch of new contributors and contributions pop up lately
(awesome!), so wanted to take some time to provide some guidelines to
newbies as its been a bit chaotic. Hopefully this will be part of the
newbie doc that Tim and Diana are working on.

*Shepherds*: It is really important to find a shepherd *before* you assign
a ticket to yourself and definitely before you submit a review. Sometimes
working with a shepherd or discussing on the ticket will reveal its
priority for the project at the current time. Look at the maintainers
 file to get an
idea for who to ask to be a shepherd.

*Reviews*: Please only submit a review *after* you have come to agreement
with your shepherd on the proposed solution. Make sure to add your shepherd
as a "reviewer" (among others) in the review. I'll be updating the review
bot to flag reviews that do not have reviewers. This will ensure that your
reviews get attention.

*Finding tickets*: If you are fairly new, it's best to pick tickets labeled
"newbie". After that, it's best to work on projects that are important for
the next release. See the tracking ticket for the release to figure out the
high priority projects or ask the release manager to guide you. You are
more likely to find shepherds and reviewers, when you work on projects that
are important for the next release.

Please remember that shepherds and reviewers are extremely busy, so any
upfront work you can do to streamline the review process, will reduce their
burden and increase the chance of your reviews getting committed.

Hope this helps and looking forward to all your contributions,

Vinod