Hey guys, first of all: Thanks for the amazing operator! We just adopted it into our observability stack. Hence, as open source is "tit for tat", we'd like to contribute back to the project. First question: Is there anything to know that is not written down in the repo? Otherwise we'll just go and tackle some issues. When screening through the issues and PRs, I noticed that there are some more opened issues that I think can be closed, e.g. • https://github.com/fluent/fluent-operator/issues/1193 • https://github.com/fluent/fluent-operator/issues/1166 and some are older an not answered or commented on, e.g.: • https://github.com/fluent/fluent-operator/issues/1211 • https://github.com/fluent/fluent-operator/issues/1151 In such cases (

done

or

won't fix

), does it make sense to close them? How do you usually handle this? Many thanks and have nice day! 🙂

Best way is probably to comment on them to that effect and highlight here 🙂 Longer term if you are willing to contribute regularly then we can give you triage and or maintainer access to help with that directly.

Thx! I'll comment and xref here, if I see smth. Aiming on contributing regularly. Let's see how this evolves. 🙂 ... nice start into the week.

Triaging is important and you can do that even with just comments initially without higher access but we can also set up triage permissions