Update contributing documentation (otwcode#3830)

* Update contributing documentation

- Add a reminder in the pull request checklist to keep <= 5 pull requests open
  at the same time.
- Remove unused issue template.
- Restructure CONTRIBUTING.md.
- Add SECURITY.md.

[skip ci]

* Fix wordings, TOS link, and Jira capitalization

[skip ci]

* Move "Suggesting new features" section

[skip ci]

Author: redsummernight

.github/ISSUE_TEMPLATE.md

@@ -1,10 +1,12 @@
 # Pull Request Checklist
 
-* [ ] Have you read [How to write the perfect pull request](https://github.com/blog/1943-how-to-write-the-perfect-pull-request)?
-* [ ] Have you read through the [contributor guidelines](https://github.com/otwcode/otwarchive/blob/master/CONTRIBUTING.md)?
-* [ ] Have you added tests for any changed functionality?
-* [ ] Have you added the [JIRA](https://otwarchive.atlassian.net) issue number as the *first* thing in your pull request title (eg: `AO3-1234 Fix thing`)
-* [ ] Have you updated or commented on the JIRA issue with the information below?
+* [ ] Have you read ["How to write the perfect pull request"](https://github.blog/2015-01-21-how-to-write-the-perfect-pull-request/)?
+* [ ] Have you read the [contributing guidelines](https://github.com/otwcode/otwarchive/blob/master/CONTRIBUTING.md)?
+* [ ] Have you added [tests for any changed functionality](https://github.com/otwcode/otwarchive/wiki/Automated-Testing)?
+* [ ] Have you added the [Jira](https://otwarchive.atlassian.net) issue number
+  as the *first* thing in your pull request title (e.g. `AO3-1234 Fix thing`)
+* [ ] Do you have fewer than 5 pull requests already open? If not, please wait
+  until they are reviewed and merged before creating new pull requests.
 
 ## Issue
 
@@ -16,19 +18,23 @@ What does this PR do?
 
 ## Testing Instructions
 
-How can the Archive's QA team verify that this is working as you intended? (If you have access, please copy this into the JIRA ticket for them!)
+How can the Archive's QA team verify that this is working as you intended?
+
+(If you have a Jira account with access, please update or comment on the issue
+with any new or missing testing instructions.)
 
 ## References
 
-Are there any other relevant issues / PRs / mailing lists discussions related to this?
+Are there other relevant issues/pull requests/mailing list discussions?
 
 ## Credit
 
 *What name do you want us to use to credit your work in the [Archive of Our Own's Release Notes](https://archiveofourown.org/admin_posts?tag=1)?*
 
-(If you have an account on JIRA, please include the same name in the "Full name" field on your JIRA profile,
-so we can find you and assign you the issues you're working on.)
+(If you have a Jira account, please include the same name in the "Full name"
+field on your Jira profile, so we can assign you the issues you're working on.)
 
 *What pronouns do you prefer (she/her, he/him, zie/hir etc)?*
 
-(If you do not fill this in, we will use your GitHub account name and will use "they" to avoid making assumptions about your gender.)
+(If you do not fill in this section, we will use your GitHub account name and
+they/them pronouns to avoid making assumptions about your gender.)

.github/PULL_REQUEST_TEMPLATE.md

@@ -13,7 +13,7 @@ Acknowledgments
 <p><a href="github.com/otwcode/otwarchive"><img alt="" valign="middle" src="http://media.archiveofourown.org/ao3/logos/GitHub_Logo.png" width="200"/> GitHub</a> for collaborative programming.</p>
 <p><a href="http://www.haproxy.org/"><img alt="" valign="middle" src="http://media.archiveofourown.org/ao3/logos/logo-med.png" width="200"/> HAProxy</a> for load balancing.</p>
 <p><a href="https://houndci.com/"><img alt="" valign="middle" src="http://media.archiveofourown.org/ao3/logos/Hound-Dribbble.png" width="200"/> Hound</a> for style guidance.</p>
-<p><a href="https://otwarchive.atlassian.net/"><img alt="" valign="middle" src="http://media.archiveofourown.org/ao3/logos/jira_rgb_blue.svg" width="200"/> JIRA</a> for our issue tracking.</p>
+<p><a href="https://otwarchive.atlassian.net/"><img alt="" valign="middle" src="http://media.archiveofourown.org/ao3/logos/jira_rgb_blue.svg" width="200"/> Jira</a> for our issue tracking.</p>
 <p><a href="https://nginx.org/en/"><img alt="" valign="middle" src="http://media.archiveofourown.org/ao3/logos/Nginx_logo.svg" width="200"/> NGINX</a> for our front end.</p>
 <p><a href="https://memcached.org/"><img alt="" valign="middle" src="http://media.archiveofourown.org/ao3/logos/Memcached.png" width="200"/> Memcached</a> for caching.</p>
 <p><a href="https://mariadb.com/products/mariadb-maxscale"><img alt="" valign="middle" src="http://media.archiveofourown.org/ao3/logos/maxscale.png" width="200"/> MaxScale</a> for MySQL load balancing.</p>

ACKNOWLEDGMENTS.md

@@ -1,57 +1,64 @@
-# Contributing to Archive of Our Own
+# Contributing to OTW-Archive
+
+## Reporting bugs
+
+We maintain a [Jira issue tracker](https://otwarchive.atlassian.net) for developers,
+and a [list of Known Issues](https://archiveofourown.org/known_issues) for
+[Archive of Our Own](https://archiveofourown.org) users, neither of which are
+publicly editable.
+
+If you need help using the site, or want to report an issue you have found,
+please [contact the AO3 Support team](https://archiveofourown.org/support).
 
-## Contributing code
 
-### Report a bug
+## Reporting security issues
 
-We have a [list of known issues](https://archiveofourown.org/known_issues).
-If you have a problem that you don't see on that list, please send a bug report
-via the [Support and Feedback Form](https://archiveofourown.org/support).
+Please refer to [SECURITY.md](https://github.com/otwcode/otwarchive/blob/master/SECURITY.md).
 
-### Pick an issue to work on
 
-You will find our [list of approved issues on JIRA](https://otwarchive.atlassian.net/projects/AO3/issues).
+## Updating documentation
 
-We regret that we cannot accept pull requests for issues we haven't already logged, with the exception of documentation
-or spelling corrections.
+Our [development wiki](https://github.com/otwcode/otwarchive/wiki) is publicly
+editable. Unless a page says at the top that it should only be edited by
+official OTW volunteers, please feel free to make changes!
 
-### Resolve the issue
 
-Consult our [Developer Documentation](https://github.com/otwcode/otwarchive/wiki) on how to set up a local development
-environment so you can work on the Archive code.
+## Suggesting new features
 
-### Submit your pull request
+Please [contact the AO3 Support team](https://archiveofourown.org/support).
 
-Please read the checklist on [our pull request template](https://github.com/otwcode/otwarchive/blob/master/.github/PULL_REQUEST_TEMPLATE.md)
-for the steps you need to perform to make sure we can accept your pull request.
 
-### Action comments on your pull request
+## Contributing code
+
+**We only accept pull requests for issues we have already added to [Jira](https://otwarchive.atlassian.net)**,
+with the exception of spelling corrections and documentation improvements
+(e.g. any Markdown files).
 
-When we review your pull request, we will make comments on GitHub. Please make sure you read these carefully and apply
-the suggestions!
+Please check out our development wiki for more information on:
 
-Due to our workload, it may take several weeks before an approved pull request is merged, so be patient - we will get to it!
+- [how to set up a development environment](https://github.com/otwcode/otwarchive/wiki)
+- [code conventions](https://github.com/otwcode/otwarchive/wiki/Commit-policy)
 
-### Testing and fixing bugs
+Please follow the checklist on [our template](https://github.com/otwcode/otwarchive/blob/master/.github/PULL_REQUEST_TEMPLATE.md) when submitting pull requests.
 
-Once your pull request is merged, it will be deployed to our internal Staging server and our manual QA team will check it.
-We may ask you to make further changes and submit a new pull request if we find any problems that will affect our users'
-ability to benefit from your changes.
+Please be patient with us! Due to our workload, it may take some time before we
+can review and eventually merge your pull request.
 
-### Release
+Once your pull request is merged, it will be deployed to our internal testing site
+and our QA team will check that everything is working as intended. If not, we may
+set the issue to ["Broken on Test"](https://github.com/otwcode/otwarchive/wiki/Issue-Tracking-with-Jira)
+and ask you to make further changes in new pull requests.
+
+If all is well, your contribution will be deployed to the [Archive of Our Own](https://archiveofourown.org)
+and you will be credited in the [release notes](https://archiveofourown.org/admin_posts?tag=1)!
 
-Once we have checked that all is well, your contribution will be deployed to [Archive of Our Own](https://archiveofourown.org) and you will be credited
-in the [AO3 Release Notes](https://archiveofourown.org/admin_posts?tag=1)! Make sure you tell us your preferred name and pronoun
-in the pull request.
 
 ## Volunteering for the OTW
 
-If you would like to donate more of your time and expertise in a multi-national, inclusive, fandom-oriented development team, you might
-enjoy becoming an official OTW volunteer.
+If you would like to donate more of your time and expertise in a multi-national,
+inclusive, fandom-oriented team, you might enjoy [becoming an official OTW volunteer](http://transformativeworks.org/how-you-can-help/volunteer).
 
-[Read more about volunteering with the OTW](http://transformativeworks.org/how-you-can-help/volunteer).
 
 ## Questions?
 
 [Drop us an email](mailto:otw-coders@transformativeworks.org) if you have any questions.
-

CONTRIBUTING.md

@@ -0,0 +1,14 @@
+# Reporting a security issue
+
+Please email us directly at [otw-coders@transformativeworks.org](mailto:otw-coders@transformativeworks.org)
+with details and reproduction steps. We will get back to you as soon as possible,
+and we may ask for additional information or guidance.
+
+Please avoid testing for security issues on the Archive of Our Own itself,
+as you risk disrupting other users and violating the [Terms of Service](https://archiveofourown.org/tos#IV.C.).
+
+Please give us a reasonable amount of time to address the issue before any
+disclosure to the public or a third-party.
+
+We thank you for your effort and responsible disclosure! We will make sure you
+receive due credit on [our public release notes](https://archiveofourown.org/admin_posts?tag=1).