| 2 weeks |
June 9 - June 23 |
• Refactoring the SW360 FOSSology connector to utilize RESTful endpoints (v2). |
|
|
|
| • Implementing basic functionality for file uploads (with job triggering) and report retrieval. |
• Basic integration is operational using v2 endpoints, demonstrated by triggering a scan and retrieving an SPDX report linked to a release. |
Completed. |
Done and Completed, will be raising a PR for this |
|
|
| 3 weeks |
June 24 - July 15 |
• Integrating pre-upload checksum computation (e.g., SHA-1) into the SW360 REST API. |
|
|
|
| • Implementing file search functionality using the /filesearch v2 endpoint. |
|
|
|
|
|
| • Updating the SW360 data model to store file checksums and corresponding FOSSology upload IDs. |
|
|
|
|
|
| • Enhancing the reuse functionality by leveraging FOSSology's "Reuser" agent capabilities, ensuring that clearing decisions and related metadata are reused as described. |
Duplicating detection and reuse are verified, enabling reuse of existing scan data for identical file content without needing immediate UI updates |
Completed. |
Partially done, 1/2 features are still left to implement. |
|
|
| 1 week (or 1.5 if can’t complete, will manage in frontend) |
July 16 - July 23 |
• Enhancing the SW360 REST API to accept user-configurable scanning agent options via API calls. |
|
|
|
| • Modifying backend logic to construct appropriate JSON payloads for triggering scans. |
|
|
|
|
|
| • Validating the integration by triggering scans with various agent configurations. |
Customizable scan options are available via the SW360 REST API. (UI changes can be deferred to a later phase.) |
Completed |
|
|
|
| MID TERM EVAL 🫡 |
July 14 - 16 |
|
|
|
|
| 2 weeks |
July 24 - Aug 10 (delaying a bit coz new semester will begin from 2 Aug, will need 1/2 days for settling down in college and getting room. New sem starts on Aug 2 |
• Extending the SW360 REST API to support generation of reports in multiple formats via the /report endpoint. |
|
|
|
| • Developing the download and attachment mechanism within the API to associate reports with the corresponding release. |
|
|
|
|
|
| • Updating storage to include FOSSology metadata such as upload IDs and report URLs, and include the upload ID in the Release’s summary response. |
• Users (via API) can generate, download, and retrieve diverse reports, with essential FOSSology metadata stored for traceability. |
Completed |
|
|
|
| 2 weeks |
Aug 11 - Aug 25 |
Frontend Integration |
Noice Frontend to work properly with the updated backend |
To be done with the org after GSoC’25 |
|
| 2 weeks |
Aug 26 - End (might get delayed a bit owing to new college session) |
• Performing comprehensive unit, integration, and performance tests in a staging environment. |
|
|
|
| • Validating error handling for network issues, large file uploads, and concurrent scans.Updating technical documentation (developer guides, API documentation) and preparing migration notes. |
|
To be done with the org after GSoC’25 |
|
|
|
| FINAL EVAL 🙏 |
|
|
|
|
|