General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: "Bill Ver Steeg (versteb)" <versteb@cisco.com>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>,
	"bloat@lists.bufferbloat.net" <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] The Great Renaming (of netperf-wrapper): Final contenders
Date: Mon, 13 Apr 2015 14:58:12 +0000	[thread overview]
Message-ID: <AE7F97DB5FEE054088D82E836BD15BE9319AECEA@xmb-aln-x05.cisco.com> (raw)
In-Reply-To: <87pp782wbt.fsf@toke.dk>

Exnett seems to work for me.

I like Ent, but it has some counter-culture references.  From urban dictionary ----- "A person who smokes marijuana. The term is named after the fictional tree characters from The Lord of the Rings after someone on Reddit noticed their slow and mellow personalities, similar to that of a stoned person." Not that this is a bad thing, but may get confusing. Actually, one of my favorite internal project names was "DOCSIS Out Of Band Internet Extensions - DOOBIE". That made for some confusing discussions at work (-8)).

Bill Ver Steeg












-----Original Message-----
From: bloat-bounces@lists.bufferbloat.net [mailto:bloat-bounces@lists.bufferbloat.net] On Behalf Of Toke Høiland-Jørgensen
Sent: Monday, April 13, 2015 5:48 AM
To: bloat@lists.bufferbloat.net
Subject: [Bloat] The Great Renaming (of netperf-wrapper): Final contenders

Hi everyone

The Great Renaming (of netperf-wrapper) has now entered its final phase (i.e., I have to make a decision now). There's a couple of contenders for a new name, see below. I'd like some feedback on which you prefer. A simple "This one!" is fine, but reasoning about why is also appreciated, of course :)

So, without further ado, the contenders are:

- "ENT: The Extensible Network Tester".
  Possible name clash: https://packages.debian.org/sid/ent

- "Exnett: The EXtensible NETwork Tester"
   Avoids the name clash; the second t is important for this.

- "Flent: The Flexible Network Tester"
  'Flent' is also the sound a bufferbloated network makes when subjected
  to testing :)

- "NetBasher"

For the first three, the abbreviation would probably be the everyday name, name of the executable, etc, with the expansion added in descriptions where appropriate.


Please comment by Thursday, as I have a deadline for something that needs to include the name then...

Thanks in advance! :)

-Toke
_______________________________________________
Bloat mailing list
Bloat@lists.bufferbloat.net
https://lists.bufferbloat.net/listinfo/bloat

  reply	other threads:[~2015-04-13 14:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-13  9:48 Toke Høiland-Jørgensen
2015-04-13 14:58 ` Bill Ver Steeg (versteb) [this message]
2015-04-13 15:36 ` Dave Taht
2015-04-14 17:30 ` Isaac Konikoff
2015-04-18 12:46 ` Toke Høiland-Jørgensen

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/bloat.lists.bufferbloat.net/

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

  git send-email \
    --in-reply-to=AE7F97DB5FEE054088D82E836BD15BE9319AECEA@xmb-aln-x05.cisco.com \
    --to=versteb@cisco.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=toke@toke.dk \
    /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