unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: peder@news.klingenberg.no (Peder O. Klingenberg)
To: emacs-devel@gnu.org
Subject: Re: Emacs author stats
Date: Fri, 24 Apr 2015 10:46:51 +0200	[thread overview]
Message-ID: <ksh9s5x69w.fsf@luna.netfonds.no> (raw)
In-Reply-To: 83mw1yzjua.fsf@gnu.org

On Thu, Apr 23 2015 at 23:10, Eli Zaretskii wrote:

> To send a patch, you need to clone the repository, develop and test
> the patch, send it for review, update it several times according to
> comments, rebase it as master gets new commits, etc.  All of which
> involves the VCS, and so many people said they will not consider
> becoming contributors unless we switched to Git.

I am not a committer, but I have contributed a patch or two.  The basis
for my contributions has always been git-controlled.  Even before the
official switchover, I used the git mirror of the bzr tree.  I have no
desire to learn more VC systems than I absolutely have to, and these
days, git is a must for almost everything.  But had the git mirror not
existed, I'm convinced I could have muddled through the necessary
cut'n'paste to download the bzr tree.

What I'm saying is that, as a non-committer and infrequent contributor,
Emacs' choice of VC system was not a big factor in my decision to
contribute to Emacs.  Had bzr been the only choice, and had it proved
irksome to use, I might not have continued to contribute, but that was
never an issue, as the git mirror was perfectly adequate.

Compared to the hassle of copyright assignment, Emacs' choice of VC was
lost in the noise.  And I did not find the copyright process especially
burdensome, just a bit time consuming.  (What do we want?  Instant
gratification!  When do we want it? NOW!)

I was in favour of the move to git, because it seemed from the outside
like the right thing to do, but the impact on me was very close to zero.
And I didn't voice my opinion at the time because I felt it wasn't my
decision to make, in part exactly because I was not a frequent
contributor, and knew that the outcome would not influence my
contribution frequency at all.

The things preventing me from contributing more have nothing to do with
versioning systems.  It is partly that annoying thing called life which
my family insists I engage in occasionally, but even more, it's a
distinct lack of itches to scratch.  Emacs mostly does what I need
really, really well already.  So thanks, all of you!

...Peder...
-- 
I wish a new life awaited _me_ in some off-world colony.





  parent reply	other threads:[~2015-04-24  8:46 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-23 17:41 Emacs author stats Lars Magne Ingebrigtsen
2015-04-23 17:49 ` Eli Zaretskii
2015-04-23 18:27   ` John Wiegley
2015-04-23 18:44   ` Lars Magne Ingebrigtsen
2015-04-23 19:54     ` Eli Zaretskii
2015-04-23 18:48   ` Artur Malabarba
2015-04-23 19:05     ` Lars Magne Ingebrigtsen
2015-04-23 19:55     ` Eli Zaretskii
2015-04-23 19:59       ` Dmitry Gutov
2015-04-23 20:10         ` Eli Zaretskii
2015-04-23 22:33           ` Artur Malabarba
2015-04-24  8:46           ` Peder O. Klingenberg [this message]
2015-04-24 13:55       ` Stefan Monnier
2015-04-23 20:01     ` chad
2015-04-24  1:43     ` Stephen J. Turnbull
2015-04-23 18:49 ` Artur Malabarba

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=ksh9s5x69w.fsf@luna.netfonds.no \
    --to=peder@news.klingenberg.no \
    --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).