Unfork

[sandstrom]

I suggest unforking from mattetti/i18n, to make it clear that this is the canonical place for the gem (forked from mattetti/i18n can cause confusion about that).

It's pretty simple to do, simply contact github and tell them you'd like to unfork, and explain why.

cc @radar

[radar]

This has always been the canonical place for it. It's got more stars, and more recent commits.

I'll still get in touch with GH and see about it.

[radar]

GH says that the request needs to come from @svenfuchs.

[sandstrom]

friendly ping @svenfuchs

[dmitry]

It could be easier to write an email directly to @svenfuchs via me@svenfuchs.com

[radar]

I'm already in direct contact with @svenfuchs and do not want to be harassing him during this time. He can attend to it when he wishes.

[wjordan]

Given the staleness of this open issue, I'd suggest forking/moving this project so that the current maintainer has control (e.g., @radar/i18n).

[radar]

What benefit would that have?

…

On 12 Jul 2018, 06:59 +0930, Will Jordan ***@***.***>, wrote: Given the staleness of this open issue, I'd suggest forking/moving this project so that the current maintainer has control (e.g., @radar/i18n). — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

[wjordan]

What benefit would that have?

The benefit discussed in this issue, for one. Given the project can't be unforked without the (inactive) project owner's participation, the alternative is to migrate the project to the current maintainer's ownership.

Another benefit is that it would reduce confusion regarding the current project owner/maintainer.

There are probably other benefits related to other permissions the project owner uniquely holds that can't be delegated to non-owner users with commit privileges.

[radar]

Right. I can understand that. I would rather that the project not be linked to a single person's account as that makes it seem like i18n is only maintained -- and can only ever be maintained -- by one person. I would much rather have an organisation account for this.

I'm already paying for one: @rubysherpas. We could move it there. I've already done this with https://github.com/rubysherpas/paranoia, so at least there's a precedent for it. I'll ask @svenfuchs to move it, since he's the only one with access currently.

[svenfuchs]

I'd prefer to use https://github.com/ruby-i18n for this, and I've emailed GitHub about unforking the repo.

[svenfuchs]

GitHub has unforked the repository.

🎉

[radar]

I'm +1 on moving this to ruby-i18n. Let's do it 👍

[tilsammans]

Hi @sandstrom @radar now we're unforked, can we move the repo to ruby-i18n? (which already exists, btw)

[radar]

I do not have the ability to do that. Only @svenfuchs as the repo's admin has that power.

[tilsammans]

Thanks. Have pinged Sven via email.

[sandstrom]

Seems to be unforked now, closing 🎉

[tilsammans]

Nice!