-
Notifications
You must be signed in to change notification settings - Fork 325
Meeting 2019 01
Martin Weinelt edited this page Jun 6, 2019
·
1 revision
- Browsable mailinglist archive
- Use gmane/spinnics for archive, neoraider will do that
-
Device definition tagging and metadata support
- People should discuss how tagging could look, then think about technical design
- better site.conf change documentation
- We will have obsoletion messages starting v2019.1
- We can now tag pull requests as requiring documentation
- Release notes will be continued as is, errors will be fixed as usual
- No imminent need to improve documentation to enable people to skip release documentation
- site.conf references:
- maybe only reference newer sites, not every one
- move sites to wiki, categorize them, reference from docs
- has been done!
- nftables
- deferred until there are changes in fw3 in OpenWrt
- No progress: Pull Request Template #1433
- would still be nice, help appreciated
-
next minor release 2018.2.2
- resolve issue wrt tunneldigger bandwidth limiting: https://github.com/freifunk-gluon/gluon/commit/d87c4b521b2e891155241c01b98a7ac90a8883b9
- openwrt+packages+routing have been bumped by hexa in master
- backport:
- routing/packages/openwrt bumps
- check other master branch commits
- hexa, cherrypicking in the next few days, then a few days testing and release until mid June
-
next major release 2019.1
- based on OpenWrt 18.06 again, newer OpenWrt release is not yet in sight
- bump to batadv v2019.2: https://github.com/freifunk-gluon/gluon/pull/1733
- yes:
- tunneldigger watchdog: https://github.com/freifunk-gluon/gluon/pull/1735
- new legacy build flag
- maybe:
- batman-adv v14/v15 coexistance
- possibly too large for smaller devices
- cpe210v3 depending on feedback
- gluon-hoodselector
- batman-adv v14/v15 coexistance
- not:
- switch to new batadv UCI config format
- questionable, because batman v14 would need netlink interface backport, so same batctl binary could be used for both
- switch to new batadv UCI config format
- based on OpenWrt 18.06 again, newer OpenWrt release is not yet in sight
-
Add gluon-hoodselector: VPN Mode #1393
- Will be reopened with updated description matching the latest code
- Could be merged in time for 2019.1, but still needs a review
-
gluon-check-connection PR #1684
- Feedback from @neoraider requested regarding the integration of these simple cron jobs
- No further discussion, because author was not presented
-
Add community package repository #1720
- almost everyone has fear for too much work or packages that won't be maintained
- people should submit their worthwhile packages to upstream gluon for proper review
-
Add gluon-geolocator #1201
- blocked because of missing encryption
-
32M/4M devices
- feature gating: reduce feature set of lowend devices to keep them alive
- waiting with this until really too big without reduction (can be done before individually by communities)
- flag a target as legacy, requiring firmware builders to decide whether to build only sysupgrade or sysupgrade and factory images
- GLUON_LEGACY={false,true,sysupgrade}
- build fails without the new flag
- set it to Z, don't build the tiny targets
- set it to X, build them without factory images
- set it to Y, build them with factory images
- https://github.com/freifunk-gluon/gluon/issues/1737
- name this issue in the release notes
- feature gating: reduce feature set of lowend devices to keep them alive
-
guidelines for Gluon development #1437
- help appreciated, no imminent requirement
-
Add a CI pipeline for pull request #1680 See also: Automated-Testing
-
docker buildenv
- multiple variants can already be found online
- hexa will submit a minimal docker buildenv into gluons root
-
Funding for Gluon projects
- Land Niedersachsen hat Fördergelder, die bisher nur für teure Hardware genutzt, wie wäre es stattdessen Entwicklungsarbeit davon zu fördern?
- No interest from the Gluon maintainers
-
ath79
- ar71xx migrated towards a DTS based target called ath79
- OpenWrt 19.0x will have both ar71xx and ath79, but the release after that will move to ath79 only
- Device integration basically needs to happen from the ground up, very few parts from ar71xx can be reused on ath79
- Extend modularity in gluon
-
Usage
-
Community
-
Development
- Device Integration
- Roadmap
- Release-life-cycle
- Protocols
- Meeting 2024/06
- Meeting 2024/05
- Meeting 2024/03
- Meeting 2024/02
- Meeting 2024/01
- Meeting 2023/06
- Meeting 2023/05
- Meetup-CCCamp
- Meeting 2023/04
- Meeting 2023/03
- Meeting 2023/02
- Meeting 2023/01
- Meeting 2022/06
- Meeting 2022/05
- Meeting 2022/04
- Meeting 2022/03
- Meeting 2022/02
- Meeting 2022/01
- Meeting 2021/01
- Meeting 2019/01
- Meeting 2018/03
- Meeting 2018/02
- Meeting 2018/01
- Meeting 2017/01
- Concepts
- Release Process
-
Debugging