Gridstack.js: Release a new version?

[shijistar]

Since this project had many code fixes and improvements in the past months, can we release a new version in bower? We have verified that the recent commits resolve some of my problems, but we can't use them for now, otherwise I have to folk this project and release a variant of this project in bower. Thanks.

[DnJealt]

I think @radiolips is dead man. No word from him or the other author since September..

[kerryj89]

It seems he has sudden bursts of commits and then disappears for a few months, maybe he'll be back soon.

[adumesny]

last burst of 'commits' (other people fixes, including some myself) was when I got involved and try to open it up for other contributors. but @radiolips and the original author never did open it up... just renamed to more public name and took pending commits. shame because I now have created a local branch and npm publish I need to maintain for fixes/features. Afraid this code is dead open source... you can't depend on 1 person.

[DnJealt]

If you fork it and open it up, I'll be happy to contribute.

[adumesny]

may have to do that... just not sure how to do it and also expose it here for others to start contributing and getting that published.

[linusg]

I would love to see an active fork... please make this happen guys! :heart:
@adumesny @DnJealt

[JohnArcher]

I tried to reach out to Dylan at Twitter but no response. :-/ So I would be interested in a maintained fork, too. @adumesny Well, as you already forked that, "just" commit your new code to your own repo and I think people who are looking for a new version will find your fork, e.g, through this issue. Or am I getting you wrong?

[krilllind]

Been talking a bit to @radiolips on email, said he has been extremely busy with other things, and that he would roll out some new updates soon. This was over a month ago tho..

So I wrote to him again and no response, my guess is that this lib might need a need a new fork and someone a bit more active.

[adumesny]

I don't think depending on one person (whoever that is) is the right way. I suggested to @radiolips before, is to open it to so anybody can check stuff in, but require maybe 2 other people to approve any CR before they can go in. Decentralize it, but not make it completely wild west either. I don't know if github support something like that.. or even opening a branch for anybody to submit to (what others have suggested).

I don't mind creating a fork and pushing in my changes and others I cherry picked, but I too have no time to support it per say...

[radiolips]

Agree with @adumesny . I'm going through the open issues as quickly as I can, and will then work on some automated rules for PRs to eliminate key dependencies on any humans.

@krilllind , @JohnArcher , my apologies for not responding. It wasn't just gridstack that I was gone from, but I'm fully back now. I'll even get through my tweets at some point...oof!

I'm leaving this ticket open for now. I'll close it when all processes are in place.

[adumesny]

Great to hear @radiolips . I've picked up the lodash removal CR that was posted a while ago, with some tweaks to match latest code, and it works great and remove yet another big dependency. We wanted to do that as well... great someone went through 98% of the effort.
Let me know if I can help at anything...

[radiolips]

(for those following my conversation with @adumesny , we've moved it to Slack! If you're reading this and you're not on Slack, join us! https://gridstackjs.troolee.com/ )

[radiolips]

It wasn't 1.0.0, but v0.4.0 was released yesterday.