Hi

I was recently involved in a discussion on the slack that mentioned the
challenge of transitioning racketeers from users who log issues(“complain
and someone will fix it”)* or offer opinions(without the time or interest
to make a contribution)* into contributors.

While racket has many great contributors, this is probably not uncommon for
OSS communities, it made me think about ways to 'nudge' users towards
becoming contributors.

The following text in issue templates is a small attempt to nudge users to
contribute, while being explicit about what is useful in bug and feature
reports respectively.

**Expected development cost**
>  As you know nothing happens magically, so do you have an idea of the
> development effort required?
>  In addition, are you willing to help because after all Racket is yours
> too?


I’ve proposed issue templates via PR
https://github.com/racket/racket/pull/3254 that include the above 'Expected
development cost' text.

An example of the templates in is at
https://github.com/spdegabrielle/clash/issues/new/choose

[image: image.png]

I hope this is a useful contribution. Feedback on or off list appreciated.
Maybe use this thread for looking at other ways nudging users towards
contributorship. or even just mention what made you decide to be a
contributor.

Kind regards
Stephen

* guilty as charged m'ludd

-- 
You received this message because you are subscribed to the Google Groups 
"Racket Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to racket-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/racket-dev/CAGHj7-JyY0d%3DFwnJHsBvfrzyJ1OJSsMP978AcFe9G6_GeSPj4A%40mail.gmail.com.

Reply via email to