[OpenWrt-Devel] Applying to Season of Docs

Paul Spooren mail at aparcar.org
Fri May 1 17:07:08 EDT 2020

Hi all,

Google offers a program[0] to stipend people writing technical documentation for
open source projects. The stipend is possible for anyone 18+ and not living in a
US embargoed country, so unlike the Google Summer of Code project not only for
students. Successful writers get a stipend of about $6000, mentors $500, from my
understanding these stipends are at least in some parts of the world tax free.

So much about the program, question is how OpenWrt could benefit from it. 

* Some time ago there where some ideas on IRC to add development information to
OpenWrt specific tools instead of managing it in the MediaWiki. Articles from
docs/techref[1] could be updated, cleaned and ported to the project
repositories. For example, move the ubus network docs[2] directly to the netifd
repository[3] so developers can update it conveniently when adding new features.
The existing wiki would then point to an online rendered version of such docs.
Using a tool like mkdocs(.org) allows to create documentation websites based on
Markdown with minimal dependencies (Python3, pip3, venv).

* Device pages, important for users, are often very similar but still vary in
steps and formulation, increasing the work of maintaining them. Also the varying
structure complicates the user. Personally I really like the template based
LineageOS device wiki[4] as it's the same structure for every device but still
covers corner cases or important notes. Some time ago I created a proof-of-
concept which could be an inspiration for further work[5]. For prioritization a
a ranking of popular wiki pages could be used, which devices are most commonly

* The wiki offers guides on how to use the LuCI for common use cases, which is
great because it's the most likely way for basic users to interact with OpenWrt.
However this could get some extra love: Partly pictures are missing[6], pictures
are outdated[7] and/or missing from the web interface overview[8]. This could be
refreshed and put in nice overview, maybe even even create click-through videos.
There must be tools that automatically click things in UIs and make screenshots,
this could make the documentation easily future proof and translatable.
A prioritization and general collaboration could happen with the participants of
the '"simplified" interface for LuCI'[9] thread. 

I'd be happy to either be a mentor or writer. Hopefully some more people are
interested in this efforts!

A first step is the application to make OpenWrt a SoD project. If approved I can
(try to) handle the paperwork. The deadline is 4th of May, sorry for the short


[0]: https://developers.google.com/season-of-docs/
[1]: https://openwrt.org/docs/techref/start
[2]: https://openwrt.org/docs/guide-developer/ubus/network
[3]: https://git.openwrt.org/?p=project/netifd.git;a=summary
[4]: https://wiki.lineageos.org/devices/peach
[5]: https://aparcar.github.io/openwrt-devices/devices/tp-link_tl-wdr4300/
[8]: https://openwrt.org/docs/guide-user/luci/start
[9]: https://lists.infradead.org/pipermail/openwrt-adm/2020-April/001368.html

openwrt-devel mailing list
openwrt-devel at lists.openwrt.org

More information about the openwrt-devel mailing list