On Tue, May 26, 2015 at 1:46 PM, Gabriel Becker <gmbecker at ucdavis.edu> wrote:> That's true, but issues, checkouts, comments, credit, etc should all be > going to the original repo.You mean the links? They are, aren't they? [...]> >From the email Gabor just sent out, it sounds like he and I agree about > this stuff anyway. I was really responding to the proposal that the > repositories actually be forked. >I cannot do much about that. Issues and wiki are turned off, but you cannot turn off forking or pull requests. Even the official mirrors at GitHub have them, e.g. the Apache Spark mirror at https://github.com/apache/spark And I don't actually want to turn off forks for these repos, because they are useful for repos that are originally not on CRAN. Anyway, in summary I'll try to do a better job at directing people to the original sources. Gabor [...] [[alternative HTML version deleted]]
----- Original Message -----> From: "G?bor Cs?rdi" <csardi.gabor at gmail.com> > To: "Gabriel Becker" <gmbecker at ucdavis.edu> > Cc: "Simon Urbanek" <simon.urbanek at r-project.org>, "Rainer M Krug" <Rainer at krugs.de>, r-devel at r-project.org > Sent: Tuesday, May 26, 2015 10:55:02 AM > Subject: Re: [Rd] MetaCran website v1.0.0-alpha > > On Tue, May 26, 2015 at 1:46 PM, Gabriel Becker > <gmbecker at ucdavis.edu> > wrote: > > > That's true, but issues, checkouts, comments, credit, etc should > > all be > > going to the original repo. > > > You mean the links? They are, aren't they? > > [...] > > > >From the email Gabor just sent out, it sounds like he and I agree > > >about > > this stuff anyway. I was really responding to the proposal that the > > repositories actually be forked. > > > > I cannot do much about that. Issues and wiki are turned off, but you > cannot > turn off forking or pull requests.No, but you can set up a 'bot' which listens for pull requests and then immediately denies them with a customizable message, perhaps giving people the url where they should be making their pull requests. Example: https://github.com/bioconductor/prbot Dan> Even the official mirrors at > GitHub have > them, e.g. the Apache Spark mirror at https://github.com/apache/spark > > And I don't actually want to turn off forks for these repos, because > they > are useful for repos that are originally not on CRAN. > > Anyway, in summary I'll try to do a better job at directing people to > the > original sources. > > Gabor > > [...] > > [[alternative HTML version deleted]] > > ______________________________________________ > R-devel at r-project.org mailing list > https://stat.ethz.ch/mailman/listinfo/r-devel >
On Tue, May 26, 2015 at 2:01 PM, Dan Tenenbaum <dtenenba at fredhutch.org> wrote: [...]> > No, but you can set up a 'bot' which listens for pull requests and then > immediately denies them with a customizable message, perhaps giving people > the url where they should be making their pull requests. Example:> https://github.com/bioconductor/prbotYes, that's what I am doing, by hand currently. I closed all of them and explained that this is not the right place for them. It's one PR per week so far, and sometimes I need to interact with the people, so it is fine. If it will be more, I'll use your robot, thanks! Gabor> Dan > > > > > Even the official mirrors at > > GitHub have > > them, e.g. the Apache Spark mirror at https://github.com/apache/spark > > > > And I don't actually want to turn off forks for these repos, because > > they > > are useful for repos that are originally not on CRAN. > > > > Anyway, in summary I'll try to do a better job at directing people to > > the > > original sources. > > > > Gabor > > > > [...] > > > > [[alternative HTML version deleted]] > > > > ______________________________________________ > > R-devel at r-project.org mailing list > > https://stat.ethz.ch/mailman/listinfo/r-devel > > >[[alternative HTML version deleted]]
On Tue, May 26, 2015 at 10:55 AM, G?bor Cs?rdi <csardi.gabor at gmail.com> wrote:> On Tue, May 26, 2015 at 1:46 PM, Gabriel Becker <gmbecker at ucdavis.edu> > wrote: > >> That's true, but issues, checkouts, comments, credit, etc should all be >> going to the original repo. > > > You mean the links? They are, aren't they? >Sort of, the link for browsing source code doesn't have any indication that you're looking at a frozen snapshot of the source-code for the latest version on CRAN. Typically links with that description point to trunk, I think. Maybe a different a description for that link would help make the source-code it points to sound less official?> > [...] > >> >From the email Gabor just sent out, it sounds like he and I agree about >> this stuff anyway. I was really responding to the proposal that the >> repositories actually be forked. >> > > I cannot do much about that. Issues and wiki are turned off, but you > cannot turn off forking or pull requests. Even the official mirrors at > GitHub have them, e.g. the Apache Spark mirror at > https://github.com/apache/spark > > And I don't actually want to turn off forks for these repos, because they > are useful for repos that are originally not on CRAN. >Well, sort of. I mean if the package is being actively developed not on github, forking your archive repo and developing a patch/etc against it won't necessarily be particularly effective, as there is no way to have the right starting point (state of trunk), right? ~G -- Gabriel Becker, PhD Computational Biologist Bioinformatics and Computational Biology Genentech, Inc. [[alternative HTML version deleted]]
On Tue, May 26, 2015 at 2:10 PM, Gabriel Becker <gmbecker at ucdavis.edu> wrote: [...]> > Well, sort of. I mean if the package is being actively developed not on > github, forking your archive repo and developing a patch/etc against it > won't necessarily be particularly effective, as there is no way to have the > right starting point (state of trunk), right? >Well, then you can do 1) git rebase or 2) get the patch if the original repo is not in git. Yes, this is not ideal. I could remove that "Browse the source" completely, that is an option, and remove the link from the version number as well. There there will be no links to github.com/cran. Experienced users will just type in the URL. That's fine with me, too. Btw. how does this look for a warning: https://github.com/cran/crayon This is the most red I could find. G. [[alternative HTML version deleted]]