lb:organization:chaosmeetings:2026:cm-2026-05

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
lb:organization:chaosmeetings:2026:cm-2026-05 [2026/04/13 18:43] – orimpelb:organization:chaosmeetings:2026:cm-2026-05 [2026/04/17 12:24] (current) – add links for logo xbr
Line 1: Line 1:
-====== ChaosMeeting 2026/04 ======+====== ChaosMeeting 2026/05 ======
  
 ^ Date                               | 13/04/2026                                          | ^ Date                               | 13/04/2026                                          |
 ^ Time                               | 20:00                                               | ^ Time                               | 20:00                                               |
 ^ Location                           | [[:chaosstuff|ChaosStuff]] / [[services:nextcloud]] | ^ Location                           | [[:chaosstuff|ChaosStuff]] / [[services:nextcloud]] |
-^ Administrative Council Attendees:  | [[user:virii]], [[user:orimpe]]       | +^ Administrative Council Attendees:  | [[user:virii]], [[user:orimpe]], [[user:xbr]]       | 
-^ Minutes Recording                  | [[user:orimpe]]                       |+^ Minutes Recording                  | [[user:xbr]]                                        |
  
 ===== Agenda ===== ===== Agenda =====
Line 11: Line 11:
   * Meshnet   * Meshnet
     * Website     * Website
-    * Handheld nodes ??? did they arrive yet? +    * Logo 
-    * Branding / how to promote/talk about Meshnet+    * Branding - how to frame Meshnet 
 +    * Handheld nodes - did they arrive?
     * Node config: regio Settings     * Node config: regio Settings
- 
  
 ===== Minutes ===== ===== Minutes =====
 +==== Meshnet ====
 +=== Website ===
 +
 +[[user:xbr]] got a skeleton website based on Hugo and the "Blowfish" theme, it's up on [[https://projects.c3l.lu/|projects.c3l.lu (Kallithea)]] under [[https://projects.c3l.lu/freifunk/meshnet/www|freifunk/meshnet/www]].
 +
 +The ''[[https://projects.c3l.lu/freifunk/meshnet/www/files/d3a1e5f71f7c87f0aaca25c837a08a613fc3c70d/README.md|README.md]]'' has documentation regarding how things work, how you can add new pages, ... . The website does not have a lot of text/content yet.
 +
 +Ideally, we should focus on 1 language to write things in, and then have translation done somehow (manual machine translation?), and the translations must also never be out of date.
 +
 +Feel free to start adding content/text to it. There are some skeleton pages for Meshtastic and Meshcore, but we need a common page for Meshnet that explains what the project is about, and most importantly, **what differentiates the subprojects, and how they belong to Meshnet**, which brings us to the following topic.
 +
 +=== Logo ===
 +
 +[[user:orimpe]] made an initial draft logo, we discussed it in [[cm-2026-03|a previous ChaosMeeting (2026/03)]], and [[user:xbr]] reworked it into a vector logo.
 +
 +During this ChaosMeeting we discussed the current logo, and tinkered with multiple variations (e.g. vertical text as [[https://projects.c3l.lu/freifunk/meshnet/artwork/raw/49bbb05fdb2894bd83a6afe39a5f869e6d3824db/verticalLogo-fontasshape.svg|an example Sticker]])
 +
 +They are available on [[https://projects.c3l.lu/|projects.c3l.lu (Kallithea)]] under [[https://projects.c3l.lu/freifunk/meshnet/artwork|freifunk/meshnet/artwork]].
 +
 +=== Branding - how to frame Meshnet ===
 +
 +**Meshnet was a great branding idea** to regroup all of our mesh network efforts.
 +
 +While it may make sense to us, it needs to make sense to people we talk to about this: people that have never heard of **Meshnet, Meshcore, Meshtastic, Freifunk**. Imagine how confused they may be:
 +> "What's what? How do they relate to one another, and why should I care? Is **Mesh**tastic like **Mesh**net, they both start with **Mesh**, unlike Freifunk?"
 +
 +We did some brainstorming on "Why did we make Meshnet? / Why are we interested in (projects)?": what came out of it was that our main interest comes from a **resiliency** perspective.
 +
 +We do trust and use networks every day, be it cellular, coax, fiber, the PSTN, the Internet, but we also know how co-dependent they have become on one another, and how one unrelated software failure can cascade into a whole ISP / Telco being down.
 +
 +It's worth noting that outside, there are other perspectives on this, f.i. preppers find interest in it for their purposes, many radio amateurs like the far-reaching network aspect of it, as it uses the same technology, but develops a solution differently, and some critical infrastructure providers may want to still be able to communicate and organize responses, even when other networks are down.
 +
 +This solves "how to brand Meshnet" but not "how to introduce the subprojects and their differences".
 +
 +=== Handheld nodes - did they arrive? ===
 +
 +Yes they did, [[user:orimpe]] and [[user:virii]] are working on it.
 +
 +We're tending more towards Meshcore nowadays, so some questions have been asked upstream regarding that.
  
 +We probably should approach this like we used to with Freifunk: have a bunch of (models of) nodes in-stock, and we can thus do workshops and sell them.
  
-=== Region scope ==== +=== Region scope === 
-^ Region     ^ Erläuterung ^  +^ Region             ^ Explanation                                              ^  
-| europe | Grundregion ganz Europa |  +| europe             | Base region, the whole of Europa                         |  
-| luxembourg | Das Land Luxemburg | +| luxembourg         | Luxembourg (country)                                     | 
-| saarlorlux | Umfasst: Saarland, Luxembourg, Lorraine, Teile von Rheinland-Pfalz | +| saarlorlux         | Saarland, Luxembourg, Lorraine, Parts of Rheinland-Pfalz | 
-| <del>de-west | Westen Deutschlands</del> ?|+| <del>de-west</del> | <del>West Germany</del> ?                                |
  • lb/organization/chaosmeetings/2026/cm-2026-05.1776098580.txt.gz
  • Last modified: 2026/04/13 18:43
  • by orimpe