Gnus development mailing list
 help / color / mirror / Atom feed
From: "Göktuğ Kayaalp" <self@gkayaalp.com>
To: Eric Abrahamsen <eric@ericabrahamsen.net>
Cc: ding@gnus.org
Subject: Re: Moving Gnus development to Emacs?
Date: Fri, 01 Jan 2016 23:43:26 +0200	[thread overview]
Message-ID: <871ta1ugap.fsf@xi.bootis> (raw)
In-Reply-To: <87bn96apq3.fsf@ericabrahamsen.net> (Eric Abrahamsen's message of "Thu, 31 Dec 2015 18:15:32 +0800")

On Thu, Dec 31 2015 at 12:15:32 PM, Eric Abrahamsen <eric@ericabrahamsen.net> wrote:
> Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
>> […]
>> So: I want to know how all y'all would feel if I closed git.gnus.org and
>> started bringing the Gnus code base in the Emacs trunk up to modern
>> Emacs standards.  That would mean removing basically all compat code.
>>
>> No more `mm-string-as-unibyte'.  No more `gnus-invisible-p'.  Freedom!
> How much more work would it be to keep the external repo, but split the
> different versions into different branches? Ie, an "emacs-master" branch
> (which gets bundled into Emacs releases), an "Xemacs" branch, and an
> "SXEmacs" branch (whatever that is).
> […]

Hi all, I'm a n00b to the list,  however I wanted to add my two cents to
the discussion.  Sorry if I say sth. silly.

If my memory is  good enough, I recall the new  GNU Emacs maintainer say
on a  recent interview [1] that  he wish to « modularise »  Emacs source
tree, i.e. move non-essential bits to their own projects.

I think vanilla  emacs bundles too many things, so  I back such attempt.
Installing packages in Emacs is very  easy today, one command is enough.
No need to bundle tetris, doctor,  etc., nor Org and Gnus.  Abrahamsen's
suggestion of branches seems good.  Alternatively, given that many Emacs
modules  begin   with  a  suit   of  /polyfills/,  maybe   a  standalone
/backports.el/ module should be created, so  that all the Elisp devs can
target  only  the  latest  release  without guilt.   Also  Gnus  can  be
developed  that way,  without  need to  maintain  /ports/ for  different
emacsen,  should a  good common  backports package  be available.   Gnus
releases target  the latest GNU  Emacs release,  and users of  older GNU
versions and  other emacsen  maintain the backports  package to  get the
cool  stuff.   This would  help  all  the  Emacs community.   Maybe  the
possiblity of this should be discussed on emacs-tangents.

[1] Sacha Chua's Emacs Chat with John Wiegley
    Video: <https://www.youtube.com/watch?v=nUjgKoOYxos>

All the best,
-gk

-- 
İ. Göktuğ Kayaalp.
http://gkayaalp.com/



  parent reply	other threads:[~2016-01-01 21:43 UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-30 11:43 Lars Magne Ingebrigtsen
     [not found] ` <mailman.1827.1451475821.29210.sxemacs-devel-sxemacs.org@lists.sxemacs.org>
2015-12-30 14:33   ` Moving Gnus development to Emacs Steve Youngs
2015-12-30 15:15     ` Ivan Shmakov
2016-01-01 19:21     ` Steinar Bang
2016-01-02  3:28     ` Lars Magne Ingebrigtsen
2015-12-30 16:33 ` Moving Gnus development to Emacs? raman
2015-12-30 19:05   ` Jay Belanger
2015-12-30 19:25     ` Nikolaus Rath
2015-12-31 17:40     ` Lars Magne Ingebrigtsen
2015-12-31 18:35       ` Benjamin Slade
2015-12-30 18:44 ` John Wiegley
2015-12-31  0:46 ` Katsumi Yamaoka
2015-12-31 13:50   ` Eli Zaretskii
2015-12-31  9:18 ` Julien Danjou
2015-12-31  9:40 ` David Engster
2015-12-31 11:43   ` Michael Albinus
2015-12-31 12:29     ` CHENG Gao
2015-12-31 14:35       ` Xue Fuqiao
2015-12-31 14:52         ` CHENG Gao
2016-01-01  0:10           ` Xue Fuqiao
2016-01-01  7:02             ` CHENG Gao
2015-12-31 17:10   ` Lars Magne Ingebrigtsen
2015-12-31 17:15     ` Adam Sjøgren
2016-01-02 17:39   ` Lars Magne Ingebrigtsen
2016-01-02 20:31     ` Steinar Bang
2016-01-03 18:24     ` Bill Wohler
2016-01-04  0:48       ` Lars Magne Ingebrigtsen
2016-01-04  1:05         ` John Wiegley
2016-01-04  3:47     ` Steve Youngs
2016-01-06  7:18       ` Lars Magne Ingebrigtsen
2016-01-06  7:38         ` CHENG Gao
2016-01-06  8:50         ` Andreas Schwab
2016-01-25 15:07     ` Ted Zlatanov
2016-01-28 12:45     ` Greg Troxel
2015-12-31 10:15 ` Eric Abrahamsen
2015-12-31 17:43   ` Lars Magne Ingebrigtsen
2016-01-01 21:43   ` Göktuğ Kayaalp [this message]
2015-12-31 17:04 ` Uwe Brauer
2016-01-18  7:26 gnus-summary-refer-parent-article bug Dave Abrahams
2016-01-18 12:43 ` Alan Schmitt
2016-01-18 15:47   ` Dave Abrahams
2016-01-19  0:25     ` Katsumi Yamaoka
2016-01-19 15:59       ` Dave Abrahams
2016-01-19 22:10         ` Katsumi Yamaoka
2016-01-20 11:04           ` Alan Schmitt
2016-01-20 23:04             ` Katsumi Yamaoka
2016-01-21 10:21               ` Alan Schmitt
2016-01-22  2:37                 ` Moving Gnus development to Emacs? Katsumi Yamaoka
2016-01-22  7:53                   ` Alan Schmitt
2016-01-22  9:45                     ` Katsumi Yamaoka
2016-01-22 11:28                       ` Michael Albinus
2016-01-24 23:35                         ` Katsumi Yamaoka
2016-01-25  1:58                           ` Mike Kupfer
2016-01-25  3:11                             ` Katsumi Yamaoka
2016-01-25 13:12                             ` Alan Schmitt
2016-01-22 12:25                       ` Alan Schmitt
2016-01-25  1:37                   ` Katsumi Yamaoka
2016-02-06  5:51                   ` Lars Ingebrigtsen
2016-02-06 14:36                     ` Adam Sjøgren
2016-02-06 14:38                       ` Adam Sjøgren

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=871ta1ugap.fsf@xi.bootis \
    --to=self@gkayaalp.com \
    --cc=ding@gnus.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.
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 NNTP newsgroup(s).