all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Thomas Koch <thomas@koch.ro>
To: emacs-orgmode@gnu.org
Cc: cberry@tajo.ucsd.edu
Subject: Re: [wish] also provide documentation for contrib
Date: Fri, 12 Oct 2012 11:03:29 +0200	[thread overview]
Message-ID: <201210121103.31473.thomas@koch.ro> (raw)
In-Reply-To: <87ipam6tt3.fsf@tajo.ucsd.edu>

cberry@tajo.ucsd.edu:
> ,----[from contrib/README]
> 
> | These contributions are not part of GNU Emacs or of the official
> | Org-mode package.  But the git repository for Org-mode is glad to
> | provide useful way to distribute and develop them as long as they are
> | distributed under a free software license.
> 
> Maybe
>          http://orgmode.org/worg/org-contrib/org-drill.html 
> is what you need?

Hi Chuck,

I know that org-drill has its own webpage with good documentation. The point 
is, that the Debian maintainer (or Fedora, Gentoo, ...) just takes the org-
mode tarball and packages everything found in there. It would be an extra 
burden for the maintainer to go out to every single contrib site and somehow 
add the documentation in the package.

It would be much easier IMHO, if the org-mode developers would not only 
distribute the code of contribs but also their documentation. I would even say 
that distributing code without documentation is kind of a bug.

It would even be an extra advantage, if you could encourage the contrib 
developers to provide documentation in info format.

Best regards,

Thomas Koch, http://www.koch.ro

  reply	other threads:[~2012-10-12  9:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-07 17:01 [wish] also provide documentation for contrib Thomas Koch
2012-10-07 18:06 ` cberry
2012-10-12  9:03   ` Thomas Koch [this message]
2012-10-18  8:11     ` Sébastien Delafond
2012-10-27  8:54       ` Bastien
2012-10-29 14:14         ` Sébastien Delafond

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=201210121103.31473.thomas@koch.ro \
    --to=thomas@koch.ro \
    --cc=cberry@tajo.ucsd.edu \
    --cc=emacs-orgmode@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.