Merge pull request #315 from Prakash-Mishra-9ghz/week-progress

docs(blog): Add project details, Community Bonding, Week 1 & 2 blog posts

Author: GMishx

docs/2025/oss-review-toolkit/index.md

@@ -2,4 +2,53 @@
 sidebar_position: 6
 title: Introduction
 slug: /2025/oss-review-toolkit/
----
+---
+<!--
+SPDX-License-Identifier: CC-BY-SA-4.0
+
+SPDX-FileCopyright Text: 2025 Prakash Mishra <prakashmishra9921@gmail.com>
+-->
+
+## Author:
+
+[Prakash Mishra](https://github.com/Prakash-Mishra-9ghz)
+
+## Contact Info:
+
+- [Email](mailto:prakashmishra9921@gmail.com)
+- [LinkedIn](https://www.linkedin.com/in/prakash-mishra-0a56472b9/)
+
+## Project Title:
+
+Integrating OSS Review Toolkit with FOSSology
+
+## What's the project about?
+
+This project aims to integrate FOSSology — a powerful license scanning tool — into the OSS Review Toolkit (ORT), a platform widely used for analyzing software dependencies.
+By developing a dedicated scanner plugin within ORT, the integration will enable users to seamlessly leverage FOSSology’s license detection capabilities as part of ORT’s automated workflows.
+
+
+## Key Deliverables
+
+The project scope includes the following key tasks:
+
+### Introduce NOMOS as an ORT Scanner Plugin ###
+Implement a new scanner plugin in ORT that integrates NOMOS, FOSSology’s primary license analysis agent.
+Ensure the plugin adheres to ORT's existing scanner interface and lifecycle.
+
+### Configure Scanning Parameters ###
+Define and expose configuration options in ORT to support custom NOMOS parameters (e.g., scanning modes, agent-specific options).
+Ensure the scanning behavior is easily customizable by end users via configuration files.
+
+###  Integration with FOSSology Server ###
+Implement communication with a standalone FOSSology server using its REST API in ORT.
+Handle job creation, status polling, and result retrieval through HTTP endpoints.
+Ensure reliable handling of asynchronous scan jobs and large file uploads.
+
+### Enable Customizable FOSSology Integration ###
+Allow users to configure: Server URL and credentials
+
+
+### Add Unit Tests ###
+Write comprehensive unit test cases to validate plugin functionality.
+Conform to ORT's test architecture and quality standards.

docs/2025/oss-review-toolkit/updates/2025-06-02.md

@@ -0,0 +1,31 @@
+---
+title: Community Bonding
+author: Prakash Mishra
+---
+<!--
+SPDX-License-Identifier: CC-BY-SA-4.0
+
+SPDX-FileCopyrightText: 2025 Prakash Mishra <prakashmishra9921@gmail.com>
+-->
+
+# Comunity Bonding Meetings and Activities
+
+## Community Meeting 1 (Introductory)
+
+*(May 12, 2025)*
+
+### Attendees
+
+Complete FOSSology Community including 
+- Org admins
+- Mentors of all the projects
+- Contributors for GSoC 2025
+
+### Discussion
+
+- This session marked the beginning of the GSoC 2025 community bonding phase.
+- It served as an opportunity for contributors, mentors, and org admins to connect and lay the groundwork for the upcoming summer.
+- Everyone took turns introducing themselves, highlighting their backgrounds and prior involvement with open source.
+- The FOSSology team shared key insights into the project structure, goals, and how the community collaborates.
+- Slack was chosen as the main channel for staying in touch and coordinating activities.
+- The meeting wrapped up with an open Q&A to ensure clarity and address early questions from participants.

docs/2025/oss-review-toolkit/updates/2025-06-07.md

@@ -0,0 +1,41 @@
+---
+title: Week 1
+author: Prakash Mishra
+---
+<!--
+SPDX-License-Identifier: CC-BY-SA-4.0
+
+SPDX-FileCopyrightText: 2025 Prakash Mishra <prakashmishra9921@gmail.com>
+-->
+
+# Week 01 Meetings and Activities
+
+## Integration of ORT with FOSSology Sync Meeting 1
+
+*(June 2, 2025)*
+
+### Attendees
+
+- [Prakash Mishra](https://github.com/Prakash-Mishra-9ghz)
+- [Kaushlendra Pratap](https://github.com/Kaushl2208)
+- [Gaurav Mishra](https://github.com/gmishx)
+
+### Discussion
+
+- Attended the first sync meeting with mentors to plan the initial phase of ORT and FOSSology integration.
+- Mentors suggested reviewing the ORT developer guide and understanding how tools like ScanCode integrate with ORT.
+- With a basic understanding now in place, I’ve identified specific tasks I’ll start working on to begin the work in the upcoming weeks.
+
+
+### Progress
+
+- Read through the ORT developer guide to understand its architecture and how scanner integrations are structured.
+- Reviewed documentation for ScanCode to learn from existing scanner integrations.
+- Interacted with the ORT community via Slack to introduce myself and seek guidance. The community shared helpful documentation.
+- Mentor also advised brushing up on Kotlin, as ORT is primarily written in it. Spent time revisiting Kotlin basics and common patterns used in the project.
+
+
+### Next Steps
+
+- Continue studying relevant plugins and Kotlin code to guide implementation.
+- Raise any blockers in the next sync meeting or community channels.

docs/2025/oss-review-toolkit/updates/2025-06-14.md

@@ -0,0 +1,42 @@
+---
+title: Week 2
+author: Prakash Mishra
+---
+<!--
+SPDX-License-Identifier: CC-BY-SA-4.0
+
+SPDX-FileCopyrightText: 2025 Prakash Mishra <prakashmishra9921@gmail.com>
+-->
+
+# Week 02 Meetings and Activities
+
+## Integration of ORT with FOSSology Sync Meeting 2
+
+*(June 9, 2025)*
+
+### Attendees
+
+- [Prakash Mishra](https://github.com/Prakash-Mishra-9ghz)
+- [Kaushlendra Pratap](https://github.com/Kaushl2208)
+
+### Discussion
+
+- Participated in the second weekly sync meeting with mentor.
+- Shared updates on my interaction with the ORT community and the guidance I received around integrating external scanners.
+- Brought up a key question about how Nomos works as a standalone tool and whether it can be invoked directly.
+- Mentor pointed me to the right resources for understanding Nomos as a standalone tool — including how to build it, use its flags, and interpret its output.
+
+### Progress
+- Successfully built Nomos as a standalone tool on my local system.
+- Tested Nomos independently on sample files to understand its CLI interface and license detection capabilities.
+- Ran Nomos with different flags to evaluate its functionality and output formats:
+  - `-J`: Produces output in **JSON**, ideal for structured parsing.
+  - `-S`: Outputs highlighting information in **plain text**, showing the locations of detected licenses and keywords within files — including details like the position (at), length, and index of each match
+  - `-l`: Ensures full file paths are included in the output.
+  - `-c` / `-d`: Used for specifying config and scan directories respectively.
+- This hands-on testing gave me a clear idea of how to invoke Nomos programmatically and parse its results for integration.
+
+### Next Steps
+
+- Begin creating the initial skeleton or wrapper code to invoke Nomos from within the ORT scanning pipeline.
+- Continue referring to existing ORT scanner plugin implementations for structure and integration best practices.

docs/2025/oss-review-toolkit/updates/_category_.json

@@ -0,0 +1,4 @@
+{
+    "label": "Weekly Updates",
+    "position": 2
+}