Remove fntlnz from everywhere

[fntlnz]

Hey all,
I've been thinking about this for a very long time and came to a conclusion that it's time
for me to focus on other things and make room for new people here and for other things in my life.

I don't know for what I'll be remembered in this project, if for the features or for the bugs but
I'm grateful for having had the opportunity to work on Falco, especially thanks to @leodido and @ldegio .

My words of gratefulness go also to @kris-nova , to @mstemm and to @Kaizhe

I'll follow with a PR to remove myself from all the repos.

• Falco docs: remove fntlnz #2123
• charts docs: remove fntlnz charts#363
• community docs: remove fntlnz community#149
• evolution docs: remove fntlnz evolution#153
• falcoctl docs: remove fntlnz falcoctl#112
• libs docs: remove fntlnz libs#471
• go plugin sdk docs: remove fntlnz plugin-sdk-go#61
• test infra docs: remove fntlnz test-infra#761
• client go docs: remove fntlnz client-go#58
• driverkit https://github.com/falcosecurity/driverkit/pull/new/remove-fntlnz
• pdig docs: remove fntlnz pdig#28
• plugins docs: remove fntlnz plugins#130
• client-rs docs: remove fntlnz client-rs#18
• event generator docs: remove fntlnz event-generator#74
• falco website docs: remove fntlnz falco-website#646
• kilt docs: remove fntlnz kilt#53
• plugin-sdk-cpp docs: remove fntlnz plugin-sdk-cpp#7
• template docs: remove fntlnz template-repository#3

I'll remove myself from the organization as well.

It was a good journey, ciao!

Ad maiora

[jasondellaluce]

Hi @fntlnz, It's sad to see you go. I didn't have the pleasure to work with you, but I came across your name in many parts of the codebase. Your work speaks by itself, thank you for all you did for the community.

As for next steps of your decision, the DCO checks are failing in all your PR. Would you please proceed and sign-off your commits?

If you like, please consider also adding yourself under the emeritus_approvers section instead of removing you from OWNERS files entirely.

[poiana]

Issues go stale after 90d of inactivity.

Mark the issue as fresh with /remove-lifecycle stale.

Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Provide feedback via https://github.com/falcosecurity/community.

/lifecycle stale

[poiana]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh with /remove-lifecycle rotten.

Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Provide feedback via https://github.com/falcosecurity/community.

/lifecycle rotten

[poiana]

Rotten issues close after 30d of inactivity.

Reopen the issue with /reopen.

Mark the issue as fresh with /remove-lifecycle rotten.

Provide feedback via https://github.com/falcosecurity/community.
/close

[poiana]

@poiana: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue with /reopen.

Mark the issue as fresh with /remove-lifecycle rotten.

Provide feedback via https://github.com/falcosecurity/community.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.