Hi OpenThread team,
While reviewing the OpenWrt packaging for ot-br-posix, I noticed that the LuCI frontend files are currently maintained directly within this repository under src/openwrt.
To align with OpenWrt packaging standards and ensure better long-term maintainability, I propose migrating the LuCI application out of the ot-br-posix tree and submitting it directly to the official openwrt/luci repository.
It helps:
-
For treewide maintenance: The OpenWrt LuCI framework frequently undergoes API changes and migrations (e.g., client-side rendering updates, JS refactoring). When LuCI applications are hosted in the central openwrt/luci repository, core maintainers automatically update them during treewide changes. Out-of-tree apps often break because they miss these automated refactors.
-
Separation of concerns: Decoupling the web UI (luci-app-openthread-br) from the core daemon package (openthread-br) simplifies the OpenWrt Makefile structure. It allows the core networking package to be maintained and built completely independently of the web interface framework.
-
Standardized workflow: Moving the UI upstream aligns with how the vast majority of OpenWrt web interfaces are handled. This makes it easier for the broader OpenWrt community to contribute, review, and manage translations via standard infrastructure.
Hi OpenThread team,
While reviewing the OpenWrt packaging for ot-br-posix, I noticed that the LuCI frontend files are currently maintained directly within this repository under src/openwrt.
To align with OpenWrt packaging standards and ensure better long-term maintainability, I propose migrating the LuCI application out of the ot-br-posix tree and submitting it directly to the official openwrt/luci repository.
It helps:
For treewide maintenance: The OpenWrt LuCI framework frequently undergoes API changes and migrations (e.g., client-side rendering updates, JS refactoring). When LuCI applications are hosted in the central openwrt/luci repository, core maintainers automatically update them during treewide changes. Out-of-tree apps often break because they miss these automated refactors.
Separation of concerns: Decoupling the web UI (luci-app-openthread-br) from the core daemon package (openthread-br) simplifies the OpenWrt Makefile structure. It allows the core networking package to be maintained and built completely independently of the web interface framework.
Standardized workflow: Moving the UI upstream aligns with how the vast majority of OpenWrt web interfaces are handled. This makes it easier for the broader OpenWrt community to contribute, review, and manage translations via standard infrastructure.