Add GSOD 2021 Call for Writers

Adds page with asking for a statement of interest, with expectations,
important dates and other links.

Signed-off-by: Ayan Sinha Mahapatra <ayansmahapatra@gmail.com>

Author: AyanSinhaMahapatra

docs/source/gsod-toc.rst

@@ -11,6 +11,7 @@ More about of GSoD - <https://developers.google.com/season-of-docs>_
 .. toctree::
    :maxdepth: 2
 
+   gsod/gsod-2021-call-for-writers
    gsod/gsod-2021
    gsod/gsod-2020
    gsod/gsod_2019_report

docs/source/gsod/gsod-2021-call-for-writers.rst

@@ -0,0 +1,94 @@
+.. _GSoD2021_call_writers:
+
+==================================================
+:index:`GSoD : Technical Writer Selection Process`
+==================================================
+
+Thank you for your interest in creating technical documentation for `scancode.io <https://github.com/nexB/scancode.io>`_.
+
+
+OUR EXPECTATIONS
+----------------
+
+Technical Writing Experience
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+You should have been actively writing technical documentation, and have multiple publicly
+available samples of your work.
+
+Familiarity with scancode.io
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+You will need to learn how scancode.io works, its functions and features in order to write
+effective and useful technical documentation. We currently have some basic documentation at
+`scancodeio.readthedocs.io <https://scancodeio.readthedocs.io/en/latest/>`_.
+
+You will also need to know or learn the key concepts of Software Composition Analysis in order
+to understand your audience. You will have access to a nexB instance of scancode.io, but you will
+also need to be able to install and run scancode.io locally on your own computer.
+
+Familiarity with Sphinx, RTD, git/GitHub
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+You should have experience writing documentation in a Sphinx/reStructuredText environment where
+the documentation is managed side by side with the code in a GitHub project repository. We treat
+technical documentation like code, tested for successful builds and checked with linters for
+quality control.
+
+Eagerness to learn about and document scancode.io
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+We expect you to try scancode.io out yourself and familiarize yourself with it, and to be eager
+to learn and document all aspects of it, particularly the How-To Guides and Tutorials.
+
+Here are some suggestions for you to consider as documentation topics:
+
+- Did you encounter any difficulties installing scancode.io locally?  Assuming that you resolved
+  them, can you improve the documentation to help others?
+- Do you understand how the pipelines work?  How would you explain pipelines to others in greater
+  detail?
+- Do you understand how to interpret and get full value from scan results?  How would you document
+  ways to get the most out of the scan results?
+
+We use `Diataxis <https://diataxis.fr/>`_ - as a design framework for our documentation.
+
+.. note::
+
+    Reach out to us if you have any specific questions on setting up and using scancode.io locally
+    or in general. `Link to Gitter Chat <https://gitter.im/aboutcode-org/gsod-season-of-docs/>`_
+
+
+STATEMENT OF INTEREST
+---------------------
+
+Applicants are expected to submit a Statement of Interest [`GSoD Official Template <https://developers.google.com/season-of-docs/docs/tech-writer-statement>`_]
+as a publicly viewable document, preferably in Google Docs, to pombredanne@nexb.com.
+[CC to dmclark@nexb.com and asmahapatra@nexb.com]
+
+It should have the following minimum sections:
+
+- `Personal Information <https://developers.google.com/season-of-docs/docs/tech-writer-statement#personal_information>`_
+- `Professional Information <https://developers.google.com/season-of-docs/docs/tech-writer-statement#professional_information>`_
+- `Project Details <https://developers.google.com/season-of-docs/docs/tech-writer-statement#project_statement>`_
+
+.. note::
+
+   Note that you do not need to suggest a budget, nor do you have to suggest a timeline. Both are specified in our organisation proposal linked below.
+
+   - Budget: $15,000
+   - Timeline: 18 May to 22 October [`GSoD Timeline <https://developers.google.com/season-of-docs/docs/timeline>`_]
+
+IMPORTANT DATES
+---------------
+
+- 10 May : Deadline to Submit Statement of Interest
+- 16 May : We announce our selection
+- 17 May 18 PM UTC : Google Season of Docs Technical Writing Hiring Deadline
+
+LINKS
+-----
+
+- `Organisation Proposal <https://docs.google.com/document/d/1jW2ogyALIBNsVpHhQ0EbBKzpfPF8BJzmT4vCfU3sQso/edit?usp=sharing>`_
+- `Gitter Chat <https://gitter.im/aboutcode-org/gsod-season-of-docs>`_
+- `Scancode.io GitHub Repository <https://github.com/nexB/scancode.io>`_
+- `Scancode.io RTD Documentation <https://scancodeio.readthedocs.io/en/latest/>`_

docs/source/gsod/gsod-2021.rst

@@ -138,7 +138,8 @@ Create and update scancode.io user and developer guides
 * Upgrade the scancode.io Web UI documentation.
 * Create an introductory `video <https://opensource.com/article/21/3/video-open-source-tools>`_
   to teach how the web UI is used.
-* Update and improve the existing Pipe libraries reference API documentation (which is generated from code documentation "docstrings").
+* Update and improve the existing Pipe libraries reference API documentation
+  (which is generated from code documentation "docstrings").
 * Sync the new documentation set with the code to support continuous integration with code changes.
 
 - **Level**