From: Eli Zaretskii <eliz@gnu.org>
To: "Andreas Röhler" <andreas.roehler@online.de>
Cc: emacs-devel@gnu.org
Subject: Re: burden of maintainance
Date: Thu, 01 Oct 2015 23:27:28 +0300 [thread overview]
Message-ID: <83bnci8hcf.fsf@gnu.org> (raw)
In-Reply-To: <560D9508.2060209@online.de>
> Date: Thu, 01 Oct 2015 22:18:16 +0200
> From: Andreas Röhler <andreas.roehler@online.de>
> CC: Eli Zaretskii <eliz@gnu.org>
>
> It would suffice to put intelligent test-writing into the focus - where
> it's not yet or not yet to extend it deserves.
This is a volunteer effort. Nothing gets done by putting some issues
into the focus: you cannot tell anyone to do something because it's in
focus. The only way things get moved in Emacs is when volunteers step
forward and take tasks upon themselves.
So the issue at hand is how to attract contributors to writing tests.
It's not a decision-making problem, it's a leadership and
team-management problem.
> > Also, I don't
> > quite see who will write tests for large portions of the C code, given
> > how few people are even prepared to work on that.
>
> Estimating one hour invested in writing the right tests might save
> ten-fold or more of development time afterwards.
I agree. But it's not enough to agree, there's a need to actually do
it.
> Not a special one at the moment. Just got the feeling the collection of
> used symbols were growing and growing last years.
My take of this is that many people here disagree with you about this
being a bad thing.
next prev parent reply other threads:[~2015-10-01 20:27 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-01 8:10 burden of maintainance Andreas Röhler
2015-10-01 16:03 ` Eli Zaretskii
2015-10-01 18:46 ` Andreas Röhler
2015-10-01 19:09 ` Eli Zaretskii
2015-10-01 20:18 ` Andreas Röhler
2015-10-01 20:27 ` Eli Zaretskii [this message]
2015-10-02 13:54 ` Przemysław Wojnowski
2015-10-02 14:15 ` Eli Zaretskii
2015-10-02 17:18 ` Tassilo Horn
2015-10-02 18:24 ` Eli Zaretskii
2015-10-02 18:47 ` joakim
2015-10-02 19:16 ` Tassilo Horn
2015-10-02 20:53 ` Eli Zaretskii
2015-10-02 19:28 ` Chad Brown
2015-10-02 7:51 ` Helmut Eller
2015-10-02 8:47 ` Eli Zaretskii
2015-10-02 8:56 ` Helmut Eller
2015-10-02 8:59 ` Eli Zaretskii
2015-10-02 11:46 ` Michael Albinus
2015-10-02 11:58 ` Phillip Lord
2015-10-02 13:14 ` Artur Malabarba
2015-10-02 13:36 ` Eli Zaretskii
2015-10-02 15:00 ` Andreas Röhler
2015-10-02 15:16 ` Eli Zaretskii
2015-10-02 17:19 ` Andreas Röhler
2015-10-02 18:08 ` Eli Zaretskii
2015-10-02 18:54 ` Andreas Röhler
2015-10-02 20:39 ` Tassilo Horn
2015-10-03 6:53 ` Andreas Röhler
2015-10-03 7:31 ` Tassilo Horn
2015-10-03 1:38 ` Richard Stallman
2015-10-03 0:38 ` Eric Ludlam
2015-10-02 23:24 ` Xue Fuqiao
2015-10-03 6:42 ` Przemysław Wojnowski
2015-10-03 7:00 ` Xue Fuqiao
2015-10-03 7:15 ` Eli Zaretskii
2015-10-01 16:34 ` Przemysław Wojnowski
2015-10-02 11:25 ` Phillip Lord
2015-10-02 12:27 ` Michael Albinus
2015-10-02 14:53 ` Phillip Lord
2015-10-02 16:56 ` Michael Albinus
2015-10-03 1:35 ` Richard Stallman
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=83bnci8hcf.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=andreas.roehler@online.de \
--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).