R devel - Jan 2018 - Why R should never move to git

On Tue, Jan 30, 2018 at 11:07 PM, Suzen, Mehmet <mehmet.suzen at
gmail.com>
wrote:
> This might be off topic, but if R-core development ever moves to git,
> I think it would make sense to have its own git service hosted by a
> university, rather than using
> github or gitlab. It is possible via https://gogs.io/ project.
>
> Just for the record.
>
>
Let the record also state that *gitlab* is an open source project and can
be downloaded and self-hosted, like gogs, but unlike github.

Barry

PS I've been running a gitlab instance for my group for a couple of years
on a private server.

	[[alternative HTML version deleted]]

On 31 January 2018 at 16:18, Barry Rowlingson
<b.rowlingson at lancaster.ac.uk> wrote:
>>
>
> Let the record also state that *gitlab* is an open source project and can
be
> downloaded and self-hosted, like gogs, but unlike github.

Good to know. Nice one: https://github.com/gitlabhq/gitlabhq

Best,
-m

> PS I've been running a gitlab instance for my group for a couple of
years on
> a private server.
Is it a smooth ride so far?

Yes, indeed Gitlab GUI Core Code is Open Source (Libre / Community
Edition): https://gitlab.com/gitlab-org/gitlab-ce
> But his instructions required command-line git, and my main claim is that
Github is not good enough to do the kinds of things I want to do and R Core
would need to do.
>
> My other claim is that git is too hard to use.
I'm sure that Git Command Line Recipe Documentation can solve this
issue, Gitlab, in particular, has a wiki in which this kind of issues
could be documented. Also Git cheat-sheets might prove useful. In
addition, any feature request could be done in Gitlab Issue Section
(See above), or if that does not still does not convince, other
options could be considered, such as Bitbucket
(https://bitbucket.org/), etc.

In addition, the Git Repository:
* Could be self-hosted in the University Servers (Just as SVN actually
is nowadays).
* Be accessed either by the Command Line or the Graphical User
Interface (As users prefer).

The main reason motivating the move to the GIT Repository, as said
before, is that it would to allow individual users or companies from
the R Consortium to do pull requests based on issues for improving
base R code.

Indeed, in some years from now I would like to help to improve base R
myself, maybe re-writing some parts of the code in C++, fixing bugs,
or who knows :)

Kind regards,
Juan Telleria

I attach the Github Flow for teams and projects with regular deployments:

https://guides.github.com/pdfs/githubflow-online.pdf

https://guides.github.com/introduction/flow/

Tips:
* Always!!!! Do pull requests based on branches (never on the master).
* Keep your Fork Synchronized with the Upstream Repository.