revision

Author: oliiso

Diff for: _docs/developer/google_summer_of_code/2024_Sophia_Oliinik.md

@@ -4,23 +4,22 @@ category: Developer > Google Summer of Code 2024
 ---
 
 ## Overview of project:
-My summer GSoC 2024 project title is Enhancing User Interface for Viewing Grades. While originally, this was intended to focus on the Rainbow Grades presentation, I also wanted to implement and update more visual representation for statistics about homework. It was decided that I should pivot a little more in the direction of gradeable specific statistics page, and bringing more updates to that. Because of this, I was able to add some updated user interface design to Rainbow Grades and the Statistics page for gradeables over the course of this summer. 
-
+Through this summer, I worked on my 2024 Google Summer of Code (GSoC) project titled "Enhancing User Interface for Viewing Grades." Initially, the project aimed to improve the presentation of Rainbow Grades. However, I also wanted to incorporate and update visual representations of statistics related to homework. It was decided that I should pivot slightly towards developing a gradeable-specific statistics page and bring more updates to it. As a result, I was able to enhance the user interface design for both Rainbow Grades and the statistics page for gradeables throughout the summer.
 
 
 ## Outside of programming
-My initial weeks were spent understanding the code base that Submitty has, along with the structure of the system. Submitty implemented a great system for continuous integration and check-ins for the summer contributors. This was successful through the daily meetings that we had. This brought a great opportunity for showing your work, getting second opionions, asking questions, keeping things accountable, and seeing where other contributors were at with their work. Another element of our meetings included demonstrating our work, and recieving feedback from the team. I was able to do so with a few of my projects. It was a great way to learn both what worked, and what changes were needed. Along with this, I also got feedback from my mentor through the summer. Through video calls and messaging, we discussed barriers I came across, and status updates. These were very helpful to me in my process of working on Submitty through the summer, and I was able to learn a lot.
+In the initial weeks, I focused on understanding the Submitty codebase and the system's structure. Submitty has implemented an effective system for continuous integration and check-ins for summer contributors, facilitated by our daily meetings. These meetings provided an excellent opportunity to showcase work, receive second opinions, ask questions, and maintain accountability. Additionally, the meetings included demonstrations of our work and feedback from the team, which I utilized for a couple of my projects. This process was invaluable for identifying what worked and what needed improvement. Throughout the summer, I also received feedback from my mentor via video calls and messaging. These discussions addressed barriers I encountered and provided status updates, which were instrumental in my progress and learning while working on Submitty.
 
 
 
 ## Pull Request work:
-Below are the pull requests that I worked on this summer. The main area of issues included Rainbow Grades UI and instructor grading data presentation. These links include documentation PR's, a PR to the Submitty repo, and PRs to the RaibowGrades repo. 
+Below are the pull requests I worked on this summer. The primary focus areas included the user interface for Rainbow Grades and the presentation of instructor grading data. These links encompass documentation pull requests, a pull request to the Submitty repository, and pull requests to the Rainbow Grades repository.
 
-- [#77](https://github.com/Submitty/RainbowGrades/pull/77) [Feature:RainbowGrades] Adding hover text to rainbow grades bad status cells
-    * This was one of the first additions I brought to Submitty. It added a feature to the rainbow grades gradebook page that implemented a hover text box for students that had a "bad status" on a homework. This brings more attention that the student can look into why they have a bad status on the assignment, and it brings convenience for instructors in their larger gradebooks to see who has a bad status and on what assignment with just hovering their mouse over the cell. 
+- [#77](https://github.com/Submitty/RainbowGrades/pull/77) [Feature:RainbowGrades] Adding hover text to Rainbow Grades bad status cells
+    * This was one of the first additions I brought to Submitty. It added a feature to the Rainbow Grades gradebook page that implemented a hover text box for students that had a "bad status" on a homework. This brings more attention that the student can look into why they have a bad status on the assignment, and it brings convenience for instructors in their larger gradebooks to see who has a bad status and on what assignment with just hovering their mouse over the cell. 
 
 - [#81](https://github.com/Submitty/RainbowGrades/pull/81) [Feature:RainbowGrades] Adding link to gradeable title
-    * Another implementation in the rainbow grades repository where I added a feature to the rainbow grades gradebook page that added a link in the gradeable titles. This was added to only student gradebooks, and was a feature that will bring convenience to students when they are viewing their rainbow grades grade report. Now, when the student sees their grade and wants to see the details of they they recieved that grade, they can click on the title on the grade report, and they are taken to that page. 
+    * Another implementation in the Rainbow Grades repository where I added a feature to the Rainbow Grades gradebook page that added a link in the gradeable titles. This was added to only student gradebooks, and was a feature that will bring convenience to students when they are viewing their Rainbow Grades grade report. Now, when the student sees their grade and wants to see the details of they they recieved that grade, they can click on the title on the grade report, and they are taken to that page. 
 
 - [#10687](https://github.com/Submitty/Submitty/pull/10687) [Feature:TAGrading] Manual Grading Histogram
     * The statistics page had tabs and data about total scores, autograding scores, and component scores, but not of manual grading scores. In this PR I added a page with a histogram of just manual grades with its data along the bottom of the histogram screen. This was a good way to learn about how data is stored.
@@ -58,4 +57,6 @@ Having this review processes this summer really taught me a lot as a new contrib
 
 
 ## Acknowledgments:
-I am very greatful for this summer opportunity to work with Submitty. Through these weeks, I was able to grow a lot as a programmer, team member, and mentee. The daily meetings were an immense help in learning how to communicate where you are at with your work, and a great place to learn to ask for help. Through these meetings I was able to grow a lot as a professional. Working on the code base itself was also a large part of how I grew this summer. I was able to take time to understand previous code that was written, and consider how to bring the changes needed in a consistent way. Halfway through the summer, I had a pivot in the focus of my project, it helped teach me to be adaptable and to learn new parts of Submitty that I was not previously accustomed to. Going through the review process of getting a pull request approved was also a great process to learn what areas are working, and what areas I can improve my code. Along with this, being able to review other contributors PR's was a great reference to be able to learn how others were improving the system, and the process they went through to bring their implementations. I want to thank Barb Cutler, Jaeseok Kang, Cameron Peterson, and Preston Carman for their mentorship through my summer with Submitty. 
+I am very grateful for the opportunity to work with Submitty this summer. Throughout these weeks, I experienced significant growth as a programmer, team member, and mentee. The daily meetings were immensely helpful in learning how to communicate my progress and provided a supportive environment for asking questions. These interactions greatly contributed to my professional development.
+Working directly with the codebase was also a crucial aspect of my growth this summer. I dedicated time to understanding the existing code and considered how to implement necessary changes consistently. Halfway through the summer, I pivoted the focus of my project, which taught me to be adaptable and explore new areas of Submitty that I was not previously familiar with.
+The pull request review process was another valuable learning experience, allowing me to identify strengths and areas for improvement in my code. Additionally, reviewing other contributors' pull requests provided insights into their approaches and the processes they followed to enhance the system. I want to extend my gratitude to Barb Cutler, Jaeseok Kang, Cameron Peterson, and Preston Carman for their mentorship throughout my summer with Submitty.