search

fluent / fluent-bit-go

Fluent Bit Golang package to build plugins
Apache License 2.0
189 stars 52 forks source link

Update Dockerfile #36

Closed ZP-AlwaysWin closed 4 years ago

ZP-AlwaysWin commented 4 years ago

fix Dockerfile typo

ZP-AlwaysWin commented 4 years ago

@PettitWesley Can you assign someone to review this PR?

ZP-AlwaysWin commented 4 years ago

@PettitWesley Can you assign someone to review this PR?

hi @PettitWesley Excuse me I want to join the fluent community and become a Member. What contribution do I need to make to qualify

PettitWesley commented 4 years ago

@ZP-AlwaysWin There are different maintainer groups actually; the fluent organization is the parent for all and @edsiper is the lead maintainer for all.

For Fluent Bit Golang, since it is a smaller project/side-project, rules have not been written down. In my case, I became Fluent Bit go maintainer because I created and maintain two widely used Go plugins (CloudWatch Logs and Kinesis Firehose).

For fluent bit core- the high level requirements have been written down. In my case, I became a maintainer there after I had built a few bigger features, and had spent a few months occasionally helping with PR reviews, small fixes, and answering questions in issues.

ZP-AlwaysWin commented 4 years ago

@ZP-AlwaysWin There are different maintainer groups actually; the fluent organization is the parent for all and @edsiper is the lead maintainer for all.

For Fluent Bit Golang, since it is a smaller project/side-project, rules have not been written down. In my case, I became Fluent Bit go maintainer because I created and maintain two widely used Go plugins (CloudWatch Logs and Kinesis Firehose).

For fluent bit core- the high level requirements have been written down. In my case, I became a maintainer there after I had built a few bigger features, and had spent a few months occasionally helping with PR reviews, small fixes, and answering questions in issues.

Ok,Thank you very much for your reply. Best Wishes