Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add in a contributors document outlining the repo's process. #597

Merged
merged 3 commits into from
Oct 25, 2022

Commits on Oct 6, 2022

  1. Add in a contributors document outlining the repo's process. julian@Airm

    This document is undoubtedly incomplete and can be iterated on.
    
    It represents, to the best of my knowledge, the *existing* process
    I have followed myself since the repository's inception, with only
    minor tweaks (back then lots of GitHub UI features didn't even
    exist!).
    
    Of course over the years it may not have been followed by everyone,
    nor even possibly by myself, but putting it here should hopefully
    make it clearer to everyone what the baseline is, in case we wish
    to make changes.
    
    There are some differences here from processes followed in other JSON
    Schema org repos -- whether this is an issue or not is of course
    constructively debatable.
    Julian committed Oct 6, 2022
    Configuration menu
    Copy the full SHA
    a6520db View commit details
    Browse the repository at this point in the history

Commits on Oct 11, 2022

  1. Configuration menu
    Copy the full SHA
    e17668e View commit details
    Browse the repository at this point in the history
  2. Explicitly mention that one approval doesn't override other concerns.

    Hopefully this was obvious regardless.
    Julian committed Oct 11, 2022
    Configuration menu
    Copy the full SHA
    f54f00a View commit details
    Browse the repository at this point in the history