I don't have much more to add than what others have written - I don't have very strong feelings about this, but it seems worth fixing if the contrib process is a significant barrier to contribution. And if that happens, I agree with Chas that it seems worth taking the time to reboot it properly, since having the CA in the project's history will probably confuse potential contributors who care about that sort of thing.
In general, I've never had the need to submit patches for nREPL since it's been stable since I started using it seriously. That's only for Clojure though, I believe there's some serious work that could be done on the ClojureScript side and IIRC that was a source of some frustration for some users a while back. I'd be very happy to see that progressing! There are also potential issues with API compatibility going forward, but I don't see those as particularly more difficult than if nREPL continues to evolve under the contrib umbrella. I also suspect that there's probably not too much risk of the community fragmenting - you'd only have to convince less than half a dozen nREPL clients to switch and you'd get essentially the whole community moving, I expect. As long as the wire protocol doesn't change during that transition I don't see why that would be too painful. Cheers, Colin On 19 July 2017 at 12:09, Chas Emerick <c...@cemerick.com> wrote: > Of course, my aim would be to gather as much consensus as possible around > a single nREPL vector; this thread is the first effort in service of that, > with presumably much more ahead. An obvious move for example would be to > shim out the legacy namespaces until a major version number change, so that > migrating would involve only swapping some project.clj/pom.xml > coordinates....where things go from there would be as much up to the > community as anything else. > > - Chas > > On 7/18/2017 17:30, Phil Hagelberg wrote: > > Thanks for continuing to maintain this lib, Chas; I'm glad to see this > move to make it more accessible to potential contributors. > > I believe the original choice of the EPL was made specifically to support > this kind of scenario. Personally I see a reboot as being a lot of effort > for little gain, but then again it's neither my effort going into it nor my > gain coming out of it. Besides, everyone's doing reboots these days. > > I do suspect that a reboot will lead to a longer transition time in which > both org.clojure/tools.nrepl and com.cemerick/nrepl are in active use by > greenfield projects, so perhaps if you do a reboot you could cut an 0.2.12 > release under the new group-id which has a stable known-good version and > then do the reboot under a 1.x series or something. This might help > alleviate the concerns raised by Colin more quickly. > > -Phil > -- > You received this message because you are subscribed to the Google > Groups "Clojure" group. > To post to this group, send email to clojure@googlegroups.com > Note that posts from new members are moderated - please be patient with > your first post. > To unsubscribe from this group, send email to > clojure+unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/clojure?hl=en > --- > You received this message because you are subscribed to a topic in the > Google Groups "Clojure" group. > To unsubscribe from this topic, visit https://groups.google.com/d/ > topic/clojure/6SX7q39lK90/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > clojure+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > > > -- > You received this message because you are subscribed to the Google > Groups "Clojure" group. > To post to this group, send email to clojure@googlegroups.com > Note that posts from new members are moderated - please be patient with > your first post. > To unsubscribe from this group, send email to > clojure+unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/clojure?hl=en > --- > You received this message because you are subscribed to the Google Groups > "Clojure" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to clojure+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
