Skip to content

How Can You Contribute?

You can directly contribute to the MASVS or MASTG in many different ways! First, go ahead and create a GitHub account for free on the GitHub homepage.

Contribution Flow

flowchart LR
    A(Open Discussion) -->|discuss| C{qualifies?}
    C -->|Yes| D(Issue)
    C -->|No| E[Close]
    D -->|open PR| F(Pull Request)
    F -->|review| G{approved?}
    F -->|make changes| F
    G -->|Yes| H[Merge]
    G -->|No| I[Close]

💬 Participate in Discussions

Our GitHub Discussions are the first place to go to ask questions, give feedback, and propose new ideas. If your proposal qualifies for the MASTG/MASVS, we'll convert it into an "Issue" (the discussion might take a while).

🎯 Create Issues

Before creating a PR, first create an Issue to be discussed for missing requirements, content or errors.

  • To avoid multiple people duplicating effort on the same issue, project leaders will assign it to only a few that will own it.
  • Explain what you think is missing in the issue, including references (if available) and suggest where it could be added.

📝 Open a Pull Request

You can contribute with content or corrections by opening a Pull Request (PR).

  • Your PR may be merged after review.
  • Be sure to follow our style guide when writing content.

Learn how to open a PR here.

✅ Become a Reviewer

You can Review Pull Requests (PRs) and also gain contributions. If you are a fluent speaker in any of the different languages that the MASVS is available in, feel free to give feedback on any of the submitted PRs.

After your PR or issue has been submitted, we will review it as quickly as possible which typically only takes a few days. If you think we have forgotten about it, feel free to give us a nudge after 7 days have passed.

Learn how to review a PR here.

🔎 Proof-reading

If you do proof-reading, these are the things we’re looking for:

  • Content cohesion & coherence
    • is there a good linkage of ideas?
    • does the paragraph make sense?
    • does it make sense with the next one? think that hundreds of people have written in here, often without considering the surroundings of the text they were including).
  • Reducing the content to a minimum (people tend to be very verbose/wordy) and in such a document we need clear and short/concise statements
  • Optimize for scannability (maybe instead of a big paragraph it would be better to have a bullet point list).
  • Any passive voice sentences? Convert to active voice.
  • Does each paragraph focus on a single topic?
  • Are key points stated at the start of each section?
  • Are commas, parentheses, colons, em-dashes, and semicolons used properly?

Refer to Google Technical Writing trainings for more info: