all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Emanuel Berg <embe8573@student.uu.se>
To: emacs-devel@gnu.org
Subject: Re: New Emacs maintainer
Date: Fri, 06 Nov 2015 03:27:32 +0100	[thread overview]
Message-ID: <87wptvdfqj.fsf@debian.uxu> (raw)
In-Reply-To: m2fv0lkp14.fsf@newartisans.com

John Wiegley <jwiegley@gmail.com> writes:

> Thank you, to everyone!!
>
> I think the key to avoided burnout will be not
> trying to do everything myself. There are excellent
> people in this community, who together have more
> time and energy than I will in a lifetime. If I can
> coordinate them, and help them focus on what they
> find fun and interesting, not only will this job be
> easier for me, it should be more fun for everyone.
> We're doing this because we love Emacs, right?
> Pursuing one's love ought to make the time spent
> feel worth every second! if not, there's an obstacle
> we need to remove.

OK, so you are the maintainer of all of Emacs?
How does that work? :O

Are there "submaintainers" for parts of Emacs -
I don't mean third-party add-ons (e.g., Emacs-w3m) or
for that matter software found in the ELPAs, which are
obviously stand-alone projects. I mean for example
help.el? In the header, it says

    Maintainer: emacs-devel@gnu.org

Does that mean you?

On my Debian, the maintainer of emacs24 is
Rob Brownin, however I take it that refers to the
Debian package, not the Emacs source.

Anyway, according to cloc [1] I have written 95 files
of Elisp totalling 3721 lines of code. That doesn't
strike me as neither a lot nor something
insignificant... But I feel pretty confident because
it works.

I mention this because if you have something that has
been abandoned or left half-baked I'm happy to lend
a hand. I can be an asset in part because what I like
in technology, few others like (which is sad for me
and... them). So if everyone wants to do LaTeX it is
good if at least a few want to do groff. (Actually
I like LaTeX and Biblatex as well.) You know what I'm
saying? Do you have a TODO list or anything?

Keep it real :)

[1] http://cloc.sourceforge.net/

-- 
underground experts united
http://user.it.uu.se/~embe8573




  reply	other threads:[~2015-11-06  2:27 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-03 20:23 New Emacs maintainer John Yates
2015-11-03 20:33 ` John Wiegley
2015-11-03 20:44   ` Kaushal Modi
2015-11-03 20:45   ` John Yates
2015-11-03 22:02   ` David Kastrup
2015-11-04  7:58   ` Nicolas Petton
2015-11-04  8:34     ` Pierre Lecocq
2015-11-05  3:07   ` Karl Fogel
2015-11-05  5:12     ` John Wiegley
2015-11-06  2:27       ` Emanuel Berg [this message]
2015-11-06  2:31         ` John Wiegley
2015-11-06  3:26           ` Emanuel Berg
2015-11-06  4:14             ` Kaushal Modi
2015-11-06 14:15           ` ToDo list and bugtracker Andreas Röhler
2015-11-06 21:40           ` New Emacs maintainer Richard Stallman
2015-11-08 16:25             ` John Wiegley

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=87wptvdfqj.fsf@debian.uxu \
    --to=embe8573@student.uu.se \
    --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.