Historic archive of defunct list bloat-devel@lists.bufferbloat.net
 help / color / mirror / Atom feed
From: richard <richard@pacdat.net>
To: "Dave Täht" <d@taht.net>
Cc: bloat-devel <bloat-devel@lists.bufferbloat.net>,
	bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] Wiki editing is enabled
Date: Tue, 08 Feb 2011 10:41:40 -0800	[thread overview]
Message-ID: <1297190500.26293.36.camel@amd.pacdat.net> (raw)
In-Reply-To: <878vxrdnxk.fsf@cruithne.co.teklibre.org>

I've done some editing on the Glossary page and added a link to it on
the main WIKI page.

To distinguish this list from all the other technical glossaries, I've
added:
"These terms are defined in the context of the overall topic,
Bufferbloat, and their relevance to the recognition, detection,
description, mitigation of this problem. As such, references to others'
definitions may be given for completeness but should be prefaced or
augmented by subjective and/or objective definition of the relationship
to the Bufferbloat problem."

I've shortened up the Bufferbloat def to make the page size reasonable -
with reference to the original page.

I've gone back over the mail list postings and grabbed some of the terms
used there - added them to the list with "definition needed" - so if you
have some time and a particular passion for a topic, please chime in.

I also won't feel bad if somebody decides that a term is too obvious or
generic for this list.

richard

On Mon, 2011-02-07 at 23:45 -0700, Dave Täht wrote:
> All:
> 
> I got a little behind last week on enabling people to edit the bloat
> wiki on www.bufferbloat.net.
> 
> There are now 24 registered users of the project, all of which should
> now be able to edit the wiki and contribute to the site.
> 
> Please feel free to edit/expand/suggest/expound on some pages! See the
> topic index and outline for what's already there and what's needed.
> 
> Textile markup is somewhat different than mediawiki markup, there is a
> reference for it on the help button, when you edit. 
> 
> There's also the usual sandbox:
> 
> http://www.bufferbloat.net/projects/bloat/wiki/Sandbox
> 
> If you are registered, and can't edit a page, please let me know.
> 
-- 
Richard C. Pitt                 Pacific Data Capture
rcpitt@pacdat.net               604-644-9265
http://digital-rag.com          www.pacdat.net
PGP Fingerprint: FCEF 167D 151B 64C4 3333  57F0 4F18 AF98 9F59 DD73


      reply	other threads:[~2011-02-08 18:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-08  6:45 Dave Täht
2011-02-08 18:41 ` richard [this message]

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=1297190500.26293.36.camel@amd.pacdat.net \
    --to=richard@pacdat.net \
    --cc=bloat-devel@lists.bufferbloat.net \
    --cc=bloat@lists.bufferbloat.net \
    --cc=d@taht.net \
    /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