State of this project about nodist HOT 17 CLOSED

Hello,

@marcelklehr I saw your messages yesterday and meant to get back to you. I had some family tragedies this fall and it has affected my ability to get in and push a new release out.

That being said, I would still like to continue to help maintaining this project. Maybe it will be possible to get a new release out and solve some of the issues we are having.

@marcelklehr I will respond to you directly on chat.

Thank you for staying in touch.

from nodist.

@marcelklehr @nullivex As nothing has happened since January, I am preparing a new release.

You can check out https://github.com/Mairu/nodist if you want. I am OK if @nullivex creates the release here, but I would also volunteer as a second maintainer and do it myself if it would help?

from nodist.

HI @Mairu, @nullivex, @marcelklehr
We use your project here in Philips-Algotec and would like to contribute to get it working well again with new NPM versions etc>
I saw your fork contains lots of goodies such the fix for NPM versions, github auth etc.
compare fork
what hinders from merging this fork , finishing the github actions pipeline and issuing a release?
I can suggest myself as a third maintainer if you need a hand

from nodist.

@marcelklehr Thank you for getting me back in gear on this project. I will try to give it a couple hours a week and push the progress along with you, rather than trying to queue up some kind of massive work.

I have adjusted my processes of the past few years and I am glad Nodist is helping developers!

from nodist.

@nullivex I'm glad we could get the ball rolling again, and even happier to have you chime in regularly, but don't feel obliged to make time you don't have. I feel optimistic that we can get something together even without your help now that we have the possibility to have more people with responsibility. In any case, I'm looking forward to new releases ✌️

from nodist.

With the project moving again. I am going to close this thread. Congratulations on the progress and new releases! I love to see the community in action.

from nodist.

Hi @nullivex 🎉 ♥️
I'm glad to hear from you and sorry to hear about tragedies in your family. I'm sorry if the above post sounded a bit harsh. Thank you for all the work you have put in so far!

That being said, I would still like to continue to help maintaining this project. Maybe it will be possible to get a new release out and solve some of the issues we are having.

That sounds great! Maybe we could still use a second maintainer to ease the burden on you a bit, if you want.

Looking forward to chatting with you :)

from nodist.

Hey @Mairu!

I think having a second maintainer would be great, especially for situations like this one! @nullivex What do you think?

from nodist.

what hinders from merging this fork, finishing the github actions pipeline and issuing a release?

Currently, this is hindered by the absence of someone with write access to the repo. Alas, it's always better to have a contingency plan...

from nodist.

Are there things nodist can do, which https://github.com/coreybutler/nvm-windows cannot?
If so, I may be willing to help a bit with the maintenance, but if not, it might be better to deprecated to that one with the appropriate notices. (Even in the latter case, if you wish, I am willing to hold write access for a while in case nvm-windows has issues and there's a later desire to revive this.)

from nodist.

Are there things nodist can do, which https://github.com/coreybutler/nvm-windows cannot?

Transparent per-project/per-directory node version switching. E.g. at my work we have several products, right now all are using Node 18, but there was a point in time when I needed to have 3 different major versions of Node to be able to work on these products. Almost every day I had to do some work on the product my team is maintaining, plus one of the other products (which integrate the first product). Each project had a .node-version file at its root, specifying which node version is needed. Personally I use a MacBook at work, and nodenv to manage node versions, which supports .node-version. On Windows, nodist supports .node-version as well. Whenever you are in a directory containing a .node-version file, running node/npm commands will use the correct version, without having to switch manually. I wouldn't have it any other way.

from nodist.

@nullivex @marcelklehr @Mairu any updates on the maintainership / new releases?

from nodist.

So, I have collab rights now. 🎉 Thank you @nullivex

from nodist.

I don't have much time for this project, but anyone who wants to help move this project forward, I'll happily merge PRs if they make sense to me and I think I also still have privs for chocolatey -- haven't used that thing in a long time, though... So, I guess if someone trustworthy provides me with a build I can publish it :) ✌️

from nodist.

@marcelklehr I am glad you got access. I have transferred the project over to the organization. I hope we can get a new build together.

I pulled the code and updated to the latest version.

from nodist.

@marcelklehr It's my own fault for snowballing tasks that dont really have a blocking sequence. There has been a swift resolution in a lot of the stress factors I have been facing over the past few years. I am happy to be moving into the next chapter. If you need me for anything, let me know. I will keep time for checking Github and doing any fixes to the build system, the rest appears to be in capable hands! 👍

from nodist.

New release 0.10.3 has been published: https://github.com/nodists/nodist/releases/tag/v0.10.3

from nodist.