<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Vedanshsaini on Medium]]></title>
        <description><![CDATA[Stories by Vedanshsaini on Medium]]></description>
        <link>https://medium.com/@vedanshsaini7719?source=rss-05c13430bd20------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*uc_KxjNMXd3lqYjh</url>
            <title>Stories by Vedanshsaini on Medium</title>
            <link>https://medium.com/@vedanshsaini7719?source=rss-05c13430bd20------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 13:19:55 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@vedanshsaini7719/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Taking Visdom from one laptop to a shared lab server: my GSoC 2026]]></title>
            <link>https://medium.com/@vedanshsaini7719/taking-visdom-from-one-laptop-to-a-shared-lab-server-my-gsoc-2026-398cdbd25320?source=rss-05c13430bd20------2</link>
            <guid isPermaLink="false">https://medium.com/p/398cdbd25320</guid>
            <category><![CDATA[google-summer-of-code]]></category>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[machine-learning]]></category>
            <dc:creator><![CDATA[Vedanshsaini]]></dc:creator>
            <pubDate>Tue, 27 Oct 2026 08:08:33 GMT</pubDate>
            <atom:updated>2026-10-27T08:08:33.742Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Notes from six months of building visdom.dev with FOSSASIA</em></p><p>If you’ve trained a model, you’ve probably done this: start the run, then keep switching back to a terminal to see whether the loss went down. <a href="https://github.com/fossasia/visdom">Visdom</a> is a small open source tool that fixes that. You add a few lines to your training script, and the loss curve, images and text show up in a browser tab while the run is still going.</p><p>It was written for one person on one machine, though. There are no accounts in it. Whoever can reach the server can see every plot on it, and delete them too. When a lab wants to share one, people usually end up running a server each.</p><p>My Google Summer of Code project with FOSSASIA this year was to change that. The result is <a href="https://visdom.dev/">visdom.dev</a>. You sign up, make a workspace for a project, invite people as admins, members or viewers, and give your training scripts an API key. Plots go into that workspace, and nobody outside it can see them. If you want to show a result to someone outside the team, you can send them a shared link. Bigger plans are paid, through Stripe.</p><p>Running visdom on your own machine works the same as it always has. I was careful about that, because most visdom users will never touch the hosted version.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*TE95Wm0s_7EpfP-8.png" /></figure><h3>Trying it</h3><p>After you sign up and make a workspace, create an API key, install the client from the dev branch and send a plot:</p><pre>pip install &quot;git+https://github.com/fossasia/visdom.git@dev&quot;</pre><pre>import visdom<br><br>vis = visdom.Visdom(<br>    server=&quot;https://visdom.dev&quot;, port=443, base_url=&quot;/vis&quot;,<br>    api_key=&quot;your key&quot;,<br>    workspace=&quot;your-workspace&quot;,<br>)<br><br>for step, loss in enumerate([0.9, 0.6, 0.4, 0.25]):<br>    vis.line(X=[step], Y=[loss], win=&quot;loss&quot;, update=&quot;append&quot;,<br>             env=&quot;experiment-1&quot;, opts={&quot;title&quot;: &quot;training loss&quot;})</pre><p>Then open the workspace in the console and click Visualizations. The curve is there, and it keeps updating as the script runs.</p><h3>What I built</h3><p>Most of the new code is in a new repository, <a href="https://github.com/fossasia/visdom-dev">fossasia/visdom-dev</a>. It has a FastAPI gateway that handles accounts, workspaces, roles, API keys, sharing and billing, and a React console for managing all of it. Postgres stores the data, and nginx sits in front so the console, the API and visdom all live on one domain.</p><p>Visdom itself needed changes too. It now keeps each workspace’s data in its own folder, sends every request and websocket to the workspace it belongs to, and tells the gateway how active each workspace is. None of that is switched on unless there is a gateway in front of it.</p><p>By the end that came to 51 merged pull requests in visdom-dev and 38 in visdom.</p><h3>Things I learned</h3><h4>Keep changes to the core small</h4><p>Visdom keeps every environment in one in-memory store, backed by one folder on disk. My first instinct was to rebuild that around workspaces. I’m glad I didn’t. It would have been one huge PR against a project a lot of people depend on, and I doubt anyone would have been comfortable reviewing it.</p><p>What I did was put a thin layer around the existing store, so each workspace gets its own part of it. The visdom PRs stayed small enough to review one at a time, and people running it locally don’t see any difference.</p><h4>Ask the gateway once</h4><p>Three kinds of traffic reach visdom: pages loading in a browser, websockets that stay open for hours, and training scripts posting plots with an API key. All of them need the same check (who is this, and which workspace are they allowed to see?). So visdom asks the gateway, keeps the answer for a short time, and the rules live in one place.</p><h4>Load test the real server</h4><p>In early October I set up a small machine on AWS in Mumbai, pointed <a href="https://k6.io/">k6</a> at visdom.dev and ramped up fake users. The live server is a 2-core Oracle VM, the largest one on their free tier. It handled about 100 people training at once with plot requests still coming back in under 30 ms. At 125 the CPU sat at 98% and plots started showing up seconds late.</p><p>The second run split users into writers (a script sending plots) and readers (someone watching the page). One writer cost about as much as 22 readers. With nobody writing, the server kept more than 12,000 pages open without trouble.</p><p>Two things came out of it that I wouldn’t have found otherwise. The health check said “healthy” while the CPU was at 100%, so it now also reports when visdom is slow or the machine is overloaded. And there was an old bug in visdom: if a viewer closed their tab at the wrong moment, the script sending the plot got a 500 error. That’s <a href="https://github.com/fossasia/visdom/pull/2054">fixed upstream</a> now.</p><h4>Payments</h4><p>Stripe handles the card form, which sits inside the console, so card numbers never reach our server. The rule I stuck to was to never act on a webhook by itself. When Stripe says someone upgraded, the gateway fetches the subscription from Stripe and checks it before it changes the plan.</p><p>The normal upgrade was quick to build. Most of the time went into the odd cases, like someone deleting their account while they’re still paying, or coming back within the 30-day grace period.</p><h4>Smaller pull requests</h4><p>My midterm review was honest. The base was good, but some flows were still mock-ups, and my PRs were too big to review properly (the very first one was over 4,000 lines). After that I kept each PR to one change, with tests, and with screenshots whenever something on screen changed. It’s a boring lesson, but it’s the one I’d pass on to anyone starting GSoC.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*QNAHQDVjeYx8qjvC.png" /></figure><h3>What’s next</h3><p>The plan is to move from visdom.dev to FOSSASIA’s own servers and to add a few more tools for the people running the service, like a plan editor and a usage page for staff. Later I’d like visdom to add and remove instances by itself as load goes up and down.</p><p>We’ve also opened some <a href="https://github.com/fossasia/visdom-dev/issues?q=is%3Aissue+label%3A%22good+first+issue%22">good first issues</a> on visdom-dev, and a few new contributors have already picked them up. Have a look if you’d like to help.</p><h3>Thanks</h3><p>Thanks to my mentors Mario Behling, Marco A. Gutiérrez, Norbert Preining, Roland Turner and Valentin Weber, and to Rajnish, Jayant and Manik, who reviewed my PRs. And thanks to everyone who signed up early and told us what broke.</p><p>If you train models with other people, try <a href="https://visdom.dev/">visdom.dev</a> and let me know how it goes. The full GSoC report, with every PR, is <a href="https://gist.github.com/vedansh-5/d8b6937b2a2945386f3c3e7bd4bae289">on GitHub</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=398cdbd25320" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[From Utility to Experience: My GSoC 2025 Journey with Scrum Helper]]></title>
            <link>https://medium.com/@vedanshsaini7719/from-utility-to-experience-my-gsoc-2025-journey-with-scrum-helper-32a9c6a5b2b1?source=rss-05c13430bd20------2</link>
            <guid isPermaLink="false">https://medium.com/p/32a9c6a5b2b1</guid>
            <dc:creator><![CDATA[Vedanshsaini]]></dc:creator>
            <pubDate>Mon, 04 Aug 2025 17:08:40 GMT</pubDate>
            <atom:updated>2025-08-04T17:08:40.714Z</atom:updated>
            <content:encoded><![CDATA[<p>Google Summer of Code 2025 was not just a chance to contribute code — it was a deep dive into solving developer pains through thoughtful tooling. I was fortunate to work with <strong>FOSSASIA</strong> on the <a href="https://github.com/fossasia/scrum_helper">Scrum Helper</a> Chrome Extension, a tool that simplifies the creation of daily developer reports by fetching GitHub activity and auto-generating summaries.</p><p>While the extension was already functional, it lacked polish and flexibility. My proposal aimed to reimagine it — from a basic helper to a smooth, customizable, and production-ready experience.</p><h3><strong>Project Overview</strong></h3><p><strong>Scrum Helper</strong> is a Chrome extension designed to reduce friction for developers writing daily standups or sprint reports. Users enter their GitHub username, select a date range, and the extension fetches their Git activity (commits, PRs, issues, reviews) and pre-fills a report.</p><p>While the original goal focused on GitHub and Google Groups, I envisioned a broader scope — platform-independent workflows, richer customization, internationalization, and better performance.</p><h3>My Contributions</h3><h4>Phase 1: Foundations and Flexibility</h4><ul><li><strong>Email Client Expansion</strong>: Extended support beyond Google Groups to include Gmail, Yahoo, and Outlook.<br> <a href="https://github.com/fossasia/scrum_helper/pull/62">#62</a></li><li><strong>Standalone Report Generator</strong>: Added a full report editor inside the popup, allowing report generation without relying on any email client.<br> <a href="https://github.com/fossasia/scrum_helper/pull/76">#76</a></li><li><strong>UI Overhaul with Tailwind CSS</strong>: Migrated from Materialize to Tailwind, enabling modern design, responsiveness, and dark mode.<br> <a href="https://github.com/fossasia/scrum_helper/pull/83">#83</a></li><li><strong>Automation &amp; Maintenance</strong>:</li><li>Added release-drafter for automated changelogs. <a href="https://github.com/fossasia/scrum_helper/pull/97">#97</a></li><li>Improved issue/PR templates. <a href="https://github.com/fossasia/scrum_helper/pull/99">#99</a></li><li>Integrated auto-labeler workflow. <a href="https://github.com/fossasia/scrum_helper/pull/101">#101</a></li><li><strong>Caching</strong>: Fetched GitHub data is cached for 10 minutes by default to minimize redundant API calls.<br> <a href="https://github.com/fossasia/scrum_helper/pull/133">#133</a></li></ul><h4>Phase 2: Auth, Insight, and International Reach</h4><ul><li><strong>PAT Support</strong>: Integrated GitHub Personal Access Tokens to allow private repo access and increased rate limits.<br> <a href="https://github.com/fossasia/scrum_helper/pull/118">#118</a></li><li><strong>Modernized Data Fetching</strong>: Replaced jQuery AJAX with fetch and async/await.<br> <a href="https://github.com/fossasia/scrum_helper/pull/133">#133</a></li><li><strong>UI/UX Enhancements</strong>:</li><li>Options split into clear sections. <a href="https://github.com/fossasia/scrum_helper/pull/143">#143</a></li><li>Dynamic repo dropdown showing user contributions. <a href="https://github.com/fossasia/scrum_helper/pull/171">#171</a></li><li><strong>PR Commit Timeline</strong>: Users can now view commit logs with timestamps inside draft or open PRs.<br> <a href="https://github.com/fossasia/scrum_helper/pull/147">#147</a></li><li><strong>i18n Support</strong>: Translates UI automatically based on browser language via _locales.<br> <a href="https://github.com/fossasia/scrum_helper/pull/193">#193</a></li><li><strong>Chrome Store Release</strong>: Publicly released the extension on the Chrome Web Store.<br> <a href="https://github.com/fossasia/scrum_helper/pull/208">#208</a></li></ul><h4>Additional Contributions</h4><ul><li><strong>Bug Fixes</strong>:</li><li>Caching issues <a href="https://github.com/fossasia/scrum_helper/pull/180">#180</a></li><li>Date range selector <a href="https://github.com/fossasia/scrum_helper/pull/173">#173</a></li><li>Email content injection <a href="https://github.com/fossasia/scrum_helper/pull/109">#109</a></li><li><strong>Documentation</strong>:</li><li>Updated README with screenshots and usage guide. <a href="https://github.com/fossasia/scrum_helper/pull/92">#92</a></li><li>Added CHANGELOG.md to track features. <a href="https://github.com/fossasia/scrum_helper/pull/209">#209</a></li></ul><h4>Collaboration &amp; Synergy</h4><p>I worked alongside <a href="https://medium.com/@asyadav11979/gsoc-2025-final-submission-336caa54689c">Preeti Yadav</a>, who focused on GitLab integration, profile syncing, and activity pipelines. We coordinated our work in parallel, keeping the project modular, avoiding redundancy, and complementing each other’s contributions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/470/1*ORf_DckuxNfPj6igEVIWjw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/469/0*KnTBNdvxi9PD2iZc" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/470/0*Un_o_cty99v3enjJ" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/470/1*EXojri9aMpmymSDz3vfVZw.png" /></figure><h3>Useful Links</h3><ul><li>GitHub Repo: <a href="https://github.com/fossasia/scrum_helper">fossasia/scrum_helper</a></li><li>GSoC Dashboard: <a href="https://summerofcode.withgoogle.com/myprojects/details/PZuZUYOI">My GSoC Page</a></li><li>Pull Requests: <a href="https://github.com/fossasia/scrum_helper/pulls?q=is%3Apr+author%3Avedansh-5">vedansh-5 PRs</a></li><li>Closed Issues: <a href="https://github.com/fossasia/scrum_helper/issues?q=is%3Aissue+assignee%3Avedansh-5+is%3Aclosed">vedansh-5 Issues</a></li><li>GSoC Proposal: <a href="https://gist.github.com/vedansh-5/40455264edc58cf61e3331b680612efa">GitHub Gist</a></li></ul><h3>Final Thoughts</h3><p>Impactful tools don’t just work — they feel smooth, predictable, and respectful of the user’s time. Through this GSoC experience, I realized how deep that responsibility runs in open source.</p><p>Thanks to my mentors, the FOSSASIA community, and Google Summer of Code for making this opportunity possible.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=32a9c6a5b2b1" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>