<feed xmlns="http://www.w3.org/2005/Atom"> <id>https://davidbtadokoro.tech/</id><title>davidbtadokoro.tech</title><subtitle>David Tadokoro personal website.</subtitle> <updated>2024-08-29T08:38:11-03:00</updated> <author> <name>David Tadokoro</name> <uri>https://davidbtadokoro.tech/</uri> </author><link rel="self" type="application/atom+xml" href="https://davidbtadokoro.tech/feed.xml"/><link rel="alternate" type="text/html" hreflang="en" href="https://davidbtadokoro.tech/"/> <generator uri="https://jekyllrb.com/" version="4.3.3">Jekyll</generator> <rights> © 2024 David Tadokoro </rights> <icon>/assets/img/favicons/favicon.ico</icon> <logo>/assets/img/favicons/favicon-96x96.png</logo> <entry><title>Planning the (short term) future of kw patch-hub</title><link href="https://davidbtadokoro.tech/posts/planning-the-short-term-future-of-kw-patch-hub/" rel="alternate" type="text/html" title="Planning the (short term) future of kw patch-hub" /><published>2024-08-27T15:00:00-03:00</published> <updated>2024-08-27T15:00:00-03:00</updated> <id>https://davidbtadokoro.tech/posts/planning-the-short-term-future-of-kw-patch-hub/</id> <content src="https://davidbtadokoro.tech/posts/planning-the-short-term-future-of-kw-patch-hub/" /> <author> <name>David Tadokoro</name> </author> <category term="rust dev" /> <category term="software engeneering" /> <category term="lore" /> <summary> In the last post, I’ve talked about how I teamed up with three really competent developers to help me with patch-hub in this semester. This post is an overall plan for our work together. This post will probably be updated as we reassess and modify the plan Goals From my knowledge of the problem at hand (i.e., the huge overhead Linux developers face when interacting with patches sent to... </summary> </entry> <entry><title>Starting collaborative work in kw patch-hub</title><link href="https://davidbtadokoro.tech/posts/starting-collaborative-work-in-kw-patch-hub/" rel="alternate" type="text/html" title="Starting collaborative work in kw patch-hub" /><published>2024-08-14T15:00:00-03:00</published> <updated>2024-08-14T15:00:00-03:00</updated> <id>https://davidbtadokoro.tech/posts/starting-collaborative-work-in-kw-patch-hub/</id> <content src="https://davidbtadokoro.tech/posts/starting-collaborative-work-in-kw-patch-hub/" /> <author> <name>David Tadokoro</name> </author> <category term="rust dev" /> <category term="software engeneering" /> <category term="lore" /> <summary> In my last post, I talked about how the rebuilding of kw patch-hub was going. With the start of the second semester in my post-graduation and the enrollment in the Advanced Topics on Software Engeneering subject, I came in contact with three great developers who will help me in this rebuilding effort. This marks the start of the new kw patch-hub as a dedicated Free Software project, and this po... </summary> </entry> <entry><title>How the new kw patch-hub is shaping up</title><link href="https://davidbtadokoro.tech/posts/how-the-new-kw-patch-hub-is-shaping-up/" rel="alternate" type="text/html" title="How the new kw patch-hub is shaping up" /><published>2024-07-28T15:00:00-03:00</published> <updated>2024-07-28T15:00:00-03:00</updated> <id>https://davidbtadokoro.tech/posts/how-the-new-kw-patch-hub-is-shaping-up/</id> <content src="https://davidbtadokoro.tech/posts/how-the-new-kw-patch-hub-is-shaping-up/" /> <author> <name>David Tadokoro</name> </author> <category term="rust dev" /> <category term="software engeneering" /> <category term="lore" /> <summary> As I’ve mentioned in a previous post, I am on a mission to rebuild a tool called kw patch-hub using Rust. My experience with kw patch-hub started with my GSoC23 project, and I found learning Rust, an excellent opportunity to rebuild it, as it had practically halted its development due to many issues. This posts describes how this rebuild is going, my assessment of it, and how the new kw patch-h... </summary> </entry> <entry><title>My journey with Rust</title><link href="https://davidbtadokoro.tech/posts/my-journey-with-rust/" rel="alternate" type="text/html" title="My journey with Rust" /><published>2024-07-15T15:00:00-03:00</published> <updated>2024-07-15T15:00:00-03:00</updated> <id>https://davidbtadokoro.tech/posts/my-journey-with-rust/</id> <content src="https://davidbtadokoro.tech/posts/my-journey-with-rust/" /> <author> <name>David Tadokoro</name> </author> <category term="rust dev" /> <category term="software engeneering" /> <summary> Earlier this month, I started learning the (Rust Programming Language)[https://www.rust-lang.org/] because I (and every other person involved in computer science) heard a great deal about the language and was curious about it and because the technology offered an opportunity to (re)build a solution for a problem I’ve been facing for a long time. </summary> </entry> <entry><title>The lore.kernel.org API</title><link href="https://davidbtadokoro.tech/posts/the-lore.kernel.org-api/" rel="alternate" type="text/html" title="The lore.kernel.org API" /><published>2023-09-04T15:00:00-03:00</published> <updated>2023-09-04T15:00:00-03:00</updated> <id>https://davidbtadokoro.tech/posts/the-lore.kernel.org-api/</id> <content src="https://davidbtadokoro.tech/posts/the-lore.kernel.org-api/" /> <author> <name>David Tadokoro</name> </author> <category term="lore" /> <category term="web" /> <category term="gsoc23" /> <summary> In my GSoC23 project, I had to understand the ins and outs of the lore API. By its API, I specifically mean the way requests to https://lore.kernel.org are responded, in other words, the syntax and semantics of requesting data stored in the lore archives, be it patches or available lists. From the outset, the most critical point in my project was if the lore API provided the necessary for kw p... </summary> </entry> </feed>
