moving ceki/logback to organizations/qos.ch/logback on github
Hi All, As discussed a few weeks back, I would like to move ceki/logback to organizations/qos.ch/logback on github. The docs [1] mention that existing forks should pick the new location as their root. For logback-android, as it's a fork of ceki/logback but already bound to the target account, we need to contact support [1]. Les, I would also like to delete the 'logback' organization because it is now redundant (given that we now have qos-ch). More importantly, I think it somehow conflicts with the rule "target user must not have a repository with the same name" [1]. Please let me now if there are objections. [1] http://help.github.com/move-a-repo/ -- Ceki http://twitter.com/#!/ceki
On Sun, May 6, 2012 at 11:54 AM, ceki <ceki@qos.ch> wrote:
For logback-android, as it's a fork of ceki/logback but already bound to the target account, we need to contact support [1].
Ok. I assume logback-android will then be a fork of qos.ch/logback instead of ceki/logback. Have you contacted support already? Do I need to do anything for this process? -Tony
On 07.05.2012 02:25, Tony Trinh wrote: Responses inline.
On Sun, May 6, 2012 at 11:54 AM, ceki <ceki@qos.ch <mailto:ceki@qos.ch>> wrote:
For logback-android, as it's a fork of ceki/logback but already bound to the target account, we need to contact support [1].
Ok. I assume logback-android will then be a fork of qos.ch/logback <http://qos.ch/logback> instead of ceki/logback.
Yes that is my understanding.
Have you contacted support already? Do I need to do anything for this process?
No I have not. I am waiting Les' response before removing the "logback" organization. I'll let you know when there is progress.
-Tony
-- Ceki http://twitter.com/#!/ceki
Oops - sorry for the delay guys. I've had some email migration issues the last two days. Anyway, I have no objections removing it. Cheers, -- Les Hazlewood CTO, Stormpath | http://stormpath.com <http://www.stormpath.com/> | 888.391.5282 PMC Chair, Apache Shiro | http://shiro.apache.org twitter: @lhazlewood | http://twitter.com/lhazlewood blog: http://leshazlewood.com stormpath blog: http://stormpath.com/blog/index<http://www.stormpath.com/blog/index> On Sun, May 6, 2012 at 11:31 PM, ceki <ceki@qos.ch> wrote:
On 07.05.2012 02:25, Tony Trinh wrote:
Responses inline.
On Sun, May 6, 2012 at 11:54 AM, ceki <ceki@qos.ch <mailto:ceki@qos.ch>>
wrote:
For logback-android, as it's a fork of ceki/logback but already bound to the target account, we need to contact support [1].
Ok. I assume logback-android will then be a fork of qos.ch/logback <http://qos.ch/logback> instead of ceki/logback.
Yes that is my understanding.
Have you contacted support already? Do I need to do anything for this
process?
No I have not. I am waiting Les' response before removing the "logback" organization.
I'll let you know when there is progress.
-Tony
-- Ceki http://twitter.com/#!/ceki ______________________________**_________________ logback-dev mailing list logback-dev@qos.ch http://mailman.qos.ch/mailman/**listinfo/logback-dev<http://mailman.qos.ch/mailman/listinfo/logback-dev>
Hi Les, No problem. Thank you for getting back to us. I've removed the logback organization although there is another issue with logback-android which I will discuss in my next message. Cheers, -- Ceki http://twitter.com/#!/ceki On 08.05.2012 19:51, Les Hazlewood wrote:
Oops - sorry for the delay guys. I've had some email migration issues the last two days.
Anyway, I have no objections removing it.
Cheers,
-- Les Hazlewood CTO, Stormpath | http://stormpath.com <http://www.stormpath.com/> | 888.391.5282 PMC Chair, Apache Shiro | http://shiro.apache.org <http://shiro.apache.org/> twitter: @lhazlewood | http://twitter.com/lhazlewood blog: http://leshazlewood.com <http://leshazlewood.com/> stormpath blog: http://stormpath.com/blog/index <http://www.stormpath.com/blog/index>
On 07.05.2012 02:25, Tony Trinh wrote:
On Sun, May 6, 2012 at 11:54 AM, ceki <ceki@qos.ch <mailto:ceki@qos.ch>> wrote:
For logback-android, as it's a fork of ceki/logback but already bound to the target account, we need to contact support [1].
Ok. I assume logback-android will then be a fork of qos.ch/logback <http://qos.ch/logback> instead of ceki/logback.
Have you contacted support already? Do I need to do anything for this process?
Tony, Actually yes, there is something you could do. Given the exchange I had with github support (see below) could you please transfer the qos-ch/logback-android repo back to tony19/ and once the move of ceki/logback to qos-ch/logbaclk is done, retransfer tony19/logback-android back to qos-ch/. Does it make sense? Cheers, -- Ceki http://twitter.com/#!/cek ----------------------------------------------------------------- Message sent to github support: Hello github, I am trying to transfer ownership of the the https://github.com/ceki/logback repo to https://github.com/qos-ch/logback. Unfortunately, the move is denied with the message "qos-ch already has a repo in the ceki/logback network". I presume this is due to the https://github.com/qos-ch/logback-android repository which is a fork of ceki/logback. What are we missing? Many thanks in advance for your help, Github's answer: From: Tekkub (GitHub Staff) Subject: Moving ceki/logback to https://github.com/organizations/qos-ch/logback That's correct, the fork must be removed to do the transfer. If you'd rather the fork become the primary repo, we can switch the network's root repo around for you. ------------------------------------------------------------------------
On Wed, May 9, 2012 at 3:11 AM, ceki <ceki@qos.ch> wrote:
Tony,
Actually yes, there is something you could do. Given the exchange I had with github support (see below) could you please transfer the qos-ch/logback-android repo back to tony19/ and once the move of ceki/logback to qos-ch/logbaclk is done, retransfer tony19/logback-android back to qos-ch/. Does it make sense?
Ok. Done. Let me know when to transfer back. Thanks, Tony
On 09.05.2012 10:42, Tony Trinh wrote:
On Wed, May 9, 2012 at 3:11 AM, ceki <ceki@qos.ch <mailto:ceki@qos.ch>> wrote:
Tony,
Actually yes, there is something you could do. Given the exchange I had with github support (see below) could you please transfer the qos-ch/logback-android repo back to tony19/ and once the move of ceki/logback to qos-ch/logbaclk is done, retransfer tony19/logback-android back to qos-ch/. Does it make sense?
Ok. Done. Let me know when to transfer back.
That was quick. Thank you Tony. I've transfered ceki/logback to qos-ch/logback. You can transfer logback-android to qos-ch at your convenience.
Thanks, Tony
-- Ceki http://twitter.com/#!/ceki
On Wed, May 9, 2012 at 4:53 AM, ceki <ceki@qos.ch> wrote:
On 09.05.2012 10:42, Tony Trinh wrote:
On Wed, May 9, 2012 at 3:11 AM, ceki <ceki@qos.ch <mailto:ceki@qos.ch>>
wrote:
Tony,
Actually yes, there is something you could do. Given the exchange I had with github support (see below) could you please transfer the qos-ch/logback-android repo back to tony19/ and once the move of ceki/logback to qos-ch/logbaclk is done, retransfer tony19/logback-android back to qos-ch/. Does it make sense?
Ok. Done. Let me know when to transfer back.
That was quick. Thank you Tony. I've transfered ceki/logback to qos-ch/logback. You can transfer logback-android to qos-ch at your convenience.
I'm now hitting the same problem as you wrt to: qos-ch already has a repo in the qos-ch/logback network I guess it's my turn to deal with support ;)
On 09.05.2012 10:59, Tony Trinh wrote:
I'm now hitting the same problem as you wrt to: qos-ch already has a repo in the qos-ch/logback network I guess it's my turn to deal with support ;)
Bummer. What about manual clone and push as explained in [1] ? If you want to try this approach, I can create the target repo under ch-qos and you'll push your repo on to it. No help from support would be necessary... WDYT? [1] http://help.github.com/move-a-repo/ -- Ceki http://twitter.com/#!/ceki
On 09.05.2012 12:08, ceki wrote:
On 09.05.2012 10:59, Tony Trinh wrote:
I'm now hitting the same problem as you wrt to: qos-ch already has a repo in the qos-ch/logback network I guess it's my turn to deal with support ;)
Bummer. What about manual clone and push as explained in [1] ? If you want to try this approach, I can create the target repo under ch-qos and you'll push your repo on to it. No help from support would be necessary... WDYT?
One downside of "manual pushing" is that existing forks of logback-android would be without a root. From what I could see, there are only two such forks which look inactive.
-- Ceki http://twitter.com/#!/ceki
On Wed, May 9, 2012 at 6:45 AM, ceki <ceki@qos.ch> wrote:
On 09.05.2012 12:08, ceki wrote:
On 09.05.2012 10:59, Tony Trinh wrote:
I'm now hitting the same problem as you wrt to: qos-ch already has a
repo in the qos-ch/logback network I guess it's my turn to deal with support ;)
Bummer. What about manual clone and push as explained in [1] ? If you want to try this approach, I can create the target repo under ch-qos and you'll push your repo on to it. No help from support would be necessary... WDYT?
One downside of "manual pushing" is that existing forks of logback-android would be without a root. From what I could see, there are only two such forks which look inactive.
That indeed looks interesting, but it sounds like it creates an independent repo (removes the fork status of logback-android)...or am I mistaken? I need it to be a fork so that I can easily merge updates from qos-ch/logback.
On 09.05.2012 13:03, Tony Trinh wrote:
That indeed looks interesting, but it sounds like it creates an independent repo (removes the fork status of logback-android)...or am I mistaken? I need it to be a fork so that I can easily merge updates from qos-ch/logback.
Good point. I am at loss for more ideas. I guess you should contact github support asking them to help you transfer logback-android. -- Ceki http://twitter.com/#!/ceki
On Wed, May 9, 2012 at 7:57 AM, ceki <ceki@qos.ch> wrote:
On 09.05.2012 13:03, Tony Trinh wrote:
That indeed looks interesting, but it sounds like it creates an independent repo (removes the fork status of logback-android)...or am I mistaken? I need it to be a fork so that I can easily merge updates from qos-ch/logback.
Good point. I am at loss for more ideas. I guess you should contact github support asking them to help you transfer logback-android.
I got a response from support. Unfortunately, GitHub currently does not allow an account (or an organization) to fork its own repos. I think it's best for logback-android to remain a fork, so that means it has to be outside of the qos-ch organization.
On 10.05.2012 03:47, Tony Trinh wrote:
On Wed, May 9, 2012 at 7:57 AM, ceki <ceki@qos.ch <mailto:ceki@qos.ch>> wrote:
On 09.05.2012 13:03, Tony Trinh wrote:
That indeed looks interesting, but it sounds like it creates an independent repo (removes the fork status of logback-android)...or am I mistaken? I need it to be a fork so that I can easily merge updates from qos-ch/logback.
Good point. I am at loss for more ideas. I guess you should contact github support asking them to help you transfer logback-android.
I got a response from support. Unfortunately, GitHub currently does not allow an account (or an organization) to fork its own repos. I think it's best for logback-android to remain a fork, so that means it has to be outside of the qos-ch organization.
Tony, thanks for letting us know. It's too bad logback-android has to remain outside qos-ch. Migration of logback-android was one of the reasons why qos-ch was created in the first place. Please let me know if I can do anything to help promoting logback-android. Cheers, -- Ceki http://twitter.com/#!/ceki
participants (3)
-
ceki -
Les Hazlewood -
Tony Trinh