From ynezz at true.cz Tue Nov 5 01:39:44 2024 From: ynezz at true.cz (Petr =?utf-8?Q?=C5=A0tetiar?=) Date: Tue, 5 Nov 2024 10:39:44 +0100 Subject: Upcoming buildbot and GPG signing changes in snapshots/24.10 Message-ID: <20241105093944.GC97201@meh.true.cz> Hi, just a quick update ? I'll soon be updating Buildbot to the latest version we've been preparing and testing. Here are the notable changes: * preparation for opkg to apk transition (APK not yet enabled) * a single buildmaster container will now handle both phase1 and phase2 buildmasters * for snapshots and the 24.10 release, we will replace the current RSA-4096 key with an Ed25519-based key (0x1D53D1877742E911), supported by a Nitrokey3 dongle[1]. Pending successful testing, this will also apply to the 23.05 release in the near future. 1. https://git.openwrt.org/?p=keyring.git;a=commit;h=6b42a5c8b7dc049b899869b2a1b94daf69ceb2f5 Cheers, Petr From ynezz at true.cz Wed Nov 6 22:46:08 2024 From: ynezz at true.cz (Petr =?utf-8?Q?=C5=A0tetiar?=) Date: Thu, 7 Nov 2024 07:46:08 +0100 Subject: Upcoming buildbot and GPG signing changes in snapshots/24.10 In-Reply-To: <20241105093944.GC97201@meh.true.cz> References: <20241105093944.GC97201@meh.true.cz> Message-ID: <20241107064608.GD97201@meh.true.cz> Petr ?tetiar [2024-11-05 10:39:44]: Hi, > just a quick update ? I'll soon be updating Buildbot to the latest version > we've been preparing and testing. Here are the notable changes: forgot to mention previously: * switch from `master` to `main` branch deployed, openwrt.git already uses `main` branch, feeds not yet > * for snapshots and the 24.10 release, we will replace the > current RSA-4096 key with an Ed25519-based key (0x1D53D1877742E911), > supported by a Nitrokey3 dongle[1]. Pending successful testing, this > will also apply to the 23.05 release in the near future. Seems to be ticking fine, Nitrokey3 reports: 2024-11-07 06:24:43 scdaemon[3798545] signatures created so far: 1845 thus I've just enabled it for 23.05 as well. Cheers, Petr From mail at aparcar.org Thu Nov 7 07:49:27 2024 From: mail at aparcar.org (Paul Spooren) Date: Thu, 7 Nov 2024 16:49:27 +0100 Subject: Travel Stipends for BattleMesh v17? Message-ID: <140D1732-880C-4BE8-9C64-08A2F2BB722E@aparcar.org> Aloha, In the middle of next year is the next round of BattleMesh, which will happen this year in Sundhausen, Germany. Who doesn?t know BattleMesh[1], it?s a get together of (wireless) network enthusiasts and OpenWrt developers. Every year attend people from all over the world and to allow people to do the travel and pay for accommodation, I?d like to ask if OpenWrt as a project would offer travel stipends for OpenWrt developers. If I?m not mistaken, we got some money in our donation fund over at SFC. Last year some stipends were paid to travel to Cypress and attend BattleMesh v16. Do we want to support the next BattleMesh, too? This is not a vote but a question to get the mood. Best, Paul Spooren [1]: https://battlemesh.org/ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: Message signed with OpenPGP URL: From hauke at hauke-m.de Thu Nov 7 12:43:09 2024 From: hauke at hauke-m.de (Hauke Mehrtens) Date: Thu, 7 Nov 2024 21:43:09 +0100 Subject: Travel Stipends for BattleMesh v17? In-Reply-To: <140D1732-880C-4BE8-9C64-08A2F2BB722E@aparcar.org> References: <140D1732-880C-4BE8-9C64-08A2F2BB722E@aparcar.org> Message-ID: On 11/7/24 16:49, Paul Spooren wrote: > Aloha, > > In the middle of next year is the next round of BattleMesh, which will happen this year in Sundhausen, Germany. Who doesn?t know BattleMesh[1], it?s a get together of (wireless) network enthusiasts and OpenWrt developers. > > Every year attend people from all over the world and to allow people to do the travel and pay for accommodation, I?d like to ask if OpenWrt as a project would offer travel stipends for OpenWrt developers. If I?m not mistaken, we got some money in our donation fund over at SFC. Last year some stipends were paid to travel to Cypress and attend BattleMesh v16. Do we want to support the next BattleMesh, too? > > This is not a vote but a question to get the mood. > > Best, > Paul Spooren > > [1]: https://battlemesh.org/ Hi, I think we should pay travel sponsorships for OpenWrt developers going to Battlemesh if we make Battlemesh v17 an official OpenWrt event or do there some sort of gathering. If you want to get sponsorship please follow the SFC travel guideline: https://sfconservancy.org/projects/policies/conservancy-travel-policy.html Hauke