Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision Next revisionBoth sides next revision | ||
| meetings:hamburg2019:start [2019/07/05 15:32] – converted notes from chaospad ynezz | meetings:hamburg2019:start [2020/02/06 19:05] – [Wiki style refresh] Issue with bootstrap theme is finally fixed tmomas | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== Hamburg 2019 ====== | ====== Hamburg 2019 ====== | ||
| + | |||
| + | {{: | ||
| + | |||
| + | * happened from **June 9th** to **June 12th** at amazing place called [[http:// | ||
| + | * **attendees (alphabetical order):** aparcar, dangole, Hauke, jow, ldir, lynxis, neoraider, | ||
| + | |||
| + | ===== Agenda preparation ===== | ||
| + | |||
| + | {{: | ||
| + | |||
| + | * on Monday morning, anyone attending the meeting wrote down arbitrary number of topics to the paper cards | ||
| + | * we've then put those cards on the two boards, merging similar topics together | ||
| + | * as there were a lot of topics, we needed to prioritize, so each attendee got five pins, each of those pins represented one vote, topics with most pins(votes) were discussed first | ||
| + | * topics with no votes were discussed with a soft timer, 6 minutes dedicated to each topic, time was extended as needed | ||
| + | |||
| + | {{: | ||
| ===== Statistics ===== | ===== Statistics ===== | ||
| Line 8: | Line 24: | ||
| * Give users something in return: notification about new firmware version availability | * Give users something in return: notification about new firmware version availability | ||
| - | * Combine it with "unattended sysupgrade server" | + | * Combine it with the [[https:// |
| ==== Problems ==== | ==== Problems ==== | ||
| Line 28: | Line 44: | ||
| ===== 19.07 release and future releases ===== | ===== 19.07 release and future releases ===== | ||
| + | On Monday, June 10th at around 21:33 CEST, after a short pizza & beer session, lynxis has branched awaited openwrt-19.07. | ||
| + | |||
| + | {{: | ||
| ==== What's the problem of releases? ==== | ==== What's the problem of releases? ==== | ||
| Line 43: | Line 62: | ||
| * We have to take care of ABI stability | * We have to take care of ABI stability | ||
| * How do we handle CVEs? | * How do we handle CVEs? | ||
| - | * TODO: create shared library versions for libubox | + | |
| ==== Decisions ==== | ==== Decisions ==== | ||
| * 6 month release cycle (+ 6 months from date of creating release branch) - "no matter what" approach | * 6 month release cycle (+ 6 months from date of creating release branch) - "no matter what" approach | ||
| - | | + | |
| * Point release cycle: | * Point release cycle: | ||
| - | | + | |
| - | * CVE and/or other security fixes ASAP | + | * CVE and/or other security fixes ASAP |
| ===== 4 MB / 32 MB devices ===== | ===== 4 MB / 32 MB devices ===== | ||
| Line 59: | Line 78: | ||
| * There are ways to reduce the image size, but most are hacky and not meant to be enabled by default. Same for memory footprint. | * There are ways to reduce the image size, but most are hacky and not meant to be enabled by default. Same for memory footprint. | ||
| * Don't use kmod, compile them in (saves memory) | * Don't use kmod, compile them in (saves memory) | ||
| + | * There is some working proof of concept in Gluon already (add link?) | ||
| * Remove opkg | * Remove opkg | ||
| * Under memory pressure, squashfs can run into an " | * Under memory pressure, squashfs can run into an " | ||
| Line 65: | Line 85: | ||
| * Custom, OpenWrt bootloader | * Custom, OpenWrt bootloader | ||
| * We will need more space for certain things. e.g. kernel size will increase. But also for hostapd/ | * We will need more space for certain things. e.g. kernel size will increase. But also for hostapd/ | ||
| - | * Should we add config option like `CONFIG_TARGET_BUILD_IMAGE_MIN_SIZE=3900k` which would allow us to filter out (using check-size? | + | * Should we add config option like '' |
| ==== Decisions ==== | ==== Decisions ==== | ||
| Line 77: | Line 97: | ||
| * News: create a news to say 19.07 will be the last official release supporting 4 MB. Explain why it should not supported. We will merge the 4MB devices into code base, but no longer build images (neither snapshots nor releases) - people will be able to adjust custom builds to fit the image in flash | * News: create a news to say 19.07 will be the last official release supporting 4 MB. Explain why it should not supported. We will merge the 4MB devices into code base, but no longer build images (neither snapshots nor releases) - people will be able to adjust custom builds to fit the image in flash | ||
| - | * Wiki: show a banner in the wiki, DO NOT BUY THOSE DEVICES | + | * <del>Wiki: show a banner in the wiki, DO NOT BUY THOSE DEVICES |
| + | * done, [[meta: | ||
| * How to mark 4MB devices in codebase, use " | * How to mark 4MB devices in codebase, use " | ||
| - | * [VOTE] do a vote this release is the last one for 4MB devices | + | |
| ===== CI and other automatic testing ===== | ===== CI and other automatic testing ===== | ||
| Line 92: | Line 113: | ||
| ===== Defragmentation of Code and Tools ===== | ===== Defragmentation of Code and Tools ===== | ||
| - | * Evaluate GitLab as a replacement for git.openwrt.org, | + | * Evaluate GitLab as a replacement for git.openwrt.org, |
| - | * we' | + | * We have received a positive reference from h01ger, a Debian developer: they have switched to GitLab from SourceForge and are quite satisfied |
| + | * See [[https:// | ||
| * Would still support patches via E-Mail | * Would still support patches via E-Mail | ||
| - | * Replace FlySpray with the GitLab issue tracker which is tighly | + | * Replace FlySpray with the GitLab issue tracker which is tightly |
| ==== TODO ==== | ==== TODO ==== | ||
| - | * instead | + | * Instead |
| ===== New People ===== | ===== New People ===== | ||
| - | * Annouce | + | * Announce |
| * Core members should be more direct with asking new people to join the team | * Core members should be more direct with asking new people to join the team | ||
| * Paul aka aparcar requested to become a member | * Paul aka aparcar requested to become a member | ||
| * richb-hanover to write draft note to send to inactive members <done - see below> | * richb-hanover to write draft note to send to inactive members <done - see below> | ||
| - | * motivate | + | * Motivate |
| ==== TODO ==== | ==== TODO ==== | ||
| - | * [VOTE] pepe2k, | + | |
| + | * < | ||
| ===== Stable discussion ===== | ===== Stable discussion ===== | ||
| - | * have a specific list of CVE and packages for one release. (similiar | + | * Have a specific list of CVE and packages for one release (similar |
| - | * have a security | + | * Have a security |
| - | * or use a general announcement | + | * Or use a general announcement |
| - | * who is doing the security mailinglist? | + | * Do a minimal supported time |
| - | * do a minimal supported time | + | * Extended life is another story, we could do the Debian LTS approach if someone |
| - | * Extended life is another story. we might could do the Debian LTS approach if someone | + | * We agree on stable releases |
| - | * we agree on stable releases | + | * We do not agree how much stable releases we should maintain |
| - | * we do not agree how much stable releases we should maintain | + | * Just 2 (current and previous) or more (maybe 3 which should result in ~1 year time span assuming 6-months release cycle)? |
| - | * Supported scope is unclear? (core packages, package feed, kernel) | + | * Supported scope is unclear (core packages, package feed, kernel)? |
| - | * different | + | * Different |
| ==== TODO ==== | ==== TODO ==== | ||
| - | * a mail should be created with the differnt opineons | + | * A mail should be created with the different opinions |
| - | * include | + | * Include |
| + | * Who is doing the security mailing list? (lynxis volounteer) | ||
| ===== Package maintainer ===== | ===== Package maintainer ===== | ||
| - | * create | + | * Create |
| - | * use those maintainer tools to know which package | + | * Use those maintainer tools to know which package |
| - | * use those maintainer tools to nicely ask our maintainers to tell them, you're missing the following things. | + | * Use those maintainer tools to nicely ask our maintainers to tell them, you're missing the following things |
| - | * document | + | * Document |
| ===== Deprecated packages ===== | ===== Deprecated packages ===== | ||
| - | * can we update old base packages? e.g. we have json-c which is outdated. | + | * Can we update old base packages |
| - | * size might be a quality metric | + | * Size might be a quality metric |
| - | * we care of size | + | * We care of size |
| - | * we should include size increase of the binaries and packages | + | * We should include size increase of the binaries and packages |
| ==== TODO ==== | ==== TODO ==== | ||
| - | * neoraider | + | * < |
| + | * [[https:// | ||
| ===== Online Image Builder ===== | ===== Online Image Builder ===== | ||
| - | * currently | + | * Currently |
| - | * nice to have | + | * Nice to have |
| - | * good for new users | + | * Good for new users |
| - | * make it official | + | * It might need 1 to 2 months |
| - | * it might need 1 to 2 month until it's ready | + | * Don't allow to remove core packages |
| - | * don't allow to remove core packages | + | |
| * How to reproduce the image? | * How to reproduce the image? | ||
| + | * **TODO:** Make it official when it's ready | ||
| ===== prpl Relationship ===== | ===== prpl Relationship ===== | ||
| - | * they could fund release maintainership | + | * They could fund release maintainership |
| - | * we need to present to them what the OpenWrt community actually needs | + | * [[https:// |
| - | * use them as a communication channel to industry players | + | * We need to present to them what the OpenWrt community actually needs |
| - | * https:// | + | * Use them as a communication channel to industry players |
| ===== Reproducible Builds ===== | ===== Reproducible Builds ===== | ||
| - | * how to do .buildinfo files in OpenWrt? | + | * How to do .buildinfo files in OpenWrt? |
| - | * h01ger is fine we're using e.g. debian | + | * h01ger is fine we're using e.g. Debian |
| - | * we can reproduce our toolchain based on a commit | + | * We can reproduce our toolchain based on a commit |
| - | * how can we make reproducible-builds.org? | + | * How can we make reproducible-builds.org? |
| * buildinfo toolchain to describe openwrt.org | * buildinfo toolchain to describe openwrt.org | ||
| - | * how to supply buildinfo files for packages? | + | * How to supply buildinfo files for packages? |
| ==== We need to recreate the same toolchains ==== | ==== We need to recreate the same toolchains ==== | ||
| - | * create | + | * Create |
| - | * create | + | * Create |
| ==== Useful documentation related to .buildinfo files ==== | ==== Useful documentation related to .buildinfo files ==== | ||
| Line 191: | Line 215: | ||
| ===== Remaining of lede-project merge? ===== | ===== Remaining of lede-project merge? ===== | ||
| - | * openwrt irc channel | + | * OpenWrt IRC channel |
| - | * how to handle mail aliases? | + | * How to handle mail aliases? |
| * How to handle contact@openwrt.org? | * How to handle contact@openwrt.org? | ||
| - | * jow will create an imap mailbox/ | + | |
| * This allows us to respond with an official @openwrt.org address | * This allows us to respond with an official @openwrt.org address | ||
| - | * paul and richb will come up with further process steps for handling this address | + | |
| - | * create | + | * **TODO:** Create |
| ===== Social things ===== | ===== Social things ===== | ||
| Line 203: | Line 227: | ||
| * How do we handle social media foo? | * How do we handle social media foo? | ||
| * Do we want to use big companies platform instead of open source? | * Do we want to use big companies platform instead of open source? | ||
| - | * Could we find someone inside the community who would like to become a "PR manager" | + | * Could we find someone inside the community who would like to become a "PR manager" |
| * How could we allow adding of the news content? | * How could we allow adding of the news content? | ||
| - | * could we have for example some repository where we could accept ideas for the news? | + | * Could we have for example some repository where we could accept ideas for the news? |
| - | * facebook | + | * Facebook |
| - | + | * Twitter? | |
| - | * use twitter alternative (mastadon) ? | + | * Use twitter alternative ([[https:// |
| ===== Library versioning ===== | ===== Library versioning ===== | ||
| - | * create | + | * Create |
| - | * like branching, just do it. | + | * Like branching, just do it |
| - | * add source package name to opkg metadata in order to be able to parse the ABI version properly | + | * Add source package name to opkg metadata in order to be able to parse the ABI version properly |
| ===== Signing of sysupgrade images ===== | ===== Signing of sysupgrade images ===== | ||
| - | * merge PR which adds support for REQUIRED_SIGNATURE | + | * Merge PR which adds support for '' |
| - | * make signing of sysupgrade images working on the buildbots | + | * Make signing of sysupgrade images working on the buildbots |
| - | * enable | + | * Enable '' |
| ===== Create a manual ===== | ===== Create a manual ===== | ||
| - | * document | + | * Document |
| - | * targeted | + | * Targeted |
| - | * respin https:// | + | * respin |
| - | * https:// | + | * [[https:// |
| ==== TODO ==== | ==== TODO ==== | ||
| Line 235: | Line 259: | ||
| ===== Switch to next stable kernel 4.19 ===== | ===== Switch to next stable kernel 4.19 ===== | ||
| - | * enable | + | * Enable |
| - | * in order to encourage focus on ath79 and to make the transition period more easier for the downstream projects were not going to remove ar71xx from the tree yet, but we will mark the target as " | + | * In order to encourage focus on ath79 and to make the transition period more easier for the downstream projects were not going to remove ar71xx from the tree yet, but we will mark the target as " |
| ===== Switch to nftables ===== | ===== Switch to nftables ===== | ||
| - | * create | + | * Create |
| - | * later it could be optimized, CLI tools could be replaced with libnftables | + | * Later it could be optimized, CLI tools could be replaced with libnftables |
| ===== LuCI translations ===== | ===== LuCI translations ===== | ||
| - | * try to find out some online service used by other open source projects | + | * Try to find out some online service used by other open source projects |
| ===== LuCI future ===== | ===== LuCI future ===== | ||
| * rpcd based, less Lua code on the backend, shell script based middle layer | * rpcd based, less Lua code on the backend, shell script based middle layer | ||
| - | * document | + | * Document |
| - | * consider | + | * Consider |
| - | * provide | + | * Provide |
| - | * should | + | * Should |
| ===== Review base packages ===== | ===== Review base packages ===== | ||
| - | * define | + | * Define |
| - | * do we really need packages like for example OpenVPN or Wireguard in the master tree? | + | * Do we really need packages like for example OpenVPN or Wireguard in the master tree? |
| - | * there might be other packages as well which could be probably moved into the packages feed | + | * There might be other packages as well which could be probably moved into the packages feed |
| ===== Approach routing feed ===== | ===== Approach routing feed ===== | ||
| - | * basically | + | * Basically |
| - | * a lot of lingering PRs and issues some of them for more then 4 years | + | * A lot of lingering PRs and issues some of them for more then 4 years |
| ==== TODO ==== | ==== TODO ==== | ||
| - | * approach | + | * < |
| - | + | * aparcar (paul) has [[https://github.com/openwrt/ | |
| - | ===== Refresh corporate^Wproject identity ===== | + | |
| - | + | ||
| - | | + | |
| - | * refresh logo, provide official vector version usable on stickers, t-shirts etc. | + | |
| - | * project color guidelines etc. | + | |
| ===== New table of hardware (TOH) ===== | ===== New table of hardware (TOH) ===== | ||
| - | * start adding RAM variable along the IMAGE_SIZE to the image Makefile | + | * Start adding RAM variable along the IMAGE_SIZE to the image Makefiles |
| - | * (TODO: add the reason for this need) | + | * (**TODO:** add the reason for this need) |
| * YAML based TOH in the tree, should be part of the patch which adds new device to the tree, which should replace current mandatory description of the device/ | * YAML based TOH in the tree, should be part of the patch which adds new device to the tree, which should replace current mandatory description of the device/ | ||
| - | * provide | + | * **TODO:** Provide |
| ===== The OpenWrt Unfair Advantage ===== | ===== The OpenWrt Unfair Advantage ===== | ||
| Line 292: | Line 311: | ||
| * OpenWrt is available on eleventy-seven architectures supporting dozens of variations | * OpenWrt is available on eleventy-seven architectures supporting dozens of variations | ||
| * OpenWrt currently supports over a bazillion different products | * OpenWrt currently supports over a bazillion different products | ||
| - | * The OpenWrt team consists of lots and lots of core developers, with a bunch more package | + | * The OpenWrt team consists of lots and lots of core developers, with a bunch more package |
| * The OpenWrt development environment rebuilds the full code body every night for every architecture, | * The OpenWrt development environment rebuilds the full code body every night for every architecture, | ||
| * The OpenWrt build system also runs a series of automated tests to ensure code quality: code coverage, notifications on build errors, notifications of relevant CVEs, what else? | * The OpenWrt build system also runs a series of automated tests to ensure code quality: code coverage, notifications on build errors, notifications of relevant CVEs, what else? | ||
| Line 298: | Line 317: | ||
| ===== T-shirts and stickers ===== | ===== T-shirts and stickers ===== | ||
| - | * create | + | * Create |
| - | * first 10 commits in the project etc. | + | * First 10 commits in the project etc. |
| - | * decide | + | * Decide |
| - | * or just approach some specific/ | + | * Or just approach some specific/ |
| - | * decide | + | * Decide |
| ===== Define the roadmap ===== | ===== Define the roadmap ===== | ||
| - | * there should be some goals defined which we would like to get into the next release | + | * There should be some goals defined which we would like to get into the next release |
| - | * improve | + | * Improve |
| - | * migrate | + | * Migrate |
| - | * aim for 100% reproducible builds at least on most popular targets | + | * Aim for 100% reproducible builds at least on most popular targets |
| ===== Redefine roles and rules ===== | ===== Redefine roles and rules ===== | ||
| - | * Our current rules tie voting right to the ability to commit access to master. | + | * Our current rules tie voting right to the ability to commit access to master |
| - | * This was a useful concept in the early days. | + | * This was a useful concept in the early days |
| - | * This can lock out package | + | * This can lock out package |
| * We will need to redefine the rules that apply to various roles in the project | * We will need to redefine the rules that apply to various roles in the project | ||
| ==== TODO ==== | ==== TODO ==== | ||
| - | * [VOTE] | + | |
| - | ===== Wiki style refresh | + | ===== Refresh project identity |
| - | * refresh the style with the modern looking Bootstrap based theme (tmomas) | + | * Unify/refresh/modernize the look/ |
| + | * Refresh logo, provide official vector version usable on stickers, t-shirts etc. | ||
| + | * Project color guidelines etc. | ||
| + | |||
| + | ==== Wiki style refresh ==== | ||
| + | |||
| + | * Refresh | ||
| + | * [[https:// | ||
| ==== TODO ==== | ==== TODO ==== | ||
| - | * [VOTE] Consensus of this meeting was to proceed, needs approval from the full group | + | |
| ===== Organize more real life meetings ===== | ===== Organize more real life meetings ===== | ||
| - | * meet periodically every 6-9 months | + | * Meet periodically every 6-9 months |
| - | * there was a discussion of possibly meeting again in Barcelona in February. Paul & Jo will touch base with ? to see if there might be a venue at BCP | + | * There was a discussion of possibly meeting again in Barcelona in February |
| + | |||
| + | ==== TODO ==== | ||
| + | |||
| + | Paul & Jo will touch base with ? to see if there might be a venue at BCP | ||
| ===== Project Constitution ===== | ===== Project Constitution ===== | ||
| - | * were still missing formal definitions for a lot of processes | + | * Were still missing formal definitions for a lot of processes |