[Documentation:Developer] update for GSoC 2024 application (#579)

bmcutler · web-flow · commit 8bd6c22c71dd · 2024-02-05T04:54:35.000-05:00
Co-authored-by: Barb Cutler &lt;Barb Cutler&gt;
diff --git a/_docs/developer/getting_started/project_ideas.md b/_docs/developer/getting_started/project_ideas.md
@@ -5,11 +5,24 @@ redirect_from:
   - /developer/project_ideas
 ---
 
-We are thrilled to announce that Submitty has been accepted
-to [Google Summer of Code (GSoC) 2023](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, and 2022.
+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
+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.  
+
+[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
@@ -19,41 +32,78 @@ projects varies, and may require different overall time commitments
 also interested in project proposals based on other topics from our
 list of open bugs and feature requests.  Submit questions or comments
 on specific issues through our [Submitty GitHub Issue
-Tracker](https://github.com/Submitty/Submitty/issues).
+Tracker](https://github.com/Submitty/Submitty/issues) and
+join
+our [Zulip server](/contact) to meet the Submitty mentors and other new
+developers.
 
 
-1. **Refactor and Performance Improvements for the Manual/TA Grading Interface**
+1. **Expand Testing of the Manual/TA Rubric Grading Interface**
 
    [Overview of Rubric Grading Interface](/grader/rubric_grading/index)
 
    Our TA grading interface is elaborate, highly-featured, and
    customizable.  However, the interface is visually overwhelming to
-   new graders.  Some of our TA grading features are not adequately
-   tested by automated unit and end-to-end regression testing.
-   Finally, the performance of these webpages is problematic for large
-   courses due to inefficient database queries.  
-
+   new graders and some of our TA grading features are not adequately
+   tested by automated unit and end-to-end (Cypress) regression testing.
 
    [Open Issues related to TA Grading](https://github.com/Submitty/Submitty/issues?q=is%3Aopen+is%3Aissue+label%3A%22TA+Grading+%2F+TA+UI%22)
 
-   _Expected Outcomes_: The goal would be to
-   expand the automated testing of the TA Grading pages,
-   patch bugs uncovered by this improved testing,
-   refactor the existing code and SQL queries to improve performance, and
-   possibly propose and execute small user interface revisions.
+   _Expected Outcomes_: The goals of a project on TA grading would
+   include expantion of our automated testing of the TA Grading pages,
+   and to patch bugs uncovered by this improved testing.  The project may be
+   expanded in scope to additionally propose and execute small or modest user
+   interface revisions that enhance the TA experience.
    
-   _Skills & Experience Required_: Some programming experience, willingness to
-   learn web and database development.  Having served as a teaching
-   assistant or instructor with grading experience
+   _Skills & Experience Required_: Some programming experience,
+   willingness to learn web and database development and
+   the Cypress end-to-end automated testing framework.  Having served
+   as a teaching assistant or instructor with grading experience
    design will be beneficial.
 
-   _Possible Mentors_: Barb Cutler, Jensen Li
+   _Possible Mentors_: Barb Cutler, Nia Heermance
+
+   _GSoC Project Size_: 90 or 175 hours
+
+   _Difficulty Level_: medium
+
+
+2. **Refactor and Performance Improvements for the Manual/TA Rubric Grading Interface**
+
+   [Overview of Rubric Grading Interface](/grader/rubric_grading/index)
+
+   Note: This project may be combined with the previous project idea.
+   The Manual/TA rubric grading interface is elaborate, highly-featured, and
+   customizable; however, the performance of these webpages is
+   problematic for large courses due to inefficient database queries and
+   delays to load data from the server that could/should be asynchronous.
+   The manual/TA rubric pages could benefit from a significant
+   technology refactor to use Vue/Vite, for example.
 
-   _GSoC Project Size_: 350 hours
+   [Open Issues related to TA Grading](https://github.com/Submitty/Submitty/issues?q=is%3Aopen+is%3Aissue+label%3A%22TA+Grading+%2F+TA+UI%22)
+
+   _Expected Outcomes_:  A detailed software design for an organized, multi-stage
+   refactor of the manual/TA rubric pages and the execution/implementation of
+   a significant portion of the new design.  The project will likely require the
+   extension and/or updating of our automated end-to-end (Cypress) testing and patching
+   bugs uncovered by this testing.  The general interface for TA/Manual grading
+   should remain similar, but the project may include small user
+   interface revisions.
+
+   _Skills & Experience Required_:  Web and database development experience.
+   Experience with end-to-end automated testing (Cypress) and and having served
+   as a teaching assistant or instructor with grading experience
+   design is beneficial but not required.
+
+   _Possible Mentors_: Barb Cutler, Nia Heermance
+
+   _GSoC Project Size_: 175 or 350 hours
 
    _Difficulty Level_: medium or hard
 
-2. **Streamline instructor configuration of automated grading**
+
+
+3. **Streamline instructor configuration of automated grading**
 
    Currently, instructors must write a configuration as a `config.json`
    (and any necessary additional files) and upload or store these
@@ -83,111 +133,14 @@ Tracker](https://github.com/Submitty/Submitty/issues).
    assistant or instructor with experience in programming assignment
    design will be beneficial.
 
-   _Possible Mentors_: Barb Cutler, Jasmine Plum
-
-   _GSoC Project Size_: 350 hours
-
-   _Difficulty Level_: medium or hard
-   
-
-
-3. **Containers for Automated Grading**
-
-   Automated testing of student submitted software carries system and
-   security risks from malicious code but also simply buggy or inefficient
-   code.  Upper level coursework on advanced topics in computer
-   science including networking, operating systems, and kernel
-   development are especially complex challenges.
-
-   Submitty supports a variety of tools to securely test including
-   both sandboxing and containerization (Docker).  These tools must
-   manage and limit system resources (time, CPU, processes, memory,
-   files, system calls, sockets, etc.)
-
-   We provide container images appropriate for the most common
-   programming languages (Python, C/C++, Java) used in introductory
-   programming courses.
-
-   [https://hub.docker.com/u/submitty](https://hub.docker.com/u/submitty)
-
-   The next step is to facilitate the creation of instructor-customized
-   container images (with specific languages,
-   packages, databases, etc.).  Care must be taken to ensure small
-   container size and efficient performance.
-
-   Advanced project idea: We would like to use Submitty to
-   automatically test and grade homework assignments that require
-   modifications to the operating system kernel.  Before doing so on a
-   production machine, we need to do testing to ensure the right
-   controls are in place.
-
-   [Open Issues related to Container Autograding](https://github.com/Submitty/Submitty/labels/Docker%2FDockerImages)
-
-   _Expected Outcomes_: Increased usage of containerized autograding in all levels
-   of courses.  Reduced size and improved performance of containerized autograding
-   for our autograding tutorial examples and selected real-world use cases of autograding.
-
-   _Skills & Experience Required_: Upper level coursework experience in operating
-   systems and/or networking programming.  Experience with virtual
-   machines and Docker containerization is beneficial.
-
-   _Possible Mentors_: Barb Cutler, William Allen, Matthew Peveler
-
-   _GSoC Project Size_: 175 or 350 hours
-
-   _Difficulty Level_: medium or hard
-
-
-4. **Continuous Integration Testing**
-
-    Each commit and pull request to github launches continuous
-    integration testing of a portion of the Submitty code base.  We
-    would like to expand the code coverage of our unit and integration
-    tests.  Furthermore, some of our more complex end-to-end test case
-    are not currently run automatically with each GitHub pull request,
-    because the system setup is too time consuming and lengthy or
-    unpredictable running times affect test stability.  We would like to
-    optimize our use of GitHub Actions and caching so we can run
-    all of these test cases.
-
-   [Open Issues related to Continuous Integration](https://github.com/Submitty/Submitty/issues?q=is%3Aopen+is%3Aissue+label%3A%22Testing+%2F+Continuous+Integration+%28CI%29%22)
-
-    _Expected Outcomes_: Increased code coverage and stability of the Submitty CI test suite,
-    increased automation of CI testing, increased performance (decreased running time)
-    for CI testing through GitHub Actions.
-
-    _Skills & Experience Required_: Advanced programming experience, experience
-    with the relevant programming languages, tuning system performance, etc.
-
-   _Possible Mentors_: Shail Patel, William Allen, Matthew Peveler
-
-   _GSoC Project Size_: 175 or 350 hours
-
-   _Difficulty Level_: medium or hard
-
-
-5. **Website Security and Penetration Testing**
-
-   Submitty is responsible for securing confidential information.  It
-   is important that we regularly assess the security of this data.
-   Once a potential vulnerability is found, the system must be
-   promptly patched and documented to prevent future problems.
-
-   _Expected Outcomes_: Security risk assessment, identification and repair
-   of specific security vulnerabilities, expansion and creation of continuous
-   integration tools to prevent introduction of new vulnerabilities.
-
-   _Skills & Experience Required_: Computer security coursework and/or practical
-   experience searching for system vulnerabilities.
-
-   _Possible Mentors_: Chris Reed, Matthew Peveler
+   _Possible Mentors_: Barb Cutler, William Allen
 
    _GSoC Project Size_: 175 or 350 hours
 
    _Difficulty Level_: medium or hard
    
 
-6. **Instructional Materials and Documentation**
+4. **Instructional Materials and Documentation**
 
    We would like to reduce the learning curve for new instructors and
    provide more starter material for instructors teaching introductory
@@ -209,7 +162,7 @@ Tracker](https://github.com/Submitty/Submitty/issues).
    assistant or instructor with experience in programming assignment
    design will be beneficial.
 
-   _Possible Mentors_: Barb Cutler, Jasmine Plum
+   _Possible Mentors_: Barb Cutler, William Allen
 
    _GSoC Project Size_: 175 hours
 
diff --git a/_docs/developer/google_summer_of_code/index.md b/_docs/developer/google_summer_of_code/index.md
@@ -6,19 +6,27 @@ redirect_from:
 ---
 
 
-Submitty is proud to have been selected for participation in [Google
-Summer of Code](https://summerofcode.withgoogle.com/) for Summer 2023!
-This will be our fifth year participating in the program!  Please read
-the student project reports from previous summers linked below.
+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.
 
 
-[![](/images/GSoC-Vertical.png){:width="250px"}](https://summerofcode.withgoogle.com/)
-
+<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!_
+
+
 ## How to Apply to Submitty for Google Summer of Code 2023
 
 1. Read the GSOC information for contributors to confirm your eligibility:  
@@ -86,7 +94,18 @@ the student project reports from previous summers linked below.
      * [https://summerofcode.withgoogle.com/](https://summerofcode.withgoogle.com/)  
 
 &nbsp;  
-  
+
+
+
+## Google Summer of Code 2023
+
+* [Continuous Integration Optimization by Cameron Peterson](/developer/google_summer_of_code/2023_Cameron_Peterson)
+
+* [Website Security and Penetration Testing by Musaab Imran](/developer/google_summer_of_code/2023_Musaab_Imran)
+
+* [Docker Containers for Autograding Improvements by Saumya Borwankar](/developer/google_summer_of_code/2023_Saumya_Borwankar)
+
+
 
 ## Google Summer of Code 2022
 
