New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Migration out of Clojure Contrib #1

Closed
cemerick opened this Issue Oct 9, 2017 · 3 comments

Comments

Projects
None yet
3 participants
@cemerick
Copy link
Collaborator

cemerick commented Oct 9, 2017

As discussed on the Clojure google group, maintenance of nREPL is moving out of the Clojure Contrib umbrella. To restate the rationale from that thread:

  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.

To move forward, I've decided to "reboot" the project; i.e. to reconstitute it as a standalone effort without any legacy tying it to its time within the Contrib system. Simply forking back to my repo here would be far easier in the short term, but I prefer a reboot at this point because, as I state later on in the aforementioned Google Groups thread:

Do I want to maintain explanations of the answers to [questions regarding the heritage and lingering impact of the Contrib process and Contributor's Agreement] for a (fork of a) project that's no longer within contrib? Most definitely not.

The vast majority of the commits in the history at tools.nrepl are mine, and the project's license will remain EPL, so this should a pretty straightforward task. I will solicit agreement from all material contributors to the tools.nrepl project in a subtask listed below, which will simply establish that their contributions are available under EPL (whereas to date, they are only available in a "CA-encumbered" state since they were provided via the Contrib process).

Migration TODOs

  • Obtain agreement from material contributors to tools.nrepl that their work is available under EPL-only terms (#2)
  • Reconstruct commit history to include only those contributors' work (this will drop things like minor build process changes, commits by the build.clojure.org buildbots, etc)
  • Change maven coordinates (back) to com.cemerick/nrepl
  • Tweak up build process to deploy to Maven central without using the Contrib parent POM, etc
  • Cut a release matching [org.clojure/tools.nrepl "0.2.13"] in every material way
  • Grant commit to additional key contributors
  • 🎉 ❗️
  • Make more sweet REPLs and other tools 😄

@cemerick cemerick referenced this issue Oct 9, 2017

Closed

Licensing your nREPL contributions under EPL #2

16 of 16 tasks complete

@cemerick cemerick modified the milestones: 1.0.0, 0.3.0 Nov 6, 2017

@bbatsov

This comment has been minimized.

Copy link
Contributor

bbatsov commented Dec 7, 2017

Cut a release matching [org.clojure/tools.nrepl "0.2.13"] in every material way

Do you have any timeline in mind for that pivotal moment? :-)

@xiongtx

This comment has been minimized.

Copy link

xiongtx commented Feb 6, 2018

Anything in particular this is waiting for?

@bbatsov

This comment has been minimized.

Copy link
Contributor

bbatsov commented May 11, 2018

@xiongtx Not anymore. Time to make this happen!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment