From: Neil Jerram <neil@ossau.uklinux.net>
To: Andy Wingo <wingo@pobox.com>
Cc: guile-devel <guile-devel@gnu.org>
Subject: Re: who wrote the manual?
Date: Mon, 11 Oct 2010 22:30:24 +0100 [thread overview]
Message-ID: <87tykspgcv.fsf@ossau.uklinux.net> (raw)
In-Reply-To: <m3mxqkecxg.fsf@unquote.localdomain> (Andy Wingo's message of "Mon, 11 Oct 2010 21:39:55 +0200")
Andy Wingo <wingo@pobox.com> writes:
> Developers with the most changed lines
> Neil Jerram 100687 (36.2%)
Quick, publish now before that changes! :-)
> Assuming that changed lines is the real measure of committing to the
> manual, we can fairly say that Neil wrote the manual, with important
> contributions from Marius on down. If we place the cutoff at 1% (and
> that's totally arbitrary), we can mention 8 more names, which is plenty
> for a preface, no?
Seriously, this is a hard question. Although Marius and I have written
a lot of new material, I'd say that our percentages are over-represented
because of the amount of large scale reorganization that we've done. (I
believe that if you just move 100 lines from A to B, Git will count that
as 100 additions and 100 deletions.)
Also supporting that, there was a great deal of manual already in
existence when I first started contributing to it (around 1998).
That then means that the top contributions are not as dominant as they
first look, and so maybe it's less fair to exclude people below some
arbitrary cutoff. In any case, perhaps we could list all of those names
in an Acknowledgements section, even if we decide to have a limited
subset upfront.
> But where is Mark Galassi in all of that, I wonder...
I'm afraid I don't know. Although I'm familiar with his name, I believe
his main involvement was before my time. I've internalised the text you
quoted about Mark writing the manual originally, and surely there must
be some substance to it - but I don't have more detail than that.
But I have a feeling (somehow) that Mark still follows the list
occasionally - so hopefully he may respond himself.
Regards,
Neil
next prev parent reply other threads:[~2010-10-11 21:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-11 19:39 who wrote the manual? Andy Wingo
2010-10-11 20:16 ` Ludovic Courtès
2010-10-11 21:01 ` Andy Wingo
2010-10-12 9:45 ` Ludovic Courtès
2010-10-30 15:42 ` Neil Jerram
2010-10-11 20:27 ` Mike Gran
2010-10-11 21:30 ` Neil Jerram [this message]
2010-10-11 22:06 ` Andy Wingo
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=87tykspgcv.fsf@ossau.uklinux.net \
--to=neil@ossau.uklinux.net \
--cc=guile-devel@gnu.org \
--cc=wingo@pobox.com \
/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).