Skip to content

Commit b7db636

Browse files
committed
add post on upcoming R Dev Days
1 parent 16524f4 commit b7db636

15 files changed

Lines changed: 3306 additions & 2 deletions

README.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -46,12 +46,12 @@ There are currently three different types of content on the website:
4646
To start a new blog post, create a new directory in the relevant years' directory, e.g.
4747

4848
```r
49-
dir.create("blog/2023/example-blog-post")
49+
dir.create("blog/2023/example-blog-post", recursive = TRUE)
5050
```
5151

5252
where the name of the directory defines the URL of your post.
5353

54-
Within the subdirectory, create a new file, `index.Rmd`, with the following header
54+
Within the subdirectory, create a new file, `index.qmd`, with the following header
5555

5656
```yaml
5757
---

blog/2025/r-dev-days/css_group.jpg

155 KB
Loading

blog/2025/r-dev-days/index.qmd

Lines changed: 66 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,66 @@
1+
---
2+
title: R Dev Days 2025
3+
author:
4+
- name: Heather Turner
5+
date: "2025-04-10"
6+
categories: [news, community]
7+
description: "Upcoming deadlines to join an R Dev Day and collaborate on contributions to the code, documentation and translations in base R"
8+
draft: false
9+
---
10+
11+
R Dev Days are events for novice and experienced contributors to
12+
collaborate on contributions to the code, documentation and translations in
13+
base R. There are several planned in the coming months with
14+
application/registration deadlines in the next couple of weeks - don't miss out!
15+
16+
![A small group at the R Dev Day after useR! 2024](css_group.jpg){width="60%" fig-align="left" fig-alt="Participants sitting around a desk with their laptops at an R Dev Day, turning to smile at the camera. The group appears to be predominantly women of multiple nationalities and one of the group may be recognised as the well-known R developer, Hadley Wickham."}
17+
18+
## Upcoming events
19+
20+
The table below summarises the events with close deadlines:
21+
22+
| Satellite to | Where | Date | Deadline |
23+
|:-----------------------------:|:----------------:|:-------------:|:---------:|
24+
| [Rencontres R 2025 (19-21 May)](https://pretix.eu/r-contributors/r-dev-day-rr2025/) | Mons, Belgium | Thu 22 May | Fri 18 Apr |
25+
| [useR! 2025 (8-10 Aug)](https://user2025.r-project.org/additional/r-dev-day) | Durham, NC, USA | Mon 11 Aug | Tue 15 Apr |
26+
| [RSECon25 (9-11 Sep)](https://warwick.ac.uk/fac/sci/statistics/news/r-dev-day-rsecon25) | Warwick, UK | Fri 12 Sep | Wed 23 Apr |
27+
28+
There may be further events later in the year - for the latest information, see
29+
the [R Dev Days](https://contributor.r-project.org/events/r-dev-days/) page on
30+
the R Contributors website. R Dev Days are also publicised on the
31+
[R-devel mailing list](https://stat.ethz.ch/mailman/listinfo/r-devel), the
32+
R Contributor [Mastodon](https://hachyderm.io/@R_Contributors),
33+
[Bluesky](https://bsky.app/profile/R-Contributors.hachyderm.io.ap.brid.gy) and
34+
[Meetup](https://www.meetup.com/R-Contributors/)
35+
accounts, and the
36+
[R Foundation LinkedIn](https://www.linkedin.com/company/the-r-foundation-for-statistical-computing/)!
37+
38+
## How do R Dev Days work?
39+
40+
Tasks are prepared in the run-up to the event, where external contribution is
41+
welcome and good progress can be made in a day. Often this will be
42+
reviewing, analysing and/or fixing code or documentation bugs reported on R’s
43+
[Bugzilla](https://bugs.r-project.org), or translating message strings from
44+
English to other languages via
45+
[Weblate](https://translate.rx.studio/projects/r-project/). You can see
46+
examples of tasks on the [r-dev-day repo](https://github.com/r-devel/r-dev-day/issues).
47+
48+
Participants express interest in tasks prior to the event or at the start of
49+
the day. This helps to allocate people into small groups that work on one or
50+
two issues for the rest of the day. At the end of the day, the groups report
51+
progress on their task and any next steps required.
52+
53+
![Two participants discuss their work with R Core developer Martin Mächler](stem_group.jpg){width="60%" fig-align="left" fig-alt="R Core developer Martin Mächler working with Ella Kaye and Kelly Bodwin at an R Dev Day"}
54+
55+
## Are R Dev Days for you?
56+
57+
R Dev Days are aimed at people with a good knowledge of R programming that
58+
are keen to contribute back to the core codebase. Most participants will be
59+
comfortable writing and debugging R functions, writing help pages and using
60+
version control. Further expertise, such as competency in C programming or
61+
advanced knowledge of statistical methods, can certainly be useful, but is not
62+
necessary for all tasks.
63+
64+
Part of the objective is to foster a more diverse community of contributors,
65+
so anyone that identifies as part of an underrepresented group is
66+
particularly encouraged to apply!

blog/2025/r-dev-days/index_files/libs/bootstrap/bootstrap-973236bd072d72a04ee9cd82dcc9cb29.min.css

Lines changed: 12 additions & 0 deletions
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.

0 commit comments

Comments
 (0)