|
| 1 | +### Title |
| 2 | + |
| 3 | +Packaging and maintenance of the Astropy ecosystem for Debian and Ubuntu |
| 4 | + |
| 5 | +### Project Team |
| 6 | + |
| 7 | +Ole Streicher [email protected]/ @olebole |
| 8 | + |
| 9 | +### Project Description |
| 10 | + |
| 11 | +This is a proposal to fund the ongoing continuous maintainance and |
| 12 | +interaction of Astropy and its related software within Debian, Ubuntu |
| 13 | +and other distributions that use Debian as a base. Aside from the |
| 14 | +major goal of providing high quality native packages of Astropy within |
| 15 | +Debian, this will improve the quality of the Astropy ecosystem by |
| 16 | +providing compatibility checks on a wide range of machine |
| 17 | +architectures and environments. |
| 18 | + |
| 19 | + |
| 20 | +### Project / Work |
| 21 | + |
| 22 | + * keep Astropy in Debian and Ubuntu up to date and in good shape |
| 23 | + |
| 24 | + - maintain distribution specific patches for Astropy and other packages |
| 25 | + (policy, tests, metadata etc.) |
| 26 | + |
| 27 | + - fix packaging related bugs |
| 28 | + |
| 29 | + - observe CI tests and rebuilds on supported platforms and ports for both |
| 30 | + Ubuntu and Debian; report problems and participate in the solution |
| 31 | + |
| 32 | + * maintain the Astropy related infrastructure in Debian |
| 33 | + |
| 34 | + - maintain required dependencies |
| 35 | + |
| 36 | + - follow changes in environment (dependencies, policy); react on new |
| 37 | + incompatibilities and requirements |
| 38 | + |
| 39 | + - ensure packaging of coordinated packages; maintain them if needed |
| 40 | + |
| 41 | + - propagate and coordinate packaging of affiliated packages and backports |
| 42 | + |
| 43 | + - Debian mentorship+sponsorship for affiliated packages if needed |
| 44 | + |
| 45 | + - observe the packaging of reverse dependencies; help in solving |
| 46 | + compatibility problems |
| 47 | + |
| 48 | + * act as a link between the Debian distribution and the Astropy community |
| 49 | + |
| 50 | + - discuss/forward bugs to upstream, backport/apply fixes if needed |
| 51 | + |
| 52 | + - participate in relevant discussion in both communities, connect |
| 53 | + people for problem solution if needed |
| 54 | + |
| 55 | + |
| 56 | +### Approximate Budget |
| 57 | + |
| 58 | +Due to the continuous nature of the work, the budget should be based |
| 59 | +on a hourly rate. By the experience from the last years, a realistic |
| 60 | +estimate would be 8 hours per month. Using a suggested rate of |
| 61 | +USD 150/hour, this would sum up to an estimated total of USD 14,400. |
| 62 | + |
| 63 | +This would also be the reasonable maximum, covering the real work that |
| 64 | +is done. I would estimate a useful minimum by USD 9,000 (equivalent to |
| 65 | +5 hours per month). |
| 66 | + |
| 67 | +### Approved Funding |
| 68 | + |
| 69 | +$14,400.00. |
0 commit comments