[Proposal] Static machine-readable export of OpenWrt wiki content
Ivan Rainbolt
openwrt-devel at membership.list.ivanthegeek.com
Mon Aug 31 04:58:04 PDT 2026
What is the point of this reply?
Did I work through the idea using AI? Yes.
Did I craft the email using AI assistance? Yes.
Did AI help me in figuring out the LED lighting issue on a Cudy WR3000P v1 router? Yes - https://github.com/openwrt/openwrt/pull/24913
Did AI help me create that PR and get it to conform to the desired state wanted by maintainers? Yes.
Did OpenWRT use AI to evaluate,triage, and confirm conformance and merge ability? Yes.
Did AI help me create the new wiki page for the Cudy WR3000P v1 device? Yes - https://openwrt.org/toh/cudy/wr3000p_v1
Did I review and direct all activities? Yes.
Spell check is tool. AI is also, just a more involved one.
The recent need to block bots/scrapers from the wiki and forum seems an even more valid reason for this proposal. There is tremendous knowledge, time, effort, and answers contained in the Wiki prose and the forum also. Pointing a local search indexer or AI at that corpus gains enormous productivity and accuracy. Having local copies makes that process better for both me (or any user) and for reduced serving requirements of OpenWRT. The toh.json is a prime example and usage of that. The email archives of this exact mailing list is another.
Regardless of AI involvement, my proposal is still valid. My resolve to solve the problem is still valid. My offer to work a plan and put the effort in to make it happen is still valid. The benefit of the implementation is still valid. The issue is a matter of those who "control" the sources and a proper implementation to access and process those sources in a resonable and efficient way is where the buy in needed. Hence the proposal. All still valid regardless of the tools used to produce it and in honesty is a much more coherent proposal email than I would have crafted without the AI help.
IvanTheGeek
More information about the openwrt-devel
mailing list