> I think the steps to be taken are: > > 1\. Prioritize. What are the most critical problems with choosenim? What > features are lacking?
Most problems are known and already filed as issues in choosenim's Github project. Some even have PRs fixing them. > 2\. Announce. Make a blog post with the list of issues sorted by priority and > invite the > community to contribute. Someone could fork the choosenim repo now, work on open issues and PRs and publish an improved version without any official blessing. AFAICS, the only thing that would be required to give such a release some degree of blessing and convey trust in it would be the ability to change the script at <https://nim-lang.org/choosenim/init.sh>. I'm not sure who maintains the channel URLs (e.g. <https://nim-lang.org/channels/stable>), but it seems they are kept up-to-date already. > 3\. (Optional) Reward. Offer a signed copy of Mastering Nim to the most > prolific contributors. Any reward of that kind would be insufficient to even remotely be adequate to compensate for the effort needed to bring this project back on track. This needs volunteers who are able and willing to invest some of their time without immediate reward. What usually makes people willing to do this are not material rewards but a degree of confidence that their effort will be appreciated and not in vain. I.e. that could be some kind of statement from the Nim maintainers that choosenim is seen as an important part of the Nim ecosystem and that they will work together with a future choosenim maintainer when it is is needed (i.e. to set up well-known URLs on nim-lang.org or work together to ensure always signed binary releases, etc.).
