From: Yavor Doganov <yavor@gnu.org>
To: emacs-devel@gnu.org
Subject: Re: dVCS vs. CVS
Date: Mon, 07 Jan 2008 17:23:06 +0200 [thread overview]
Message-ID: <87prwd7j8l.GNU's_Not_Unix!%yavor@gnu.org> (raw)
In-Reply-To: <87y7b36ojw.fsf@bzg.ath.cx>
Bastien wrote:
>
> The risk of switching to a dVCS is not one of loosing
> functionnalities, but one of loosing those developers who don't want
> to learn a new tool (I don't think there are any here...?)
Maybe there aren't, and probably what I am going to say does not
relate at all to the Emacs project. But there are two important
things that were missed in that huge thread:
Lifting the barrier -
dVCS (and the fact that there are many of them) are a nightmare for
contributors who are not programmers, like translators and
documentation writers. A dVCS is a sophisticated tool and a
complicated concept that such people do not understand, or at least
they do after substantial investment of time and sweat.
Not a silver bullet -
Autoconf, Automake, m4, Gnulib and other projects switched to Git some
time ago. One would expect that there will be an avalanche of new
contributors who were not volunteering only because they needed a
modern VCS to go ahead. False assumption -- pretty much the same
people hack on these projects after the switch.
next prev parent reply other threads:[~2008-01-07 15:23 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-06 14:01 dVCS vs. CVS Bastien
2008-01-07 15:23 ` Yavor Doganov [this message]
2008-01-07 16:03 ` Tassilo Horn
2008-01-07 21:00 ` Alan Mackenzie
2008-01-07 22:45 ` Tassilo Horn
2008-01-08 2:46 ` Michael Olson
2008-01-08 9:28 ` Yavor Doganov
2008-01-08 12:59 ` Miles Bader
2008-01-07 16:05 ` David Kastrup
2008-01-07 21:52 ` Bastien
2008-01-07 21:59 ` Stephen J. Turnbull
2008-01-07 22:19 ` David Kastrup
2008-01-08 8:57 ` Stephen J. Turnbull
2008-01-09 11:37 ` Richard Stallman
2008-01-07 22:33 ` Bastien
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='87prwd7j8l.GNU'\''s_Not_Unix'\!'%yavor@gnu.org' \
--to=yavor@gnu.org \
--cc=emacs-devel@gnu.org \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).