From: dan <dandenson@gmail.com>
To: Frantisek Borsik <frantisek.borsik@gmail.com>
Cc: libreqos <libreqos@lists.bufferbloat.net>,
bloat <bloat@lists.bufferbloat.net>,
"Dave Taht via Starlink" <starlink@lists.bufferbloat.net>,
"Jeremy Austin via Rpm" <rpm@lists.bufferbloat.net>,
bloat-ietf@lists.bufferbloat.net,
"Cake List" <cake@lists.bufferbloat.net>,
codel@lists.bufferbloat.net, l4s-discuss@ietf.org,
"Herbert Wolverson" <hwolverson@libreqos.io>,
"Robert Chacón" <robert@libreqos.io>
Subject: Re: [Rpm] [LibreQoS] Please, co-sign Dave Taht's nomination for Jonathan B. Postel Service Award
Date: Thu, 19 Jun 2025 16:25:37 -0600 [thread overview]
Message-ID: <CAA_JP8X31acErGTjKWgmWP3QED2P7kL=V-CeqMsXKgbo6VhWCA@mail.gmail.com> (raw)
In-Reply-To: <CAJUtOOh_VSdHr37nmVtTMqBErA5p4dhzpaCS6gGiPowQcms_-Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1686 bytes --]
signed
On Thu, Jun 19, 2025 at 2:09 PM Frantisek Borsik via LibreQoS <
libreqos@lists.bufferbloat.net> wrote:
> Hello to all,
>
> It's my great pleasure to send out this email. Dave's nomination is ready
> to be co-signed *HERE
> <https://docs.google.com/document/d/1hRtD9xE6H9cJGQaKIXHi_f_HpoRNK4-4-lS1ZwYacXU/edit?tab=t.0>*
> (Google Docs).
>
> We are also looking for at least 2 (but the more, the better!) people that
> would be willing to write us letters of recommendation that are needed to
> be attached to the nomination
> <https://wp.apps.internetsociety.org/wp/postel-award/nomination-form/>.
>
> I'm please to announce, that Vint Cerf will be a nominal nominator and we
> all know that Dave will appreciate it as much as we all do!
>
> Looking forward to see co-signees pouring in, as well as volunteers
> willing to write the letter.
>
> *We need to submit it ASAP, the deadline for the nomination is July 11.*
>
> Thank you very much.
>
> PS: In order to learn more about the award, please visit its website
> <https://www.internetsociety.org/grants-and-awards/postel-service-award/#timeline>
> .
>
> All the best,
>
> Frank
>
> Frantisek (Frank) Borsik
>
>
> *In loving memory of Dave Täht: *1965-2025
>
> https://libreqos.io/2025/04/01/in-loving-memory-of-dave/
>
>
> https://www.linkedin.com/in/frantisekborsik
>
> Signal, Telegram, WhatsApp: +421919416714
>
> iMessage, mobile: +420775230885
>
> Skype: casioa5302ca
>
> frantisek.borsik@gmail.com
> _______________________________________________
> LibreQoS mailing list
> LibreQoS@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/libreqos
>
[-- Attachment #2: Type: text/html, Size: 3712 bytes --]
next prev parent reply other threads:[~2025-06-19 22:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-19 19:46 [Rpm] " Frantisek Borsik
2025-06-19 22:25 ` dan [this message]
2025-06-22 18:36 ` [Rpm] [Codel] " Roger Jørgensen
2025-06-25 22:26 ` [Rpm] [L4s-discuss] " Jón Ingi Ingimundarson
2025-07-02 21:31 ` [Rpm] " Frantisek Borsik
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/rpm.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAA_JP8X31acErGTjKWgmWP3QED2P7kL=V-CeqMsXKgbo6VhWCA@mail.gmail.com' \
--to=dandenson@gmail.com \
--cc=bloat-ietf@lists.bufferbloat.net \
--cc=bloat@lists.bufferbloat.net \
--cc=cake@lists.bufferbloat.net \
--cc=codel@lists.bufferbloat.net \
--cc=frantisek.borsik@gmail.com \
--cc=hwolverson@libreqos.io \
--cc=l4s-discuss@ietf.org \
--cc=libreqos@lists.bufferbloat.net \
--cc=robert@libreqos.io \
--cc=rpm@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