The OpenWrt/LEDE Project relies on the considerable efforts of its volunteer developers, the core documentation team, the forum moderators, and the host of people who're actively using and testing the products. The OpenWrt/LEDE team has also provisioned many physical and virtual servers that “make the OpenWrt (and former LEDE) Project go.”
We run the following services internally to support the OpenWrt project:
|OpenWrt website and documentation||Dokuwiki||Wiki with open registration||DigitalOcean droplet|
|OpenWrt Forum||Discourse||Provides a place for people to ask and answer questions about using OpenWrt, developing it, and other topics||DigitalOcean droplet|
|Git server||gitweb||Primary OpenWrt source code repositories||DigitalOcean droplet|
|Bug tracker||Flyspray||The place where bugs and feature requests are tracked||DigitalOcean droplet|
|?||Handles incoming emails to @openwrt.org domain||DigitalOcean droplet|
|Buildbot master||Buildbot||Coordinates builders||Hetzner|
|Download site||Hosts all current and released images, SDK, Imagebuilder||Hetzner|
|Sources archive||Hosts a copy of sources of all software used in OpenWrt||Hetzner|
|Images archive||Hosts old OpenWrt images and releases||?|
We also rely on the following services that are run by external entities:
|Download CDN||CDN||Alternate download location for images||KeyCDN|
|Sources CDN||CDN||Alternate download location for sources||KeyCDN|
|openwrt-devel mailing list||Mailman||Main medium of communication for developers||infradead|
|openwrt-adm mailing list||Mailman||Main medium of communication for administrative matters||infradead|
|Patch tracking||Patchwork||Used to track patches sent to the openwrt-devel mailing list||Ozlab|
|Github mirror||Github||Mirror of OpenWrt repository. Pull-requests are accepted.||Github|
All services that are managed internally are run on servers devoted to the OpenWrt/LEDE Project.
|Hetzner||3x ex40||buildbot master, downloads||Paid privately|
|DigitalOcean||Many droplets||wiki, forum, git, mails||Free (open source project support)|
|OSUOSL||OpenStack VMs||Free (open source project support)||bjonglez|
There are several buildbot instances: one for master, and one for each release. In addition, there is phase1 to build images, and phase2 to build packages.
Buildbot machines detect updates to the source and kick off the build process for each supported device.
|fsf-dock-*||4x 16C/32T||gcc compile farm / OSUOSL||bjonglez|
There is a private discussion about possibilities of some sort of crowdfunding to allow the community to pay back the core team for their expenses, and fund the project going forward, but there is no public news yet.