Add CLA to this repo #224
Merged
Add CLA to this repo #224
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Alan Jowett <alan.jowett@microsoft.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request introduces comprehensive documentation for contributing, development, governance, and testing in the BPF Performance project. The new documents establish clear guidelines and processes for contributors and maintainers, covering coding standards, review and approval workflows, and testing methodologies. These resources are designed to improve project quality, maintainability, and community collaboration.
Contribution and Community Guidelines:
CONTRIBUTING.mdoutlining how to report bugs, submit patches, propose new features, and the contributor license agreement process. It also references the project's code of conduct and development practices.docs/Governance.mdto define project roles (contributors, maintainers), pull request review and approval requirements, issue management, release process, and decision-making protocols.Development Standards:
docs/DevelopmentGuide.mdspecifying coding conventions, header file practices, style guide (including automated formatting and license headers), naming conventions, and testing requirements for code changes.Testing Framework and Best Practices:
docs/TestingGuide.mddescribing the project's approach to performance, unit, integration, and regression testing. It details test organization, data requirements, running tests locally and in CI, guidelines for new tests, metrics collection, and troubleshooting strategies.