I am a maintainer yeah, more on the devops/infra side and also provide a downstream distro for enterprises to pay the bills:
https://github.com/fluentdo/agent
Getting a timeline on a review is tricky because it depends on what actually is included/changing and how well implemented it is. Plus there may be other urgent things for folks to take care of with imminent major releases or CVEs or something similar. I'm not going to promise anything there - this is OSS and done in spare time mostly for lots of folks.
Normally you can expect a review in a couple of weeks or so but if it needs a few rounds then it may take longer. The best approach is to follow contribution guidelines, make sure it has tests and config/docs all as part of the initial PR and ensure all CI is green so reviewers do not have to flag this then you have to wait for another review. If something is not ready to be merged, do not ask for a review.
https://github.com/fluent/fluent-bit/blob/master/CONTRIBUTING.md
You can also join the community meetings as well to encourage things or get feedback, etc.:
https://www.meetup.com/fluent-community-meeting/
Feel free to ping me if you need anything nudging on the CI side when you have a PR up or want pointers for docs, etc.
Once merged it will then go into the next release but that may be a while off, particularly if you it is not backported to the current stable release. There are nightly builds though if you want to test.