Skip to content

Commit a5d26a4

Browse files
Merge pull request #357 from rajuljha/updates/week9_10
chore(docs): Add week 9,10 atarashi docs Reviewed-by: shaheem.azmal@siemens.com
2 parents ee1108b + a4bd0e3 commit a5d26a4

File tree

3 files changed

+111
-0
lines changed

3 files changed

+111
-0
lines changed
Lines changed: 52 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,52 @@
1+
---
2+
title: Week 9
3+
author: Rajul Jha
4+
tags: [gsoc25, Atarashi]
5+
---
6+
7+
<!--
8+
SPDX-License-Identifier: CC-BY-SA-4.0
9+
SPDX-FileCopyrightText: 2025 Rajul Jha <rajuljha49@gmail.com>
10+
-->
11+
12+
# Week 9
13+
14+
*(July 24, 2025 - July 30, 2025)*
15+
16+
## Overview
17+
18+
This week was focused on integrating the **core logic of Atarashi** into **FOSSology**. The work involved interacting with various components such as the Atarashi wrapper, FOSSology’s agent structure, and the backend database handling mechanisms.
19+
20+
---
21+
22+
## Development Progress
23+
24+
* Worked on the **Atarashi wrapper for FOSSology**:
25+
* Integrated the core classification logic.
26+
* Ensured agent-specific parameters were properly parsed and passed.
27+
* Explored and understood the relevant **database tables** where Atarashi’s output will be stored.
28+
* Investigated and adapted existing **database handler functionalities** to support Atarashi's results.
29+
30+
---
31+
32+
## Meeting
33+
34+
* I was **unable to attend the weekly sync meeting** this week due to a **doctor's appointment at AIIMS Delhi**.
35+
* Underwent a scheduled **endoscopy** on July 30.
36+
* Had a follow-up **consultation** on July 31.
37+
38+
---
39+
40+
## Status
41+
42+
* Significant progress made in aligning Atarashi’s logic with FOSSology’s agent framework.
43+
* Database integration groundwork laid out, enabling result persistence in future iterations.
44+
* Missed the team meeting, but will catch up via notes or mentor communication.
45+
46+
---
47+
48+
## Next Steps
49+
50+
* Finalize the database integration and test the complete pipeline.
51+
* Work on the UI form for triggering Atarashi with agent/similarity options.
52+
* Sync up with mentors to align on next milestones and get feedback on current progress.
Lines changed: 59 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,59 @@
1+
---
2+
title: Week 10
3+
author: Rajul Jha
4+
tags: [gsoc25, Atarashi]
5+
---
6+
7+
<!--
8+
SPDX-License-Identifier: CC-BY-SA-4.0
9+
SPDX-FileCopyrightText: 2025 Rajul Jha <rajuljha49@gmail.com>
10+
-->
11+
12+
# Week 10
13+
14+
*(July 31, 2025 - August 06, 2025)*
15+
16+
## Overview
17+
18+
This week marked a significant milestone in the project — the **core integration of the Atarashi agent into FOSSology** was successfully completed and tested. The Atarashi binary is now being **built as part of the FOSSology build process** and can be **invoked as a standalone agent** within the framework.
19+
20+
---
21+
22+
## Development Progress
23+
24+
* **Successfully integrated the Atarashi agent** into the FOSSology system.
25+
* The agent binary is now **compiled during FOSSology's build**.
26+
* It executes correctly with the input data and logs outputs as expected.
27+
28+
![image](/img/atarashi/atarashi_cli_output_1.png)
29+
30+
* Validated the **end-to-end pipeline** from scheduling to execution.
31+
32+
---
33+
34+
## Meeting
35+
36+
* Had a detailed discussion with the mentors regarding the agent configuration approach.
37+
* **Key decision**:
38+
* The user will not configure sub-agents (e.g., tfidf, Ngram) from the Atarashi binary.
39+
* The user will only select Atarashi as a license scanner in FOSSology.
40+
* Agents inside of atarashi will be controlled via an `atarashi.conf` file within the agent’s directory.
41+
* Direction agreed upon: **Atarashi will be treated as a singular agent**, and the best-performing internal logic will be selected automatically.
42+
43+
---
44+
45+
## Status
46+
47+
* Core agent integration complete.
48+
* Binary built with FOSSology.
49+
* Basic execution tested successfully.
50+
* Alignment achieved with mentors on configuration flow.
51+
52+
---
53+
54+
## Next Steps
55+
56+
* Refactor Atarashi as a **single-agent interface** with no user-exposed options.
57+
* Move agent/similarity selection logic into `atarashi.conf`.
58+
* Implement logic to **select the best-performing agent internally by default**.
59+
* Begin working on UI integration to expose Atarashi agent selection in a clean and simple way.
318 KB
Loading

0 commit comments

Comments
 (0)