all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: David Kastrup <dak@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Paul Eggert <eggert@cs.ucla.edu>, emacs-devel@gnu.org
Subject: Re: Omitting Windows-specific parts from infrastructure changes
Date: Wed, 21 Jan 2015 21:49:29 +0100	[thread overview]
Message-ID: <87egqnhnae.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <831tmnx4e6.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 21 Jan 2015 22:30:57 +0200")

Eli Zaretskii <eliz@gnu.org> writes:

>> Date: Wed, 21 Jan 2015 11:39:34 -0800
>> From: Paul Eggert <eggert@cs.ucla.edu>
>
>> This is starting to get ridiculous.  Let's drop the discussion, as we're 
>> not making any progress (quite the reverse, I'm afraid).
>
> I already suggested several ways to resolve this.  Feel free to make
> your own suggestions, provided that the result will be that such
> changes are done everywhere, without unduly punishing your fellow
> developers who offer you help to do parts of your job.

It's not his job.  We are rather talking about how to enable different
people interested in different things to continue working on code in the
same Emacs repository.  As far as I know, it is nobody's _job_ to do so
currently (Gerd Möllmann once had a job working on the Emacs 21 display
engine if I remember correctly).  Neither the parts he did are his
"job", nor the parts he did not do.

In a project driven by volunteers it makes good sense when people invest
those kinds of work that otherwise would cause a much larger workload.
Sometimes this does not work, like when basically the best-suited person
for pretty much any task is the same person.  In that case, there is
some sense in others doing part of the work in spite of them being less
efficient at it, simply because there are limits to what a single person
can do.

However, in a project as large and diverse as Emacs, when we indeed have
the situation "if I had to tell anybody what I am doing, I would not
have enough time to do it", this is basically an unmaintainable
situation where indeed it might be more prudent from refraining to a
change where not even the resources for properly implementing it
throughout the code base _or_ communicating the necessary changes are
available.

-- 
David Kastrup



  reply	other threads:[~2015-01-21 20:49 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-16  9:54 Omitting Windows-specific parts from infrastructure changes Eli Zaretskii
2015-01-17  3:39 ` Paul Eggert
2015-01-17  8:34   ` Eli Zaretskii
2015-01-18 18:09     ` Paul Eggert
2015-01-18 18:23       ` Eli Zaretskii
2015-01-18 19:25         ` Paul Eggert
2015-01-18 19:50           ` Eli Zaretskii
2015-01-18 20:34             ` Paul Eggert
2015-01-19 16:03               ` Eli Zaretskii
2015-01-19 18:00                 ` Paul Eggert
2015-01-19 18:32                   ` Eli Zaretskii
2015-01-19 22:14                     ` Paul Eggert
2015-01-20 16:32                       ` Eli Zaretskii
2015-01-20 21:28                         ` Paul Eggert
2015-01-21 15:48                           ` Eli Zaretskii
2015-01-21 17:32                             ` Paul Eggert
2015-01-21 17:55                               ` Eli Zaretskii
2015-01-21 19:39                                 ` Paul Eggert
2015-01-21 20:07                                   ` Dmitry Gutov
2015-01-21 20:38                                     ` Eli Zaretskii
2015-01-21 20:08                                   ` David Kastrup
2015-01-21 20:49                                     ` Eli Zaretskii
2015-01-21 20:57                                       ` David Kastrup
2015-01-22  3:53                                         ` Eli Zaretskii
2015-01-21 20:30                                   ` Eli Zaretskii
2015-01-21 20:49                                     ` David Kastrup [this message]
2015-01-22  3:51                                       ` Eli Zaretskii
2015-01-22 14:20                                         ` Stefan Monnier

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=87egqnhnae.fsf@fencepost.gnu.org \
    --to=dak@gnu.org \
    --cc=eggert@cs.ucla.edu \
    --cc=eliz@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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.