[GenABEL-dev] Proposal to move to Github
Yurii Aulchenko
yurii.aulchenko at gmail.com
Fri May 2 10:27:34 CEST 2014
On Fri, May 2, 2014 at 12:25 AM, Diego Fabregat <
fabregat at aices.rwth-aachen.de> wrote:
> I like the idea of moving to git. I have no experience with github, but
> I'm using git on an almost daily basis (we have our own git server in our
> group for code and papers). I would have no problem in uploading OmicABEL
> to a git repo.
>
> Does dropping R-forge have a (bad) impact on the visibility of the project
> or on the user experience (e.g., installation of R packages)?
>
In my opinion - not really (visibility: I do not think we get many users
because they've found us at r-forge; also we can keep the account and make
links from there; as for installation, the argument partly holds only for
R-packages). What we need to think is of course how we keep/move all parts
such as a) code b) trackers c) project docs such as code guidelines
To me it seems that the idea to migrate few packages first is the most
reasonable; few are likely to stay at r-forge for long
Yurii
>
> On 04/28/2014 10:09 PM, L.C. Karssen wrote:
>
> Dear Maarten, dear all,
>
> Moving to github... Hmm... That is quite a decision, so I've renamed the
> subject to better reflect the discussion. I've also dropped the older
> e-mails from the bottom of the thread.
>
> First off, are there any people that have experience with git and/or
> github? I've got some git experience (still learning), but no real
> experience with github.
>
> I agree with Maarten that SVN is showing its age. As he indicates things
> like branching are much easier in git. Moreover, since I'm travelling
> regularly being able to work without internet connection is a pro.
>
> On the other hand, moving to git (whether github or elsewhere) means
> leaving R-forge, which is our well-known infrastructure. Furthermore,
> such a move operation will cost quite some time, I guess. Moving all
> bugs, features, etc... If we decide to move we should plan well and not
> rush. And then the current developers will need to learn git if they
> don't already know how to use it.
>
> One thing I think we should definitely do is migrate slowly, package by
> package. Given that Maarten is positive about such a move and that I am
> in a bit of limbo but not fully against, it seems logical that ProbABEL
> is the first package to try such a migration.
>
>
> Looking forward to your comments!
>
>
> Lennart.
>
>
> On 28-04-14 20:39, Maarten Kooyman wrote:
>
> Dear all,
>
> I think it is easier to use for code review github:
>
> Please check to get a impression
> :https://github.com/jquery/jquery/pull/1241/files
>
> I think we should reconsider an other the software version system: the
> current system is not up to date to current usability. Bug tracking and
> branching is quite hard in terms of usability. Please have a look atgithub.com to get a impression what is possible.
>
> Kind regards,
>
> Maarten
>
>
>
> --
> *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
> L.C. Karssen
> Utrecht
> The Netherlands
> lennart at karssen.orghttp://blog.karssen.org
> GPG key ID: A88F554A
> -*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-
>
>
>
>
> _______________________________________________
> genabel-devel mailing listgenabel-devel at lists.r-forge.r-project.orghttps://lists.r-forge.r-project.org/cgi-bin/mailman/listinfo/genabel-devel
>
>
>
> _______________________________________________
> genabel-devel mailing list
> genabel-devel at lists.r-forge.r-project.org
> https://lists.r-forge.r-project.org/cgi-bin/mailman/listinfo/genabel-devel
>
--
-----------------------------------------------------
Yurii S. Aulchenko
[ LinkedIn <http://nl.linkedin.com/in/yuriiaulchenko> ] [
Twitter<http://twitter.com/YuriiAulchenko>] [
Blog <http://yurii-aulchenko.blogspot.nl/> ]
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.r-forge.r-project.org/pipermail/genabel-devel/attachments/20140502/bf91c976/attachment-0001.html>
More information about the genabel-devel
mailing list