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]]
Re your point 3: Because you have managed to create a GitHub version of your repository that is not a fork of https://github.com/rforge/ecdat, but its own independent repository, contacting GitHub support might not be the right way forward. Note that https://github.com/rforge is simply a read-only mirror of the complete R-Forge repository (and at least to me it is unclear of whether GitHub itself or some independent party is responsible for it, but I would assume it is not GitHub). So the easiest way to change something in https://github.com/rforge/ecdat would be to make the corresponding change in your R-forge repository and wait until it propagates to GitHub. So either delete the R-forge repository or make a final commit replacing its content with a README pointing towards the new GitHub repo at https://github.com/sbgraves237/Ecdat. Together with emailing all previous project members this should ensure that interested party will know about the new place where your package is being developed/hosted. You might also want to add a new README to the new GitHub repository which replaces the current R-forge one and provides installation instructions. Best, Henrik Am Fr., 28. Juni 2019 um 06:01 Uhr schrieb Spencer Graves < spencer.graves at prodsyse.com>:> Hi, Henrik Singmann et al.: > > > Thanks for the suggestions. I tried again to pull > "https://github.com/sbgraves237/Ecdat" > <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" <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" > <https://github.com/sbgraves237/Ecdat> to my local computer and confirm > that it works. > > > 2. Modify "https://r-forge.r-project.org/projects/ecdat/" > <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" <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" > <https://github.com/sbgraves237/Ecdat>. > > > 4. Email all the previous project members on > "https://r-forge.r-project.org/projects/ecdat/" > <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>: > >> >> > 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 > > >-- Dr. Henrik Singmann Assistant Professor, Department of Psychology University of Warwick, UK http://singmann.org [[alternative HTML version deleted]]
On Fri, Jun 28, 2019 at 6:01 AM Spencer Graves <spencer.graves at prodsyse.com> wrote: [...]> 1. Clone a copy of "https://github.com/sbgraves237/Ecdat" > to my local computer and confirm that it works. >I suggest you put each package in its own repository, because our R tooling (e.g. Travis CI, etc.) works best if you do that. This is quite easy to do nowadays: https://stackoverflow.com/a/17864475/604364> 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". >You don't need do that. It is unlikely that they would remove *someone else's* repository, anyway, unless the repository has some copyright or license problems. Which it does not, since your packages are GPL. GitHub as a company does not manage https://github.com/rforge. This read only mirror was set up by a fellow GitHub user, and it is best if it is kept as a read-only mirror. Instead, you can do as Duncan suggested, and put a README in your R-Forge repository, that points to *your* GitHub repositor(y/ies). Then the https://github.com/rforge/ecdat read only mirror will pick this up and will point there as well. Gabor [...] [[alternative HTML version deleted]]
Spencer, on your point 3. below, we took a different path in migrating
several packages.
After we migrated to github as the new master copy, we made new commits
to the now orphaned R-Forge copies to include a new .onAttach function
as so:
.onAttach <- function(libname, pkgname) {
repo <- "https://github.com/sbgraves237/Ecdat
<https://github.com/braverock/quantstrat>"
packageStartupMessage(
"WARNING: this package was installed from R-Forge, but development
has\n",
"moved to GitHub. Please re-install the package using the GitHub repo
at:\n",
repo, ".")
}
And to update the README in the main pkg/ dir on R-Forge.
So all the old references in talks, papers, StackOverflow, whatever will
point to the R-Forge version, but the R-Forge version will point anyone
to github.
Regards,
Brian
On 6/28/19 12:00 AM, Spencer Graves wrote:> 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]]
>
> ______________________________________________
> R-devel at r-project.org mailing list
> https://stat.ethz.ch/mailman/listinfo/r-devel
--
Brian G. Peterson
http://braverock.com/brian/
Ph: 773-459-4973
IM: bgpbraverock
[[alternative HTML version deleted]]