Hacktoberfest 2024 Info

[kehoecj]

Thank you to the OSS Community for the 325 GitHub ⭐ and all the contributors who have added features to the config-file-validator tool. You have made such a big impact on this project and we really appreciate it!

We wanted to announce that we're participating in Hacktoberfest 2024 and highlight some ways that you can participate.

How to participate

Work an existing issue

We have gone through and marked all of our issues that we felt were good candidates for hacktoberfest with the https://github.com/Boeing/config-file-validator/labels/hacktoberfest label. These issues should be fairly straightforward to implement without much or any code refactoring. If there is an issue that you'd like to work that is not labeled https://github.com/Boeing/config-file-validator/labels/hacktoberfest you can still work that too. To work an issue follow the steps below:

1. Comment on the issue that you'd like to work it. We'll assign the issue first-come first serve. If you later decide you can't work it please let us know so that we can reassign the issue.
2. During development use the issue to ask any clarifying questions, start architecture discussions, etc
3. After development is complete submit the PR for review. Your PR will be reviewed by two maintainers and you will need to resolve all the comments.
4. Once the review is complete the maintainers will merge it and add the hacktoberfest-accepted Valid PR Hacktoberfest PR label

Create and work an issue

If you have an idea that is not on the existing issue list that you'd like to work please submit it! The process will be similar to working an existing issue with a few additional steps.

1. Create a new issue with your idea or bug and mark it with the https://github.com/Boeing/config-file-validator/labels/hacktoberfest label. Be as descriptive as possible so that the maintainers can understand the issue.
2. The maintainers will review the issue and ask any clarifying questions
3. Once all questions have been resolved the maintainers will assign you the issue
4. During development use the issue to ask any clarifying questions, start architecture discussions, etc
5. After development is complete submit the PR for review. Your PR will be reviewed by two maintainers and you will need to resolve all the comments.
6. Once the review is complete the maintainers will merge it and add the hacktoberfest-accepted Valid PR Hacktoberfest PR label

The maintainers will try stay on top of the issues and PR's so that the OSS community can get timely feedback and credit for their hacktoberfest submissions.

Thank you in advance and let us know if there are any questions!

[kehoecj]

Thank you to all the Hacktoberfest contributors! The following PR's were merged during October:

• [ISSUE-190] Update go version in go.mod to use 1.N.P format #191
• Add function to dynamically determine package version for PKGBUILD #186
• docs: replace example images with gif from terminalizer #185
• Include support for multiple reporter output types, solves #109 #181
• Add PKGBUILD for Arch User Repository #180
• Display excludeable file types and validate #178
• Support env variables for config (#111) #177
• Add SARIF as a reporter option #166

@xanish @gurukiran07 @nikonhub @shiina4119 @danielingegneri @timwehrle @jackneer @jameskim0987