From igauravsehrawat at gmail.com  Sun Aug 24 13:10:23 2014
From: igauravsehrawat at gmail.com (Gaurav Sehrawat)
Date: Sun, 24 Aug 2014 16:40:23 +0530
Subject: [Rd] Why R-project source code is not on Github
In-Reply-To: <CANROs4ewiNwp-p1-e-jgGh1CSQtz55emjhKSeNpD00VFxhJn2Q@mail.gmail.com>
References: <CAC2qNN50TnpgCK_J027aBwn4Obm52O3CqqJ=2oTeetT=okWDWw@mail.gmail.com>
	<69D351C3-AA81-430E-8F66-D06863C18702@me.com>
	<E2C615A5-EFB9-4BCA-9696-258AB8859BBA@r-project.org>
	<CANROs4ewiNwp-p1-e-jgGh1CSQtz55emjhKSeNpD00VFxhJn2Q@mail.gmail.com>
Message-ID: <CAC2qNN59QafjkpnvLHsucNpoXvCe2AgYDRexsXD=s7r5sUjdmA@mail.gmail.com>

I was moreover concerned over bridging gap between web2.0 and web1.0
development methodologies  & thus passing code to younger generation .

But never mind . Sooner or later .

Cheers.


On Fri, Aug 22, 2014 at 9:30 AM, Yihui Xie <xie at yihui.name> wrote:

> As someone who has merged more than a hundred pull requests on Github,
> I cannot agree more. Sometimes I can take patches on my mobile phone
> while I'm still in bed if they look reasonable and simple enough.
> Sometimes the patches are not worth emails back and forth, such as the
> correction of typos. I cannot think of anything else that is more
> efficient than being able to discuss the patch right in the lines of
> diff's.
>
> Regards,
> Yihui
> --
> Yihui Xie <xieyihui at gmail.com>
> Web: http://yihui.name
>
>
> On Thu, Aug 21, 2014 at 10:58 AM, Simon Urbanek
> <simon.urbanek at r-project.org> wrote:
> >
> > On Aug 21, 2014, at 6:40 AM, Marc Schwartz <marc_schwartz at me.com> wrote:
> >
> >> On Aug 21, 2014, at 3:11 AM, Gaurav Sehrawat <igauravsehrawat at gmail.com>
> wrote:
> >>
> >>> R-Project is missing something important in regards to its development
> ,
> >>> one simply can't ignore Github ,where collaboration is at it's best .
> >>>
> >>> OR If i am wrong is this the correct R-source :
> >>> https://github.com/wch/r-source
> >>>
> >>> Is anyone thinking to bring R-project org on Github ? Maybe there
> might be
> >>> some difficulty while porting its version system to Github .
> >>>
> >>> Just a suggestion .
> >>>
> >>> Thanks
> >>> Gaurav Sehrawat
> >>> http://igauravsehrawat.com
> >>
> >>
> >> The link you have above is to a read-only mirror (perhaps not the only
> one) of the R source code that is kept in the official Subversion repo:
> >>
> >>  https://svn.r-project.org/R/
> >>
> >> There are also some documents that describe R's development cycle and
> related processes:
> >>
> >>  http://www.r-project.org/certification.html
> >>
> >> Your suggestion to move to Github is perhaps based upon a false
> premise, that the R community at large has the ability to directly post
> code/patches to the official distribution. We can contribute code and
> patches, primarily here on R-Devel, to the code base. However, only the
> members of R Core team (http://www.r-project.org/contributors.html) have
> write access to the SVN repo above and have to approve any such
> contributions.
> >>
> >
> > How is this different from Github? Github just makes it much easier to
> create and post patches to the project - it has nothing to do with write
> access - typically on Github the community has no write access, either.
> Using pull requests is certainly much less fragile than e-mails and patches
> are based on forked branches, so you can directly build the patched version
> if you want without manually applying the patch - and you see the whole
> history so you can pick out things logically. You can comment on individual
> patches to discuss them and even individual commits - often leading to a
> quick round trip time of revising it.
> >
> > Cheers,
> > Simon
>
> ______________________________________________
> R-devel at r-project.org mailing list
> https://stat.ethz.ch/mailman/listinfo/r-devel
>

	[[alternative HTML version deleted]]



[Rd] Why R-project source code is not on Github
Gaurav Sehrawat