Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: bloat <bloat@lists.bufferbloat.net>,
	"cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>
Subject: [Cerowrt-devel] marketing #102 - giving netperf-wrapper a better name?
Date: Thu, 12 Mar 2015 16:01:34 -0700	[thread overview]
Message-ID: <CAA93jw523E4iF9HNir+QdsMF1twKPM8HhXTjXPdY7NmQKL3g_A@mail.gmail.com> (raw)

as netperf-wrapper has grown to include far more tests than netperf,
with quite a few more on their way, calling it this is increasingly
less appropriate:

A noted cynic wrote me privately last month, about netperf-wrapper:

'why don't you rename the friggin thing "bufferbloat" or
"bloattest" or something?  Netperf-wrapper is a terrible name,
seemingly still whatever the programmer called it when he wrote the
first sketchy version, one step up from "foo"'

Hmm...  we need a name with more foo, for sure, a better, more
descriptive name. Anyone got any ideas? Maybe run a contest somewhere?

One (technical) hope would be to find a good file extension for the
output, so it could be more easily parsed by browsers... but to heck
with that... a better name?

Toke had some ideas also:

- NQT - http://acronyms.thefreedictionary.com/NQT - I especially like
  "Not Quite There". nqt.org points to this: http://dyslexiafoundation.org/nqt/

- NetQual - http://www.qoesystems.com/NETQUAL.html

- NQ-tester - doesn't seem to be taken by anything obvious


-- 
Dave Täht
Let's make wifi fast, less jittery and reliable again!

https://plus.google.com/u/0/107942175615993706558/posts/TVX3o84jjmb

             reply	other threads:[~2015-03-12 23:01 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-12 23:01 Dave Taht [this message]
2015-03-12 23:04 ` Toke Høiland-Jørgensen
     [not found] ` <550221CD.8030606@hp.com>
     [not found]   ` <CAA93jw7tdVUV70P8CtC4U5ALmtwrU5XtX8oSpdg_PtN+Z9HetA@mail.gmail.com>
2015-03-13  0:10     ` [Cerowrt-devel] [Bloat] " Dave Taht
2015-03-13  7:07 ` Rémi Cardona
2015-03-20 20:08   ` Bill Ver Steeg (versteb)
2015-03-20 20:25     ` Jonathan Morton
2015-03-20 21:08       ` Bill Ver Steeg (versteb)
2015-03-21  0:19         ` David P. Reed
2015-03-21 11:35         ` Alex Burr

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

  List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAA93jw523E4iF9HNir+QdsMF1twKPM8HhXTjXPdY7NmQKL3g_A@mail.gmail.com \
    --to=dave.taht@gmail.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=cerowrt-devel@lists.bufferbloat.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