Closed klaraward closed 2 years ago
Ping @malaporte
I have no issues whatsoever to transfer ownership of this repo if needed - I haven't written any Java code in ages and I no longer use it personally.
Or maybe a fork is more appropriate since you'll need to change the groupId
, and then I update the readme here to point to your fork? Just tell me what works best for you 😁
(let me still ask if somebody at Coveo uses it and wants to take ownership, but I'd be surprised since most Java teams are using the Eclipse formatter)
Well that wasn't long, here is the answer I got:
Having a discussion with @klaraward right now - since we (Coveo) no longer use this plugin we'll be transferring ownership of the repo to Spotify. In the meantime I'll grant her write access here and push a release if needed, while we figure out the transfer thing.
If Spotify takes over this repo, it would be under https://github.com/spotify and with the new groupId com.spotify
Repo is now in the Spotify org
See also #97
We need to change the groupId to something else to be able to deploy ofc.
Ping @dimi-nk
Original title of issue: "Possibly forking this repo to create new releases