<feed xmlns="http://www.w3.org/2005/Atom"> <id>swastkk.github.io/blogs/</id><title>Blogs | Swastik</title><subtitle>A Blog website for technical writing.</subtitle> <updated>2024-09-16T07:03:21+00:00</updated> <author> <name>Swastik Sharma</name> <uri>swastkk.github.io/blogs/</uri> </author><link rel="self" type="application/atom+xml" href="swastkk.github.io/blogs/feed.xml"/><link rel="alternate" type="text/html" hreflang="en" href="swastkk.github.io/blogs/"/> <generator uri="https://jekyllrb.com/" version="4.3.3">Jekyll</generator> <rights> © 2024 Swastik Sharma </rights> <icon>/assets/img/favicons/favicon.ico</icon> <logo>/assets/img/favicons/favicon-96x96.png</logo> <entry><title>Coding Period Week 4 &amp; 5</title><link href="swastkk.github.io/blogs/posts/coding-week-4-5/" rel="alternate" type="text/html" title="Coding Period Week 4 &amp;amp; 5" /><published>2024-06-30T01:55:00+00:00</published> <updated>2024-06-30T01:55:00+00:00</updated> <id>swastkk.github.io/blogs/posts/coding-week-4-5/</id> <content src="swastkk.github.io/blogs/posts/coding-week-4-5/" /> <author> <name>swastik</name> </author> <category term="python" /> <category term="package" /> <category term="summary" /> <category term="tests" /> <category term="assembly" /> <summary> Week 4 &amp;amp; 5 progess (June 17 - June 30) These two weeks were crucial for the project as the mid-term evaluation approached, and we needed to cover most of the work. We held a special meeting in addition to our weekly status call, where my mentors and I discussed the project in a more detailed and thorough manner. After receiving valuable feedback from my mentors on my PR, I began working o... </summary> </entry> <entry><title>Coding Period Week 3</title><link href="swastkk.github.io/blogs/posts/coding-week-3/" rel="alternate" type="text/html" title="Coding Period Week 3" /><published>2024-06-16T01:55:00+00:00</published> <updated>2024-06-16T01:55:00+00:00</updated> <id>swastkk.github.io/blogs/posts/coding-week-3/</id> <content src="swastkk.github.io/blogs/posts/coding-week-3/" /> <author> <name>swastik</name> </author> <category term="python" /> <category term="package" /> <category term="summary" /> <category term="tests" /> <summary> Week 3 Progress (June 10 - June 16) This week mostly went through passing the tests in the Draft PR and written a basic test for the Post Scan Plugin --package-summary with pytest in commit. Implemented a unit test for the basic plugin:- Imported required modules in test_package_summary import pytest from os import path from commoncode.testcase import FileDrivenTestin... </summary> </entry> <entry><title>Coding Period Week 2</title><link href="swastkk.github.io/blogs/posts/coding-week-2/" rel="alternate" type="text/html" title="Coding Period Week 2" /><published>2024-06-09T01:55:00+00:00</published> <updated>2024-06-09T01:55:00+00:00</updated> <id>swastkk.github.io/blogs/posts/coding-week-2/</id> <content src="swastkk.github.io/blogs/posts/coding-week-2/" /> <author> <name>swastik</name> </author> <category term="python" /> <category term="package" /> <category term="summary" /> <summary> Week 2 Progress (June 3 - June 9) This week was completely focused on integrating the post-scan plugin --package-summary for the computation of package-level summaries. These plugins primarily handle data processing, summarization, and reporting, relying on results from all scan plugins. They introduce new attributes at the codebase or file level, and may also remove or modify data as needed fo... </summary> </entry> <entry><title>Coding Period Week 1</title><link href="swastkk.github.io/blogs/posts/coding-week-1/" rel="alternate" type="text/html" title="Coding Period Week 1" /><published>2024-06-02T01:55:00+00:00</published> <updated>2024-06-02T01:55:00+00:00</updated> <id>swastkk.github.io/blogs/posts/coding-week-1/</id> <content src="swastkk.github.io/blogs/posts/coding-week-1/" /> <author> <name>swastik</name> </author> <category term="python" /> <category term="package" /> <category term="summary" /> <summary> Week 1 Progress (May 27 - June 2) In scancode-toolkit, we previously computed the summary and license clarity scores for the whole scan. Now, we need to implement this for each package and its related files. With the ability to identify which files are associated with a package, this is now achievable. There are two levels of reporting license detections: File/package level License Detecti... </summary> </entry> <entry><title>GSoC'24 | Community Bonding Period</title><link href="swastkk.github.io/blogs/posts/gsoc24-community-bonding-period/" rel="alternate" type="text/html" title="GSoC&amp;apos;24 | Community Bonding Period" /><published>2024-05-28T01:55:00+00:00</published> <updated>2024-05-28T01:55:00+00:00</updated> <id>swastkk.github.io/blogs/posts/gsoc24-community-bonding-period/</id> <content src="swastkk.github.io/blogs/posts/gsoc24-community-bonding-period/" /> <author> <name>swastik</name> </author> <category term="python" /> <category term="package" /> <category term="summary" /> <summary> With the announcement of the Google Summer of Code (GSoC) results on May 1, 2024, my excitement was so overwhelming that I didn’t even study for my University End Semester Exam. I can still recall the subject: “Power System Analysis.” This summer, I’ll be collaborating with the AboutCode organization on the project “Compute summary for all the detected packages.” The most crucial phase of my GS... </summary> </entry> </feed>
