No longer maintained?

[aponxi]

Seeing that there are a lot of open issues I'm guessing that this project is no longer maintained?

Does anybody have a fork that is being patched and developed ? Or is this pretty much dead?

[mreinstein]

I'm worried about this too. Nodeunit is relied upon by a lot of really important projects. If it's not going to be supported anymore then I'll need to find another option and standardize on that.

[gutomaia]

I share the same felling. Yesterday, I've twetted @caolan about my pull request (https://twitter.com/gutomaia/status/307857063357329408). Anyway, in twenty days the project will reach exactly one year without commits.

Beside him, I believe that the project dosen't have any other with pull request permissions. Or even permissions to submit a new releases to NPM package management.

That lead us to the option to fork and rename the project and create the "new" xyunit on NPM. However, we might start running in circles when that happen again.

In fact, since NPM dosen't have any way to delagate projects to friends, well at least as far as I know, I assume that In time, several project might sofrer from real world issues. Like death. We need to discuss that also with NPM guys.

That way we could create a renamed forked with not one, but several guys with release permission bounded and commited to release rules.

We must address NPM team about this issues this particular concern, and find a way to we all build a community.

[mreinstein]

@gutomaia I'm all for building a community- or in this case, keeping the community going. Nodeunit is a great module and I'd prefer to not fork or diverge if we can help it. I'm sure @caolan is probably busy with a lot of other projects. Let's first try to get a discussion going with him and see if maybe we can get an additional project maintainer. That's going to be a lot easier and better for the community IMO.

@caolan what are your thoughts on the future of nodeunit? If you are busy with more pressing matters, can we find some suitable maintainer(s) to sort through these issues and pull requests?

[aponxi]

@mreinstein As you were typing this, I've created an organization and forked this project. I've created pull requests from this repo's pull request, and merged the ones I could automatically merge (Now that I think about it, maybe I shouldn't have merged just yet - anyway we can always roll back.) https://github.com/NodeXI/nodeunit is the repo's address. I have added @mreinstein and @gutomaia as Managers for nodeunit project and if you'd like you can manage this fork from there.

I really like this plugin too and maybe through this fork we might be able to get together and patch things up.

If anyone would like to participate please let me know here.

[aponxi]

But then again, if we can discuss with @caolan and find a solution without diverging from this community that would be best.

[mreinstein]

Agreed. I'm sure Caolan is probably busy with a lot of other projects. Let's see if we can get a discussion going with him to get a sense of where the project is going and offer to help with some of these maintenance activities, if he's ok with that. Everyone wins that way. : )

[mreinstein]

@gutomaia and @aponxi, Caolan has granted me commit access to this repository to assist him with maintenance. I'm planning to sift through the pull requests today and pick some easy ones to merge in. If there are any that really stand out as being super useful, let me know and I'll prioritize looking at them first.

[aponxi]

I'm happy to hear that @mreinstein

One thing I really wanted was when an assert passed, you know how we can provide with a message parameter, that never was echoed in the console. If you spot anything related to that, please look at it first.