Skip to content

Commit 3c5719c

Browse files
maellesteffilazerte
maelle
and
steffilazerte
authored
Remove all mentions of the forum (#93)
* Remove all mentions of the forum * Update rsrc_usecases.qmd Co-authored-by: Steffi LaZerte <steffi@steffi.ca> --------- Co-authored-by: Steffi LaZerte <steffi@steffi.ca>
1 parent c36d455 commit 3c5719c

3 files changed

Lines changed: 20 additions & 42 deletions

File tree

‎rsrc_channels.qmd‎

Lines changed: 16 additions & 33 deletions
Original file line numberDiff line numberDiff line change
@@ -16,20 +16,21 @@ The following table lists every communication channel and its purpose.
1616
Below that we describe how we use a few specific channels and provide some advice on deciding whether a question you might have is one for rOpenSci or belongs in a more general forum.
1717

1818
```{r, results = "asis", echo = FALSE}
19-
library(tibble)
19+
library(tibble)
2020
library(kableExtra)
21-
tribble(~Channel, ~Purpose,
22-
"Website <https://ropensci.org/> <https://github.com/ropensci/roweb3>", "Home of rOpenSci",
23-
"[Newsletter](https://ropensci.org/news/)", "A digest of R package news, use cases, blog posts, events, curated every two weeks. [Subscribe](https://ropensci.org/news/) via RSS (XML), JSON feed, or email.",
24-
"[Videos](https://vimeo.com/ropensci)", "Videos from past Community Calls on Vimeo",
25-
"[Mastodon](https://hachyderm.io/@rOpenSci)", "Posts about rOpenSci software, use cases, blog posts, tech notes, events",
26-
"Video conferencing", "Community Calls and remote co-working sessions on Zoom",
27-
"[GitHub - ropensci](https://github.com/ropensci)", "Mature R packages contributed by rOpenSci staff or community-contributed peer-reviewed packages; software peer review system; rOpenSci website",
28-
"[GitHub - ropenscilabs](https://github.com/ropenscilabs)", "Experimental packages and code experiments from staff, collaborators, and participants of unconfs and related events",
29-
"[GitHub - ropensci-org](https://github.com/ropensci-org)", "Non-code repositories like this guide, the blog guide, ideas for Community Calls",
30-
"[Discussion forum](https://discuss.ropensci.org/)", "Public forum on Discourse for use cases, Q & A about rOpenSci packages, exploration of ideas and best practices",
31-
"Slack", "A semi-open space for communications among people who contribute to rOpenSci",
32-
"Email: info at ropensci dot org", "To reach rOpenSci staff when other modes are not suitable") %>%
21+
tribble(
22+
~Channel , ~Purpose ,
23+
"Website <https://ropensci.org/> <https://github.com/ropensci/roweb3>" , "Home of rOpenSci" ,
24+
"[Newsletter](https://ropensci.org/news/)" , "A digest of R package news, use cases, blog posts, events, curated every two weeks. [Subscribe](https://ropensci.org/news/) via RSS (XML), JSON feed, or email." ,
25+
"[Videos](https://vimeo.com/ropensci)" , "Videos from past Community Calls on Vimeo" ,
26+
"[Mastodon](https://hachyderm.io/@rOpenSci)" , "Posts about rOpenSci software, use cases, blog posts, tech notes, events" ,
27+
"Video conferencing" , "Community Calls and remote co-working sessions on Zoom" ,
28+
"[GitHub - ropensci](https://github.com/ropensci)" , "Mature R packages contributed by rOpenSci staff or community-contributed peer-reviewed packages; software peer review system; rOpenSci website" ,
29+
"[GitHub - ropenscilabs](https://github.com/ropenscilabs)" , "Experimental packages and code experiments from staff, collaborators, and participants of unconfs and related events" ,
30+
"[GitHub - ropensci-org](https://github.com/ropensci-org)" , "Non-code repositories like this guide, the blog guide, ideas for Community Calls" ,
31+
"Slack" , "A semi-open space for communications among people who contribute to rOpenSci" ,
32+
"Email: info at ropensci dot org" , "To reach rOpenSci staff when other modes are not suitable"
33+
) %>%
3334
kable(format = "markdown")
3435
```
3536

@@ -47,23 +48,6 @@ see [Collaborating with issues and pull requests](https://docs.github.com/en/git
4748
To learn about Markdown formatting for interacting with others in issues and pull requests see [Getting started with writing and formatting on GitHub](https://docs.github.com/en/github/writing-on-github/getting-started-with-writing-and-formatting-on-github).
4849
For guidance on connecting R to GitHub we recommend Happy Git and GitHub for the useR - [https://happygitwithr.com/](https://happygitwithr.com/).
4950

50-
51-
<div id="channels-forum"></div>
52-
53-
**Public discussion forum**
54-
55-
[The forum](https://discuss.ropensci.org/) is where we encourage people to have Q & A on a wide range of topics.
56-
It is organized in categories including [**Use Cases**](#usecases) where people post examples of how they've used rOpenSci packages,
57-
[**Blog**](#blog) where an entry is made every time a new post or tech note appears on our blog, [**Statistical Software Peer Review**](#statsreview) for discussion related to developing a software peer review system for statistical software in R,
58-
**Wishlist** for discussions about requested new R packages,
59-
**Antarctic** for discussions about R in Antarctic and Southern Ocean science, and others!
60-
It includes posts like "How do you hire data people in a fair and unbiased way?" in the Community category, to specific help requests about our packages like "Taxize: Get rank of lowest common taxon".
61-
62-
The benefit of posting to our forum, rather than our semi-open Slack space or by email,
63-
is that it is open for others to benefit, searchable within the forum,
64-
and discoverable by browser-based searches.
65-
Posting in the forum requires login and we encourage people to use their real names.
66-
6751
<div id="channels-slack"></div>
6852

6953
**Slack**
@@ -120,6 +104,5 @@ and an rOpenSci Community Call - [How to Ask Questions so they get Answered! Pos
120104
* Read our [Code of Conduct](https://ropensci.org/code-of-conduct/) to ensure you are ready to participate
121105
* **Follow [rOpenSci on Mastodon](https://hachyderm.io/@rOpenSci)**
122106
* **Subscribe to our [Newsletter](https://ropensci.org/news/)**
123-
* **Ask or answer questions**. Participate in discussions in the [forum](https://discuss.ropensci.org/), on GitHub or on Slack
124-
* **Try a 2-hour [remote co-working session](https://www.cscce.org/2020/02/04/online-co-working-partnerships-are-community-of-practice-in-action/)** with someone in our Slack #co-working channel
125-
* **Seek community feedback on your package ideas in the "Packages" category in our [forum](https://discuss.ropensci.org/c/packages)**
107+
* **Ask or answer questions**. Participate in discussions on GitHub or on Slack
108+
* **Try a 2-hour [remote co-working session](https://www.cscce.org/2020/02/04/online-co-working-partnerships-are-community-of-practice-in-action/)** with someone in our Slack #co-working channel

‎rsrc_statsreview.qmd‎

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -13,8 +13,6 @@ This work is [supported by the Sloan Foundation](https://ropensci.org/blog/2019/
1313
### How to contribute
1414

1515
* **Read our in-progress book** [rOpenSci Statistical Software Peer Review](https://stats-devguide.ropensci.org/index.html) to familiarize yourself with standards and processes under development
16-
* **Follow the discussion**.
17-
Browse the dedicated [area for discussion on the rOpenSci forum](https://discuss.ropensci.org/c/statistical-software-peer-review/28) and share your comments or questions.
1816
* **Make a suggestion**.
1917
We welcome contributions to the project either by filing suggestions as [issues in the book's GitHub repository](https://github.com/ropenscilabs/statistical-software-peer-review/issues), or by submitting a pull request.
2018
* **Contact us** directly (via [Slack](#channels-slack) or our

‎rsrc_usecases.qmd‎

Lines changed: 4 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
## Use cases {#usecases}
22

33

4-
You can **find use cases** for rOpenSci packages and resources on our [rOpenSci Use Cases page](https://ropensci.org/usecases/) or in [our public forum UseCases category](https://discuss.ropensci.org/c/usecases/10).
4+
You can **find use cases** for rOpenSci packages and resources on our [rOpenSci Use Cases page](https://ropensci.org/usecases/).
55

66
A "use case" here is a write-up of an example, including an explanation of what you did,
77
some code, and where possible, an image showing an outcome.
@@ -16,9 +16,7 @@ tweets about fires, and others!
1616
Some use cases outline examples of how resources like our [guide on package development, review and maintenance](#devguide) have been used independently of rOpenSci
1717
Read more in our blog post, [What are Your Use Cases for rOpenSci Tools and Resources?](https://ropensci.org/blog/2019/10/15/use-cases/)
1818

19-
You can **search or sort by package, title or date** on the rOpenSci Use Cases page and **topics in the forum are tagged with the names of rOpenSci packages** they address
20-
Clicking on a tag will show you all other posts in the forum that share that tag
21-
You can also search with terms like "[weather](https://discuss.ropensci.org/search?q=weather%20category%3A10)" or "[doi](https://discuss.ropensci.org/search?q=doi%20category%3A10)" to find use cases in an area of application.
19+
You can **search or sort by package, title or date** on the [rOpenSci Use Cases page](https://ropensci.org/usecases).
2220

2321
We love it when people share their use cases
2422
For so many reasons.
@@ -32,11 +30,10 @@ Developers and users will thank you and you'll get the credit and some visibilit
3230

3331
### How to contribute
3432

35-
* **Explore use cases** on the [rOpenSci Use Cases page](https://ropensci.org/usecases/) or in [our public forum UseCases category](https://discuss.ropensci.org/c/usecases/10)
36-
Comment on or [emoji heart] use cases that you find useful or inspiring.
33+
* **Explore use cases** on the [rOpenSci Use Cases page](https://ropensci.org/usecases/).
3734
Consider posting or sharing to other platforms if you find them particularly helpful.
3835
* We've made it easy to **submit your use cases** for rOpenSci packages (including your own) or resources by creating a template to guide you.
39-
When you [post your use case in the forum](https://discuss.ropensci.org/c/usecases/10) we'll post to Mastodon about it to rOpenSci's followers,
36+
When you [post your use case](https://ropensci.org/usecases/) we'll post to Mastodon about it to rOpenSci's followers,
4037
tagging you and the package or resource author,
4138
and we might feature it in our [newsletter](#channels).
4239
* **Encourage your peers to submit use cases**.

0 commit comments

Comments
 (0)