Skip to content

Commit 0629725

Browse files
committed
Spell out managers schedule and responsibilities in more detail.
1 parent 6941f59 commit 0629725

File tree

1 file changed

+23
-12
lines changed

1 file changed

+23
-12
lines changed

finance/proposal-calls/cycle3/user-dev-support-rse.md

Lines changed: 23 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -21,6 +21,8 @@ based on the available budget.
2121

2222
### Project / Work
2323

24+
#### Research software engineer
25+
2426
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.
2527

2628
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
3032
bugs as listed in the issue trackers for the core package and the coordinated packages;
3133
more bugs and issues are available than can be addressed by this position, so the
3234
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.
3636

3737
The RSE position is distinct from the Software Operational Support Specialist (SOSS)
3838
position in that the RSE is expected to take on and complete discrete *projects*, rather
@@ -44,15 +44,6 @@ Roadmap](https://github.com/astropy/astropy-project/blob/main/roadmap/roadmap.md
4444
community has already prioritized, but not yet found the resources to implement.
4545

4646
Example projects:
47-
* *Restructure the Astropy developer documentation*: The current developer documentation
48-
pages have a wealth of content aimed at both new contributors and expert technical
49-
engineers, but it is mixed and hard for contributors with different skill levels to
50-
easily find the content most appropriate for them. The goal of this project is to
51-
restructure the documentation pages to provide easier pathways for potential or
52-
existing contributors with different skill levels to find relevant developer
53-
documentation they need to make a contribution. Relevant issues:
54-
[#11620](https://github.com/astropy/astropy/issues/11620),
55-
[#11621](https://github.com/astropy/astropy/issues/11621)
5647
* *Implement robust benchmark reporting for pull requests* ([drawn from the Astropy
5748
Roadmap](https://github.com/astropy/astropy-project/blob/main/roadmap/roadmap.md)): This
5849
project would enable a way of evaluating the performance impact of pull requests by
@@ -64,6 +55,26 @@ Roadmap](https://github.com/astropy/astropy-project/blob/main/roadmap/roadmap.md
6455
Ensure that coordinated and infrastructure packages have integration tests that check
6556
the joint usage of Astropy and these other packages together, rather than individually
6657
(as is often the case now).
58+
* *Restructure the Astropy developer documentation*: The current developer documentation
59+
pages have a wealth of content aimed at both new contributors and expert technical
60+
engineers, but it is mixed and hard for contributors with different skill levels to
61+
easily find the content most appropriate for them. The goal of this project is to
62+
restructure the documentation pages to provide easier pathways for potential or
63+
existing contributors with different skill levels to find relevant developer
64+
documentation they need to make a contribution. Relevant issues:
65+
[#11620](https://github.com/astropy/astropy/issues/11620),
66+
[#11621](https://github.com/astropy/astropy/issues/11621)
67+
68+
#### Mananger
69+
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.
6778

6879

6980
### Approximate Budget

0 commit comments

Comments
 (0)