You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: report_2023.txt
+250Lines changed: 250 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -4,6 +4,256 @@ ref: report 2023
4
4
lang: en
5
5
---
6
6
7
+
## 2023-12-02 PROJECT MEETING
8
+
9
+
*Saturday the 2th of December 2023 at 13:00 UTC (14:00 CET, 10:00 ART).*
10
+
11
+
Time: 13:00-14:16 UTC
12
+
13
+
**People:** Cri, Chris
14
+
15
+
Welcome Chris, he is a Linux System Administrator from Minnesota, U.S.A
16
+
Cri shared documentation from antennine network
17
+
18
+
### Website
19
+
20
+
we have the possibility to keep the same structure of the old website: jeckyll + ascii-doc but with a different theme: this is good because the content input can be txt file, and we reuse txt file to put the doc in the firmware and be readable by browser.
21
+
22
+
Cris: I'm happy that we keep the old habits about the structure oof the content, but with this restyl we move in a more fashionable shape. And I think is motivating also to update the documentation :) that probably the next work that we have to do... for the new year
23
+
Chris: I think the new theme looks nice. (But I am not a designer)
24
+
25
+
From this assembly the opinion looks positive to the merge of the "new restyle" of the website. we wait a week to see reaction in mailinglist, and after I(Cris) can accept merge request.
26
+
27
+
### Testing
28
+
29
+
two people answered to this call https://lists.autistici.org/message/20231101.163202.5a0742ed.en.html
30
+
I, Cris, think that both are trustable people.. I expected that some of them come to this meeting, but this not happen.
31
+
32
+
Scenarios to check:
33
+
34
+
* checking if the internet connection internet1 goes down, if the wifi
35
+
clients (common AP name) still have connection
36
+
* checking if the internet connection internet2 goes down, if the wifi
37
+
clients (common AP name) still have connection
38
+
* checking if the internet connection internet1 goes down, if the cabled
39
+
clients (on dual_band#2) still have connection
40
+
* checking if the internet connection internet2 goes down, if the cabled
41
+
clients (on dual_band#2) still have connection
42
+
* checking roaming, e.g. with an audio call
43
+
* define exactly how router wire to router is connected: LAN to LAN with
Pony proposal and devices: https://lists.autistici.org/message/20231126.160655.2b35dc1f.en.html
48
+
Cris: good point that the devices are with DSA.. not clear "None of them are running babeld though" and not clear if this is give problem to test, for example the first 2 scenarios:
Cris: Good point is that can have a test in a real infrastructure. I would like know if the devices are with DSA or not..
52
+
53
+
we can wait answer in the mailinglist, if is present DSA on the devices is better to test because is one of the new feature present in openwrt23 and 23.
we just introduced the topics.. we are happy to listen proposals in the next weeks in the mailinglist.
64
+
the last year with the opportunity and money (circa 3k euro) from th GSoC we wrote Ansible roles to automated the build of the Libremesh release candidate. and this was really good for the Libremesh project.
65
+
So lets go to think something of improving for the next year. The work will be done in summer 2024 and we need also 2 people that apply as Mentor.
66
+
we can propose probably 2 projects.. but all the year depend from freifunk and google how many project can be really realized.
67
+
68
+
Topics:
69
+
* Assign the work-grant for testing the release candidate
70
+
* Website restyling, e.g. https://libremesh.antennine.campiinrete.org
71
+
* Next release name
72
+
* GSoC2024
73
+
74
+
## 2023-11-01 PROJECT MEETING
75
+
76
+
*Wednesday the 1st of November 2023 at 13:00 UTC (14:00 CET, 10:00 ART).*
77
+
78
+
**People**
79
+
80
+
SAn, Ilario, Ger, Cri, Gothos, Maden
81
+
82
+
**Topics**
83
+
84
+
* How to use donations (buying hardware?)
85
+
* News about Altermundi roadmap 2023
86
+
* Where to store the log of the meetings
87
+
* OpenWrt 22 or OpenWrt 23 as a base for the next release candidate?
88
+
* Outdated release server
89
+
* Free discussion about other projects and LibreMesh
90
+
* Firmware signatures
91
+
* Next meeting
92
+
93
+
94
+
Past meeting topics:
95
+
* news
96
+
* website and documentation update
97
+
* need of a Docker image for unit testing on OpenWrt 22.03
98
+
* decide the list of targets for being compiled for release 2020.2 based on OpenWrt 19.07
99
+
* upcoming release LibreMesh 2020.2
100
+
* News about Altermundi roadmap 2023 ?
101
+
* how to use the donations on OpenCollective (e.g. a compilation server, or donation to Battlemesh) https://opencollective.com/libremesh
102
+
* news about battlemesh
103
+
* next meetings dates
104
+
* resume of previous technical meetings and announcement of next technical meeting date
105
+
for the next TECH meeting:
106
+
* proposal: move the report in the wiki of github? another wiki? what is thi?https://gitlab.com/libremesh
107
+
* Check that issues and the label is:issue is:open label:"in progress" is actulized
* future release LibreMesh 2023.1 (based on openwrt-22.03)
110
+
* prioritise a list of issues to be resolved for the next LibreMesh 2023.1 release based on OpenWrt 22.03 https://github.com/orgs/libremesh/projects/3/views/1
111
+
* decide a list of packages to be included in next LibreMesh 2023.1 https://github.com/libremesh/libremesh.github.io/issues/103
112
+
* This question from Elektra during past tech meeting: - How are people porting new devices?
* internet1 and internet2 should preferably be two different internet connections, but if they are the same it is ok
171
+
172
+
Physical setup requirements:
173
+
* none, even if all the routers are on the same table it is ok
174
+
* wifi channels have to be selected for avoiding wifi connections between routers that are not indicated as connected (i.e. dual_band#1 and dual_band#2 should be on the same channels. single_band#1 and single_band#2 should be on the same channel, but a different one from the one used by the dual band routers)
175
+
176
+
Scenarios to check:
177
+
178
+
* checking if the internet connection internet1 goes down, if the wifi clients (common AP name) still have connection
179
+
* checking if the internet connection internet2 goes down, if the wifi clients (common AP name) still have connection
180
+
* checking if the internet connection internet1 goes down, if the cabled clients (on dual_band#2) still have connection
181
+
* checking if the internet connection internet2 goes down, if the cabled clients (on dual_band#2) still have connection
182
+
* checking roaming, e.g. with an audio call
183
+
* define exactly how router wire to router is connected: LAN to LAN with mesh configuration e.g. https://github.com/libremesh/network-profiles/tree/master/calafou#lime-community-configuration-3
184
+
185
+
Additional tasks:
186
+
187
+
* document how to set ethernet interfaces for mesh only or clients only
188
+
189
+
### News about Altermundi roadmap 2023
190
+
191
+
Cri asked in the ML
192
+
SAn answered that is working in the hardware of LibreRouter2
193
+
194
+
### Where to store the log of the meetings
195
+
196
+
ML is ok
197
+
Website also ok (the archive of the ML is public anyway, so public is ok)
198
+
Cri will copy the info to the website
199
+
200
+
### OpenWrt 22 or OpenWrt 23 as a base for the next release candidate?
201
+
Currently, the release candidate 2023.1 is based on OpenWrt 22
202
+
203
+
Ilario: 23
204
+
SAn: 23
205
+
Madez: 23
206
+
Cri: 22 or 23 are ok
207
+
Gothos: 23
208
+
209
+
Ilario: let's name the new release candidate 2024.1-rc1
210
+
211
+
SCENARIO ESISTENTE:
212
+
213
+
rete mista openwrt & libremesh, feedback that the developing of libremesh is not enought fast as openwrt to releasing. Which relation there is with gluon? and which different?
0 commit comments