From: Alex Schroeder <alex@gnu.org>
Subject: Re: Emacs Website. Was: 21.2 release. Was: dabbrev can hang in presence of fields
Date: Fri, 22 Mar 2002 11:07:57 +0100 [thread overview]
Message-ID: <87d6xwkj9e.fsf@gnu.org> (raw)
In-Reply-To: Pine.SUN.3.91.1020321085114.5863N-100000@is
eliz@is.elta.co.il (Eli Zaretskii) writes:
>> <plug>That's what I like about the Emacs Wiki. When I'm not there,
>> somebody else will be. The entry barrier is just one click away -
>> anybody can edit the pages. And once you fix something, there is no
>> implicit expectation that you will continue to do so.</plug>
>
> Are you suggesting the same for the Emacs home page?
I would, if I thought it would stand a chance. I just assume that
either the GNU people running the server don't want to install weird
software (such as the wiki script), or people are affraid of abuse.
But other than that, yes, I think it is a good solution. It works
fine on the wiki. It has now 731 pages, and managed to get lots of
hits:
Hits Bytes Visits PViews Month
73,336 559,873,686 11,519 66,214 Jan 2002
75,276 592,474,181 11,548 71,494 Feb 2002
And still I can remember only one case of abuse and it was easily
corrected by the next person coming along (the old pages are kept for
a certain time).
So I think there are no significant drawbacks and it would fix the
maintainer problem. I never voluntered for the Emacs page on gnu.org
because that means responsability and work -- on the emacswiki,
however, responsability and work is shared.
If installing a wiki doesn't work for you for the reasons given above,
then perhaps "outsourcing" as much information as possible to the
existing wiki is the way to go. The main page could just say "Emacs
is an Editor and more. This site only features the Emacs manual
(link), the elisp manual (link) and the NT Emacs FAQ (link). Pointers
to CVS, the latest released version, the online FAQ, etc. are
maintained over at the Emacs Wiki (link)."
Ok, enough plugging. :)
Alex.
--
http://www.emacswiki.org/
_______________________________________________
Bug-gnu-emacs mailing list
Bug-gnu-emacs@gnu.org
http://mail.gnu.org/mailman/listinfo/bug-gnu-emacs
next prev parent reply other threads:[~2002-03-22 10:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.SUN.3.91.1020318185849.10731D-100000@is>
[not found] ` <yebbsdl9ccy.fsf@xpc21.ast.cam.ac.uk>
[not found] ` <Pine.SUN.3.91.1020319133309.17982F-100000@is>
[not found] ` <yeb663sagok.fsf@xpc21.ast.cam.ac.uk>
[not found] ` <Pine.SUN.3.91.1020319164023.19703B@is>
[not found] ` <87pu1zcx8y.fsf_-_@gnu.org>
2002-03-21 6:52 ` Emacs Website. Was: 21.2 release. Was: dabbrev can hang in presence of fields Eli Zaretskii
2002-03-22 10:07 ` Alex Schroeder [this message]
2002-03-22 11:53 ` Eli Zaretskii
2002-03-22 13:18 ` Alex Schroeder
2002-03-22 14:23 ` Eli Zaretskii
2002-03-24 6:49 ` 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=87d6xwkj9e.fsf@gnu.org \
--to=alex@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.