Meeting 2023 02

Gluon Meetup 2023-02

11.04.2023 - 20:00 CEST - mumble.freifunk.net

Notes from Last Meetup: Meeting-2023-01

Please add your name to the topic you want to add!

[ 👤 lemoer] Discussion on the roadmap.
[ 👤 aiyion] documentation of unresolveable known issues - post release (context: #2839)
[ 👤 aiyion] lack of communication
[ 👤 tomh] gluon-setup-mode: allow network-triggered activation (#2778)
[ 👤 djfe] v2022.1.4/v2023.1 - how are Gluon releases planned? (device support and other changes)
[ 👤 maurerle] wpa_supplicant issue 2023 #2829
[ 👤 rotanid] backports to the latest stable branch
[ 👤 djfe] GitHub Label "stale" for closed stale commits

Are people working towards new goals?
What about usteer? Is this active?
- Blocktrron does not plan to merge this to gluon. This will stay in community-packages.
[ 👤 lemoer] moved his "RestAPI for Config Mode" to stale. He is currently not working on this anymore.
- Currently, there is no use case for [ 👤 lemoer].
Seems like babeld is still stale.
- It was suggested to remove babeld soon.
- Even if we drop babel, then we will still have a layer 3 routing protocol with oslrd now.
- However, the general opinion seems to be that we should remove this soon.
  - We would have more flexibility to add oslrd.
  - We would also gain more flexibility in the code in general.
- Suggestion: Open a PR that would removes babeld?
  - Yes.
  - We could merge this later on, if we decide so. Opening this PR doesn't mean, it must be merged.
  - At least, the PR is then already open.
- We would also like to get rid of mmfd.
  - But this is another issue, since gluon-oslrd is also using this.
  - First, we would need a replacement.

Should we alter the "Known Issues" in the documentation of releases that were in the past?
Discussion about yes or no.
We could instead use labels in the github issue tracker to track affected releases of bugs.
- [ 👤 NeoRaider] says, that the description in the issue should be understandable then.
- This is possible. We are able to edit the description of the issue.
In general, the known issues in the documentation can link to the github issue tracker.
Aiyion will open a PR.

Please respond to communication.
If you have no time, this is fine.
- (Then please just respond that you have no time. Respect each others invested time!)
Most of us have little time. Should we do review days in the future?
- [ 👤 blocktrron]: I am more productive, when I do the reviews separately.
- [ 👤 NeoRaider]: It's an occasion to do reviews for me. Otherwise I wouldn't review that much probably.
- [ 👤 lemoer]: We can continue to have review days for my opinion.
- [ 👤 aiyion]: Sometimes, PRs get stuck at some point and nobody knows why. A review day helps there.
Aiyion will invite for the next review day. Let's see what happens.

blocktrron will look into it again and then a merge should happen at some point

when is the next release based on master? (device support and other changes)
- releases are not planned long term
- someone stumbles across free time and puts it into it.
- we agree, it would be nice if one of us would stumble across some in the near future ;)
- may happen sooner or later
thoughts:
- branching Gluon 2023.1.x soon after OpenWrt branched 23.0x, afterwards Gluon master can move to be based on OpenWrt 23.0x

Likely a site config issue, maurerle will report back when there is anything new

no changed policy, e.g. for device support old policy still applies: https://github.com/freifunk-gluon/gluon/wiki/Device-Integration
backports via labels (by maintainers) or by asking (non-maintainers)
less backports are likely only because of lower time&motivation

Closed stale PRs will usually have a "waiting-for-author" tag, so no separate tag is needed to filter for stale PRs.
Filter is:pr is:unmerged is:closed label:"2. status: waiting-on-author"

Disclaimer: Please note that this wiki can be edited by anyone. Please be careful when using it.