> On 26 Jun 2019, at 17:25, Duncan Murdoch <murdoch.duncan at gmail.com> wrote: > > R-Forge is mirrored on Github; see https://github.com/rforge/ecdat, for example. That shows 418 commits in its history; presumably that's the full R-forge history. I think that's newer than Michael Friendly's gist. > > So I suspect (but haven't tried to do this) that migration now is as simple as doing a Github fork to your own Github account, and then basically forgetting about the R-forge stuff, or deleting it (and I don't know how to do that).I think it's better to avoid the Fork button in this case, because forks are treated specially in the Github UI. In this case you'll want your repo to appear as a main repo, and not a fork. AFAIK the only way to unfork a repo is to ask the Github staff to do it. So instead of forking, use the "+" button on github.com and select "Import a repository". This supports both git and svn repos. Best, Lionel
????? Thanks to Duncan, Lionel and Henrik for their quick replies. I have further questions: ??? ?? ???? 1.? Will GitHub automatically transfer the commits I made to R-Forge in the past couple of days?? R-Forge is now at Rev. 420, and GitHub is still at 418.? Will 419 and 420 be automatically mirrored onto "https://github.com/rforge/ecdat" sometime in the next 24 hours or so?? Is there something easy I can do to force that update? ??? ?? ???? 2.? Is there a way to make this GitHub version the master?? It currently says it is a 'Read-only mirror of "ecdat" from r-forge SVN.'? I can probably change "r-forge.r-project.org/projects/ecdat" so I'm the only one authorized to make changes there and then stop committing changes there.? However, before I do that, I'd want to make sure I can commit directly to the GitHub version, etc. ??? ?? ???? 3.? How can I make myself the owner and a contributor for the GitHub version?? I'm a "Project Admin" on the R-Forge version, but currently no one can make any changes to the GitHub version except via R-Forge.? There must be a recommended migration process. ????? I could create a separate version of this package on GitHub, but all the history would be lost. ????? Thanks again, ????? Spencer Graves On 2019-06-26 10:35, Lionel Henry wrote:>> On 26 Jun 2019, at 17:25, Duncan Murdoch <murdoch.duncan at gmail.com> wrote: >> >> R-Forge is mirrored on Github; see https://github.com/rforge/ecdat, for example. That shows 418 commits in its history; presumably that's the full R-forge history. I think that's newer than Michael Friendly's gist. >> >> So I suspect (but haven't tried to do this) that migration now is as simple as doing a Github fork to your own Github account, and then basically forgetting about the R-forge stuff, or deleting it (and I don't know how to do that). > I think it's better to avoid the Fork button in this case, because forks are > treated specially in the Github UI. In this case you'll want your repo to > appear as a main repo, and not a fork. AFAIK the only way to unfork a repo > is to ask the Github staff to do it. > > So instead of forking, use the "+" button on github.com and select > "Import a repository". This supports both git and svn repos. > > Best, > Lionel
I think all 3 issues are solved by: 1. Use the "+" button on github.com <http://github.com/> and select "Import a repository". 2. Pass the URL of your SVN repo. Lionel> On 26 Jun 2019, at 18:58, Spencer Graves <spencer.graves at prodsyse.com> wrote: > > Thanks to Duncan, Lionel and Henrik for their quick replies. I have further questions: > > > 1. Will GitHub automatically transfer the commits I made to R-Forge in the past couple of days? R-Forge is now at Rev. 420, and GitHub is still at 418. Will 419 and 420 be automatically mirrored onto "https://github.com/rforge/ecdat" sometime in the next 24 hours or so? Is there something easy I can do to force that update? > > > 2. Is there a way to make this GitHub version the master? It currently says it is a 'Read-only mirror of "ecdat" from r-forge SVN.' I can probably change "r-forge.r-project.org/projects/ecdat" so I'm the only one authorized to make changes there and then stop committing changes there. However, before I do that, I'd want to make sure I can commit directly to the GitHub version, etc. > > > 3. How can I make myself the owner and a contributor for the GitHub version? I'm a "Project Admin" on the R-Forge version, but currently no one can make any changes to the GitHub version except via R-Forge. There must be a recommended migration process. > > > I could create a separate version of this package on GitHub, but all the history would be lost. > > > Thanks again, > Spencer Graves > > > On 2019-06-26 10:35, Lionel Henry wrote: >>> On 26 Jun 2019, at 17:25, Duncan Murdoch <murdoch.duncan at gmail.com> wrote: >>> >>> R-Forge is mirrored on Github; see https://github.com/rforge/ecdat, for example. That shows 418 commits in its history; presumably that's the full R-forge history. I think that's newer than Michael Friendly's gist. >>> >>> So I suspect (but haven't tried to do this) that migration now is as simple as doing a Github fork to your own Github account, and then basically forgetting about the R-forge stuff, or deleting it (and I don't know how to do that). >> I think it's better to avoid the Fork button in this case, because forks are >> treated specially in the Github UI. In this case you'll want your repo to >> appear as a main repo, and not a fork. AFAIK the only way to unfork a repo >> is to ask the Github staff to do it. >> >> So instead of forking, use the "+" button on github.com and select >> "Import a repository". This supports both git and svn repos. >> >> Best, >> Lionel >[[alternative HTML version deleted]]
Whereas it is true that one has to contact GitHub to detach a GitHub repository, it really is no problem (or at least was no problem in 2016). I wanted to do so when I took over the maintainer role of LaplacesDemon which only remained on GitHub as a fork on some other person's private account. So I forked and then contacted GitHub support and simply asked them to remove the "forked form" reference on my new repository. They then quickly detached my repository. As you can see, the "forked from" is gone: https://github.com/LaplacesDemonR/LaplacesDemon In their response to my request they used the phrasing "Fork is detached." which suggests that this is their preferred term for this step. Best, Henrik Am Mi., 26. Juni 2019 um 16:38 Uhr schrieb Lionel Henry <lionel at rstudio.com>:> > > On 26 Jun 2019, at 17:25, Duncan Murdoch <murdoch.duncan at gmail.com> > wrote: > > > > R-Forge is mirrored on Github; see https://github.com/rforge/ecdat, for > example. That shows 418 commits in its history; presumably that's the full > R-forge history. I think that's newer than Michael Friendly's gist. > > > > So I suspect (but haven't tried to do this) that migration now is as > simple as doing a Github fork to your own Github account, and then > basically forgetting about the R-forge stuff, or deleting it (and I don't > know how to do that). > > I think it's better to avoid the Fork button in this case, because forks > are > treated specially in the Github UI. In this case you'll want your repo to > appear as a main repo, and not a fork. AFAIK the only way to unfork a repo > is to ask the Github staff to do it. > > So instead of forking, use the "+" button on github.com and select > "Import a repository". This supports both git and svn repos. > > Best, > Lionel > ______________________________________________ > R-devel at r-project.org mailing list > https://stat.ethz.ch/mailman/listinfo/r-devel >-- Dr. Henrik Singmann Assistant Professor, Department of Psychology University of Warwick, UK http://singmann.org [[alternative HTML version deleted]]
Hi, Henrik Singmann et al.: ????? Thanks for the suggestions.? I tried again to pull "https://github.com/sbgraves237/Ecdat" from R-Forge, with the same "Error 500" as before.? Then I tried pulling from "https://github.com/rforge/ecdat", which seemed to work ... AND the copy I pulled was at the latest revisions I had posted to R-Forge (520), so that makes it easier going forward. ????? What do you suggest I do next?? I'm thinking of the following: ??? ??????? 1.? Clone a copy of "https://github.com/sbgraves237/Ecdat" to my local computer and confirm that it works. ??? ??????? 2.? Modify "https://r-forge.r-project.org/projects/ecdat/" to make me the only remaining project member, if I can. ??? ??????? 3.? Contact GitHub support and ask them if they can delete "https://github.com/rforge/ecdat", because it is an orphan with 0 contributors, and anyone who might want it should be referred to "https://github.com/sbgraves237/Ecdat". ???? ??????? 4.? Email all the previous project members on "https://r-forge.r-project.org/projects/ecdat/" to tell them what I've done, in case they want to do anything more with this in the future. ????? I believe I know how to do 1, 2, and 4, and I can probably figure out 3.? However, before I start on this, I felt a need to thank everyone who contributed to this thread and invite comments, especially if someone thinks I might be better off doing something different. ????? Spencer Graves On 2019-06-26 16:34, Henrik Singmann wrote:> Whereas it is true that one has to contact GitHub to detach a GitHub > repository, it really is no problem (or at least was no problem in > 2016). I wanted to do so when I took over the maintainer role of > LaplacesDemon which only remained on GitHub as a fork on some other > person's private account. So I forked and then contacted > GitHub?support?and simply asked them to remove the "forked form" > reference on my new repository.?They then quickly detached my > repository.?As you can see, the "forked from" is gone: > https://github.com/LaplacesDemonR/LaplacesDemon > > In their response to my request they used the phrasing "Fork is > detached." which suggests that this is their preferred term for this > step. > > Best, > Henrik > > > > Am Mi., 26. Juni 2019 um 16:38?Uhr schrieb Lionel Henry > <lionel at rstudio.com <mailto:lionel at rstudio.com>>: > > > > On 26 Jun 2019, at 17:25, Duncan Murdoch > <murdoch.duncan at gmail.com <mailto:murdoch.duncan at gmail.com>> wrote: > > > > R-Forge is mirrored on Github; see > https://github.com/rforge/ecdat, for example.? That shows 418 > commits in its history; presumably that's the full R-forge > history.? I think that's newer than Michael Friendly's gist. > > > > So I suspect (but haven't tried to do this) that migration now > is as simple as doing a Github fork to your own Github account, > and then basically forgetting about the R-forge stuff, or deleting > it (and I don't know how to do that). > > I think it's better to avoid the Fork button in this case, because > forks are > treated specially in the Github UI. In this case you'll want your > repo to > appear as a main repo, and not a fork. AFAIK the only way to > unfork a repo > is to ask the Github staff to do it. > > So instead of forking, use the "+" button on github.com > <http://github.com> and select > "Import a repository". This supports both git and svn repos. > > Best, > Lionel > ______________________________________________ > R-devel at r-project.org <mailto:R-devel at r-project.org> mailing list > https://stat.ethz.ch/mailman/listinfo/r-devel > > > > -- > Dr. Henrik Singmann > Assistant Professor, Department of Psychology > University of Warwick, UK > http://singmann.org[[alternative HTML version deleted]]