Skip to content

chore: establish community contribution process#845

Open
marythought wants to merge 1 commit intomainfrom
dspx-2421-community-process
Open

chore: establish community contribution process#845
marythought wants to merge 1 commit intomainfrom
dspx-2421-community-process

Conversation

@marythought
Copy link
Contributor

Summary

  • Replaces the bare DCO-only CONTRIBUTING.md with a full community contribution guide
  • Adds Code of Conduct link (canonical CoC lives in opentdf/platform)
  • Documents community feedback channels (bugs → issues, features/questions → platform Discussions)
  • Adds contribution workflow, branch naming conventions, commit message format (Conventional Commits), and PR guidelines
  • Retains full DCO section unchanged

Test plan

  • Review rendered Markdown on GitHub
  • Verify all links resolve correctly

Closes DSPX-2421

@marythought marythought requested a review from a team as a code owner February 19, 2026 22:47
@gemini-code-assist
Copy link

Summary of Changes

Hello @marythought, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request significantly enhances the opentdf/web-sdk project's community engagement by establishing a comprehensive and clear contribution process. It transforms the previously minimal CONTRIBUTING.md into a full guide, providing contributors with structured workflows, communication channels, and coding standards. The changes aim to streamline the contribution experience, foster a more organized development environment, and ensure legal compliance for all community-driven efforts.

Highlights

  • Comprehensive Contribution Guide: The existing DCO-only CONTRIBUTING.md has been replaced with a detailed guide covering various aspects of community contribution.
  • Code of Conduct Integration: A link to the OpenTDF Code of Conduct has been added, emphasizing expected community behavior.
  • Defined Feedback Channels: Clear guidelines are now provided for reporting bugs, requesting features, asking questions, and suggesting documentation improvements, directing users to appropriate GitHub features like Issues and Discussions.
  • Structured Contribution Workflow: New sections outline the contribution process, including checking existing issues, aligning on approach, forking and branching, making changes, signing off commits, and opening pull requests.
  • Standardized Branching and Committing: Detailed instructions for branch naming conventions (e.g., feat/, fix/) and Conventional Commits format are included to ensure consistency.
  • Pull Request Guidelines: Specific guidelines for creating pull requests have been added, focusing on referencing issues, keeping PRs focused, updating documentation, and ensuring CI checks pass.
  • Retained DCO Section: The Developer Certificate of Origin (DCO) section has been preserved to maintain legal integrity for contributions.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Changelog
  • CONTRIBUTING.md
    • Expanded the file to include a full community contribution guide.
    • Added sections for Code of Conduct, Community Feedback, How to Contribute, Development Setup, Branch Naming, Commit Messages, and Pull Request Guidelines.
    • Integrated links to relevant external resources and other OpenTDF repositories.
    • Retained and slightly reformatted the existing Developer Certificate of Origin (DCO) section.
Activity
  • No human activity has been recorded on this pull request yet.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

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

Code Review

The pull request introduces a comprehensive community contribution guide, which is a significant improvement over the previous DCO-only document. It provides clear instructions on how to engage with the community, the development workflow, and standards for branches and commits. The adoption of Conventional Commits and standardized branch naming will help maintain a clean project history. My suggestions are minor and aimed at improving the formatting of the DCO instructions for better Git compatibility and ensuring the PR guidelines encourage local testing.

CONTRIBUTING.md Outdated
(see [Branch Naming](#branch-naming) below).
4. **Make your changes**: follow the dev setup and code style below.
5. **Sign off your commits**: see [DCO](#developer-certificate-of-origin-dco) below.
6. **Open a pull request**: a [CODEOWNER](CODEOWNERS) will review and merge.

Choose a reason for hiding this comment

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

medium

The term 'CODEOWNER' is singular here, but the file being linked is 'CODEOWNERS'. It is more conventional to refer to the 'code owners' or simply use the plural form to match the file name.

Suggested change
6. **Open a pull request**: a [CODEOWNER](CODEOWNERS) will review and merge.
6. **Open a pull request**: the [CODEOWNERS](CODEOWNERS) will review and merge.

CONTRIBUTING.md Outdated
- Keep PRs focused — one logical change per PR is easier to review and revert.
- Update documentation for any interface or behavior changes.
- Ensure all CI checks pass before requesting review.
- Run `make lint` before pushing.

Choose a reason for hiding this comment

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

medium

It is recommended to run tests locally before pushing to ensure that the changes do not break existing functionality, in addition to the linting check.

Suggested change
- Run `make lint` before pushing.
- Run make lint and make test before pushing.

@github-actions
Copy link

Replaces bare DCO-only CONTRIBUTING.md with a full guide covering
code of conduct, community feedback channels, contribution workflow,
branch naming, commit message format, PR guidelines, and DCO.

Closes DSPX-2421

Signed-off-by: Mary Dickson <mary.dickson@virtru.com>
@marythought marythought force-pushed the dspx-2421-community-process branch from 3791b3a to 1c7f6a9 Compare February 20, 2026 01:13
@github-actions
Copy link

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.

1 participant