On 18 July 2017 at 15:48, Chas Emerick <c...@cemerick.com> wrote: > Hi all, > > I've been approached many, many times over the years (and more frequently > since the development and inclusion of socket-repl) about the potential of > moving nREPL[1] out of clojure contrib…either back to its original > location[2], or under one of the various Clojure community organizations. > I've generally demurred or ghosted on these suggestions, sometimes out of a > lack of time/attention, and often out of just not wanting to stir the pot. > The pace of them has quickened somewhat lately though, and I'd like to put > the whole topic to bed and hopefully get the project to a better footing in > the process. > > First, to stipulate a few things: > > 1. nREPL is an essential bit of infrastructure in Clojure tooling > 2. On balance, I have neglected the project in recent years, to the > detriment of all of the users of the aforementioned tooling. > 3. On balance, contributors and potential contributors have been less > involved (or turned away entirely) because of the well-known friction that > comes with the contrib process and requirements. (tbh, this is a factor in > #2, though not the majority) > 4. No one (least of all me) would object to nREPL having its > contribution process managed through github or gitlab. > > So basically everyone wants nREPL to be a "regular" project, and subject > to and beneficiary of the same expectations as 99.9% of all of the other > OSS projects we all interact with daily. How does that happen? > > > The only routes AFAICT are: > > 1. to fork back elsewhere, which would require keeping the EPL license > and copyright assignment of the current codebase. Literally anyone can do > this at any time, without any coordination with anyone else. > 2. for me to reboot the project. This would not be difficult given I > "own" the vast majority of the project's commits. This would allow for the > elimination of the copyright assignment, and potentially a different > license (I'm partial to MPLv2, but we'll see). If this route is taken, we > could set up a project issue where the other contributors of nontrivial > patches could agree (or not) to the reconstitution of their code w/o the > copyright assignment, etc. > > In either case, this "new" nREPL project's artifacts would end up being > distributed under a different maven groupId (`com.cemerick`, if I'm to > continue deploying, etc). The clojure-contrib nREPL project remain, and any > releases that are done from it after the fork/reboot would continue to be > under the `org.clojure` coordinates. Downstream projects need to choose > whether or not to change dependencies; I'd expect the vast majority of > future motion to gravitate to the reboot, but that's just speculation at > this point. > > > I would like to hear *here* (no more private mails, please! :-) from any > nREPL users, contributors, etc. As much as possible, I would like *not *to > debate/re-litigate the merits of contrib and its process here; let's focus > on what steps will yield the best outcome for nREPL and its stakeholders. >
My vote is for a project reboot spearheaded by you. I doubt people would have objections to the relicensing of the project and I promise to help as much as I can if the project gets "freed" from the shackles of contrib. I do thing it might make sense for the project to be housed under a nREPL org on github, which can also house related important middleware and potentially client libraries for different languages. > > Thanks! > > > - Chas > > [1] https://github.com/clojure/tools.nrepl/ > [2] https://github.com/cemerick/nrepl > > -- > 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.
