Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cycle 4: Moritz to work on astropy.io.ascii and X-ray spectral modelling #385

Merged
merged 2 commits into from
Apr 29, 2024
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
47 changes: 47 additions & 0 deletions finance/proposal-calls/cycle4/moritz_ascii.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,47 @@
### Title

Addressing issues in `astropy.io.ascii`

### Project Team

- Moritz Guenther (@hamogu)

### Project Description

Address (by fixing or closing) open issues in `astropy.io.ascii`
hamogu marked this conversation as resolved.
Show resolved Hide resolved


### Project / Work

hamogu marked this conversation as resolved.
Show resolved Hide resolved
At the time of writing there are [66 open issues in astropy tagged `io.ascii`](https://github.com/astropy/astropy/issues?q=is%3Aopen+is%3Aissue+label%3Aio.ascii), 57 of which are older than 18 months.

While astropy clearly thrives with those bugs and issues, each of them represents at least one user
who was stopped in their work and found this annoying enough to open an issue. We know anecdotally, that
many users who do not think of themselves as "developers" don't open issues on github (e.g. they might not
even have an account) so each bug probably represents several or more users who have run
into a problem. For a smooth user experience, we should close out bugs and fill in feature requests
where we can.

Not all of these issues are actionable (e.g. some
require upstream fixes or
[would require fairly invasive changes that would break backwards compatibility in a way that does not seem warrented](https://github.com/astropy/astropy/issues/5440#issuecomment-880703756));
however most can be addressed given some developer time.

hamogu marked this conversation as resolved.
Show resolved Hide resolved
Moritz proposes to pay a sub-grant to MIT to pay for some of his time to
work on those issues. Based on previous PRs, I estimate that I can address
on average one issue in one to two work days, so paying for 10% of my work time for one year should allow me to address the majority of the currently open issues.



### Approximate Budget

Budget breakdown (nominal):

- $25,000 for 10% of my time for 1 year
hamogu marked this conversation as resolved.
Show resolved Hide resolved

(Since this will be a sub-award to MIT, my salary is fixed by MIT and the overhead rate is fixed by agreement between MIT and the US government. We can change the length of the contract, but not the hourly rate.)

The minimum useful time is determined by how much effort it is to set up that sub-award. I can work on one issue in 8 hours of work, but neither MIT nor NumFOCUS would want to write and process a subaward contract for that little money. Realistically, it's probably not worth the effort if less than $5-10k are allocated to this project.

### Period of Performance
1 year
hamogu marked this conversation as resolved.
Show resolved Hide resolved