Skip to content

Latest commit

 

History

History
54 lines (33 loc) · 3.49 KB

CONTRIBUTING.md

File metadata and controls

54 lines (33 loc) · 3.49 KB

Contributing To SBOMit

We welcome contributions to the SBOMit project! By participating in this project, you agree to abide by the Code of Conduct.

Getting Started

To contribute to the SBOMit specification repository, follow these steps:

  1. Fork the repository.
  2. Create a new branch for your contribution: 
    git checkout -b feature/new-feature
  3. Make your desired changes to the codebase.
  4. Commit your changes with a descriptive commit message.
  5. Push your branch to your forked repository: 
    git push origin feature/new-feature
  6. Open a pull request against the main branch of the SBOMit specification repository.

For larger changes, please discuss your ideas with the community in an issue before starting to work on them.

Feature Request

If you wish to propose a new feature, we kindly request that you adhere to our established procedures by following the official feature request template feature request template. The template provides essential guidance to ensure a comprehensive and structured submission of your feature request. Thank you for your cooperation and commitment to our project's standards.

Maintainers

For questions, guidance, and assistance with specific areas of the codebase, please contact the relevant maintainers listed in the MAINTAINERS.md file.

Create an Issue or Bug

If you encounter any issues/bugs or have suggestions for improvements, please open an issue on the issue tracker and follow the issue template for guidance on creating a issue/bug.

Developer Certificate of Origin

To ensure a clear licensing history and proper attribution, code commits in the project require a signoff. The signoff indicates that you have read and agree to the Developer Certificate of Origin (DCO), which states that you have the right to contribute the code and that it does not infringe on any copyright or intellectual property rights. The DCO signoff helps protect the project and its contributors.

By making a contribution to this project, I certify that:

  1. The contribution was created in whole or in part by me and I have the right to submit it under the open source license indicated in the file; or

  2. The contribution is based upon previous work that, to the best of my knowledge, is covered under an appropriate open source license and I have the right under that license to submit that work with modifications, whether created in whole or in part by me, under the same open source license (unless I am permitted to submit under a different license), as indicated in the file; or

  3. The contribution was provided directly to me by some other person who certified 1., 2. or 3. and I have not modified it.

  4. I understand and agree that this project and the contribution are public and that a record of the contribution (including all personal information I submit with it, including my sign-off) is maintained indefinitely and may be redistributed consistent with this project or the open source license(s) involved.

License

When contributing to the SBOMit project, it is important to understand and agree to the licensing terms. All contributions to the project will be licensed under the Community Specification License 1.0. By submitting a pull request, you are agreeing to these terms.

Thank you for contributing to SBOMit project! We appreciate your help in making our project better.