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
This repo seems to be unmaintained: there are several open issues that report problems that critically affect the usability of Mons. I think the developer @coloursofnoise may have been caught up with something this year and cannot spare to work on Celeste-related projects, and this is totally fine.
However, it is still bad that this project is basically unusable now, and a CLI mod manager for Celeste is still something that people need to use. Therefore, what I propose here is that we can let Everest team maintain a fork of this project, and permit them to publish releases to the PyPI package (by inviting some other team member's PyPI account as a collaborator of the PyPI package or by trusting the forked repo as a publisher so that it can publish via GitHub Actions).
I myself is not a member of Everest team, so this is just an unmature proposal, but I do think it is worth considering.
This repo seems to be unmaintained: there are several open issues that report problems that critically affect the usability of Mons. I think the developer @coloursofnoise may have been caught up with something this year and cannot spare to work on Celeste-related projects, and this is totally fine.
However, it is still bad that this project is basically unusable now, and a CLI mod manager for Celeste is still something that people need to use. Therefore, what I propose here is that we can let Everest team maintain a fork of this project, and permit them to publish releases to the PyPI package (by inviting some other team member's PyPI account as a collaborator of the PyPI package or by trusting the forked repo as a publisher so that it can publish via GitHub Actions).
I myself is not a member of Everest team, so this is just an unmature proposal, but I do think it is worth considering.
There are some contexts on Discord.
The text was updated successfully, but these errors were encountered: