OpenWrt meeting November 2024 November 27

Hi, we had another meeting, please find the meeting notes below, in the wiki[1] or in the
forum[2].

[1]: https://openwrt.org/meetings/20241126
[2]: https://forum.openwrt.org/t/openwrt-meeting-november-2024...

Please have a nice day,
Paul

## OpenWrt One Status Update

- The platform now supports running Doom.
- Available for purchase on AliExpress.
- Anticipated availability in the United States soon.

## APK Transition

- For APK-related pull requests, please refer to: [APK Pull
Requests](https://github.com/openwrt/openwrt/pulls?q=is%3Apr+is%3Ao...).
- For APK-related issues, please visit: [APK
Issues](https://github.com/openwrt/openwrt/issues?q=is%3Aissue+is...).
- Proposal to implement a "Message of the Day":
  - Inform users about the transition to APK, emphasizing the new command "apk add" instead of
"opkg install."
  - Paul will provide further details.
- Addressing issues related to ABI version changes: [ABI Version
Changes](https://github.com/openwrt/rpcd/pull/10).
- A wiki transition page will be created:
  - Reference Eric's contributions in the forum: [Forum
Discussion](https://forum.openwrt.org/t/the-future-is-now-opkg-vs-apk...).
- Acknowledgment of feedback regarding the communication of the APK transition:
  - We apologize for any confusion caused.

## Release 24.10

- Discussion on making APK the default package manager:
  - Decision to continue using opkg for the 24.10 release.
- Plan to conduct a release candidate (RC) testing phase in the coming days, led by Hauke.
- Proposal to eliminate the USE_APK configuration option to reduce user confusion.

## Project Milestones and Future Developments

- Focus on APK integration.
- Exploration of Rust support within the core.
- Consideration of LLVM integration in the core.
- Development of a notification system: [Notification System
PR](https://github.com/openwrt/openwrt/pull/13137).
- Discussion on the potential removal of usign and ucert in favor of a unified PKI solution,
possibly utilizing "px5g" as proposed by Felix.
- Increased use of ucode instead of Bash scripts.
- Initiation of a forum thread to gather user feedback, to be managed by Paul.

## OpenWrt Summit Status

- Reference to the potential OpenWrt Summit in Central Europe in March/April: [Summit
Discussion](https://lists.openwrt.org/pipermail/openwrt-adm/2024-June...).
  - Current status indicates that this event may not proceed (Hauke).
  - No response received regarding the status inquiry made on November 7 in Matrix.

## Battlemesh 2025

- Information on Battlemesh V17: [Battlemesh Details](https://battlemesh.org/BattleMeshV17).
- Location: Sundhausen, Thuringia, Germany. [Map
Location](https://www.openstreetmap.org/relation/2903169#map=13/51....).
- Event Dates: June 10-17, 2025.
- Proposal for collaboration with OpenWrt or co-locating an OpenWrt conference.
- Advantages:
  - Opportunity for in-person meetings.
  - Minimal organizational effort required.
- Disadvantages:
  - Remote location with limited nearby accommodations.
  - Potential shuttle service availability.
  - Tent camping options available.
- Support for endorsing Battlemesh.
- Agreement to support travel for OpenWrt developers.
- Paul will initiate a forum thread to discuss the use of donated funds for travel stipends.
- Battlemesh intends to incorporate OpenWrt branding in their marketing, and we are supportive of
this initiative.

## Rust Support in Core

- The kernel is beginning to incorporate components relevant to our needs, particularly in
drivers/net/phy.
- This integration would facilitate better compatibility with projects not utilizing Cargo,
specifically in include/meson.mk.
- Daniel will engage with the Rust community within OpenWrt to encourage contributions to the
core.

## LLVM and Clang Support

- Discussion on including a full host and target build of LLVM and Clang to enhance support for
Rust packages that depend on [rust-bindgen](https://github.com/rust-lang/rust-bindgen).
- This would enable the development of projects utilizing LLVM for JIT compilation on the target,
such as Mesa LLVMPipe, Vulkan drivers, and OpenCL support (intel_clc).
- Ansuel and Paul will investigate a centralized ccache solution to improve build efficiency. If
issues arise with ccache, alternative solutions will be explored.

## Proposal for Compiled Video.git Feed

- We propose the introduction of a weekly or monthly build of the video feed to provide precompiled
binaries. Recent developments include support for local displays, with successful implementations
of Wayland, Mesa (including Vulkan), GTK+4, WPEWebKit, and two ports of Doom. These have been
tested on x86/64 architectures with Intel and AMD GPUs, as well as on ARM using Lima and Panfrost.
Additionally, support has been established for SPI-connected MIPI-DBI displays on devices lacking
dedicated GPU or video interfaces. WPEWebKit can facilitate local displays for applications such as
Grafana, LuCI, or WiFi credentials via QR codes. Given the extensive scope of LLVM, Mesa, and
WebKit, which significantly exceed the lines of code of the rest of OpenWrt combined, it is
advisable not to include these in standard buildbot runs unless we implement CCACHE instances in
each data center.
- Ansuel and Paul will further investigate this proposal.

## Seccomp Support for RISC-V (USE_SECCOMP in procd)

- Daniel will explore the implementation of seccomp support for the RISC-V architecture.

## LoongArch64 Support

- Currently, LoongArch64 is unsupported due to a lack of available hardware for testing.
  - We welcome any hardware donations to facilitate this effort.



Attachment: signature.asc (type=application/pgp-signature)
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEET9u727/azpOjlPU55vUy2S4FSaUFAmdG9lUACgkQ5vUy2S4F
SaVPyRAAmZnJuacPW8jcVLlAxWXJOAGdygJbQGfW5MZTiyKEfoqduK7k0cHWNHxe
R3U0SQ/JKztGfLxOYLloXqdyK5zYRA9K3rvMPrtWdG5AavgvbalsR4FXelIxqNOR
WEjXYw3iM0tVKtaqHL/URX81KhGKSMLZLCAyMR1ktQrFgSQlBD0f5iUkx9UJoJd9
cEVGDbzKR66ZlIRIyijYbe/uBn01U64W7Wt2qqJ6QAf799iayiUduWqPbeY2XgP/
ZA1iGTRCg0PI2RMCabkFvsZEnpYIuwcDbe1RlyAd2gfgMxAXk+3FCNEnP7jXkzQW
i/8vLY0FFramvuOJhCEX0YWA7GYjHZLyYcS0GInJ2rylOAR2icdh4ujhE+5qLLhC
0hx7A7h2baI+ov2lfqell3LcOg8cACGECYiuKfW9m+4697985JQvEPJXWBTDdU10
ZsnjaqbZ1+EYTp6yBUXhyLl/1of68b8MqWeOFZsI0BZmtjjs02lPp1vtukQ3qquj
38lUppqtL79+dhYeoLC0hYb7GwdkXdLl95JZcrcozpyeTochpgBQmSw8LVU1HcVm
LICh9vmrhC/Xhj9MmjdleuaHWeq0QPemB0DsM8/OL5Vjjyk3n00XZdW0SswN0Fgw
GVAZ95Wa3Kc9WjoHPAWpJs5rf+6PHCbieIMr6mt9uOgtdggvtOg=
=Us/T
-----END PGP SIGNATURE-----


Attachment: None (type=text/plain)
_______________________________________________
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel