Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Next revisionBoth sides next revision
meetings:hamburg2019:start [2019/07/10 00:00] – [Create a manual] pepe2kmeetings:hamburg2019:start [2020/02/06 19:05] – [Wiki style refresh] Issue with bootstrap theme is finally fixed tmomas
Line 4: Line 4:
  
   * happened from **June 9th** to **June 12th** at amazing place called [[http://www.dock-europe.net|Dock Europe]], located in [[https://www.openstreetmap.org/node/375717634#map=16/53.5585/9.9443|Hamburg Altona]]    * happened from **June 9th** to **June 12th** at amazing place called [[http://www.dock-europe.net|Dock Europe]], located in [[https://www.openstreetmap.org/node/375717634#map=16/53.5585/9.9443|Hamburg Altona]] 
-  * **attendees (left to right):** aparcar, ldir, richb-hanover, dangole, Hauke, tmomasynezz, lynxis, jow, neoraider, pepe2k+  * **attendees (alphabetical order):** aparcar, dangole, Hauke, ​jowldir, lynxis, neoraider, pepe2k, richb-hanover,​ tmomas, ynezz
  
 ===== Agenda preparation ===== ===== Agenda preparation =====
Line 97: 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 (tmomas)+  * <del>Wiki: show a banner in the wiki, DO NOT BUY THOSE DEVICES (tmomas)</del> 
 +    * done, [[meta:infobox:432_warning|infoboxes have been updated]]
   * How to mark 4MB devices in codebase, use "BROKEN" flag?   * How to mark 4MB devices in codebase, use "BROKEN" flag?
   * **[VOTE]** do a vote this release is the last one for 4MB devices   * **[VOTE]** do a vote this release is the last one for 4MB devices
Line 112: Line 113:
 ===== Defragmentation of Code and Tools ===== ===== Defragmentation of Code and Tools =====
  
-  * Evaluate GitLab as a replacement for git.openwrt.org, patchworks and the repos on GitHub.+  * Evaluate GitLab as a replacement for git.openwrt.org, patchworks and the repos on GitHub
     * We have received a positive reference from h01ger, a Debian developer: they have switched to GitLab from SourceForge and are quite satisfied     * We have received a positive reference from h01ger, a Debian developer: they have switched to GitLab from SourceForge and are quite satisfied
     * See [[https://www.fooishbar.org/blog/gitlab-fdo-introduction/|Introducing freedesktop.org GitLab]] for another migration story     * See [[https://www.fooishbar.org/blog/gitlab-fdo-introduction/|Introducing freedesktop.org GitLab]] for another migration story
   * Would still support patches via E-Mail   * Would still support patches via E-Mail
-  * Replace FlySpray with the GitLab issue tracker which is tighly integrated with commits and merge requests, automatic closing of the issues from the commit messages, API access+  * Replace FlySpray with the GitLab issue tracker which is tightly integrated with commits and merge requests, automatic closing of the issues from the commit messages, API access
  
 ==== TODO ==== ==== TODO ====
  
-  * instead of migrating projects like fw3, procd etc. from git.openwrt.org to GtiHub in order to enable CI testing on CircleCI, setup complete testing environment on Lynxis Gitlab instance with external CI runners (ynezz, lynxis, aparcar)+  * Instead of migrating projects like fw3, procd etc. from git.openwrt.org to GtiHub in order to enable CI testing on CircleCI, setup complete testing environment on Lynxis GitLab instance with external CI runners (ynezz, lynxis, aparcar)
  
 ===== New People ===== ===== New People =====
  
-  * Annouce in Wiki and  Forum that we want more people to help out+  * Announce in Wiki and Forum that we want more people to help out
   * 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
Line 133: Line 134:
  
   * **[VOTE]** <del>pepe2k, NeoRaider and ynezz have two new developers in mind to grant commit access</del>   * **[VOTE]** <del>pepe2k, NeoRaider and ynezz have two new developers in mind to grant commit access</del>
-    * [[http://lists.infradead.org/pipermail/openwrt-adm/2019-June/001053.html|voting in progress]]+    * <del>[[http://lists.infradead.org/pipermail/openwrt-adm/2019-June/001053.html|voting in progress]]</del>
 ===== Stable discussion ===== ===== Stable discussion =====
  
-  * have a specific list of CVE and packages for one release(similar to sdwalker, but without all packages and only show CVE) +  * Have a specific list of CVE and packages for one release (similar to sdwalker, but without all packages and only show CVE) 
-  * have a security mailinglist for releases - similar to debian list +  * Have a security mailing list for releases - similar to Debian list 
-    * or use a general announcement mailing list +    * Or use a general announcement mailing list 
-  * do a minimal supported time +  * Do a minimal supported time 
-  * Extended life is another storywe might could do the Debian LTS approach if someone ones to support more than 1.5 year +  * Extended life is another storywe could do the Debian LTS approach if someone wants to support more than 1.5 year 
-  * 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 
-  * Supported scope is unclear(core packages, package feed, kernel) +    * Just 2 (current and previous) or more (maybe 3 which should result in ~1 year time span assuming 6-months release cycle)? 
-    * different parts could have diffeernt support times+  * Supported scope is unclear (core packages, package feed, kernel)? 
 +    * Different parts could have different support times
  
 ==== TODO ==== ==== TODO ====
  
-  * mail should be created with the differnt opinions to have this discussion with a broarder audience on the mailing list (Hauke) +  * mail should be created with the different opinions to have this discussion with a broader audience on the mailing list (Hauke) 
-    * include package feed maintainers +    * Include package feed maintainers 
-  * who is doing the security mailinglist? (lynxis volounteer)+  * Who is doing the security mailing list? (lynxis volounteer)
  
 ===== Package maintainer ===== ===== Package maintainer =====
  
-  * create maintainer tools +  * Create maintainer tools 
-  * use those maintainer tools to know which package don't have a maintainer +  * Use those maintainer tools to know which package don't have a maintainer 
-  * 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 a golden package and how to do it (partial already there)+  * Document a golden package and how to do it (partial already there)
  
 ===== Deprecated packages ===== ===== Deprecated packages =====
  
-  * can we update old base packagese.g. we have json-c which is outdated. +  * Can we update old base packages (e.g. we have json-c which is outdated)? 
-  * 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 ====
Line 173: Line 175:
 ===== Online Image Builder ===== ===== Online Image Builder =====
  
-  * currently running at chef.libremesh.org +  * Currently running at chef.libremesh.org 
-  * nice to have +  * Nice to have 
-  * good for new users +  * Good for new users 
-  * it might need 1 to 2 month until it's ready +  * It might need 1 to 2 months until it's ready 
-  * don't allow to remove core packages +  * Don't allow to remove core packages
-  * **TODO:** make it official when it's ready+
   * 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://www.freexian.com/services/debian-lts.html]] 
-  * use them as a communication channel to industry players +  * We need to present to them what the OpenWrt community actually needs 
-  * [[https://www.freexian.com/services/debian-lts.html]]+  * 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 as base (=if reproducing (initialy) needs to be done using the same system, whether debian or whatever) +  * h01ger is fine we're using e.g. Debian as base (=if reproducing (initially) needs to be done using the same system, whether Debian or whatever) 
-  * 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? inside the .ipk? next to it?+  * How to supply buildinfo files for packages? Inside the .ipk? Next to it?
  
 ==== We need to recreate the same toolchains ==== ==== We need to recreate the same toolchains ====
  
-  * create a .buildinfo for the toolchain (document the host) +  * Create a .buildinfo for the toolchain (document the host) 
-  * create a .buildinfo for packages (containing the openwrt.git & packages.git & [..feed.git] commit hashs and the version+  * Create a .buildinfo for packages (containing the openwrt.git & packages.git & [..feed.git] commit hashes and the version
  
 ==== Useful documentation related to .buildinfo files ==== ==== Useful documentation related to .buildinfo files ====
Line 213: Line 215:
 ===== Remaining of lede-project merge? ===== ===== Remaining of lede-project merge? =====
  
-  * OpenWrt irc channel OP: Who has access? How to become OP? Who is the founder? +  * OpenWrt IRC channel OP: Who has access? How to become OP? Who is the founder? 
-  * how to handle mail aliases?+  * How to handle mail aliases?
   * How to handle contact@openwrt.org?   * How to handle contact@openwrt.org?
     * **TODO:** jow will create an imap mailbox/reflector to handle contact@openwrt.org     * **TODO:** jow will create an imap mailbox/reflector to handle contact@openwrt.org
     * This allows us to respond with an official @openwrt.org address     * This allows us to respond with an official @openwrt.org address
     * **TODO:** paul and richb will come up with further process steps for handling this address     * **TODO:** paul and richb will come up with further process steps for handling this address
-  * **TODO:** create a guide line for business guide. What's the high-level process to get a board into OpenWrt?+  * **TODO:** Create a guide line for business guide. What's the high-level process to get a board into OpenWrt?
  
 ===== Social things ===== ===== Social things =====
Line 227: Line 229:
   * 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 account? +  * Facebook account? 
-  * twitter +  * Twitter? 
-    * use twitter alternative ([[https://joinmastodon.org/|mastodon]])?+    * Use twitter alternative ([[https://joinmastodon.org/|mastodon]])?
  
 ===== Library versioning ===== ===== Library versioning =====
  
-  * create library version for "our" packages (libubox, ...). +  * Create library version for "our" packages (libubox, ...) 
-    * 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 ''REQUIRED_SIGNATURE'' 
-  * make signing of sysupgrade images working on the buildbots +  * Make signing of sysupgrade images working on the buildbots 
-  * enable ''REQUIRED_SIGNATURE=1'' on ath79 for testing ASAP in order to iron out all possible bugs before the next release+  * Enable ''REQUIRED_SIGNATURE=1'' on ath79 for testing ASAP in order to iron out all possible bugs before the next release
  
 ===== Create a manual ===== ===== Create a manual =====
Line 339: Line 341:
   * **[VOTE]** Vote on putting wiki people onto the contact address   * **[VOTE]** Vote on putting wiki people onto the contact address
  
-===== Refresh corporate project identity =====+===== Refresh project identity =====
  
   * Unify/refresh/modernize the look/presentation of the project to the outside world   * Unify/refresh/modernize the look/presentation of the project to the outside world
Line 348: Line 350:
  
   * Refresh the style with the modern looking Bootstrap based theme (tmomas)   * Refresh the style with the modern looking Bootstrap based theme (tmomas)
 +  * [[https://github.com/giterlizzi/dokuwiki-template-bootstrap3/issues/389#issuecomment-582637443|Issue with bootstrap theme is finally fixed]] -> Bootstrap theme can now be used
  
 ==== TODO ==== ==== TODO ====
  • Last modified: 2020/02/09 16:53
  • by ynezz