From: ludo@gnu.org (Ludovic Courtès)
To: David Kastrup <dak@gnu.org>
Cc: 19883@debbugs.gnu.org
Subject: bug#19883: Correction for backtrace
Date: Fri, 27 Feb 2015 10:55:04 +0100 [thread overview]
Message-ID: <874mq7vfuv.fsf@gnu.org> (raw)
In-Reply-To: <87lhjkbhlp.fsf@fencepost.gnu.org> (David Kastrup's message of "Thu, 26 Feb 2015 20:25:22 +0100")
David Kastrup <dak@gnu.org> skribis:
> Three years ago in August there was a meeting of developers at my house,
> a lot of information was passed around and in a concerted effort
> LilyPond-2.16.0 was released.
>
> Since then all developments would properly be labelled a one-person
> project or side-project.
OK. I viewed LilyPond as a project with more people involved.
> Now if you take a look at GUILE 2.1 development, in particular all
> commits that are _not_ merges from the 2.0 branch, you'll find that
> quite more than 90% have come from the same person.
>
> LilyPond development is quite more diverse, but the various changes in
> the last years have invariably been one-person projects.
>
> Of the three large GUILE-based applications Gnucash, TeXmacs, and
> LilyPond, the only successful migration to GUILEv2 so far has been
> Gnucash, and its integration with GUILE is much smaller than that of
> LilyPond.
>
> The one-person projects concerning finding and/or fixing language and
> compiler problems or restructuring the related code areas have been
> exclusively mine. That is not necessarily a good match since my
> productivity drops to near zero when I lose interest with a problem, and
> without anybody else keeping the ball rolling, it can easily stay there.
Sure. There’s quite a number of names showing up in the lilypond-devel
archive though. We need them to feel concerned about this.
Ludo’.
next prev parent reply other threads:[~2015-02-27 9:55 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87mvieh7mu.fsf@gnu.org>
2015-02-16 16:41 ` bug#19883: Smob's mark_smob has become unreliable in Guile 2.x David Kastrup
2015-02-16 18:13 ` bug#19883: Correction for backtrace David Kastrup
2015-02-25 22:16 ` Ludovic Courtès
2015-02-25 23:17 ` David Kastrup
2015-02-26 11:35 ` Ludovic Courtès
2015-02-26 12:32 ` David Kastrup
2015-02-26 14:03 ` Ludovic Courtès
2015-02-26 15:30 ` David Kastrup
2015-02-26 18:15 ` Ludovic Courtès
2015-02-26 19:25 ` David Kastrup
2015-02-27 9:55 ` Ludovic Courtès [this message]
2015-02-27 10:18 ` David Kastrup
2016-06-23 9:50 ` Andy Wingo
2016-06-23 10:36 ` Andy Wingo
2016-06-23 13:13 ` Ludovic Courtès
2016-06-23 13:12 ` Ludovic Courtès
2015-03-01 6:51 ` bug#19883: Smob's mark_smob has become unreliable in Guile 2.x Mark H Weaver
2015-03-01 10:09 ` David Kastrup
2015-03-01 17:02 ` Mark H Weaver
2015-03-01 18:38 ` David Kastrup
2015-03-01 15:00 ` David Kastrup
2016-10-09 7:51 ` bug#19883: The “finalized” SMOB type Artyom Poptsov
[not found] ` <87vax2klj6.fsf@elephant.savannah>
[not found] ` <87fuo5hc88.fsf@gnu.org>
2016-10-09 19:00 ` Artyom Poptsov
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/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874mq7vfuv.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=19883@debbugs.gnu.org \
--cc=dak@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.
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).