Skip to content

Add contribution guidance (CONTRIBUTING.md) - #509

Open
dgarske wants to merge 1 commit into
wolfSSL:mainfrom
dgarske:contributing_md
Open

Add contribution guidance (CONTRIBUTING.md)#509
dgarske wants to merge 1 commit into
wolfSSL:mainfrom
dgarske:contributing_md

Conversation

@dgarske

@dgarske dgarske commented Aug 11, 2026

Copy link
Copy Markdown
Member

Description

Adds a CONTRIBUTING.md to the repository root. None of the wolfSSL repositories had one, so our contributor agreement requirement was only discovered after someone had already done the work. See wolfSSL/wolfssh#1146, where an outside contributor withdrew a PR over it and asked us to document the requirement up front.

The same repo-agnostic file is being added to wolfSSL, wolfSSH, wolfMQTT, wolfTPM, wolfBoot, wolfPKCS11, wolfHSM, wolfProvider, wolfSentry and wolfCLU. It covers how to contribute, the contributor agreement and how to request one, our CI (GitHub Actions is public, Jenkins failures get pasted in by a maintainer), coding expectations, and where to report security issues. Please read the file itself rather than a summary here.

Testing

Documentation only - no code changes.

Copilot AI lite review requested due to automatic review settings August 11, 2026 23:00

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Warning

Copilot couldn't run its full agentic review because it didn't start before the timeout. Make sure your repository has a runner available, or add a copilot-code-review.yml file specifying one with the runs-on attribute. See the docs for more details.

Adds a repository-root CONTRIBUTING.md to make wolfSSL Inc.’s contribution process (especially the required contributor agreement) explicit up front, addressing prior contributor confusion.

Changes:

  • Introduces a standardized contribution guide applicable across wolfSSL Inc. repositories
  • Documents contributor agreement requirement and alternatives when it can’t be signed
  • Describes CI visibility (GitHub Actions vs internal Jenkins) and security reporting process

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

Comment thread CONTRIBUTING.md
@@ -0,0 +1,97 @@
# Contributing

Thank you for your interest in contributing to wolfSSL. This guide applies to all wolfSSL Inc. repositories (wolfSSL, wolfSSH, wolfTPM, wolfBoot, wolfMQTT, wolfCLU, wolfPKCS11, wolfHSM, wolfProvider, wolfSentry, and the rest). Please read the "Contributor Agreement" section below - it is the one requirement that surprises people, and we would rather you know about it up front.
Comment thread CONTRIBUTING.md

## Before You Start

- **Check `master` first.** The fix may already be in, or the surrounding code may have moved. Please base your work on the current `master`.
Comment thread CONTRIBUTING.md
Comment on lines +47 to +49
1. Fork the repository and create a topic branch off `master`.
2. Keep commits focused; one logical change per commit, with a clear message.
3. Open the pull request against `master`.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants