slack handbook section - initial #59
Conversation
|
pre-commit.ci autofix |
| ## Setting up a Slack bot using Slack Workflows | ||
| Administrators in the pyOpenSci Slack space can set up [workflows](https://slack.com/help/articles/16583775096083-Automations--What-is-a-Slack-workflow), which are automated bots that complete tasks based on automatic triggers. We currently use a workflow to onboard new members to the Slack space, and if there are additional bots you feel would be helpful, please reach out to Leah or Jesse. | ||
|
|
||
| ## Setting up an automatic feed to post from GitHub into Slack: |
There was a problem hiding this comment.
Here are a few note
- The slack integration settings can be found here in GitHub. IF YOU HIT THE configure button, it will allow you to configure which repositories are available to the slack / github integration bot.
@kierisi the part that i can't remember here is how i initially set this up. It may have been by calling a command in slack which lead me to the initial setup. Or i may have started on this website where you can add the bot to an organization?
does that help? the commands below that you wrote out look correct to me.
There was a problem hiding this comment.
@lwasser that helps! it looks like the link you've shared is the way to go in order to set up the integration for the overall slack workspace, so I can update everything!
There was a problem hiding this comment.
@kierisi this looks great. i've left a few comments and some information on the slack integration. id say make those edits and then please merge. If you need more info from me on slack please also say the word! But i'm approving this to be merged!
community/slack.md
Outdated
| * Everyone invited to Slack has generally already contributed to pyOpenSci in some way, and therefore have a vested interest in the community upon joining. | ||
| ### Who we invite to the community: |
There was a problem hiding this comment.
| * Everyone invited to Slack has generally already contributed to pyOpenSci in some way, and therefore have a vested interest in the community upon joining. | |
| ### Who we invite to the community: | |
| * Everyone invited to Slack has generally already contributed to pyOpenSci in some way, and therefore have a vested interest in the community upon joining. | |
| ### Who we invite to the community: |
There was a problem hiding this comment.
it's a good idea to have a full line break after a section heading. can you please fix this throughout? sphinx might allow it but generally we want a return before a new heading for readability too!
There was a problem hiding this comment.
yes! I'll get that sorted - thanks for flagging!
community/slack.md
Outdated
| ### Who we invite to the community: | ||
| We invite people to Slack who have contributed to pyOpenSci in some way. This can include attending and contributing via a sprint, submitting a package (normally this happens after the package has been accepted, but may occur earlier on an ad-hoc basis. Invites are rarely sent before the review is finished), being a reviewer or editor, contributing to a guidebook, or signing up to become involved. Often if someone signs up we meet with them prior to sending a Slack invitation. | ||
|
|
||
| We also occasionally invite people that would be valuable contributors to our community in some way, even if they haven’t already contributed! These might be people who express interest in work we are doing and who want to learn more or get involved. |
There was a problem hiding this comment.
We might also invite people who are from partner community and/or are doing work that is mission aligned!
|
|
||
| We have also strategically invited people with expertise in the field, including core packaging experts, community members and others with knowledge that is incredibly valuable to our community’s development. | ||
| ### How we invite new community members | ||
| Generally speaking, the Executive Director invites individuals who have not already contributed to pyOpenSci. These invitations are at their discretion, while package developers are usually invited by a pyOpenSci editor as part of the review process. |
There was a problem hiding this comment.
Just a note - ROS i think has the community manager invite people after reviews are done. i think they do it on fridays. we can feel out what works best here of ourse!
There was a problem hiding this comment.
@lwasser I have a calendar reminder to check our membership every Thursday (to grab folks that have been invited by editors so I can do a welcome post). I don't have insight into the review process at this point in terms of who's reviewing a package. would keeping an eye on github work? or do you have a suggestion for the best place to get that information?
accepted changes Co-authored-by: Leah Wasser <leah@pyopensci.org>
initial text for the Slack section of the pyOpenSci handbook. @lwasser if you could review, but also check the section on adding automated GitHub feeds to Slack, that would be great. I haven't (yet) set up a GitHub feed to Slack, so I'm not sure if these instructions are still accurate, or if they're clear enough.