Many ISPs need the kinds of quality shaping cake can do
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: libreqos <libreqos@lists.bufferbloat.net>,
	bloat <bloat@lists.bufferbloat.net>,
	 Dave Taht via Starlink <starlink@lists.bufferbloat.net>
Subject: [LibreQoS] everything open conference in australia CFP
Date: Mon, 16 Jan 2023 10:38:53 -0800	[thread overview]
Message-ID: <CAA93jw5u9g8jH1H==vAeLKxodZbHPXVJ672uc+jar2jXpJfX-g@mail.gmail.com> (raw)

I enjoyed most of my last LCA conference. (the apnic bufferbloat one)
This one - (same organizers)  is being put on in a rush, it seems, the
CFP is due next week, and the conference itself is in mid-march. I'm
too broke, and too grumpy, to want to travel this far.

https://2023.everythingopen.au/

       This year, instead of LCA, there's going ot be a new
conference, 'Everything Open'.
        Call for presentations closes next week --- get an abstract in
soon if you've done
        anything open-source,   open-hardware, open-data,
open-government, or open-anything!
        A abstract needs only a couple of hundred words that should be
aimed (at this stage)
        to convince the selection committee you have something
interesting to say,
        and that you're the right person to say it.

-- 
This song goes out to all the folk that thought Stadia would work:
https://www.linkedin.com/posts/dtaht_the-mushroom-song-activity-6981366665607352320-FXtz
Dave Täht CEO, TekLibre, LLC

                 reply	other threads:[~2023-01-16 18:39 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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

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

  git send-email \
    --in-reply-to='CAA93jw5u9g8jH1H==vAeLKxodZbHPXVJ672uc+jar2jXpJfX-g@mail.gmail.com' \
    --to=dave.taht@gmail.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=libreqos@lists.bufferbloat.net \
    --cc=starlink@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