Transfer ownership of bindbc-imgui

[LunaTheFoxgirl]

Transfer ownership of bindbc-imgui

[WebFreak001]

I see you own the bindbc-imgui package, do you want to change its package name?

Changing repository/owner is something you can do on your own in the settings, but not renaming the package name on DUB.

Since we don't want to break existing users and if the bindbc developers intend to make an official package, it might make more sense to let the bindbc devs start as a fork of your package. You could then change the repo location on DUB to the fork and re-register the original repo under a new name. When that's done we can also change the DUB user ownership of the package on the registry.

[ichordev]

Here to confirm about the transfer.

Since we don't want to break existing users and if the bindbc developers intend to make an official package, it might make more sense to let the bindbc devs start as a fork of your package. You could then change the repo location on DUB to the fork and re-register the original repo under a new name. When that's done we can also change the DUB user ownership of the package on the registry.

Yep my plan is to do that basically: Inochi2D/i2d-imgui#24
Also no need for the plurals, there's only one of me. :)

Changing repository/owner is something you can do on your own in the settings, but not renaming the package name on DUB.

Really, how? I only know about this text.

[WebFreak001]

yes, under the repository tab you can configure which GitHub / other repository is used to fetch releases and source code from. If you fork Inoch2D/bindbc-imgui to your BindBC org, Luna or dub admins can then change the repository location in the package settings. (the migrate screenshot you posted)

So that would bascially mean:

1. Fork Inochi2D/bindbc-imgui to YourBindBCOrg/bindbc-imgui (something IchorDev can do)
2. DUB package bindbc-imgui: repository Inochi2D/bindbc-imgui -> YourBindBCOrg/bindbc-imgui (something Luna or dub admins can do)
3. now Inochi2D/bindbc-imgui can freely rename and change the package name in the dub.json/dub.sdl file and later reregister on DUB under Inochi2D/i2d-imgui (something Luna can do)

Afterwards we can also transfer the package owner on dub, so you (IchorDev) are admin of the package, instead of Luna, so you can also trigger new releases, change image, etc. (This is something only s-ludwig can do though, I think, as it needs database access right now)

[ichordev]

Yep, here it is: https://github.com/BindBC/bindbc-imgui

also oops I screenshot the wrong text, but basically I thought you were saying you could transfer package ownership through the web interface.

[ichordev]

Any updates on this? The new BindBC-ImGui is basically ready for an alpha-release.

[WebFreak001]

ok dub package points to BindBC/bindbc-imgui now. Should the dub account ownership also be transferred somewhere or stay with @LunaTheFoxgirl's account?

@LunaTheFoxgirl you can also rename your package in dub.json/dub.sdl and re-register it. Note that you will need to rewrite git history if you want previous versions to work as well (otherwise only new versions with the new package name will properly function)

[ichordev]

It’s probably simplest to transfer the existing package and then wait for the Inochi2D team register a new one. I’m just about ready to release the new BindBC-ImGui version, but I want to be able to mention where the other bindings have moved to when I do.

[WebFreak001]

the package is already transferred, when you make new releases they will appear on dub. What's your username on dub so we can also give you access to the package admin interface that can be used for manual release triggers?

[ichordev]

the package is already transferred, when you make new releases they will appear on dub. What's your username on dub so we can also give you access to the package admin interface that can be used for manual release triggers?

ichordev :)

[WebFreak001]

@s-ludwig can you do the package ownership migration?

[s-ludwig]

Done!