Gnus development mailing list
 help / color / mirror / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: Gnus and GMail coexistence: need manual section
Date: Mon, 15 Sep 2008 12:49:43 -0500	[thread overview]
Message-ID: <86fxo1padk.fsf@lifelogs.com> (raw)
In-Reply-To: <86ljy27ifq.fsf@lifelogs.com>

On Mon, 08 Sep 2008 10:42:33 -0500 Ted Zlatanov <tzz@lifelogs.com> wrote: 

TZ> On Sun, 07 Sep 2008 16:27:45 -0700 "Eric Schulte" <schulte.eric@gmail.com> wrote: 

ES> I would recommend the page on EmacsWiki which does a very good job of
ES> addressing all of these points, and could probably be dropped into the
ES> gnus documentation with minimal editing

ES> http://www.emacswiki.org/cgi-bin/wiki/GnusGmail

TZ> Should the link be in the manual?  Should the manual freeze this
TZ> information?  I can see both sides of the argument but it seems that
TZ> freezing the information *and* providing the URL would be technically
TZ> best but also most confusing to the user.

Ping?  I'd like some opinions please.  This is about how the Gnus manual
coexists with emacswiki.org and similar sites, not just about GMail, so
I don't want to make the decision on my own.  

My vote is for freezing the information through some semi-automated
system that updates CVS from emacswiki.org or other sources (never
automatically!), and keeping all the information plus links to the
original and credits in a separate manual section.

This requires a look at any possible legal issues of bringing in
emacswiki.org content into the manual.  Who would know about this?

Thanks
Ted




  reply	other threads:[~2008-09-15 17:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-05 15:12 Ted Zlatanov
2008-09-07 23:27 ` Eric Schulte
2008-09-08 15:42   ` Ted Zlatanov
2008-09-15 17:49     ` Ted Zlatanov [this message]
2008-09-16 12:44       ` Greg Stark
2008-09-16 19:08         ` Ted Zlatanov

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=86fxo1padk.fsf@lifelogs.com \
    --to=tzz@lifelogs.com \
    --cc=ding@gnus.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.
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).