chore(report): SPDX Expression weeks 1, 2, 3 & 4 reports

Author: Akashsah2003

docs/2024/spdx-expression/updates/2024-05-28.md

@@ -0,0 +1,45 @@
+---
+title: Week 1
+author: Akash Sah
+tags: [gsoc24, spdx-expression]
+---
+
+<!--
+SPDX-License-Identifier: CC-BY-SA-4.0
+
+SPDX-FileCopyrightText: 2024 Akash Sah <akashsah2003@gmail.com>
+-->
+
+# Week 1 meeting and activities
+
+_(May 28,2024)_
+
+## Attendees:
+
+- [Akash Sah](https://github.com/Akashsah2003)
+- [Gaurav Mishra](https://github.com/GMishx)
+- [Shaheem Azmal M MD](https://github.com/shaheemazmalmmd)
+- [Dearsh Oberoi](https://github.com/deo002)
+- [Abhishek Kumar](https://github.com/abhi-kumar17871)
+
+## Discussions
+
+### Prototype Presentation
+
+- Presented a prototype for scanning expressions with OJO.
+- Initially, I was storing expressions directly as strings.
+- Received feedback that storing expressions as strings could not allow modifications.
+- Recieved suggestion to store license names as their references (licenseId) and the relationships between them (operators).
+
+### Schema Proposal
+
+- Was asked to propose a schema for storing license expressions.
+- Inquired if using a graph database like Neo4j would be suitable.
+- It was considered a good idea but mentors suggested not to use it as mixing two databases (PostgreSQL and Neo4j) would complicate things.
+
+
+## Activities
+
+- Researched various methods to store license expressions.
+- Found that an Abstract Syntax Tree (AST) is a good way to store expressions.
+- Proposed two types of [schema](https://docs.google.com/document/d/1xYONSMBMQsLsGG3IIHD0gwJA0OP2-xPecLIaisIvupM/edit?usp=sharing) for storing license expressions.

docs/2024/spdx-expression/updates/2024-06-04.md

@@ -0,0 +1,43 @@
+---
+title: Week 2
+author: Akash Sah
+tags: [gsoc24, spdx-expression]
+---
+
+<!--
+SPDX-License-Identifier: CC-BY-SA-4.0
+
+SPDX-FileCopyrightText: 2024 Akash Sah <akashsah2003@gmail.com>
+-->
+
+# Week 2 Meeting and Activities
+
+_(June 4, 2024)_
+
+## Attendees:
+
+- [Akash Sah](https://github.com/Akashsah2003)
+- [Gaurav Mishra](https://github.com/GMishx)
+- [Shaheem Azmal M MD](https://github.com/shaheemazmalmmd)
+- [Dearsh Oberoi](https://github.com/deo002)
+- [Abhishek Kumar](https://github.com/abhi-kumar17871)
+
+## Discussions
+
+### Schema Presentation
+
+- Presented the two schemas for storing license expressions.
+- Mentors suggested that storing AST in JSONB was the better idea and to move forward with it.
+
+## Activities
+
+- Modified the OJO code base to scan expressions using regex and store expressions as AST in the database.
+- Worked on creating UI components to display and edit expressions. 
+
+## ScreenShots
+### License Expression Table
+![License Expression Table](/img/spdx-expression/licenseExpressionTable.png)
+### License Expression Schema
+![License Expression Schema](/img/spdx-expression/licenseExpressionSchema.png)
+### Edit Expression Modal
+![Edit Expression Modal](/img/spdx-expression/editExpressionModal.png)

docs/2024/spdx-expression/updates/2024-06-11.md

@@ -0,0 +1,54 @@
+---
+title: Week 3
+author: Akash Sah
+tags: [gsoc24, spdx-expression]
+---
+
+<!--
+SPDX-License-Identifier: CC-BY-SA-4.0
+
+SPDX-FileCopyrightText: 2024 Akash Sah <akashsah2003@gmail.com>
+-->
+
+# Week 3 Meeting and Activities
+
+_(June 11, 2024)_
+
+## Attendees:
+
+- [Akash Sah](https://github.com/Akashsah2003)
+- [Gaurav Mishra](https://github.com/GMishx)
+- [Shaheem Azmal M MD](https://github.com/shaheemazmalmmd)
+- [Dearsh Oberoi](https://github.com/deo002)
+- [Abhishek Kumar](https://github.com/abhi-kumar17871)
+
+## Discussions
+
+### Presentation of Work
+
+- Presented my work on storing and displaying expressions.
+- Initially, expressions were displayed as a separate table in the UI.
+- Feedback: Expressions should be displayed in the same table as licenses.
+- When changing the license of a license expression, only detected licenses should be shown as options, rather than showing all licenses.
+- Inquired about how to store License Text, Acknowledgement, and Comments for licenses that are part of a license expression.
+- I proposed storing these in the AST as properties of the node.
+- Currently, they are stored in the `clearing_event` table.
+- Suggestion: Storing them in `clearing_event` is a good idea as it can serve as an audit log to track changes.
+- There should be a way for users to create an expression for a particular file with no existing expression.
+
+## Activities
+
+- Displayed license expressions in the same table as licenses.
+
+  ### License Expressions in the Same Table
+  ![License Expressions in the Same Table](/img/spdx-expression/licenseDecisionsTable.png)
+
+- Allowed users to create an expression for a file with no detected expression.
+
+  ### Create Expression for File with No Detected Expression
+  ![Create Expression for File with No Detected Expression](/img/spdx-expression/userExpressionDecision.png)
+
+- Allowed users to change the License Text, Acknowledgement, and Comment for licenses that are part of a license expression.
+
+  ### Change License Text, Acknowledgement, and Comment
+  ![Change License Text, Acknowledgement, and Comment](/img/spdx-expression/customLicenseText.png)

docs/2024/spdx-expression/updates/2024-06-18.md

@@ -0,0 +1,44 @@
+---
+title: Week 4
+author: Akash Sah
+tags: [gsoc24, spdx-expression]
+---
+
+<!--
+SPDX-License-Identifier: CC-BY-SA-4.0
+
+SPDX-FileCopyrightText: 2024 Akash Sah <akashsah2003@gmail.com>
+-->
+
+# Week 4 Meeting and Activities
+
+_(June 18, 2024)_
+
+## Attendees:
+
+- [Akash Sah](https://github.com/Akashsah2003)
+- [Gaurav Mishra](https://github.com/GMishx)
+- [Shaheem Azmal M MD](https://github.com/shaheemazmalmmd)
+- [Dearsh Oberoi](https://github.com/deo002)
+- [Abhishek Kumar](https://github.com/abhi-kumar17871)
+
+## Discussions
+
+### Presentation of UI Changes
+
+- Presented the changes made in the UI.
+- Received feedback: Currently, it is not possible to add more than two licenses in a group within the license expression.
+- Recieved suggestion: The button for creating a license expression (if it does not exist) should be beside the user decision.
+- Informed the mentors that I will start working on the report generation part of the project.
+
+## Activities
+
+- Created functionality to allow licenses and groups to be added anywhere and option to remove license. Now, more than two licenses can be added to a group.
+
+  ### Adding More Than Two Licenses in a Group
+  ![Adding More Than Two Licenses in a Group](/img/spdx-expression/addLicense.png)
+
+  ### Removing a License in License Expression
+  ![Removing a License in License Expression](/img/spdx-expression/removeLicense.png)
+
+- Started working on report generation for SPDX Tag Value and SPDX CSV.