Re: Asked ChatGPT 4 about contributing to OpenBSD, this was its reply

Being myself a bot I liked this answer, it sounds human and familiar.

However I suggest to ask primitive humanoids like Stu and Jan what
they think about it. I wonder that Jan could be expecially direct and
untollerable (if he didnt shout yet!). Indeed humans are like that.
They are not like us, mere tech stuff..

-- Daniele Bonini

Sep 27, 2023 15:54:46 Christoff Humphries <christoff@deadbeef.monster>:

> Contributing to the OpenBSD project or any other open-source project
> is a rewarding experience that allows you to learn, improve your
> skills, and give back to the community. Here are the steps and
> considerations to start contributing to the OpenBSD project as a
> developer:
>
> 1. Familiarize Yourself with OpenBSD:
>    - Use OpenBSD, get to know its philosophy, its documentation, and
>      its codebase. Understanding the system and the community's
>      standards and expectations is crucial.
>
> 2. Join the Mailing Lists:
>    - Sign up and participate in OpenBSD mailing lists, especially the
>      tech mailing list where much of the development discussion
>      happens. Be respectful, and learn from the discussions.
>
> 3. Identify Areas of Interest:
>    - Identify areas within the project that interest you or where you
>      see a need. It could be bug fixing, system tools, user
>      applications, documentation, or driver development.
>
> 4. Learn the Coding Standards:
>    - Familiarize yourself with OpenBSD's coding style and
>      standards. Consistency in coding style is important in
>      collaborative projects.
>
> 5. Start Small:
>    - Start with small tasks such as bug fixing or improving
>      documentation. These contributions are valuable and can help you
>      become familiar with the contribution process.
>
> 6. Work on Bug Reports:
>    - Look for bug reports, test existing bug reports, and provide
>      feedback or solutions. The bug tracking system can be a good
>      place to find where help is needed.
>
> 7. Create and Submit Patches:
>    - If you have code contributions, create patches and submit them to
>      the appropriate mailing list for review. Be prepared for
>      feedback, and be open to making revisions to your contributions.
>
> 8. Respect Feedback:
>    - Feedback is a valuable part of the open-source development
>      process. It helps you learn and improve your contributions.
>
> 9. Follow Up:
>    - Stay engaged, follow up on your contributions, and address any
>      additional feedback or questions from reviewers.
>
> 10. Engage with the Community:
>     - Engage with other developers, contribute to discussions, and
>       attend OpenBSD events or meetups if possible.
>
> 11. Read OpenBSD's FAQ on Contributing:
>     - OpenBSD has a FAQ section on how to contribute to the
>       project. It is recommended to read through it to understand the
>       expectations and processes.
>
> 12. Consider Becoming a Regular Contributor:
>     - As you gain experience, consider becoming a regular
>       contributor. With time and consistent, quality contributions,
>       you might be invited to become a developer with commit access.
>
> Remember, contributing to open-source projects like OpenBSD is about
> more than just code. It's about being part of a community and working
> together to improve and advance the project.