Misc doc changes and test fixes

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

Author: AyanSinhaMahapatra

docs/source/contribute/index.rst

@@ -11,4 +11,3 @@
    gsoc17_final_report
    gsoc19_final_report
    gsoc21_final_report
-   long_running_issues

docs/source/contribute/long_running_issues.rst

@@ -303,7 +303,7 @@ We now have a new codebase level attribute ``license_detections`` which has Uniq
 license detection across the codebase, in both packages and resources. They are
 linked by a common attribute ``identifier`` containing the ``license_expression``
 and a UUID generated from the match content. The match level data is only present
-at the resource level if needed, to look at details. 
+at the resource level if needed, to look at details.
 
 New codebase level attribute::
 
@@ -684,7 +684,7 @@ LicenseDetection Data
 This is referencing by LicenseDetections objcts, and has one or multiple
 license matches. This is linked to the resource level detections through
 an ``identifier`` attribute present in both resource and codebase level
-detections. See the `unique license detections section <license_detections_unique>`_ 
+detections. See the `unique license detections section <license_detections_unique>`_
 above for more details on this.
 
 There could be a list of ambiguous detections as a summary to review.

docs/source/explanations/license-detection-reference.rst

@@ -123,7 +123,7 @@ operating system by going to the `project releases page <https://github.com/nexB
 
 For example, Version 30.0.1 archive can be obtained from
 `Toolkit release 30.0.1 <https://github.com/nexB/scancode-toolkit/releases/tag/v30.0.1>`_
-under assets options. 
+under assets options.
 
 .. Note::
 
@@ -347,7 +347,7 @@ the standard Python package management tool.
     Apple M1 chips, as some non-native dependencies does not have pre-built wheels
     for ARM (like py-ahocorasick, intbitset). See :ref:`system_requirements` for
     more information. See related issues for more info:
-    
+
     - `Fallback pure-python deps <https://github.com/nexB/scancode-toolkit/issues/3210>`_
     - `pip install failing on M1 <https://github.com/nexB/scancode-toolkit/issues/3205>`_
 

docs/source/getting-started/install.rst

@@ -252,17 +252,6 @@ Good First Issues
 A `good first issue <https://github.com/nexB/scancode-toolkit/labels/good%20first%20issue>`_
 means it's recommended for people who haven't contributed to Scancode Toolkit before.
 
-#. Refer the detailed documentation for :ref:`good_first_issue`.
-#. :ref:`good_1st_issue_links` for Good First issues are also compiled.
-#. :ref:`good_1st_issue_understand_b4_solving`
-#. :ref:`good_1st_issue_workflow`
-
-A `first timers only <https://github.com/nexB/scancode-toolkit/labels/%20first%20timers%20only>`_
-issue means we've worked to make it more legible to folks who either **haven't contributed to our
-codebase before, or even folks who haven't contributed to open source before**.
-
-Refer the detailed documentation for :ref:`first_timers_only`.
-
 .. _newcomer_add_functionalirty:
 
 Add new Functionality/Enhancement to ScanCode
@@ -324,14 +313,13 @@ If you want to participate in any of the two programs:
 Then:
 
 #. Keep an eye out for Application Timelines.
-#. Solve multiple of these :ref:`good_first_issue` to demonstrate your skills,
+#. Solve multiple of these :ref:`newcomer_good_first_issue` to demonstrate your skills,
    and improve your chances of selection.
 #. Refer the Projects Ideas list for details on tentative projects.
 
-     - :ref:`GSoC2019`
-     - :ref:`GSoD2019`
+     - `GSoC2023 <https://github.com/nexB/aboutcode/wiki/GSOC-2023>`_
 
-#. Remain active in Gitter and talk with the organization mentors well ahead of the deadlines.
+#. Remain active in Element and talk with the organization mentors well ahead of the deadlines.
 #. Select projects according to your skills and finalize project proposals.
 #. Discuss your proposals extensively with corresponding mentors.
 #. Apply for the Programs well before the Deadline.

docs/source/getting-started/newcomer.rst

@@ -54,7 +54,7 @@ And more attributes which are not mandatory but nice to have always (if applicab
 We want to use `minimum_coverage` when there are other licenses which are very similar
 and we want to make sure we match correctly these licenses, and `notes` for interesting
 cases of licenses with descriptions to help identify origin, similarities to other licenses,
-notes about the SPDX keys and others. 
+notes about the SPDX keys and others.
 
 Some URLs:
 

docs/source/how-to-guides/add_new_license.rst

@@ -34,7 +34,7 @@ might have a filename: `mit_and_apache-2.0_10.RULE`.
 
 Save your rule text in this file, if there are specific words like company names,
 projects or other, it is better to have rules with and without these so we have
-better detection. 
+better detection.
 
 For a simple `mit AND apache-2.0` license expression detection, here is an example
 rule file::

docs/source/how-to-guides/add_new_license_detection_rule.rst

@@ -139,7 +139,7 @@ Then you can define a test class and call the ``build_tests`` method defined in
         clazz=TestLicenseDataDriven1, regen=scancode_config.REGEN_TEST_FIXTURES)
 
 The ``tests/data`` directory contains a file for each license:
-a license text file with a YAML frontmatter specifying the expected license expression 
+a license text file with a YAML frontmatter specifying the expected license expression
 from the test.
 
 Finally, install the plugin and run the test: