unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Michael Albinus <michael.albinus@gmx.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Karl Fogel <kfogel@red-bean.com>, emacs-devel@gnu.org
Subject: Re: Improving documentation of Org Mode integration into Emacs.
Date: Wed, 05 Jan 2022 15:17:30 +0100	[thread overview]
Message-ID: <87r19m5ksl.fsf@gmx.de> (raw)
In-Reply-To: <83lezu9tv1.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 05 Jan 2022 15:48:02 +0200")

Eli Zaretskii <eliz@gnu.org> writes:

Hi Eli,

> I think we should explain the issue concisely, and then provide
> specific instructions.  This text is IMO enough for the first part:
>
>   +Sometimes a package that ships as part of GNU Emacs is maintained as a
>   +separate project, with its own upstream repository, its own maintainer
>   +group, its own development conventions, etc.  The upstream project's
>   +code is periodically merged into Emacs (exactly when and how such
>   +merges happen depends on the package).
>   +
>   +So when you are making a contribution -- such as fixing a bug or
>   +proposing an enhancement -- to one of these externally maintained
>   +packages, you often need to deal with that package at its upstream
>   +source.
>
> Following that, we should provide a full, exhaustive list of all such
> packages in Emacs core, each one with a corresponding URL (mailing
> list, upstream repository with an issue tracker, etc.).  It might be a
> good idea to have this list on a separate file, perhaps in etc/, and
> only have CONTRIBUTE point to that file.

We have already admin/MAINTAINERS, which could easily be extended for
this. I, for example, am mentioned there as responsible for
Tramp. Adding the Tramp relevant URLs would be easy, and so for all
other external maintained packages.

> Thanks.

Best regards, Michael.



  reply	other threads:[~2022-01-05 14:17 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-04 21:14 Improving documentation of Org Mode integration into Emacs Karl Fogel
2021-12-04 21:18 ` Karl Fogel
2021-12-04 22:09 ` [External] : " Drew Adams
2021-12-05  5:16 ` Stefan Monnier
2021-12-05  6:38 ` Eli Zaretskii
2022-01-03  5:05   ` Karl Fogel
2022-01-03  5:44     ` Stefan Monnier
2022-01-05  3:09       ` Karl Fogel
2022-01-05 13:48         ` Eli Zaretskii
2022-01-05 14:17           ` Michael Albinus [this message]
2022-01-05 14:26             ` Eli Zaretskii
2022-01-06 12:40               ` Michael Albinus
2022-01-06 13:58                 ` Eli Zaretskii
2022-01-07 10:41                   ` Protesilaos Stavrou
2022-01-09 22:34           ` Karl Fogel
2022-01-10  8:46             ` Michael Albinus
2022-01-10  9:03               ` Michael Albinus
2022-01-10  9:13                 ` Karl Fogel
2022-01-10  9:17                   ` Michael Albinus
2022-01-10 11:01                   ` Robert Pluim
2022-01-10 16:10                     ` Karl Fogel
2022-01-10  9:06               ` Karl Fogel
2022-01-10  9:24                 ` Michael Albinus
2022-01-10 16:20                   ` Karl Fogel
2022-01-10 18:24                     ` Eli Zaretskii
2022-01-11  7:49                       ` Michael Albinus
2022-01-10 18:14             ` Eli Zaretskii
2022-01-10 19:08               ` Karl Fogel
2022-01-03  8:52     ` Michael Albinus
2022-01-03 12:06     ` Protesilaos Stavrou
2022-01-03 13:31     ` Eli Zaretskii
2022-01-03 20:45     ` Rudolf Adamkovič

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=87r19m5ksl.fsf@gmx.de \
    --to=michael.albinus@gmx.de \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=kfogel@red-bean.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.
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).