Proposing a new Fluentd maintainer

[kenhys]

Which issue(s) this PR fixes:

N/A

What this PR does / why we need it:

According to our governance policy, we need to vote for changing maintainership.

As @daipom contributing to fluentd a lot, so I'll propose @daipom as a new maintainer.

Currently, there are following organizations:

• @sonots (ZOZO)
• @cosmo0920 , @edsiper (Calyptia)
• @toru-takahashi (Treasure Data)
• @ashie, @kenhys (ClearCode)

And individual developers.

• @okkez
• @repeatedly
• @tagomoris
• @fujimotos

(We need to also update affilicated compaty information in MAINTAINERS.md later)

Thus, the total number of organization is 8 and satisfying the majority of 2/3 must be not less than 6.

So every organization need to show 👍 or 👎

Docs Changes:

N/A

Release Note:

N/A

[edsiper]

Hi @kenhys

I think we need to put a plan in place to incorporate new maintainers, happy to support that and have a voting system. Would @daipom open a PR and document intentions and list of contributions that can help to attribute him a maintainer status ?

[daipom]

Thanks for proposing me.

I am interested in processing Ruby and log data. I want to learn these things through this product, and I want to leverage the benefits and new features of Ruby for this product.

Would @daipom open a PR and document intentions and list of contributions that can help to attribute him a maintainer status ?

Sure!
Would it be better to comment on this PR this time? Or is it better to open a new PR?

[cosmo0920]

• @hatake, @edsiper (Calyptia)

FYI: My GitHub account name is @cosmo0920 not @hatake...

[kenhys]

FYI: My GitHub account name is @cosmo0920 not @hatake...

Oh, orz... fixed it.

[daipom]

Thanks for proposing me.

I describe myself below.
Please let me know if any explanations are missing.

Intentions

I deliver Fluentd enterprise services in ClearCode over the past year.
I want to make Fluentd a better software, not only within the framework of our service.
This is also the philosophy of ClearCode. Our goal is to develop and grow free softwares.

Personally, I am interested in processing Ruby and log data.
I want to learn these things through this product, and I want to leverage the benefits and new features of Ruby for this product.

I would be happy to contribute more to Fluentd, a great software that is used a lot in the world.

List of contributions

My contributions to this repository:

• I have made 50 commits to this repositories in the past year. This is 2nd highest.
  • https://github.com/fluent/fluentd/graphs/contributors?from=2022-01-01&to=2023-02-27&type=c
  • https://github.com/fluent/fluentd/commits?author=daipom
• My main PRs:
  • Enable server plugins to specify socket-option SO_LINGER #3644
  • Add sigdump func to fluent-ctl #3680
  • Fix wrong calcuration of retry interval and detecting retry limit #3649
    • Fix retry specification with @ashie
    • I did some reviews and added tests in the following PR.
      • [For #3649] Add scenario test of RetryState #3685
  • Add new system-config to set interval to restart workers #3768
    • I also fixed ServerEngine to add a new feature to Fluentd.
    • Add interval to restart worker treasure-data/serverengine#120
  • out_forward: fix error of ack handling conflict on stopping with require_ack_response enabled #4030
  • I have recently been working on improving features related to buffer corruption: Add more checks for buffer corruption on startup #3970
    • buffer: backup broken file chunk #4025
    • buffer: warning message for restoring buffer with flush_at_shutdown #4027
    • buffer: add log for time periods of restored chunks which may be broken #4028
  • I also have been working on improving the initialization process of Fluentd: Logger: Log format setting is not applied to the first log #4037
    • Windows: Fix a bug that the wrong log file is reopened with log rotate setting when flushing or graceful reloading #4054
    • Fix problem that some system configs are not reflected #4064
    • Refactor logger initialization #4065
• I also have been working on supporting Ruby 3.2 with @ashie.
  • http_server: Ready to support Async 2.0 gem #3842
  • Adapt Console::Logger to Fluent::Log #3987

My contributions to fluentd-website:

• I have made 12 commits in the past year. This is 3rd highest.
  • https://github.com/fluent/fluentd-website/graphs/contributors?from=2022-01-01&to=2023-02-27&type=c

My contributions to fluentd-docs-gitbook :

• I have made 19 PRs in the past year or so.
  • https://github.com/fluent/fluentd-docs-gitbook/pulls?q=is%3Apr+author%3Adaipom

I participated in the development of some plugins:

• https://github.com/fluent-plugins-nursery/fluent-plugin-sigdump
• https://github.com/fluent-plugins-nursery/fluent-plugin-windows-exporter

In addition to these plugins, I also maintain the following plugin.

• https://github.com/fluent-plugins-nursery/fluent-plugin-remote_syslog

I want to be able to maintain other plugins etc. little by little.

[kenhys]

I think we need to put a plan in place to incorporate new maintainers, happy to support that and have a voting system. Would @daipom open a PR and document intentions and list of contributions that can help to attribute him a maintainer status ?

It may be better to use a proper voting-system in the future, but anyway, daipom explains his contributions in this PR. it is good enough at the moment.

Current status:

• @sonots (ZOZO) N/A
• @cosmo0920 , @edsiper (Calyptia) (only @cosmo0920 agreed with proposal)
• @toru-takahashi (Treasure Data) N/A
• @ashie, @kenhys (ClearCode) 👍 (@ashie, @kenhys agreed with proposal)

And individual developers.

• @okkez N/A
• @repeatedly N/A
• @tagomoris N/A
• @fujimotos N/A

[ashie]

Current voting status

Companies:

• ZOZO: N/A
  • @sonots: N/A
• Calyptia: 👍 (Proposing a new Fluentd maintainer #4069 (comment))
  • @cosmo0920: 👍 (Proposing a new Fluentd maintainer #4069 (comment))
  • @edsiper : N/A
  • Although @edsiper doesn't vote yet, @cosmo0920 already voted so I treat the organization vote of Calyptia as one vote.
• Treasure Data: 👍
  • @toru-takahashi: 👍 (Proposing a new Fluentd maintainer #4069 (comment))
• ClearCode: 👍
  • @ashie: 👍 (Proposing a new Fluentd maintainer #4069 (comment))
  • @kenhys: 👍 (Proposing a new Fluentd maintainer #4069 (comment))

Individual developers.

• @okkez: 👍 (Proposing a new Fluentd maintainer #4069 (comment))
• @repeatedly: 👍 (Proposing a new Fluentd maintainer #4069 (comment))
• @tagomoris: 👍 (Proposing a new Fluentd maintainer #4069 (comment))
• @fujimotos N/A

Result

New maintainers are proposed by an existing maintainer and are elected by a 2/3 majority organization vote.

Now we've got 6/8 votes, so we are able to have @daipom as a new maintainer.
I'll merge this and grant him write permission of fluentd related repositories.
If you have any objection, please let me know in a few days.

[daipom]

Thanks!
I am honored to join the maintainers.
I’ll keep on trying to make Fluentd and the community better!