How to claim a package when we are a community fork?

[neo451]

Hi, we are currently in the process of creating a community fork of obsidian.nvim, repo here: https://github.com/obsidian-nvim/obsidian.nvim
The fork happens because the original author has not been actively maintaining the repo. epwalsh/obsidian.nvim#820
The plugin itself has already been added to luarocks by the neorocks developers, and the original author has not claimed the package.
So I want to ask how to make the package point to the new repo? Maybe just take down the package and we set it up from scratch?

[mrcjkb]

Hey 👋

I'll change the config so that our workflow points to your fork after work today.

Or if you'd like to upload releases yourselves, we can also transfer ownership of the luarocks package to your org.
It would probably be best to get consent from the original maintainer though (if you haven't already), just in case they decide they want to keep maintaining their plugin later on.

[neo451]

hi, thank you for your timely response, I think for now we can just work with you changing the repo, since we are still at early stage.
in regards to consent from author, we have not been able to contact him from github and is in the process of waiting for the auhor's response. Even if he wants to work on we can yield the control back then.

[mrcjkb]

Alright, I've updated this repo to fetch your fork.
Since you don't have any semver releases yet, it will only publish to the dev manifest for now (rocks.nvim and luarocks will prioritise the root manifest by default).
The workflow runs every 4 hours, so once you do publish a release, it should be available on the luarocks.org root manifest not long after.

[neo451]

thank you for your work！