IMPORTANT: If you have already filed an RFS task the existing task can be updated and new service tags added as needed. Please do not file duplicate RFS tasks for the same project. Multiple #Security-Readiness-Reviews can be created as subtasks as part of the same project.
//Some information may be not applicable or filled in at a later time for a maturing project. That's OK. //
= Basic Information Section =
=== Brief description ===
- Reason for request. This is an outline of the intention and purpose for the project.
=== Primary Contacts ===
- `@phabname` is appropriate here. //Two// contacts are requested.
=== Do you have a project/product/program plan or documentation? ===
- Please link to existing documentation such as the project homepage.
- Documents can be attached to this task if needed.
=== What Security Team services do you anticipate needing? ===
- https://www.mediawiki.org/wiki/Wikimedia_Security_Team/Services
- https://phabricator.wikimedia.org/project/subprojects/4420/
> set services from above / all of the above / I don’t know (Perfectly fine)
=== What is the 'go live' date for deployment of this project ===
> 3 months / 6 months / 1 year
----
= Technical Information Section =
=== Will any sensitive data to be collected, stored or exposed? ===
- https://foundation.wikimedia.org/wiki/Privacy_policy
- Examples: `PII, credit cards, UA/IP, credentials`
=== Do related discussions exist in Phab, on wiki, or in an RFC'? ===
- https://www.mediawiki.org/wiki/Requests_for_comment
- Please link to existing tasks or discussions
=== Technology Stack ===
- Link to code repository / patchset
- Please list all relevant languages, platforms, hardware, etc.
- Please list all known internal and external dependencies, including hosting providers
=== Post-deployment ===
- Name of team responsible for project support post-deployment and primary contact(s).
=== Working test environment ===
- Please link or describe setup process for setting up a test environment.