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
I am in the process to upgrade the astropy version on Debian to 5.1, ensuring that all packages are compatible (i.e. pass their tests). For hipspy, I found that it does not work well with a number of problems. Hipspy did not see a commit since 2020, and it already for the past versions needed some adjustment.
I am willing to go through the required adjustments and make a PR; however this is only useful if there is a hope the package is kept alive for the next year or so (we will probably have our next Debian version in 2023).
Therefore, I would like to know what the status here is: It hipspy going to be maintained in the future or are we seeing it evaporate slowly?
Best regards
Ole
The text was updated successfully, but these errors were encountered:
Hi Ole, hipspy was developed as part of the GSoC program back in 2017. Since then we haven't worked on adding any new features or bug fixes. Although we're happy to receive PRs that improve / extend the code base, it is unlikely that this project will be actively maintained from our side. Maybe @cdeil can comment on this.
Dear maintainers,
I am in the process to upgrade the astropy version on Debian to 5.1, ensuring that all packages are compatible (i.e. pass their tests). For hipspy, I found that it does not work well with a number of problems. Hipspy did not see a commit since 2020, and it already for the past versions needed some adjustment.
I am willing to go through the required adjustments and make a PR; however this is only useful if there is a hope the package is kept alive for the next year or so (we will probably have our next Debian version in 2023).
Therefore, I would like to know what the status here is: It hipspy going to be maintained in the future or are we seeing it evaporate slowly?
Best regards
Ole
The text was updated successfully, but these errors were encountered: