Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

net/frr - style cleanup and unify forms #4450

Merged
merged 2 commits into from
Jan 8, 2025
Merged

net/frr - style cleanup and unify forms #4450

merged 2 commits into from
Jan 8, 2025

Conversation

AdSchellevis
Copy link
Member

Apply frontend / api changes to align more with current core patterns.

This has been on my list for quite some time, but finally found some time to cleanup the frontend code.

@AdSchellevis AdSchellevis added the cleanup Low impact changes label Jan 6, 2025
@AdSchellevis AdSchellevis requested a review from mimugmail January 6, 2025 13:26
@AdSchellevis AdSchellevis self-assigned this Jan 6, 2025
@AdSchellevis
Copy link
Member Author

@mimugmail @fabianfrz do you mind if I change the maintainer of this plugin to myself?

Apply frontend / api changes to align more with current core patterns.
Copy link
Member

@mimugmail mimugmail left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It looks better now, thx. Ok for me to change the ownership, but I think it always was Fabian, not myself :)

@AdSchellevis
Copy link
Member Author

@mimugmail thanks, looking at the last couple of years, you have been most active on the subject, so I'll change the maintainer in this PR for clarity.

We're slowly bringing the plugin and documentation "up to spec" from our end, @Monviech added docs earlier in opnsense/docs#629, restructuring the code has been on my list for quite some time.

@mimugmail
Copy link
Member

Be aware that FRR9 and FRR10 brings lots of breaking changes, e.g. switching from separated config files to one huge, I can create a tracking issue with all relavant breakings

@AdSchellevis
Copy link
Member Author

@mimugmail yes please, if you have the time and spirit, we should probably plan an upgrade together (and determine what the next target should be). It's probably a good opportunity to refactor the configuration files as well anyway, I left those out for now to lower the risk.

@AdSchellevis AdSchellevis merged commit fc23b6a into master Jan 8, 2025
@AdSchellevis AdSchellevis deleted the frr_cleanup branch January 8, 2025 08:27
@fabianfrz
Copy link
Member

fabianfrz commented Jan 8, 2025

@mimugmail @AdSchellevis I was always the maintainer of a lot of stuff because I wrote the initial plugins. I am more than happy if you take over the maitainership as I am not really working on it anymore.

BTW: A big thanks should go to mimugmail as he extended them a lot.

@AdSchellevis
Copy link
Member Author

@fabianfrz very logical, thanks for starting this venture, it was (and is) an important addition. @mimugmail has spend quite some time on the subject indeed and I hope he will keep doing that to help improve this part of our system.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cleanup Low impact changes
Development

Successfully merging this pull request may close these issues.

3 participants