chore(report) : Add community bonding report

docs/2024/ci-scanner/index.md

@@ -6,7 +6,7 @@ slug: /2024/ci-scanner/
 <!--
 SPDX-License-Identifier: CC-BY-SA-4.0
 
-SPDX-FileCopyrightText: 2024 Rajul Jha <email.here>
+SPDX-FileCopyrightText: 2024 Rajul Jha <rajuljha49@gmail.com>
 -->
 
 ## Author
@@ -15,17 +15,33 @@ SPDX-FileCopyrightText: 2024 Rajul Jha <email.here>
 
 ## Contact info
 
-- [Email](mailto:email.here)
-- [LinkedIn](https://linkedin.com/in/my-user)
+- [Email](mailto:rajuljha49@gmail.com)
+- [LinkedIn](https://linkedin.com/in/rajuljha)
 
 ## Project title
 
 CI Scanner Improvements
 
 ## What's the project about?
 
-Insert Text Here
+To be able to easily and continuously scan packages with
+fossology checks in CI pipelines, a docker image
+(fossology/fossology:scanner) capable of running license checks (using
+nomos or ojo) and keyword and copyright scans is available.
+This project aims to improve the CI Scanner Image in
+various aspects and numerous quality of life improvements, like
+highlighting the exact location of violation, ability to customize the
+keywords used by the scanner, and improving user experience – allow
+whitelisting from a custom location and ability to download and scan
+dependencies
 
 ## What should be done?
 
-What are the plans for the project?
+1. Highlight the exact location (line number) of a violation during
+reporting
+2. Allow users to customize keyword scanning using their own
+keyword.conf
+3. Allow users to store allowlist.json file elsewhere (currently, it is
+required to be present at the root of the project)
+4. Allow users to download and scan dependencies by providing a path
+at CI/CD pipeline trigger.

docs/2024/ci-scanner/updates/2023-05-30.md

@@ -5,21 +5,39 @@ author: Rajul Jha
 <!--
 SPDX-License-Identifier: CC-BY-SA-4.0
 
-SPDX-FileCopyrightText: 2024 Rajul Jha <email.here>
+SPDX-FileCopyrightText: 2024 Rajul Jha <rajuljha49gmail.com>
 -->
 
-# Meeting 1
+## Meeting 1
 
-*(May 30,2024)*
+*(May 7, 2024)*
 
-## Attendees:
+### Discussion:
+- Could not attend due to family emergency.
 
-## Discussion:
 
-# Meeting 2
+## Meeting 2
 
-*(May 18,2023)*
+*(May 9, 2024)*
 
-## Attendees:
+### Discussion:
+- I gave my introduction in the meeting.
+- Got to know my mentors and colleagues.
 
-## Discussion:
+## Meeting 3
+
+*(May 16, 2024)*
+
+### Discussion:
+- Discussed a problem in setting up my development environment on mac.
+- Contributors shared their weekly updates.
+- Discussed and decided time for weekly project specific meetings.
+
+## Meeting 4
+
+*(May 23, 2024)*
+
+### Discussion:
+- Everyone had final discussions on projects.
+- Made sure everyone was on the same page.
+- Understood the fossology codebase and asked few doubts on how to approach the line number task to mentors.