Host under the nREPL org? about nrebl.middleware HOT 7 OPEN

I guess we should remind @RickMoynihan about this. :-)

from nrebl.middleware.

Would love to see this happen 💯

from nrebl.middleware.

Hey bug,

Yes, I brought this up on #cider when I first got something working and I'd love to do that. I've been meaning to ask you about what's involved to do this?

What hoops do we need to jump through, and what does being in the nrepl org meaning with regards to commit rights etc? Also are there any hoops you'd like me to jump through to do it?

from nrebl.middleware.

No hoops really. I'll sent you an invite to join to org and once you accept it you can transfer the repo.

You'll have the same rights that you have right now. I'll just ask you to add a lein project once we do the transfer for consistency with the other official nREPL projects and to rename the deployment coordinates to nrepl/nrebl (also for consistency).

Once the transfer is done we'll setup the CI, etc.

from nrebl.middleware.

Great. I've joined the organisation. Thanks for the invite!

The project.clj/consistency, and coordinate stuff was really what I was referring to as hoops. I agree we should do those.

Curious also about what CI/travis setup you'd like to establish, in particular regarding clojars deployment etc.

One concern of mine is around the quality expectations of nrebl, particularly now that it will be in the nrepl organisation. I don't think there's much fundamentally wrong with it (as there's not much code), it just needs a bit of love in terms of documentation, and working out various compatability issues. I'd also like to eventually explore the possibility of some cider client side integrations.

from nrebl.middleware.

Curious also about what CI/travis setup you'd like to establish, in particular regarding clojars deployment etc.

Same as for nREPL and all other project in the org - ideally auto-deployments of successful builds at some point. We're looking into replacing Travis with Circle, but that's not at the top of the prio list.

One concern of mine is around the quality expectations of nrebl, particularly now that it will be in the nrepl organisation. I don't think there's much fundamentally wrong with it (as there's not much code), it just needs a bit of love in terms of documentation, and working out various compatability issues. I'd also like to eventually explore the possibility of some cider client side integrations.

Quality is a very subjective term, you know. :-) As long as it gets the job done, the code does not read like some some black magic spell and is documented reasonably well - that's fine by me. :-)

from nrebl.middleware.

@RickMoynihan re-ping 😉

from nrebl.middleware.