From: Julien Danjou <julien@danjou.info>
To: Eric Abrahamsen <eric@ericabrahamsen.net>
Cc: ding@gnus.org, emacs-devel@gnu.org
Subject: Re: Gnus work
Date: Thu, 05 Oct 2017 08:53:05 +0200 [thread overview]
Message-ID: <m0a816ulv2.fsf@danjou.info> (raw)
In-Reply-To: <87vajudasc.fsf@ericabrahamsen.net> (Eric Abrahamsen's message of "Wed, 04 Oct 2017 11:32:03 -0700")
[-- Attachment #1: Type: text/plain, Size: 1198 bytes --]
On Wed, Oct 04 2017, Eric Abrahamsen wrote:
Hi Eric,
> I've been very slowly reading the Gnus code base, and looking at how to
> go about doing some refactoring, cleanups, and a few new features. I
> wrote a roadmap which I'm attaching here -- it's not so much an actual
> roadmap as a collection of possible changes, as a starting point for
> argument. It's also not meant to be a mini bug tracker in Org -- my idea
> was that if any of the ideas looked like they were going to be
> acceptable, the todo items would turn into real bug reports on debbugs.
As a former regular Gnus contributor and as a current and long time Gnus
user, I want to give you my blessing. :-)
They are definitively ton of little code improvement you can make. All
of this technical debt reduction will lead to a better Gnus and a better
development future, so yes please!
I don't know how true it is nowadays, but a lot of what was blocking
improvement back then was support for old Emacs version and XEmacs
support. Now that Gnus is in Emacs source tree, I imagine that might not
applies anymore, so, lucky you! :)
--
Julien Danjou
# Free Software hacker
# https://julien.danjou.info
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2017-10-05 6:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-04 18:32 Gnus work Eric Abrahamsen
2017-10-04 18:43 ` Emanuel Berg
2017-10-04 18:53 ` Eric Abrahamsen
2017-10-04 21:07 ` Emanuel Berg
2017-10-04 20:21 ` Thien-Thi Nguyen
2017-10-05 17:14 ` Eric Abrahamsen
2017-10-04 21:09 ` Tim Landscheidt
2017-10-05 6:53 ` Julien Danjou [this message]
2017-10-05 13:31 ` Lars Ingebrigtsen
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=m0a816ulv2.fsf@danjou.info \
--to=julien@danjou.info \
--cc=ding@gnus.org \
--cc=emacs-devel@gnu.org \
--cc=eric@ericabrahamsen.net \
/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).