You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: finance/proposal-calls/cycle3/user-dev-support-rse.md
+23-12Lines changed: 23 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -21,6 +21,8 @@ based on the available budget.
21
21
22
22
### Project / Work
23
23
24
+
#### Research software engineer
25
+
24
26
The Astropy Project is seeking to hire a full-time or part-time research software engineer on a fixed-time contract to develop and implement new features that the community has identified as high priorities in the roadmap but that the volunteer contributors do not have the capacity to deliver, as well as address smaller, but long-standing bugs and issues in the astropy core package and the coordinated packages.
25
27
26
28
The broad scope of work for the RSE includes any efforts to support both Astropy users
@@ -30,9 +32,7 @@ given below). In particular, the RSE shall tackle a number of long-standing issu
30
32
bugs as listed in the issue trackers for the core package and the coordinated packages;
31
33
more bugs and issues are available than can be addressed by this position, so the
32
34
choice of which ones to address will be guided by community input, and the experience
33
-
and expertise of the RSE, under the manager's supervision. To reduce the burden on volunteer
34
-
maintainers, the funded manager will perform a first review where appropriate, to keep the
35
-
effort needed for the sub-package maintainers to a minimum.
35
+
and expertise of the RSE, under the manager's supervision.
36
36
37
37
The RSE position is distinct from the Software Operational Support Specialist (SOSS)
38
38
position in that the RSE is expected to take on and complete discrete *projects*, rather
Together with the RSE role, there will be a funded manager position filled by an experienced member of the astropy project with commit permissions in the main repository. The manager will be responsible for the following tasks:
70
+
71
+
- Onboarding the RSE to the project and the community.
72
+
- Providing guidance and feedback to the RSE.
73
+
- To reduce the burden on volunteer maintainers, the funded manager will perform a first review where appropriate, to keep the effort needed for the sub-package maintainers to a minimum. We expect this to be one of the main responsibilities of the manager.
74
+
- The manager organizes the community input on which topics and road-map issues to prioritize for the RSE.
75
+
- Report progress, issues, and challenges to the Astropy Project community.
76
+
77
+
The manager is funded for 0.1 FTE. This time will be spread that over the same period that the RSE is active, the managers work is not evenly distributed over that period, though. We expect considerably more involvement in the beginning with onboarding and the first few PRs, and relatively less involvement in later phases; however, on average over a 12 months period, the manager's level of effort is expected to be 0.1 FTE; for example, if the RSE contract runs for 9 months, this could be distributed as, 8 h/week for the first three months, 4 h/week for the next three months and 0 h/week for the last three months of the year (when the RSE is no longer active). The exact details as to be determined by the manager and the RSE, it is the manager's responsibility to track their effort and report it to the Astropy Project.
0 commit comments