From: Marcin Borkowski <mbork@wmi.amu.edu.pl>
To: ntg-context@ntg.nl
Subject: Re: git or svn
Date: Fri, 27 Sep 2013 15:26:25 +0200 [thread overview]
Message-ID: <20130927152625.12c967ca@aga-netbook> (raw)
In-Reply-To: <524583AC.8070505@sil.org>
Dnia 2013-09-27, o godz. 09:10:04
Lars Huttar <lars_huttar@sil.org> napisał(a):
> On 9/26/2013 9:10 PM, Aditya Mahajan wrote:
> > Github seems to be the most popular DVCS hosting site at the moment.
> > For manuals, I think that Github is particularly useful because you
> > can click on edit and make the change. Github automatically creates
> > a fork, a new branch, and pull request for you. So the technical
> > barrier to participation is low.
>
> I would question the perception that the technical barrier to
> participation on Github is low. Not long ago I tried to submit a patch
> to a project on Github, improving documentation and adding features.
> It took several hours (distributed over a couple of weeks) to learn
> how to do all that was required. It was *not* automatic. It strongly
> discouraged me from making more contributions to that project.
>
> Maybe some major things have changed on Github since then. In any
> case, I have no doubt that once you know the system, and have the
> infrastructure set up, it's easy to participate. And I'm not saying
> that SVN makes it easy for non-SVN users to participate. All I'm
> saying is that for non-Git users, the technical barrier to
> participation was substantial, last time I tried it.
>
> Again, I'm not arguing against a move to Git. I would just like to
> contribute my recent experience toward a well-informed decision
> process.
Just my 3 cents.
I am not a heavy Git user (though I am quite accustomed to Mercurial
instead), and I agree that the entry point for Git is not very low.
However, it seems that nowadays, for a *new* user, learning to use SVN
is pointless (unless he joins a project where SVN is used etc.):
distributed VCSs seem to be just much better (and I heard that SVN has
its own problems, too). So I would perceive this question as touching
a demography issue: younger people are more likely to know/use Git (and
not know SVN), older folk might know/use SVN.
Also, if this matters, Git has an excellent Emacs front-end, Magit. I
don't know whether SVN has something similar.
> Lars
Best,
--
Marcin Borkowski
http://octd.wmi.amu.edu.pl/en/Marcin_Borkowski
Adam Mickiewicz University
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2013-09-27 13:26 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-18 19:53 ConTeXt Manual Errata Thangalin
2013-09-21 17:15 ` Marco Patzer
2013-09-26 17:44 ` Marco Patzer
2013-09-26 20:07 ` Thangalin
2013-09-26 20:15 ` Aditya Mahajan
2013-09-26 20:31 ` Marco Patzer
2013-09-26 20:42 ` Peter Münster
2013-09-26 21:22 ` Mica Semrick
2013-09-26 21:50 ` git or svn (was: ConTeXt Manual Errata) Peter Münster
2013-09-26 21:56 ` Mica Semrick
2013-09-26 23:24 ` Thangalin
2013-09-27 6:46 ` git or svn Peter Münster
2013-09-27 1:10 ` git or svn (was: ConTeXt Manual Errata) Aditya Mahajan
2013-09-27 7:01 ` git or svn Peter Münster
2013-09-27 7:38 ` Taco Hoekwater
2013-09-27 13:01 ` Lars Huttar
2013-09-27 13:10 ` Lars Huttar
2013-09-27 13:26 ` Marcin Borkowski [this message]
2013-09-27 14:02 ` Peter Münster
2013-09-27 14:27 ` Hans Hagen
2013-09-27 17:08 ` Mica Semrick
2013-09-26 23:22 ` ConTeXt Manual Errata Thangalin
2013-09-27 9:10 ` Marco Patzer
2013-09-27 9:27 ` Peter Münster
2013-09-26 20:17 ` Marco Patzer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130927152625.12c967ca@aga-netbook \
--to=mbork@wmi.amu.edu.pl \
--cc=ntg-context@ntg.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).