Hi Gábor,
just to you :
Gábor Csárdi csardi.ga...@gmail.com
on Tue, 26 May 2015 14:16:00 -0400 writes:
On Tue, May 26, 2015 at 2:10 PM, Gabriel Becker gmbec...@ucdavis.edu
wrote:
[...]
Well, sort of. I mean if the package is being actively developed not on
On Tue, May 26, 2015 at 1:43 PM, Henrik Bengtsson henrik.bengts...@ucsf.edu
wrote:
[...]
If people send pull requests, maybe adding a generic open pull request
to each repository with title MIRROR ONLY: Do not send pull requests
here would help. The fancy version would be to say MIRROR ONLY:
- Original Message -
From: Gábor Csárdi csardi.ga...@gmail.com
To: Gabriel Becker gmbec...@ucdavis.edu
Cc: Simon Urbanek simon.urba...@r-project.org, Rainer M Krug
rai...@krugs.de, r-devel@r-project.org
Sent: Tuesday, May 26, 2015 10:55:02 AM
Subject: Re: [Rd] MetaCran website
On Tue, May 26, 2015 at 2:01 PM, Dan Tenenbaum dtene...@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.
That's true, but issues, checkouts, comments, credit, etc should all be
going to the original repo. Anything else seems grossly unfair to the
package author(s). This issue is exacerbated even further when the the
author isn't developing the package on github at all, and github users may
On Tue, May 26, 2015 at 1:46 PM, Gabriel Becker gmbec...@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
On Tue, May 26, 2015 at 10:55 AM, Gábor Csárdi csardi.ga...@gmail.com
wrote:
On Tue, May 26, 2015 at 1:46 PM, Gabriel Becker gmbec...@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
On Tue, May 26, 2015 at 2:10 PM, Gabriel Becker gmbec...@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
On Tue, May 26, 2015 at 12:45 AM, Gábor Csárdi csardi.ga...@gmail.com wrote:
On Mon, May 25, 2015 at 8:28 PM, Simon Urbanek simon.urba...@r-project.org
wrote:
One issue I have with this is that it doesn't point to the original GitHub
repositories of the packages, so you end up with additional
I cannot speak for other package authors, but for all my own packages,
I have provided the BugReports field in DESCRIPTION that points to the
Github issues page. You can probably use this field to check if a
package is on Github or not. If it is, you may just fork the original
repo instead of
Or maybe it would be sensible to ask GitHub if they can fix this.
If it's a common-ish use case (e.g. for mirrors), it's not something that
should be terribly challenging engineering-wise, and it would prevent a lot
of hooha.
Funfact: GitHub is run and staffed by actual people, most of them
What you are doing is great, and that's a pretty clear warning (I would go
ahead and add DO NOT FORK ME to the verbiage since I am one of the
dumbasses who submitted a pull request in such a fashion, whereupon the
original author got to set up a Git repo, I re-PR'ed against that, and all
was
On Tue, May 26, 2015 at 12:18 PM, Gabriel Becker gmbec...@ucdavis.edu wrote:
On Tue, May 26, 2015 at 9:25 AM, Yihui Xie x...@yihui.name wrote:
I cannot speak for other package authors, but for all my own packages,
I have provided the BugReports field in DESCRIPTION that points to the
Github
On Tue, May 26, 2015 at 1:26 PM, Hadley Wickham h.wick...@gmail.com wrote:
Maybe I'm missing something, but why would you fork the repo instead of
just using the existing repo?
One advantage of a fork is that you have permanent archive even if the
original goes away.
Exactly. Even if the
On Tue, May 26, 2015 at 9:25 AM, Yihui Xie x...@yihui.name wrote:
I cannot speak for other package authors, but for all my own packages,
I have provided the BugReports field in DESCRIPTION that points to the
Github issues page. You can probably use this field to check if a
package is on
On 25.05.2015 02:29, Gábor Csárdi wrote:
On Sun, May 24, 2015 at 7:40 PM, Uwe Ligges
lig...@statistik.tu-dortmund.de
mailto:lig...@statistik.tu-dortmund.de wrote:
Thanks for letting us know about the new website. Some comments:
- Download statistics: Where are they from? CRAN does
One issue I have with this is that it doesn't point to the original GitHub
repositories of the packages, so you end up with additional repositories on
Github in Gabor's name that have nothing to do with the actual Github
repositories of the packages. I understand that it's technically
Gábor Csárdi csardi.ga...@gmail.com writes:
Dear All,
[ I was wondering if this should have gone to the new mailing list. Maybe. ]
As some of you maybe know from my earlier posts, I am building a simple
search engine for R packages. Now the search engine has a proper web site,
where you
On May 24, 2015 2:44 AM, Rainer M Krug rai...@krugs.de wrote:
Gábor Csárdi csardi.ga...@gmail.com writes:
Dear All,
[ I was wondering if this should have gone to the new mailing list.
Maybe. ]
As some of you maybe know from my earlier posts, I am building a simple
search engine for
Please tell me what you think.
I think it is awesome, just like the CRAN-github bridge.
It would be cool if you provided CRAN authors with instructions on how to
fork the CRAN-github clones of the source code so that I don't have to
retarget pull requests ;-)
In conclusion, keep up the great
Thanks for letting us know about the new website. Some comments:
- Download statistics: Where are they from? CRAN does not monitor
downloads generally, maybe some selected mirrors do.
- Section Recently updated can only hold 9 packages, but frequently
more than 9 get accepted even within an
Hi Uwe,
On 25 May 2015 at 01:40, Uwe Ligges wrote:
| Thanks for letting us know about the new website. Some comments:
|
| - Download statistics: Where are they from? CRAN does not monitor
| downloads generally, maybe some selected mirrors do.
This is the standard data set which has been
On Sun, May 24, 2015 at 7:40 PM, Uwe Ligges lig...@statistik.tu-dortmund.de
wrote:
Thanks for letting us know about the new website. Some comments:
- Download statistics: Where are they from? CRAN does not monitor downloads
generally, maybe some selected mirrors do.
It's the RStudio
Dear All,
[ I was wondering if this should have gone to the new mailing list. Maybe. ]
As some of you maybe know from my earlier posts, I am building a simple
search engine for R packages. Now the search engine has a proper web site,
where you can also browse CRAN packages.
24 matches
Mail list logo
