All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bernd Schubert <bernd-schubert@gmx.de>
To: cel@citi.umich.edu
Cc: nfs@lists.sourceforge.net, nfsv4@linux-nfs.org
Subject: Re: wiki.linux-nfs.org
Date: Tue, 28 Feb 2006 00:11:09 +0100	[thread overview]
Message-ID: <200602280011.09331.bernd-schubert@gmx.de> (raw)
In-Reply-To: <44032127.1070008@citi.umich.edu>

On Monday 27 February 2006 16:56, Chuck Lever wrote:
> Bernd Schubert wrote:
> >>by adding the FAQ to the wiki, are you proposing that it should be
> >>removed from sourceforge, and maintained by whomever wants to edit the
> >
> > That was the idea, but thatswhy I also asked for objections.
>
> you posted your question at 9am (EST) on a non-workday, then you waited

Well, I'm working too much nowadays. Almost have forgotten that weekends ar=
e=20
non-workdays ;)

> less than an hour before proceeding with the transfer.  that's hardly
> "asking for objections."

Sorry, the initial transfer was more or less just a test how well it works=
=20
automatically.

>
> also, why didn't you contact me about this first?  i am the FAQ
> maintainer, after all.  is there a problem you are trying to address?
> is there something missing in the FAQ?  have i been slacking?

Sorry, clearly my fault. I was really unpolite, please excuse me.

>
> >>wiki pages?  i'm not really comfortable with that.  the FAQ is very very
> >>carefully crafted and vetted so that it contains good information.
> >
> > Well, thats the general problem of a wiki. Usually it works, but
> > sometimes there is vandalism. On the other hand, most pages of the NFSv4
> > stuff also can be edited by all.
> > Maybe we should add a page where people wanting to modify the wiki can
> > enter their username and email and Bryce can unlock them on request? (I
> > hope this is possible with mediawiki, we unlock per user with moinmoin).
>
> i think wikis are a great tool, but here's the problem.
>
> if anyone (in the NFS community) can edit the FAQ, what stops people
> from adding erroneous advice, or even advice that opens a security hole
> or that could cause silent data corruption?
>
> for example, what happens if someone comes along and sees the "async"
> export option on the server and says "oh wow!  i can make my server 10x
> faster with this!  i'm going to add something to the FAQ that encourages
> everyone to use the 'async' export option!"
>
> or even worse, someone adds advice to export shares without root
> squashing because it makes accessing the data "so much easier", or
> misconfigure Kerberos, and on and on.
>
> sure, you can back it out easily, because it's a wiki.  but this all
> depends on us knowing the NFS implementation well enough, testing the
> advice, and being on top of the changes so we can quickly remove advice
> that is destructive.
>
> basically, people trust that this information won't screw them.  if we
> let anyone edit this page, it will become worthless information.  you
> don't see the Linux kernel developed this way, and for exactly the same
> reasons.
>
> i don't deny that the FAQ and How-To could use some help.  but please,
> let's reasonably discuss why we want to do this first, and see if we can
> address those issues with what we have.

Actually, I just wanted to add a how-to about high-availibility, moving a n=
fs=20
exported partition and more details about the fsid usage.
I have now removed the transferred FAQ, but I'm still planning to add some =
ha=20
stuff there. It only too late now (midnight).

What do you think about naming the section in the Wiki 'User FAQ' and then =
to=20
put a big disclaimer on that page, that shortly explains that this is not t=
he=20
official howto?


Sorry again,
	Bernd

=2D-=20
Bernd Schubert
PCI / Theoretische Chemie
Universit=E4t Heidelberg
INF 229
69120 Heidelberg

  reply	other threads:[~2006-02-27 23:11 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-25 17:10 wiki.linux-nfs.org Bernd Schubert
2006-02-25 17:24 ` wiki.linux-nfs.org Bryce Harrington
2006-02-25 17:57   ` wiki.linux-nfs.org Bernd Schubert
2006-02-26  0:28     ` wiki.linux-nfs.org Bryce Harrington
2006-02-25 21:28 ` wiki.linux-nfs.org Chuck Lever
2006-02-26 13:54   ` wiki.linux-nfs.org Bernd Schubert
2006-02-26 17:52     ` wiki.linux-nfs.org Bryce Harrington
2006-02-27 12:21       ` wiki.linux-nfs.org Bernd Schubert
2006-02-27 15:56     ` wiki.linux-nfs.org Chuck Lever
2006-02-27 23:11       ` Bernd Schubert [this message]
2006-02-28  0:13         ` wiki.linux-nfs.org Chuck Lever

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=200602280011.09331.bernd-schubert@gmx.de \
    --to=bernd-schubert@gmx.de \
    --cc=cel@citi.umich.edu \
    --cc=nfs@lists.sourceforge.net \
    --cc=nfsv4@linux-nfs.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 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.