If one wishes to change the repo name of an add-on that is already in the translation system, what is the correct procedure?

I'm guessing that what I have to do is:

* Rename the add-on source repo.
* Rename the nvdaaddons fork of the repo to match.
* Re-register the add-on as a new add-on in mrconfig.

Is that correct, or is there a better way of doing it?
Would this cause any kind of problem for translators that I don't know about?

I also thought of merging in the nvdaaddons stable branch of the fork, and creating an entirely new repo in nvdaaddons. That might be just as good. Then I could just archive the old fork.

Luke

Hi Luke,

That process is correct. The alternative with making a fork is also fine, and might be safer.

We are uncertain of any problem with translators, however if any are flagged after following this process, please let us know.

I'm looking to create documentation for this process as we speak.

The ikiwiki pages may also need to be updated to use the new add-on ID

Actually, it seems that mrconfig / nvdaaddons is independent from addonFiles.

The shortname in addonFiles and the addonID in the data store, does not need to match the add-on registered in mrconfig and forked in nvdaaddons.

If issues arise and unexpected dependence is discovered, we may need to follow steps like you have suggested here.

Documentation for migration from addonFiles is being added via this PR: https://github.com/nvaccess/addon-datastore/pull/299

Sean

In the end, I renamed SayProductNameAndVersion to sayProductNameAndVersion, both the source repo, and the nvdaaddons fork.

Interestingly, all of the references in the Assembla repository already reflected this, except for the ikiwiki page, which still used spnav. So I'm not sure if I need to re-register.

I tried to find where mrconfig / the code backing the Assembla repository clones the repo from, to figure out if it was pulling nvdaaddons/SayProductNameAndVersion or nvdaaddons/sayProductNameAndVersion.

Unfortunately I couldn't find it. I think it's being done in a script called "getGithubURL", but I don't know where that is.

Luke

Hi Luke,

It seems that the add-on was originally registered as sayProductNameAndVersion, so I don't think there should be any issues with changes of casing.