From: Dave Taht <dave.taht@gmail.com>
To: Make-Wifi-fast <make-wifi-fast@lists.bufferbloat.net>
Subject: [Make-wifi-fast] Fwd: [Battlemesh] Call for Participation - Wireless Battlemesh 2022
Date: Wed, 6 Jul 2022 08:19:16 -0700 [thread overview]
Message-ID: <CAA93jw53yx+Svh7JvHGDA3XcwEL54uL8EXPJcuBUDfjgGfgZ1g@mail.gmail.com> (raw)
In-Reply-To: <5d985197-5e83-832d-43ed-1ebb2286891f@gmx.at>
Anyone from here going?
---------- Forwarded message ---------
From: Paul Fuxjäger <paul.fuxjaeger@gmx.at>
Date: Thu, Jun 30, 2022 at 6:03 AM
Subject: [Battlemesh] Call for Participation - Wireless Battlemesh 2022
To: <battlemesh@ml.ninux.org>
Are you also tired of "yet another online meeting"?
You cannot wait to actually MEET fellow network enthusiasts and
activists again?
Then join us at Wireless Battlemesh v14!
https://www.battlemesh.org/BattleMeshV14
We will get physical in an unsually well lit, ventilated hackerspace in
beautiful Rome: The Fusolab. For a few intensive days in late September,
we will turn that place into a FUSIONLab around a variety of topics:
- Wireless Community Networks
- Mesh Routing Protocol Development
- Free hardware and free software for Community Networks
- Community Networks that deploy Fiber-to-the-Home (FTTH) networks
- TV white space as a precious network resource (radio spectrum)
- How to organize a durable community structure?
- How to involve non-technical people? To "digital stewardship" and beyond?
- How to disseminate the spirit of community networks, knowledge etc?
- Connecting rural areas: challenges and solutions
- Public fiber networks: architecture, funding, private actors involved,
oversight
- Internet of Things (IoT) networks and their impact on society
- Local Internet Exchange Points (IXPs) as a common infrastructure
To submit your draft proposal, please send a short mail to v14 AT
battlemesh.org based on this template:
Subject: Event proposal
Topic: [......]
Name/Nick: [......]
Type of event: [hackathon / talk / workshop / panel discussion / other]
Duration: [e.g. 30 min or 1h for talks]
Preferred Date: [ 19 / 20 / 21 / 22 ]
(Optional) Affiliations: [community, country, employer...]
Summary: [couple of sentences on the planned content]
thanks for forwarding/syndicating this call faar and wiide!
Your sincerely,
WBMv14 Org Team
_______________________________________________
Battlemesh mailing list
Battlemesh@ml.ninux.org
https://ml.ninux.org/mailman/listinfo/battlemesh
--
FQ World Domination pending: https://blog.cerowrt.org/post/state_of_fq_codel/
Dave Täht CEO, TekLibre, LLC
parent reply other threads:[~2022-07-06 15:19 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <5d985197-5e83-832d-43ed-1ebb2286891f@gmx.at>]
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/make-wifi-fast.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAA93jw53yx+Svh7JvHGDA3XcwEL54uL8EXPJcuBUDfjgGfgZ1g@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=make-wifi-fast@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