Re: Starter tickets

[Alexander Murmann]

Hi all,

I consolidated all labels mentioned above under "starter" and "starter++"
and updated the how to contribute page

accordingly.

At this point we have 21 and 3 tickets for those labels. Especially the
number of "starter" tickets seems like it's very much in the healthy range.
Let's make sure they all stay relevant.

Looking good to everyone?

On Fri, Mar 2, 2018 at 3:12 PM, Patrick Rhomberg 
wrote:

> I don't really think "newbie" has a negative connotation, but then again,
> I've been a gamer long enough to see a difference between terms "newb" and
> a "n00b."
>
> I do love consistency, though.  (You might even say "consistency is a
> must.")
>
> We currently have tickets tagged with "newbie" and its variants, a few
> "low-hanging-fruit", one closed "easyfix."
>
> Glancing at other Apache JIRAs, it looks like "starter," "newbie," and
> "beginner" are popular.
>
> If anyone knows how the ASF Bot works and has the ability to enforce a
> standard, I'd personally love to see us pick one label or another, and have
> the bot switch any of those other tags to what we land on.  Which sounds
> like it ought to be "starter."  But it defeats the purpose if after this
> thread slips from immediate memory, people go back to tagging tickets with
> whatever is top of their mind.  Otherwise we'd have to expect new
> contributors to know the ump-teen tags that would be a good starting point.
>
> On Fri, Mar 2, 2018 at 1:45 PM, Joey McAllister 
> wrote:
>
> > +1 to "starter" over "newbie." I think the ++ plan makes sense, too.
> >
> > Thanks for the initiative on this, Alexander. It seems like a very
> valuable
> > effort for the community.
> >
> > On Fri, Mar 2, 2018 at 1:35 PM Alexander Murmann 
> > wrote:
> >
> > > I am glad this already revealed that we aren't consistent in what
> labels
> > we
> > > are using. I assume the idea of newbie++ was to facilitate a
> > progression? I
> > > really like that and would love to keep something like that.
> > >
> > > I don't think the term "newbie" is great. To me it has a little bit of
> a
> > > negative connotation.
> > >
> > > Does anyone have an issue with adopting "starter" and "starter++"
> > > consistently? I am happy to do the conversion work and make sure the
> > > communication in the wiki etc. is consistent going forward.
> > >
> > > Mike, I agree that there is probably a lot of great work that someone
> who
> > > doesn't know the code base well can do in Pulse. I'd suggest that we
> > still
> > > decide on a case by case basis. A quick glance showed a few bugs that
> > > probably should be tackled sooner rather than later. I'll take a pass
> at
> > > all Pulse related tickets and see if they are a good fit.
> > >
> > > On Fri, Mar 2, 2018 at 10:45 AM, Michael Stolz 
> > wrote:
> > >
> > > > I'd love to tag all the pulse issues as newbie if we could.
> > > >
> > > >
> > > >
> > > > On Fri, Mar 2, 2018 at 1:34 PM, Anthony Baker 
> > wrote:
> > > >
> > > > > Good idea!  We he have a few other labels relevant to this as well:
> > > > >
> > > > > - newbie
> > > > > - low-hanging-fruit
> > > > >
> > > > > Anthony
> > > > >
> > > > >
> > > > > > On Mar 2, 2018, at 10:03 AM, Alexander Murmann <
> > amurm...@pivotal.io>
> > > > > wrote:
> > > > > >
> > > > > > Hi all,
> > > > > >
> > > > > > I think we could make it easier for people to find tasks that can
> > be
> > > > > their
> > > > > > first contribution to Geode. The wiki page on how to contribute
> > > > > >  > to+Contribute
> > > >
> > > > > has a
> > > > > > list of suggested projects. Most of those are pretty ambitious
> and
> > > > likely
> > > > > > would be overwhelming to first time contributors. There also is a
> > > link
> > > > > > to tickets
> > > > > > labeled with "Starter"
> > > > > >  > > > > 3D%20Geode%20AND%20labels%20%3D%20starter%20AND%20status%
> > > > > 20in%20%28Open%2C%20%22In%20Progress%22%2C%20Reopened%29>.
> > > > > > I think the later is probably a much better angle for someone to
> > > start
> > > > > > contributing to Geode. Unfortunately there was less than a
> handful
> > of
> > > > > > tickets labeled as starter tickets.
> > > > > >
> > > > > > My suggestion is to find tickets that strike a healthy balance
> > > between
> > > > > being
> > > > > >
> > > > > >   - simple enough that someone new to the code base can
> > realistically
> > > > > take
> > > > > >   them on
> > > > > >   - rewarding enough that someone can feel a sense of
> > accomplishment
> > > > > after
> > > > > >   having their PR merged
> > > > > >   - small enough that it can be accomplished in an evening or at
> > > most a
> > > > > >   long weekend
> > > > > >   - unlikely to result in conflicts with larger efforts that
> > 

Re: Starter tickets

[Patrick Rhomberg]

I don't really think "newbie" has a negative connotation, but then again,
I've been a gamer long enough to see a difference between terms "newb" and
a "n00b."

I do love consistency, though.  (You might even say "consistency is a
must.")

We currently have tickets tagged with "newbie" and its variants, a few
"low-hanging-fruit", one closed "easyfix."

Glancing at other Apache JIRAs, it looks like "starter," "newbie," and
"beginner" are popular.

If anyone knows how the ASF Bot works and has the ability to enforce a
standard, I'd personally love to see us pick one label or another, and have
the bot switch any of those other tags to what we land on.  Which sounds
like it ought to be "starter."  But it defeats the purpose if after this
thread slips from immediate memory, people go back to tagging tickets with
whatever is top of their mind.  Otherwise we'd have to expect new
contributors to know the ump-teen tags that would be a good starting point.

On Fri, Mar 2, 2018 at 1:45 PM, Joey McAllister 
wrote:

> +1 to "starter" over "newbie." I think the ++ plan makes sense, too.
>
> Thanks for the initiative on this, Alexander. It seems like a very valuable
> effort for the community.
>
> On Fri, Mar 2, 2018 at 1:35 PM Alexander Murmann 
> wrote:
>
> > I am glad this already revealed that we aren't consistent in what labels
> we
> > are using. I assume the idea of newbie++ was to facilitate a
> progression? I
> > really like that and would love to keep something like that.
> >
> > I don't think the term "newbie" is great. To me it has a little bit of a
> > negative connotation.
> >
> > Does anyone have an issue with adopting "starter" and "starter++"
> > consistently? I am happy to do the conversion work and make sure the
> > communication in the wiki etc. is consistent going forward.
> >
> > Mike, I agree that there is probably a lot of great work that someone who
> > doesn't know the code base well can do in Pulse. I'd suggest that we
> still
> > decide on a case by case basis. A quick glance showed a few bugs that
> > probably should be tackled sooner rather than later. I'll take a pass at
> > all Pulse related tickets and see if they are a good fit.
> >
> > On Fri, Mar 2, 2018 at 10:45 AM, Michael Stolz 
> wrote:
> >
> > > I'd love to tag all the pulse issues as newbie if we could.
> > >
> > >
> > >
> > > On Fri, Mar 2, 2018 at 1:34 PM, Anthony Baker 
> wrote:
> > >
> > > > Good idea!  We he have a few other labels relevant to this as well:
> > > >
> > > > - newbie
> > > > - low-hanging-fruit
> > > >
> > > > Anthony
> > > >
> > > >
> > > > > On Mar 2, 2018, at 10:03 AM, Alexander Murmann <
> amurm...@pivotal.io>
> > > > wrote:
> > > > >
> > > > > Hi all,
> > > > >
> > > > > I think we could make it easier for people to find tasks that can
> be
> > > > their
> > > > > first contribution to Geode. The wiki page on how to contribute
> > > > >  to+Contribute
> > >
> > > > has a
> > > > > list of suggested projects. Most of those are pretty ambitious and
> > > likely
> > > > > would be overwhelming to first time contributors. There also is a
> > link
> > > > > to tickets
> > > > > labeled with "Starter"
> > > > >  > > > 3D%20Geode%20AND%20labels%20%3D%20starter%20AND%20status%
> > > > 20in%20%28Open%2C%20%22In%20Progress%22%2C%20Reopened%29>.
> > > > > I think the later is probably a much better angle for someone to
> > start
> > > > > contributing to Geode. Unfortunately there was less than a handful
> of
> > > > > tickets labeled as starter tickets.
> > > > >
> > > > > My suggestion is to find tickets that strike a healthy balance
> > between
> > > > being
> > > > >
> > > > >   - simple enough that someone new to the code base can
> realistically
> > > > take
> > > > >   them on
> > > > >   - rewarding enough that someone can feel a sense of
> accomplishment
> > > > after
> > > > >   having their PR merged
> > > > >   - small enough that it can be accomplished in an evening or at
> > most a
> > > > >   long weekend
> > > > >   - unlikely to result in conflicts with larger efforts that
> someone
> > is
> > > > >   already undertaking
> > > > >
> > > > > It would be great to have a variety of tickets that have different
> > > levels
> > > > > of complexity and required effort to allow new contributors of
> > varying
> > > > > experience levels to start contributing meaningfully and maybe even
> > > > support
> > > > > somewhat of a progression curve for someone who wants to become a
> > > regular
> > > > > contributor or even committer.
> > > > >
> > > > > I'd also suggest to not allow the list to grow too large. If the
> list
> > > > gets
> > > > > bigger than 20-30 tickets it might get too hard to keep a clear
> grasp
> > > on
> > > > it
> > > > > and the risk of having tickets that aren't relevant anymore
> > 

Re: Starter tickets

[Brian Baynes]

+1  on starter/starter++

It will be nice to already have a group of possibilities to point folks to.


On Mar 2, 2018 2:26 PM, "Kirk Lund"  wrote:

+1 for using starter and starter++

On Fri, Mar 2, 2018 at 1:45 PM, Joey McAllister 
wrote:

> +1 to "starter" over "newbie." I think the ++ plan makes sense, too.
>
> Thanks for the initiative on this, Alexander. It seems like a very
valuable
> effort for the community.
>
> On Fri, Mar 2, 2018 at 1:35 PM Alexander Murmann 
> wrote:
>
> > I am glad this already revealed that we aren't consistent in what labels
> we
> > are using. I assume the idea of newbie++ was to facilitate a
> progression? I
> > really like that and would love to keep something like that.
> >
> > I don't think the term "newbie" is great. To me it has a little bit of a
> > negative connotation.
> >
> > Does anyone have an issue with adopting "starter" and "starter++"
> > consistently? I am happy to do the conversion work and make sure the
> > communication in the wiki etc. is consistent going forward.
> >
> > Mike, I agree that there is probably a lot of great work that someone
who
> > doesn't know the code base well can do in Pulse. I'd suggest that we
> still
> > decide on a case by case basis. A quick glance showed a few bugs that
> > probably should be tackled sooner rather than later. I'll take a pass at
> > all Pulse related tickets and see if they are a good fit.
> >
> > On Fri, Mar 2, 2018 at 10:45 AM, Michael Stolz 
> wrote:
> >
> > > I'd love to tag all the pulse issues as newbie if we could.
> > >
> > >
> > >
> > > On Fri, Mar 2, 2018 at 1:34 PM, Anthony Baker 
> wrote:
> > >
> > > > Good idea!  We he have a few other labels relevant to this as well:
> > > >
> > > > - newbie
> > > > - low-hanging-fruit
> > > >
> > > > Anthony
> > > >
> > > >
> > > > > On Mar 2, 2018, at 10:03 AM, Alexander Murmann <
> amurm...@pivotal.io>
> > > > wrote:
> > > > >
> > > > > Hi all,
> > > > >
> > > > > I think we could make it easier for people to find tasks that can
> be
> > > > their
> > > > > first contribution to Geode. The wiki page on how to contribute
> > > > >  to+Contribute
> > >
> > > > has a
> > > > > list of suggested projects. Most of those are pretty ambitious and
> > > likely
> > > > > would be overwhelming to first time contributors. There also is a
> > link
> > > > > to tickets
> > > > > labeled with "Starter"
> > > > >  > > > 3D%20Geode%20AND%20labels%20%3D%20starter%20AND%20status%
> > > > 20in%20%28Open%2C%20%22In%20Progress%22%2C%20Reopened%29>.
> > > > > I think the later is probably a much better angle for someone to
> > start
> > > > > contributing to Geode. Unfortunately there was less than a handful
> of
> > > > > tickets labeled as starter tickets.
> > > > >
> > > > > My suggestion is to find tickets that strike a healthy balance
> > between
> > > > being
> > > > >
> > > > >   - simple enough that someone new to the code base can
> realistically
> > > > take
> > > > >   them on
> > > > >   - rewarding enough that someone can feel a sense of
> accomplishment
> > > > after
> > > > >   having their PR merged
> > > > >   - small enough that it can be accomplished in an evening or at
> > most a
> > > > >   long weekend
> > > > >   - unlikely to result in conflicts with larger efforts that
> someone
> > is
> > > > >   already undertaking
> > > > >
> > > > > It would be great to have a variety of tickets that have different
> > > levels
> > > > > of complexity and required effort to allow new contributors of
> > varying
> > > > > experience levels to start contributing meaningfully and maybe
even
> > > > support
> > > > > somewhat of a progression curve for someone who wants to become a
> > > regular
> > > > > contributor or even committer.
> > > > >
> > > > > I'd also suggest to not allow the list to grow too large. If the
> list
> > > > gets
> > > > > bigger than 20-30 tickets it might get too hard to keep a clear
> grasp
> > > on
> > > > it
> > > > > and the risk of having tickets that aren't relevant anymore
> > increases.
> > > > > Nothing would be more frustrating to a new contributor than
> investing
> > > > their
> > > > > personal time just to find out that it was wasted. So let's be
> > mindful
> > > of
> > > > > not using this as a dumping ground for everything we'd like to
see,
> > but
> > > > > know we'll never get to.
> > > > >
> > > > > I already labeled a few more tickets as starter. Please feel free
> to
> > > > > validate that I didn't violate my own suggestions in doing so.
> > > > >
> > > > > Thoughts?
> > > >
> > > >
> > >
> >
>

Re: Starter tickets

[Kirk Lund]

+1 for using starter and starter++

On Fri, Mar 2, 2018 at 1:45 PM, Joey McAllister 
wrote:

> +1 to "starter" over "newbie." I think the ++ plan makes sense, too.
>
> Thanks for the initiative on this, Alexander. It seems like a very valuable
> effort for the community.
>
> On Fri, Mar 2, 2018 at 1:35 PM Alexander Murmann 
> wrote:
>
> > I am glad this already revealed that we aren't consistent in what labels
> we
> > are using. I assume the idea of newbie++ was to facilitate a
> progression? I
> > really like that and would love to keep something like that.
> >
> > I don't think the term "newbie" is great. To me it has a little bit of a
> > negative connotation.
> >
> > Does anyone have an issue with adopting "starter" and "starter++"
> > consistently? I am happy to do the conversion work and make sure the
> > communication in the wiki etc. is consistent going forward.
> >
> > Mike, I agree that there is probably a lot of great work that someone who
> > doesn't know the code base well can do in Pulse. I'd suggest that we
> still
> > decide on a case by case basis. A quick glance showed a few bugs that
> > probably should be tackled sooner rather than later. I'll take a pass at
> > all Pulse related tickets and see if they are a good fit.
> >
> > On Fri, Mar 2, 2018 at 10:45 AM, Michael Stolz 
> wrote:
> >
> > > I'd love to tag all the pulse issues as newbie if we could.
> > >
> > >
> > >
> > > On Fri, Mar 2, 2018 at 1:34 PM, Anthony Baker 
> wrote:
> > >
> > > > Good idea!  We he have a few other labels relevant to this as well:
> > > >
> > > > - newbie
> > > > - low-hanging-fruit
> > > >
> > > > Anthony
> > > >
> > > >
> > > > > On Mar 2, 2018, at 10:03 AM, Alexander Murmann <
> amurm...@pivotal.io>
> > > > wrote:
> > > > >
> > > > > Hi all,
> > > > >
> > > > > I think we could make it easier for people to find tasks that can
> be
> > > > their
> > > > > first contribution to Geode. The wiki page on how to contribute
> > > > >  to+Contribute
> > >
> > > > has a
> > > > > list of suggested projects. Most of those are pretty ambitious and
> > > likely
> > > > > would be overwhelming to first time contributors. There also is a
> > link
> > > > > to tickets
> > > > > labeled with "Starter"
> > > > >  > > > 3D%20Geode%20AND%20labels%20%3D%20starter%20AND%20status%
> > > > 20in%20%28Open%2C%20%22In%20Progress%22%2C%20Reopened%29>.
> > > > > I think the later is probably a much better angle for someone to
> > start
> > > > > contributing to Geode. Unfortunately there was less than a handful
> of
> > > > > tickets labeled as starter tickets.
> > > > >
> > > > > My suggestion is to find tickets that strike a healthy balance
> > between
> > > > being
> > > > >
> > > > >   - simple enough that someone new to the code base can
> realistically
> > > > take
> > > > >   them on
> > > > >   - rewarding enough that someone can feel a sense of
> accomplishment
> > > > after
> > > > >   having their PR merged
> > > > >   - small enough that it can be accomplished in an evening or at
> > most a
> > > > >   long weekend
> > > > >   - unlikely to result in conflicts with larger efforts that
> someone
> > is
> > > > >   already undertaking
> > > > >
> > > > > It would be great to have a variety of tickets that have different
> > > levels
> > > > > of complexity and required effort to allow new contributors of
> > varying
> > > > > experience levels to start contributing meaningfully and maybe even
> > > > support
> > > > > somewhat of a progression curve for someone who wants to become a
> > > regular
> > > > > contributor or even committer.
> > > > >
> > > > > I'd also suggest to not allow the list to grow too large. If the
> list
> > > > gets
> > > > > bigger than 20-30 tickets it might get too hard to keep a clear
> grasp
> > > on
> > > > it
> > > > > and the risk of having tickets that aren't relevant anymore
> > increases.
> > > > > Nothing would be more frustrating to a new contributor than
> investing
> > > > their
> > > > > personal time just to find out that it was wasted. So let's be
> > mindful
> > > of
> > > > > not using this as a dumping ground for everything we'd like to see,
> > but
> > > > > know we'll never get to.
> > > > >
> > > > > I already labeled a few more tickets as starter. Please feel free
> to
> > > > > validate that I didn't violate my own suggestions in doing so.
> > > > >
> > > > > Thoughts?
> > > >
> > > >
> > >
> >
>

Re: Starter tickets

[Joey McAllister]

+1 to "starter" over "newbie." I think the ++ plan makes sense, too.

Thanks for the initiative on this, Alexander. It seems like a very valuable
effort for the community.

On Fri, Mar 2, 2018 at 1:35 PM Alexander Murmann 
wrote:

> I am glad this already revealed that we aren't consistent in what labels we
> are using. I assume the idea of newbie++ was to facilitate a progression? I
> really like that and would love to keep something like that.
>
> I don't think the term "newbie" is great. To me it has a little bit of a
> negative connotation.
>
> Does anyone have an issue with adopting "starter" and "starter++"
> consistently? I am happy to do the conversion work and make sure the
> communication in the wiki etc. is consistent going forward.
>
> Mike, I agree that there is probably a lot of great work that someone who
> doesn't know the code base well can do in Pulse. I'd suggest that we still
> decide on a case by case basis. A quick glance showed a few bugs that
> probably should be tackled sooner rather than later. I'll take a pass at
> all Pulse related tickets and see if they are a good fit.
>
> On Fri, Mar 2, 2018 at 10:45 AM, Michael Stolz  wrote:
>
> > I'd love to tag all the pulse issues as newbie if we could.
> >
> >
> >
> > On Fri, Mar 2, 2018 at 1:34 PM, Anthony Baker  wrote:
> >
> > > Good idea!  We he have a few other labels relevant to this as well:
> > >
> > > - newbie
> > > - low-hanging-fruit
> > >
> > > Anthony
> > >
> > >
> > > > On Mar 2, 2018, at 10:03 AM, Alexander Murmann 
> > > wrote:
> > > >
> > > > Hi all,
> > > >
> > > > I think we could make it easier for people to find tasks that can be
> > > their
> > > > first contribution to Geode. The wiki page on how to contribute
> > > >  >
> > > has a
> > > > list of suggested projects. Most of those are pretty ambitious and
> > likely
> > > > would be overwhelming to first time contributors. There also is a
> link
> > > > to tickets
> > > > labeled with "Starter"
> > > >  > > 3D%20Geode%20AND%20labels%20%3D%20starter%20AND%20status%
> > > 20in%20%28Open%2C%20%22In%20Progress%22%2C%20Reopened%29>.
> > > > I think the later is probably a much better angle for someone to
> start
> > > > contributing to Geode. Unfortunately there was less than a handful of
> > > > tickets labeled as starter tickets.
> > > >
> > > > My suggestion is to find tickets that strike a healthy balance
> between
> > > being
> > > >
> > > >   - simple enough that someone new to the code base can realistically
> > > take
> > > >   them on
> > > >   - rewarding enough that someone can feel a sense of accomplishment
> > > after
> > > >   having their PR merged
> > > >   - small enough that it can be accomplished in an evening or at
> most a
> > > >   long weekend
> > > >   - unlikely to result in conflicts with larger efforts that someone
> is
> > > >   already undertaking
> > > >
> > > > It would be great to have a variety of tickets that have different
> > levels
> > > > of complexity and required effort to allow new contributors of
> varying
> > > > experience levels to start contributing meaningfully and maybe even
> > > support
> > > > somewhat of a progression curve for someone who wants to become a
> > regular
> > > > contributor or even committer.
> > > >
> > > > I'd also suggest to not allow the list to grow too large. If the list
> > > gets
> > > > bigger than 20-30 tickets it might get too hard to keep a clear grasp
> > on
> > > it
> > > > and the risk of having tickets that aren't relevant anymore
> increases.
> > > > Nothing would be more frustrating to a new contributor than investing
> > > their
> > > > personal time just to find out that it was wasted. So let's be
> mindful
> > of
> > > > not using this as a dumping ground for everything we'd like to see,
> but
> > > > know we'll never get to.
> > > >
> > > > I already labeled a few more tickets as starter. Please feel free to
> > > > validate that I didn't violate my own suggestions in doing so.
> > > >
> > > > Thoughts?
> > >
> > >
> >
>

Re: Starter tickets

[Alexander Murmann]

I am glad this already revealed that we aren't consistent in what labels we
are using. I assume the idea of newbie++ was to facilitate a progression? I
really like that and would love to keep something like that.

I don't think the term "newbie" is great. To me it has a little bit of a
negative connotation.

Does anyone have an issue with adopting "starter" and "starter++"
consistently? I am happy to do the conversion work and make sure the
communication in the wiki etc. is consistent going forward.

Mike, I agree that there is probably a lot of great work that someone who
doesn't know the code base well can do in Pulse. I'd suggest that we still
decide on a case by case basis. A quick glance showed a few bugs that
probably should be tackled sooner rather than later. I'll take a pass at
all Pulse related tickets and see if they are a good fit.

On Fri, Mar 2, 2018 at 10:45 AM, Michael Stolz  wrote:

> I'd love to tag all the pulse issues as newbie if we could.
>
>
>
> On Fri, Mar 2, 2018 at 1:34 PM, Anthony Baker  wrote:
>
> > Good idea!  We he have a few other labels relevant to this as well:
> >
> > - newbie
> > - low-hanging-fruit
> >
> > Anthony
> >
> >
> > > On Mar 2, 2018, at 10:03 AM, Alexander Murmann 
> > wrote:
> > >
> > > Hi all,
> > >
> > > I think we could make it easier for people to find tasks that can be
> > their
> > > first contribution to Geode. The wiki page on how to contribute
> > > 
> > has a
> > > list of suggested projects. Most of those are pretty ambitious and
> likely
> > > would be overwhelming to first time contributors. There also is a link
> > > to tickets
> > > labeled with "Starter"
> > >  > 3D%20Geode%20AND%20labels%20%3D%20starter%20AND%20status%
> > 20in%20%28Open%2C%20%22In%20Progress%22%2C%20Reopened%29>.
> > > I think the later is probably a much better angle for someone to start
> > > contributing to Geode. Unfortunately there was less than a handful of
> > > tickets labeled as starter tickets.
> > >
> > > My suggestion is to find tickets that strike a healthy balance between
> > being
> > >
> > >   - simple enough that someone new to the code base can realistically
> > take
> > >   them on
> > >   - rewarding enough that someone can feel a sense of accomplishment
> > after
> > >   having their PR merged
> > >   - small enough that it can be accomplished in an evening or at most a
> > >   long weekend
> > >   - unlikely to result in conflicts with larger efforts that someone is
> > >   already undertaking
> > >
> > > It would be great to have a variety of tickets that have different
> levels
> > > of complexity and required effort to allow new contributors of varying
> > > experience levels to start contributing meaningfully and maybe even
> > support
> > > somewhat of a progression curve for someone who wants to become a
> regular
> > > contributor or even committer.
> > >
> > > I'd also suggest to not allow the list to grow too large. If the list
> > gets
> > > bigger than 20-30 tickets it might get too hard to keep a clear grasp
> on
> > it
> > > and the risk of having tickets that aren't relevant anymore increases.
> > > Nothing would be more frustrating to a new contributor than investing
> > their
> > > personal time just to find out that it was wasted. So let's be mindful
> of
> > > not using this as a dumping ground for everything we'd like to see, but
> > > know we'll never get to.
> > >
> > > I already labeled a few more tickets as starter. Please feel free to
> > > validate that I didn't violate my own suggestions in doing so.
> > >
> > > Thoughts?
> >
> >
>

Re: Starter tickets

[Michael Stolz]

I'd love to tag all the pulse issues as newbie if we could.



On Fri, Mar 2, 2018 at 1:34 PM, Anthony Baker  wrote:

> Good idea!  We he have a few other labels relevant to this as well:
>
> - newbie
> - low-hanging-fruit
>
> Anthony
>
>
> > On Mar 2, 2018, at 10:03 AM, Alexander Murmann 
> wrote:
> >
> > Hi all,
> >
> > I think we could make it easier for people to find tasks that can be
> their
> > first contribution to Geode. The wiki page on how to contribute
> > 
> has a
> > list of suggested projects. Most of those are pretty ambitious and likely
> > would be overwhelming to first time contributors. There also is a link
> > to tickets
> > labeled with "Starter"
> >  3D%20Geode%20AND%20labels%20%3D%20starter%20AND%20status%
> 20in%20%28Open%2C%20%22In%20Progress%22%2C%20Reopened%29>.
> > I think the later is probably a much better angle for someone to start
> > contributing to Geode. Unfortunately there was less than a handful of
> > tickets labeled as starter tickets.
> >
> > My suggestion is to find tickets that strike a healthy balance between
> being
> >
> >   - simple enough that someone new to the code base can realistically
> take
> >   them on
> >   - rewarding enough that someone can feel a sense of accomplishment
> after
> >   having their PR merged
> >   - small enough that it can be accomplished in an evening or at most a
> >   long weekend
> >   - unlikely to result in conflicts with larger efforts that someone is
> >   already undertaking
> >
> > It would be great to have a variety of tickets that have different levels
> > of complexity and required effort to allow new contributors of varying
> > experience levels to start contributing meaningfully and maybe even
> support
> > somewhat of a progression curve for someone who wants to become a regular
> > contributor or even committer.
> >
> > I'd also suggest to not allow the list to grow too large. If the list
> gets
> > bigger than 20-30 tickets it might get too hard to keep a clear grasp on
> it
> > and the risk of having tickets that aren't relevant anymore increases.
> > Nothing would be more frustrating to a new contributor than investing
> their
> > personal time just to find out that it was wasted. So let's be mindful of
> > not using this as a dumping ground for everything we'd like to see, but
> > know we'll never get to.
> >
> > I already labeled a few more tickets as starter. Please feel free to
> > validate that I didn't violate my own suggestions in doing so.
> >
> > Thoughts?
>
>

Re: Starter tickets

[Anthony Baker]

Good idea!  We he have a few other labels relevant to this as well:

- newbie
- low-hanging-fruit

Anthony


> On Mar 2, 2018, at 10:03 AM, Alexander Murmann  wrote:
> 
> Hi all,
> 
> I think we could make it easier for people to find tasks that can be their
> first contribution to Geode. The wiki page on how to contribute
>  has a
> list of suggested projects. Most of those are pretty ambitious and likely
> would be overwhelming to first time contributors. There also is a link
> to tickets
> labeled with "Starter"
> .
> I think the later is probably a much better angle for someone to start
> contributing to Geode. Unfortunately there was less than a handful of
> tickets labeled as starter tickets.
> 
> My suggestion is to find tickets that strike a healthy balance between being
> 
>   - simple enough that someone new to the code base can realistically take
>   them on
>   - rewarding enough that someone can feel a sense of accomplishment after
>   having their PR merged
>   - small enough that it can be accomplished in an evening or at most a
>   long weekend
>   - unlikely to result in conflicts with larger efforts that someone is
>   already undertaking
> 
> It would be great to have a variety of tickets that have different levels
> of complexity and required effort to allow new contributors of varying
> experience levels to start contributing meaningfully and maybe even support
> somewhat of a progression curve for someone who wants to become a regular
> contributor or even committer.
> 
> I'd also suggest to not allow the list to grow too large. If the list gets
> bigger than 20-30 tickets it might get too hard to keep a clear grasp on it
> and the risk of having tickets that aren't relevant anymore increases.
> Nothing would be more frustrating to a new contributor than investing their
> personal time just to find out that it was wasted. So let's be mindful of
> not using this as a dumping ground for everything we'd like to see, but
> know we'll never get to.
> 
> I already labeled a few more tickets as starter. Please feel free to
> validate that I didn't violate my own suggestions in doing so.
> 
> Thoughts?