Merge pull request fossology#209 from Akashsah2003/chore/report/commu…

…nity-bonding

chore(report): Community bonding report spdx expression project

docs/2024/spdx-expression/index.md

@@ -6,7 +6,7 @@ slug: /2024/spdx-expression/
 <!--
 SPDX-License-Identifier: CC-BY-SA-4.0
 
-SPDX-FileCopyrightText: 2024 Akash Sah <email.here>
+SPDX-FileCopyrightText: 2024 Akash Sah <akashsah2003@gmail.com>
 -->
 
 ## Author
@@ -15,17 +15,31 @@ SPDX-FileCopyrightText: 2024 Akash Sah <email.here>
 
 ## Contact info
 
-- [Email](mailto:email.here)
-- [LinkedIn](https://linkedin.com/in/my-user)
+- [Email](mailto:akashsah2003@gmail.com)
+- [LinkedIn](https://www.linkedin.com/in/akashsah2003/)
 
 ## Project title
 
 SPDX License Expression Support
 
 ## What's the project about?
 
-Insert Text Here
+This project aims to support the detection and reporting of SPDX License Expressions. Currently, FOSSology uses regular expressions, full-text match, and fuzzy match to scan licenses, stores all types of license expressions as a list of licenses, and wrongly classifies them as conjunctive licenses or disjunctive licenses. It also stores license exceptions as licenses and does not differentiate exceptions from licenses.
+
+In the project, I will be working on scanning license expressions using regular expressions with Ojo, storing them in the database, creating UI components to see license expressions in the file clearing page, and finally updating reports to export the expressions in the correct format.
 
 ## What should be done?
 
-What are the plans for the project?
+1. Detect and validate license expressions
+    - Develop algorithms for accurately detecting SPDX license expressions and validating them.
+
+2. Store license expressions and metadata in database
+    - Design and implement a database schema to store complete license expressions and associated metadata.
+    - Develop mechanisms for efficient retrieval and manipulation of license expression data.
+
+3. Improve User Interface
+    - Create intuitive UI components to visualize and manage license expressions.
+    - Allow users to interactively create and edit license expressions.
+
+4. Update Report Generation:
+    - Enhance and correct SPDX report generation functionality to accurately represent license expressions.

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

@@ -0,0 +1,67 @@
+---
+title: Community Bonding Report
+author: Akash Sah
+---
+<!--
+SPDX-License-Identifier: CC-BY-SA-4.0
+
+SPDX-FileCopyrightText: 2024 Akash Sah <akashsah2003@gmail.com>
+-->
+
+# Community Bonding Report
+
+
+## Meeting 1
+
+*(May 7, 2024)*
+
+### Discussion:
+- Mentors and contributors introduced themselves.
+- Agreed on the time and platform for general weekly meetings.
+
+
+## Meeting 2
+
+*(May 9, 2024)*
+
+### Discussion:
+- Mentors emphasized the importance of communication in open source.
+- Held a general Q&A session.
+
+
+## Week 1 Activities
+
+*(May 9, 2024 - May 15, 2024)*
+
+- Explored parts of the codebase related to the project and UI.
+- Resolved a [bug](https://github.com/fossology/fossology/pull/2738) found in the user interface.
+
+
+## Meeting 3
+
+*(May 16, 2024)*
+
+### Discussion:
+- Contributors provided updates on their progress.
+- Mentors checked if everyone was able to set up their local development environment.
+
+
+## Week 2 Activities
+
+*(May 16, 2024 - May 22, 2024)*
+
+- Began working on the prototype and furthered my understanding of FOSSology.
+- Engaged with the community and resolved a [query](https://github.com/fossology/fossology/discussions/2735) in the discussions.
+
+
+## Meeting 4
+
+*(May 23, 2024)*
+
+### Discussion:
+- Contributors shared their progress.
+- Mentors encouraged making small contributions to gain a better understanding of the project.
+- Finalized timings for project-specific weekly meetings.
+
+
+This report summarizes my activities and interactions during the GSoC community bonding period.