<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
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.<br>
<br>
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)?<br>
<br>
<div class="moz-cite-prefix">On 04/28/2014 10:09 PM, L.C. Karssen
wrote:<br>
</div>
<blockquote cite="mid:535EB58D.6010900@karssen.org" type="cite">
<pre wrap="">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:
</pre>
<blockquote type="cite">
<pre wrap="">Dear all,
I think it is easier to use for code review github:
Please check to get a impression
:<a class="moz-txt-link-freetext" href="https://github.com/jquery/jquery/pull/1241/files">https://github.com/jquery/jquery/pull/1241/files</a>
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 at
github.com to get a impression what is possible.
Kind regards,
Maarten
</pre>
</blockquote>
<pre wrap="">
--
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
L.C. Karssen
Utrecht
The Netherlands
<a class="moz-txt-link-abbreviated" href="mailto:lennart@karssen.org">lennart@karssen.org</a>
<a class="moz-txt-link-freetext" href="http://blog.karssen.org">http://blog.karssen.org</a>
GPG key ID: A88F554A
-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-
</pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
genabel-devel mailing list
<a class="moz-txt-link-abbreviated" href="mailto:genabel-devel@lists.r-forge.r-project.org">genabel-devel@lists.r-forge.r-project.org</a>
<a class="moz-txt-link-freetext" href="https://lists.r-forge.r-project.org/cgi-bin/mailman/listinfo/genabel-devel">https://lists.r-forge.r-project.org/cgi-bin/mailman/listinfo/genabel-devel</a></pre>
</blockquote>
<br>
</body>
</html>