Procedures: Community contributions

Open
#23 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Quiet
Domain
documentation

Research direction

Start by reviewing the existing contributor-docs guidance and repository structure to find the appropriate location for these procedures. Define coverage for feature requests, questions, contributor feedback, and graceful closure, then confirm the document addresses each listed topic and matches the project's contribution practices.

Written by the indexing model from the issue text.

Description

category-documentation github-migration-triaged team-wallet-framework wf-documentation

This document would cover guidelines on working with code contributions from the community. It would include subtopics such as:

  • How to respond to feature requests
  • How to respond to questions
  • How to give feedback to contributors
  • How to close submissions gracefully
Dominant language
JavaScript
Stars
86
Forks
42
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from MetaMask/contributor-docs

All issues in MetaMask/contributor-docs

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.