Skip to content

Commit 2118147

Browse files
authored
Merge pull request #223 from jdswinbank/finance-ctte-update-2021-11
December 2021 Finance Ctte update mail
2 parents 800f728 + cde8934 commit 2118147

File tree

1 file changed

+116
-0
lines changed

1 file changed

+116
-0
lines changed

finance/community-updates/2021-12.txt

Lines changed: 116 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,116 @@
1+
Dear Astropy Community,
2+
3+
The Finance Committee would like to give you some updates on our activities
4+
over the last year or so.
5+
6+
# NASA funding
7+
8+
In January of this year, several members of the project submitted a proposal
9+
to the NASA ROSES-2020 call, section E.7 (Support for Open Source Tools,
10+
Frameworks, and Libraries). The proposal included a mix of Project-wide
11+
infrastructure improvements, targeted work on specific areas of the code
12+
that are in need of support, enhancements to the our educational materials,
13+
and better support for affiliated packages. The full text (with some
14+
personal details redacted) is available at [1].
15+
16+
The proposal was successful, and has provides a further $634,590 to support
17+
the fantastic work being undertaken by the Astropy Project. The Finance
18+
Committee will arrange processes for disbursing the funds which are
19+
consistent with the goals of the proposal and based on the model we've
20+
adopted for assigning Moore funding over the past couple of years.
21+
22+
This is a huge milestone for the project: it shows that we've successfully
23+
used the Moore funding to build a solid set of processes and a governance
24+
structure which enables us to obtain support from more “traditional” sources
25+
of finance. This is a great step towards ensuring the financial viability of
26+
the project into the future.
27+
28+
[1] https://drive.google.com/file/d/18JsTRahNWnvign6ao6BP_OkINHnP8g3n/view
29+
30+
# Gemini contract
31+
32+
The Science User Support Department at Gemini Observatory has provided
33+
funding to the Astropy Project for maintenance and development work that
34+
benefits both the Astropy and DRAGONS projects. We've enlisted Simon Conseil
35+
as a part-time contractor (averaging 5 hours per week over a period of a
36+
year or two) to do this work. The details of the work are described in the
37+
statement of work [2].
38+
39+
Having major facilities like Gemini invest in Astropy is another sign of
40+
both the critical role that the project plays in astronomical infrastructure
41+
worldwide, and of the increasing level of trust displayed in the project's
42+
responsible and sustainable governance.
43+
44+
[2] https://docs.google.com/document/d/1sKiFr5ypS3prkEqEu3s5nEejs0bD93cF7ihXSz3RdZM/edit
45+
46+
# Distribution of Moore funds
47+
48+
We organized a process to select and distribute funds from the Moore grant
49+
to a variety of projects, suggested and selected by the project membership.
50+
We've announced results in detail in the past [3] so we won't reiterate them
51+
in detail here, but we're delighted to report that most many of the projects
52+
are now well underway.
53+
54+
We except to organize similar processes to distribute Moore and NASA funding
55+
in future years. We intend to keep improving our approach to make this as as
56+
transparent and effective as possible. To that end, We conducted a survey of
57+
the community to solicit your views [4]. This showed that:
58+
59+
- There's a roughly even split between folks who like the established way of
60+
voting (“thumbs up on GitHub”) and those who prefer an anonymous system;
61+
62+
- There may be an opportunity to introduce more nuance to the voting (e.g.
63+
by assigning priorities);
64+
65+
- There's broad support for paying people to work on Astropy through an
66+
institution;
67+
68+
- The community places a roughly even priority on bringing in new people and
69+
supporting existing maintainers.
70+
71+
We will fold these results into our future plans, and continue to welcome your
72+
feedback at any time.
73+
74+
[3] https://groups.google.com/g/astropy-dev/c/c1M2F7rZoF4/m/nbNdg1OsAAAJ
75+
[4] https://groups.google.com/g/astropy-dev/c/odnYnaBCZKI
76+
77+
# Meetings, workshops, and other travel
78+
79+
We've supported project members to participate in and represent Astropy at a
80+
number of conferences and workshops over the last year. These include:
81+
82+
- Three project members were funded to (virtually) attended ADASS XXX, where
83+
Brigitta Sipocz spoke on “astroquery: a community driven collaboration of
84+
data providers and data consumers”. [5]
85+
86+
- Three project members hosted the “Astropy and NumFocus Sponsored Projects”
87+
booth in the Virtual Exhibit Hall at AAS 237. Project members also
88+
provided two workshops: “Introduction to Astropy” and “Research with
89+
Astropy”. [6]
90+
91+
- Similarly, three project members participated in AAS 238, again hosting
92+
workshops entitled “Introduction to Astropy” and “Astronomical Research
93+
with Astropy”. [7]
94+
95+
- We also supported three project members to participate in the SciPy 2021
96+
conference and workshop. [8]
97+
98+
The links below provide more information and take-away messages from each of
99+
these meetings.
100+
101+
[5] https://github.com/astropy/astropy-project/issues/141
102+
[6] https://github.com/astropy/astropy-project/issues/140
103+
[7] https://github.com/astropy/astropy-project/issues/201
104+
[8] https://github.com/astropy/astropy-project/issues/210
105+
106+
# No longer an Interim Finance Committee
107+
108+
One of the first acts of the recently-elected Coordination Committee
109+
(“CoCo3”) was to confirm the Finance Committee, with its current members, as
110+
a part of standing project organization and to remove the “interim” from its
111+
title. We're now just the “Astropy Finance Committee”! 🎉
112+
113+
Cheers,
114+
115+
John
116+
on behalf of the Astropy Finance Committee

0 commit comments

Comments
 (0)