Plots2: Brainstorm list of supportive additions to Welcomebot

[jywarren]

Our new welcomebot "expandable sections" are great for offering support without overwhelming:

https://github.com/publiclab/plots2/blob/master/.github/config.yml

Let's brainstorm more additions!

On first opening an issue

Opening first PR

• [ ] ask people to join the weekly check-in
• [ ] put hints on Travis debugging
• [ ] installation help

Merging first PR

• [x] help someone else

[CleverFool77]

@jywarren How about these points -

• Ask to read code of conduct
• Give a link to gitter or chat channel
• Provide a link to first-timer issues

[jywarren]

oh, very nice ideas!

On Thu, Mar 21, 2019 at 11:28 AM Lekhika Dugtal [e-mail]
wrote:

@jywarren https://github.com/jywarren How about these points -

• Ask to read code of conduct
• Give a link to gitter or chat channel
• Provide a link to first-timer issues

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/publiclab/plots2/issues/5179#issuecomment-475276404,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AABfJ3vVmCcwngGQsmEgpu-kJ_D5-g1oks5vY6TmgaJpZM4b8o21
.

[IshaGupta18]

@jywarren a couple of more points:

Solving some issue

1. show related issues when the contributor is stuck (this would be very helpful to the contributor in taking reference)
2. after merging of a PR, show similar issues on which the contributor can work

[ananya]

Hey @jywarren @gauravano I have made a pr at #5242 and added gitter chat link, weekly check-in and installation help. I wasn't sure about travis debugging :sweat_smile: , please let me know about a good source to add it from.

[jywarren]

thank you!!! We'll check it out.

IshaGupta18, i wonder if there's a related issues bot we can install?

For travis, I'm thinking something like:

If you see errors, or a red X by your commits, this means the Travis
service has found some issues. Dangerbot may highlight what these are and
offer some links, but either way, clicking on the red X will let you read
through the log output as our tests run on your new code. Skim through and
look for lines with "ERROR" or "FAIL" to see if they have hints as to what
lines caused the issue. It can be helpful to copy the error text into the
comments so others can see and offer help in debugging.

Although the tests will say "ERROR" and "FAIL", please don't be
discouraged. Failing tests are supposed to be helpful, and to help build
your confidence in the final code. It's perfectly fine to open a PR with
some errors, because then other community members will be able to help you
figure them out! And it'll feel extra good when you solve them and the Xs
turn into green checkmarks.

With some nice friendly emoji too! What do you think?

On Sun, Mar 24, 2019 at 7:38 AM Ananya Agrawal [e-mail]
wrote:

Hey @jywarren https://github.com/jywarren @gauravano
https://github.com/gauravano I have made a pr at #5241
https://github.com/publiclab/plots2/pull/5241 and added gitter chat
link, weekly check-in and installation help. I wasn't sure about travis
debugging 😅 , please let me know about a good source to add it from.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/publiclab/plots2/issues/5179#issuecomment-475950525,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AABfJxOqIBQfg7FtLe2vmXkb6gWC87N3ks5vZ2OVgaJpZM4b8o21
.

[IshaGupta18]

Yes I think this sounds really good. We can do a related issues bot thing,
that could prove to be really useful and will make the contributor more
independent.

On Tue, Mar 26, 2019, 1:45 AM Jeffrey Warren [e-mail]
wrote:

thank you!!! We'll check it out.

IshaGupta18, i wonder if there's a related issues bot we can install?

For travis, I'm thinking something like:

If you see errors, or a red X by your commits, this means the Travis
service has found some issues. Dangerbot may highlight what these are and
offer some links, but either way, clicking on the red X will let you read
through the log output as our tests run on your new code. Skim through and
look for lines with "ERROR" or "FAIL" to see if they have hints as to what
lines caused the issue. It can be helpful to copy the error text into the
comments so others can see and offer help in debugging.

Although the tests will say "ERROR" and "FAIL", please don't be
discouraged. Failing tests are supposed to be helpful, and to help build
your confidence in the final code. It's perfectly fine to open a PR with
some errors, because then other community members will be able to help you
figure them out! And it'll feel extra good when you solve them and the Xs
turn into green checkmarks.

With some nice friendly emoji too! What do you think?

On Sun, Mar 24, 2019 at 7:38 AM Ananya Agrawal [e-mail]
wrote:

Hey @jywarren https://github.com/jywarren @gauravano
https://github.com/gauravano I have made a pr at #5241
https://github.com/publiclab/plots2/pull/5241 and added gitter chat
link, weekly check-in and installation help. I wasn't sure about travis
debugging 😅 , please let me know about a good source to add it from.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<https://github.com/publiclab/plots2/issues/5179#issuecomment-475950525
,
or mute the thread
<
https://github.com/notifications/unsubscribe-auth/AABfJxOqIBQfg7FtLe2vmXkb6gWC87N3ks5vZ2OVgaJpZM4b8o21

.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/publiclab/plots2/issues/5179#issuecomment-476359685,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Am54ZzjcuMwJe3E58kTyisvykmXfFp7Lks5vaS5vgaJpZM4b8o21
.