Merge branch 'main' into add-create-term-docs

Author: bmcutler

.github/workflows/test.yml

@@ -16,7 +16,7 @@ jobs:
 
     - name: Get Ruby version
       id: rubyversion
-      run: echo "::set-output name=version::$(curl https://raw.githubusercontent.com/github/pages-gem/master/.ruby-version)"
+      run: echo "::set-output name=version::3.2"
 
     - name: Set up Ruby
       uses: ruby/setup-ruby@v1

Gemfile

@@ -10,3 +10,5 @@ gem 'wdm', '>= 0.1.1' if Gem.win_platform?
 gem "webrick", "~> 1.8"
 
 gem 'html-proofer', "~> 3.19.4"
+
+gem 'json'

Gemfile.lock

@@ -1,7 +1,7 @@
 GEM
   remote: https://rubygems.org/
   specs:
-    activesupport (7.1.2)
+    activesupport (7.1.3)
       base64
       bigdecimal
       concurrent-ruby (~> 1.0, >= 1.0.2)
@@ -14,14 +14,14 @@ GEM
     addressable (2.8.6)
       public_suffix (>= 2.0.2, < 6.0)
     base64 (0.2.0)
-    bigdecimal (3.1.4)
+    bigdecimal (3.1.6)
     coffee-script (2.4.1)
       coffee-script-source
       execjs
     coffee-script-source (1.11.1)
     colorator (1.1.0)
     commonmarker (0.23.10)
-    concurrent-ruby (1.2.2)
+    concurrent-ruby (1.2.3)
     connection_pool (2.4.1)
     dnsruby (1.70.0)
       simpleidn (~> 0.2.1)
@@ -34,13 +34,11 @@ GEM
       ffi (>= 1.15.0)
     eventmachine (1.2.7)
     execjs (2.9.1)
-    faraday (2.7.12)
-      base64
-      faraday-net_http (>= 2.0, < 3.1)
-      ruby2_keywords (>= 0.0.4)
-    faraday-net_http (3.0.2)
+    faraday (2.9.0)
+      faraday-net_http (>= 2.0, < 3.2)
+    faraday-net_http (3.1.0)
+      net-http
     ffi (1.16.3)
-    ffi (1.16.3-x64-mingw-ucrt)
     forwardable-extended (2.6.0)
     gemoji (3.0.1)
     github-pages (228)
@@ -229,18 +227,26 @@ GEM
       jekyll (>= 3.5, < 5.0)
       jekyll-feed (~> 0.9)
       jekyll-seo-tag (~> 2.1)
-    minitest (5.20.0)
+    minitest (5.22.2)
     mutex_m (0.2.0)
-    nokogiri (1.15.5-arm64-darwin)
+    net-http (0.4.1)
+      uri
+    nokogiri (1.16.2-aarch64-linux)
+      racc (~> 1.4)
+    nokogiri (1.16.2-arm-linux)
+      racc (~> 1.4)
+    nokogiri (1.16.2-arm64-darwin)
+      racc (~> 1.4)
+    nokogiri (1.16.2-x86-linux)
       racc (~> 1.4)
-    nokogiri (1.15.5-x64-mingw-ucrt)
+    nokogiri (1.16.2-x86_64-darwin)
       racc (~> 1.4)
-    nokogiri (1.15.5-x86_64-linux)
+    nokogiri (1.16.2-x86_64-linux)
       racc (~> 1.4)
     octokit (4.25.1)
       faraday (>= 1, < 3)
       sawyer (~> 0.9)
-    parallel (1.23.0)
+    parallel (1.24.0)
     pathutil (0.16.2)
       forwardable-extended (~> 2.6)
     public_suffix (4.0.7)
@@ -273,14 +279,17 @@ GEM
     unf (0.1.4)
       unf_ext
     unf_ext (0.0.9.1)
-    unf_ext (0.0.9.1-x64-mingw-ucrt)
     unicode-display_width (1.8.0)
+    uri (0.13.0)
     webrick (1.8.1)
     yell (2.2.2)
 
 PLATFORMS
-  arm64-darwin-20
-  x64-mingw-ucrt
+  aarch64-linux
+  arm-linux
+  arm64-darwin
+  x86-linux
+  x86_64-darwin
   x86_64-linux
 
 DEPENDENCIES
@@ -289,4 +298,4 @@ DEPENDENCIES
   webrick (~> 1.8)
 
 BUNDLED WITH
-   2.4.21
+   2.5.6

README.md

@@ -130,3 +130,10 @@ above structure. Currently, the site only supports three levels of nesting (sub-
 
 This repository was created via a fork of Edition, which is a product documentation theme for Jekyll created
 by by [CloudCannon](http://cloudcannon.com/), the Cloud CMS for Jekyll.
+
+
+
+### Ruby Version Troubleshooting
+
+In February 2024:
+* https://ritviknag.com/tech-tips/ruby-versioning-hell-with-jekyll-&-github-pages/

_docs/developer/development_instructions/automated_grading.md

@@ -77,6 +77,7 @@ number:
         "capabilities": [
             "extra_ram"
         ],
+        "enabled": true,
         "num_autograding_workers": 2
     }
    ```

_docs/developer/getting_started/project_ideas.md

@@ -5,25 +5,26 @@ redirect_from:
   - /developer/project_ideas
 ---
 
-Submitty has been a participating organization of [Google Summer of
-Code](https://summerofcode.withgoogle.com/) for five successful
-seasons.
-See [Submitty GSoC Application & Reports](/developer/google_summer_of_code/index) for more information
+[comment]: <> Submitty has been a participating organization of
+[comment]: <> [Google Summer of Code](https://summerofcode.withgoogle.com/)
+[comment]: <> for five successful seasons.
+
+We are thrilled to announce that Submitty has been accepted to [Google
+Summer of Code (GSoC) 2024](https://summerofcode.withgoogle.com/).
+See [Submitty GSoC Application &
+Reports](/developer/google_summer_of_code/index) for more information
 about the application process and to read reports from Submitty GSoC
-contributors from Summers 2018, 2019, 2020, 2022, and 2023.
-We have applied for selection for Summer 2024 and our Project Ideas
-list below has been updated.  The organizations selected for Summer
-2024 Google Summer of Code will be announced in late February.  
+contributors in past summers.
+
+[comment]: <> We have applied for selection for
+[comment]: <> Summer 2024 and our Project Ideas list below has been updated.  The
+[comment]: <> organizations selected for Summer 2024 Google Summer of Code will be
+[comment]: <> announced in late February.
 
 [comment]: <> _NOTE: The organizations selected for Summer 2023 Google Summer of
 [comment]: <>   Code will be announced in late February.  The instructions below
 [comment]: <>    are from 2022 and will be updated if Submitty is accepted!_
 
-[comment]: <> We are thrilled to announce that Submitty has been accepted
-[comment]: <> to [Google Summer of Code (GSoC) 2023](https://summerofcode.withgoogle.com/).
-
-
-
 
 The project ideas listed below target a variety of different topics
 and require different levels of prior experience.  The scope of these
@@ -38,6 +39,9 @@ our [Zulip server](/contact) to meet the Submitty mentors and other new
 developers.
 
 
+&nbsp;    
+  
+
 1. **Expand Testing of the Manual/TA Rubric Grading Interface**
 
    [Overview of Rubric Grading Interface](/grader/rubric_grading/index)
@@ -70,6 +74,8 @@ developers.
 
    _Difficulty Level_: introductory to medium
 
+   &nbsp;    
+
 
 2. **Refactor and Performance Improvements for the Manual/TA Rubric Grading Interface**
 
@@ -112,6 +118,7 @@ developers.
 
    _Difficulty Level_: medium to challenging
 
+   &nbsp;
 
 
 3. **Notebook Builder: UI To Streamline Instructor Configuration of Automated Grading**
@@ -163,7 +170,8 @@ developers.
    _GSoC Project Size_: 90 or 175 or 350 hours
 
    _Difficulty Level_: introductory or medium
-   
+
+   &nbsp;    
 
 4. **Expansion of Examples and Documentation of Intermediate and Advanced Autograding Features**
 
@@ -219,6 +227,8 @@ developers.
 
    _Difficulty Level_: medium to challenging
 
+   &nbsp;
+        
 
 5. **AI/ML to Enhance and Steamline Manual / TA Grading**
 
@@ -267,7 +277,7 @@ developers.
    data and the potential for improving the efficiency of the
    manual/TA grading process and the quality/accuracy and quantity of
    useful constructive feedback to students.
-  
+   
    _Skills & Experience Required_: Coursework and/or professional
    experience in AI/ML and modern AI/ML technology.  Moderate to
    advanced programming experience, and willingness to learn web and
@@ -281,6 +291,8 @@ developers.
 
    _Difficulty Level_:  medium to challenging
 
+   &nbsp;    
+
 6. **Other Topics**
 
    The Submitty team welcomes GSoC project proposals on other topics
@@ -301,6 +313,7 @@ developers.
 
    _Difficulty Level_:  introductory to medium to challenging
 
+&nbsp;    
 
 See also:
 

_docs/developer/getting_started/vm_install_using_vagrant.md

@@ -221,10 +221,23 @@ Below are quick steps to get everything installed and running.
    vagrant up
    ```
 
-   Vagrant will build your VM.  This will take maybe 30 minutes to a
-   few hours depending on your Internet connection speed.  When this
-   command finishes, your VM is ready to use.
+   If you are using VirtualBox as your provider, you will by default use
+   a pre-packaged Submitty VM. This will have all of Submitty already setup.
+   Vagrant will build your VM for you. This process will take 10 minutes to
+   maybe half an hour depending on your internet connection speed.
+   When this command finishes, your VM is ready to use.
 
+   If you wish to run `vagrant up` from scratch, on Linux or Mac type:
+   ```
+   BASE_BOX=1 vagrant up
+   ```
+   or on Windows, type: 
+   ```
+   SET BASE_BOX=1
+   vagrant up
+   ```
+   This process will take anywhere from 30 minutes to a few hours depending on your
+   internet speed. 
 
 7. When the `vagrant up` command completes successfully, you will be
    able to access the Submitty website (instructions follow in the

_docs/developer/google_summer_of_code/index.md

@@ -6,36 +6,29 @@ redirect_from:
 ---
 
 
-Submitty has been a participating organization of [Google Summer of
-Code](https://summerofcode.withgoogle.com/) for five successful
-seasons.  Please read the student project reports from previous
-summers linked below.  We have applied for selection for Summer
-2024 and our [Project ideas](/developer/project_ideas)
-list has been updated.
-
+We are thrilled to announce that Submitty has been accepted to [Google
+Summer of Code (GSoC) 2024](https://summerofcode.withgoogle.com/).
+Project reports from participants in previous summers are linked
+below.
 
 <center>
 <a href="https://summerofcode.withgoogle.com"><img src="/images/GSoC-Vertical.png" width="250px"></a>
 </center>
 
-[comment]: <> _NOTE: The organizations selected for Summer 2023 Google Summer of
-[comment]: <>   Code will be announced in late February.  The instructions below
-[comment]: <>    are from 2022 and will be updated if Submitty is accepted!_
-
-_NOTE: The organizations selected for Summer 2024 Google Summer of
-Code will be announced in late February.  The instructions below
-are from 2023 and will be updated if Submitty is accepted!_
+[comment]: <> _NOTE: The organizations selected for Summer 2024 Google Summer of
+[comment]: <> Code will be announced in late February.  The instructions below
+[comment]: <> are from 2023 and will be updated if Submitty is accepted!_
 
 
-## How to Apply to Submitty for Google Summer of Code 2023
+## How to Apply to Submitty for Google Summer of Code 2024
 
 1. Read the GSOC information for contributors to confirm your eligibility:  
 
    * [https://summerofcode.withgoogle.com/](https://summerofcode.withgoogle.com/)  
 
    * [https://developers.google.com/open-source/gsoc/faq#what_are_the_eligibility_requirements_for_participation](https://developers.google.com/open-source/gsoc/faq#what_are_the_eligibility_requirements_for_participation)
 
-   * [https://opensource.googleblog.com/2022/11/get-ready-for-google-summer-of-code-2023.html](https://opensource.googleblog.com/2022/11/get-ready-for-google-summer-of-code-2023.html)
+   * [https://opensource.googleblog.com/2024/02/mentor-organizations-announced-for-google-summer-of-code-2024.html](https://opensource.googleblog.com/2024/02/mentor-organizations-announced-for-google-summer-of-code-2024.html)
 
 2. Read our [Suggestions for New Developers](/developer).
 
@@ -44,7 +37,7 @@ are from 2023 and will be updated if Submitty is accepted!_
    in a virtual machine on your computer.
 
 4. Review our project ideas list:   
-   [https://submitty.org/developer/project_ideas](/developer/project_ideas)
+   [https://submitty.org/developer/getting_started/project_ideas](/developer/getting_started/project_ideas)
 
 5. Join our Zulip server to ask questions and meet other new developers:   
    [https://submitty.org/contact](/contact)
@@ -75,21 +68,22 @@ are from 2023 and will be updated if Submitty is accepted!_
    [https://submitty.org/developer/getting_started/review_a_pull_request](/developer/getting_started/review_a_pull_request)
 
 10. Prepare your application. We recommend prospective contributors focus on one
-   of our suggested projects from the project ideas list above. Successful
+   of our suggested projects from the [project ideas](/developer/getting_started/project_ideas) list. Successful
    applicants will be able to expand and enhance the proposed project idea
    with a timeline of design and implementation milestones, and will
    demonstrate curiosity and motivation for the topic.  
 
 11. Document your skills, relevant coursework, non-course experience, and future
-   career goals that qualify you to work on this project.  Include your
-   approximate schedule for the summer, including start date, end date,
-   and number of hours of work per week, and any
-   classes, employment, or other time commitments during that period.
+   career goals that qualify you to work on this project.
+
+12. Include your approximate schedule for the summer: start date, end date,
+   and number of hours of work per week.  Also, describe any
+   classes, employment, or other time commitments during that time period.
 
-12. The application window for Google Summer of Code closes on April 4th, 2023 at 18:00 UTC.
+12. The application window for Google Summer of Code closes on April 2th, 2024 at 18:00 UTC.
    Please carefully read all of the program requirements.  
 
-     * [Google Summer of Code 2023 Timeline](https://developers.google.com/open-source/gsoc/timeline)  
+     * [Google Summer of Code 2024 Timeline](https://developers.google.com/open-source/gsoc/timeline)  
 
      * [https://summerofcode.withgoogle.com/](https://summerofcode.withgoogle.com/)  
 

_docs/instructor/assignment_preparation/index.md

@@ -10,8 +10,8 @@ redirect_from:
 ### Create a New Gradeable
 
 To create a new gradeable, instructor users should click "New
-Gradeable" in the sidebar on the left of the screen. 
-Fill out this form (details in the following sections) and press "Create New Gradeable".
+Gradeable" in the sidebar on the left of the screen. Either [Upload a JSON file](/instructor/assignment_preparation/upload_gradeable), or
+fill out this form (details in the following sections) and press "Create New Gradeable".
 
 Most of the fields on the Create/Edit Gradeable form can be changed
 later.  You can return to this form from the main page by pressing the