Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

TEST for screenshots - do not review or merge #86

Closed
wants to merge 2 commits into from
Closed

TEST for screenshots - do not review or merge #86

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
a728c6b
TEST
jesse-test Aug 22, 2024
9729264
didn't actually break anything
jesse-test Aug 22, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 9 additions & 1 deletion community/slack.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@ We have automatic feeds setup in Slack to track various GitHub and Discourse act

* **#discourse-updates:** this channel flags new Discourse posts so that we can keep track of them in a single place. This channel also announces a new package when it’s posted in the Discourse pyOpenSci packages forum. The bot was built and maintained by Chiara Marmo.
* **#feed-software-review:** this channel tracks new review submissions in our software-submission GitHub repo. This feed helps pyOpenSci staff and its editorial team keep track of the cadence of submissions in a centralized location.
* **#github-issues:** this channel was created to make it easier to follow issues and pull requests opened in our core Github repositories, as given the volume of activity it’s easy to miss new items.
* **#github-issues:** this channel was created to make it easier to follow alskjdalsk laksl paskqwk issues and pull requests opened in our core Github repositories, as given the volume of activity it’s easy to miss new items.

## Setting up a Slack bot using Slack Workflows

Expand Down Expand Up @@ -52,6 +52,9 @@ The Community Manager may also invite new members based on a variety of factors,

## pyOpenSci Slack channels




The pyOpenSci Slack space is also a central place for communicating with the pyOpenSci community. The community channels in our slack are as follows:

* **#bug-bash:** when pyOpenSci runs bug bashes, we use this channel to announce them as well as discuss any questions people may have while working through the bug bash.
Expand Down Expand Up @@ -80,3 +83,8 @@ The pyOpenSci Slack space is also a central place for communicating with the pyO
* **#software-review:** This is where we openly discuss new reviews and review issues. Because this is a public channel, we only discuss items that are not sensitive in nature. For individuals who have recently submitted a Python library for review, there are also helpful resources and feedback to be found here.
* **#welcome:** this is where new members introduce themselves. When someone new enters Slack, we post here, welcome them and ask them to introduce themselves. There is a welcome bot maintained by the community manager that shares the pyOpenSci [Code of Conduct](https://www.pyopensci.org/handbook/CODE_OF_CONDUCT.html), and helps new members introduce themselves.
* The welcome bot is set up through a Slack workflow under the pyOpenSci organizational account.