all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Glenn Morris <rgm@gnu.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: emacs-devel@gnu.org, Bruno Haible <bruno@clisp.org>,
	Alexandre Garreau <galex-713@galex-713.eu>,
	bug-gettext@gnu.org
Subject: Re: [bug-gettext] ELPA and gettext.el
Date: Sat, 19 Jan 2019 17:08:46 -0500	[thread overview]
Message-ID: <yjbm4cuwpd.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <05edc689-8d29-345e-3cc8-98a511f34025@cs.ucla.edu> (Paul Eggert's message of "Sat, 19 Jan 2019 09:58:22 -0800")


>   1) The responsibility of po-mode.el was transferred to the Emacs community
>      at the same time. Yes, it would be welcome if someone could take care of
>      the 5 open bugs regarding the PO mode. [1][2][3][4][5]

Simply moving the files to another repository (GNU Emacs or ELPA) won't
create a maintainer for them. There is no GNU ELPA community AFAIK.
Excepting perhaps Stefan, it seems to be individuals maintaining their
own packages. Emacs itself has a small number of active people, but less
used components can languish.

>  2) The documentation is handled appropriately. Currently it is documented
>     through some texinfo-formatted documentation [6]. Whereas ELPA packages,
>     as far as I can see, currently only have plain text documentation, which
>     is inferior to texinfo / hypertext formatted documentation.

ELPA packages may contain info pages. Ref

https://www.gnu.org/software/emacs/manual/html_node/elisp/Multi_002dfile-Packages.html

Personally, I strongly recommend creating an ELPA package rather than
adding to Emacs itself.



  reply	other threads:[~2019-01-19 22:08 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-19  1:47 ELPA and gettext.el Alexandre Garreau
     [not found] ` <87zhrxxvsv.fsf-GJHrUhKTnLMAVn7cI0sOhGhLVPiuUekF@public.gmane.org>
2019-01-19 11:37   ` Bruno Haible
2019-01-19 17:58     ` [bug-gettext] " Paul Eggert
2019-01-19 22:08       ` Glenn Morris [this message]
     [not found]         ` <yjbm4cuwpd.fsf-iW7gFb+/I3LZHJUXO5efmti2O/JbrIOy@public.gmane.org>
2019-01-20 10:58           ` Bruno Haible
2019-01-20 18:10             ` [bug-gettext] " Alexandre Garreau
2019-01-25 20:58             ` Paul Eggert
2019-01-26  0:53               ` Stefan Monnier
     [not found]                 ` <jwvsgxgw8b2.fsf-monnier+emacs-mXXj517/zsQ@public.gmane.org>
2019-01-26  7:18                   ` Eli Zaretskii

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=yjbm4cuwpd.fsf@fencepost.gnu.org \
    --to=rgm@gnu.org \
    --cc=bruno@clisp.org \
    --cc=bug-gettext@gnu.org \
    --cc=eggert@cs.ucla.edu \
    --cc=emacs-devel@gnu.org \
    --cc=galex-713@galex-713.eu \
    /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.