<?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 Tatyana Manaseryan on Medium]]></title>
        <description><![CDATA[Stories by Tatyana Manaseryan on Medium]]></description>
        <link>https://medium.com/@itstatyana?source=rss-8f6fdb0e7c8e------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*udhwAv-26BcDoYO_iB3zOQ.jpeg</url>
            <title>Stories by Tatyana Manaseryan on Medium</title>
            <link>https://medium.com/@itstatyana?source=rss-8f6fdb0e7c8e------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 06:24:23 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@itstatyana/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[The History of Open-Source]]></title>
            <link>https://medium.com/@itstatyana/the-history-of-open-source-a88c67b64d99?source=rss-8f6fdb0e7c8e------2</link>
            <guid isPermaLink="false">https://medium.com/p/a88c67b64d99</guid>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[open-source-software]]></category>
            <category><![CDATA[openai]]></category>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[mlops]]></category>
            <dc:creator><![CDATA[Tatyana Manaseryan]]></dc:creator>
            <pubDate>Mon, 17 Mar 2025 10:04:48 GMT</pubDate>
            <atom:updated>2025-03-18T07:19:32.868Z</atom:updated>
            <content:encoded><![CDATA[<h4>The brief history of open-source</h4><p><strong>Before Open-Source Had a Name</strong></p><h3>The 1950–1960s:</h3><p>Back in the 1950s and 60s, computers were huge, expensive machines mostly used by universities and research labs. Software wasn’t yet a product or a business; it was simply an inseparable part of the massive hardware it ran on.</p><p>Only a few companies made computers, with <strong>IBM dominating the industry</strong>. At the time, software was a community effort, freely shared and exchanged among programmers who saw it as a tool rather than a commodity. It was common practice for developers to share code like recipes, helping each other fix bugs and improve functionality.</p><p>Collaboration, not competition, drove progress.</p><figure><img alt="Collaboration, not competition, drove progress." src="https://cdn-images-1.medium.com/max/513/1*ZJ_Tx4EiK2_qNPgBCeKWOg.jpeg" /><figcaption>Grace Hopper and UNIVAC, 1960</figcaption></figure><h3>The 1970s: The Rise of Proprietary Software</h3><p>However, as the industry evolved, software started gaining <strong>value as a standalone product</strong>. Companies wanted to protect their intellectual property, control distribution, and prevent unauthorized modifications.</p><p>The major shift came in <strong>1969</strong>, when <strong>IBM </strong>“unbundled” software from hardware. This meant that software was no longer included for free, it had to be purchased separately. That decision marked the birth of <strong>the proprietary software industry</strong>.</p><p>By the mid-1970s, software licensing became the norm. In <strong>1976</strong>,<strong> Bill Gates</strong> wrote his famous <strong>“Open Letter to Hobbyists,”</strong> criticizing the widespread sharing of Microsoft’s Altair BASIC without payment.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YoN9KPgtBAf_laek9eoCsw.jpeg" /><figcaption>In 1976 <a href="https://en.wikipedia.org/wiki/Bill_Gates">Bill Gates</a> wrote an essay entitled “<a href="https://en.wikipedia.org/wiki/Open_Letter_to_Hobbyists">Open Letter to Hobbyists</a>”, in which he expressed dismay at the widespread sharing of Microsoft’s product <a href="https://en.wikipedia.org/wiki/Altair_BASIC">Altair BASIC</a> by hobbyists without paying its licensing fee.</figcaption></figure><p>Around the same time, both software-only companies and computer vendors began charging for licenses through <strong>copyrights, trademarks, and leasing contracts</strong>.</p><p>Still, not all software followed this model. Some projects maintained a <strong>free distribution approach</strong>:</p><ul><li><strong>SPICE (1973)</strong>: A circuit simulation tool, released for free by Donald Pederson.</li><li><strong>TeX (1978): </strong>A typesetting system openly distributed by Donald Knuth.</li><li><strong>Unix (1973): </strong>Developed at AT&amp;T Bell Labs, widely used in universities with <strong>academic licenses allowing modification</strong>.</li></ul><p>While these weren’t called “open-source” at the time, they paved the way for what was coming next.</p><h3>The 1980s: The Birth of Free Software</h3><p>As proprietary software became the standard, some developers pushed back. The <strong>free software movement</strong> gained momentum in the 1980s, driven by frustration over corporate restrictions.</p><p>In <strong>1983</strong>, Richard Stallman, a programmer at MIT, launched the <strong>GNU Project</strong>, aiming to create a completely <strong>free</strong> operating system. He defined <strong>four fundamental freedoms</strong> for software users:</p><ol><li>Use the software for any purpose.</li><li>Study and modify the source code.</li><li>Share copies with others.</li><li>Distribute modified versions.</li></ol><p>To legally protect these freedoms, he introduced the <strong>GNU General Public License (GPL) in 1989</strong> — one of the most influential software licenses in history.</p><p>At the same time, universities and research groups were improving <strong>BSD Unix</strong>, an open version of Unix. In <strong>1989</strong>, parts of BSD were released under the <strong>permissive BSD license</strong>, allowing broader use.</p><p>These efforts laid the foundation for the modern open-source movement.</p><h3>The 1990s: Open-Source Goes Public</h3><p>By the early 90s, free software projects had grown, but <strong>there was still no fully open-source operating system</strong>. That changed in <strong>1991</strong>, when <strong>Linus Torvalds</strong>, a Finnish student, released the first version of the <strong>Linux kernel</strong>.</p><p>With Linux as the core and GNU tools providing essential utilities, <strong>the first fully open-source operating system was born</strong>. Around the same time, BSD Unix distributions (<strong>NetBSD, FreeBSD, OpenBSD</strong>) emerged as alternatives. The <strong>Internet</strong> played a crucial role in spreading open-source projects, allowing global collaboration in real-time.</p><p>The real turning point came in <strong>1998</strong>, when <strong>Netscape</strong> announced that it would open-source its web browser code — what later became <strong>Mozilla Firefox</strong>. This was a <strong>game-changer</strong>. To make open-source more appealing to businesses, the term <strong>“open-source software”</strong> was officially introduced, distancing itself from the politically charged “free software.”</p><p>That same year, the <strong>Open Source Initiative (OSI)</strong> was founded to promote open-source principles. In <strong>1997</strong>, <strong>Eric Raymond’s essay “The Cathedral and the Bazaar”</strong> argued that decentralized, open development (like Linux) was superior to top-down proprietary models. Netscape <strong>cited this essay</strong> when announcing its decision to open-source its browser.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/685/1*66I7jr3zmofM2auhXy-0Wg.png" /></figure><p>These events led to a pivotal meeting in Palo Alto, where <strong>the term “open-source” was coined</strong>, marking a new era for software development.</p><h3>The 2000s-Today: Open-Source as a game changer</h3><p>Once seen as a niche idea, open-source became mainstream in the 2000s:</p><ul><li><strong>Linux</strong> dominated servers, cloud computing, and embedded systems.</li><li><strong>Apache</strong> powered most of the web.</li><li><strong>Android</strong>, built on Linux, became the world’s leading mobile OS.</li><li><strong>Git</strong>, created by Linus Torvalds in 2005, became the standard for version control.</li><li>Major companies like <strong>Google, Microsoft, and Amazon</strong> embraced open-source, integrating it into their businesses</li></ul><p>Today, open-source isn’t just about software, it’s a<strong> global movement</strong>. From AI frameworks like PyTorch and TensorFlow to blockchain and cloud computing, open-source is <strong>everywhere</strong>.</p><h3>Why Does It Matter?</h3><p>The open-source revolution proved that software doesn’t need to be locked away to be valuable. It enables collaboration, innovation, and progress without permission or barriers.</p><p>And the best part?</p><p><strong>It’s still evolving.</strong> <strong>The future of tech is open, and anyone can be a part of it.</strong></p><p>I’m Tatyana from <a href="https://aimstack.io/">Aim</a> (open-source, AI metadata tracking tool).</p><p>Feel free to join the <a href="https://discord.com/invite/zXq2NfVdtF">Aim Community</a> on Discord for more open-source, AI/ML discussions, share your knowledge, and learn from other ML folks.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a88c67b64d99" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Beginner’s guide: How to start contributing to open-source]]></title>
            <link>https://medium.com/@itstatyana/beginners-guide-how-to-start-contributing-to-open-source-211ad1f040a3?source=rss-8f6fdb0e7c8e------2</link>
            <guid isPermaLink="false">https://medium.com/p/211ad1f040a3</guid>
            <category><![CDATA[machine-learning]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[mlops]]></category>
            <category><![CDATA[contribute-to-open-source]]></category>
            <category><![CDATA[open-source]]></category>
            <dc:creator><![CDATA[Tatyana Manaseryan]]></dc:creator>
            <pubDate>Fri, 17 May 2024 19:06:34 GMT</pubDate>
            <atom:updated>2024-05-18T17:01:15.370Z</atom:updated>
            <content:encoded><![CDATA[<p>Contributing to open-source is rewarding in many ways. You can improve your coding skills, learn new technologies, and get more practice. It’s also a great way to meet new people and work together. Since potential employers can see your work, it might even help you land a job. Plus, it’s personally fulfilling to solve real-world problems.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PXruPai-KVD5tmDmuW8VDA.jpeg" /><figcaption>Image generated by ChatGPT</figcaption></figure><h3>How to contribute to open-source projects?</h3><p>Sometimes, people want to contribute to open-source but find it challenging to get started. They have questions about how to find projects that need contributions, the best strategies to begin, or how to make their contributions valuable.</p><blockquote>I have several tips that may help if you’re looking to get involved in open-source projects.</blockquote><p>The open-source community thrives on mutual learning. Teams are open to contributions and will welcome your initiative. Every contribution, no matter its size, holds value. The most challenging aspect is identifying a project that aligns with your interests and skills.</p><h3>Choosing the right: What to consider?</h3><p>Choose a project driven by your personal interests. Which open-source tools do you use or know really well? What aspects could you improve? If you have an answer to this question, you’re already halfway there :)))</p><p>If no specific tool comes to mind, look for issues labeled as “good first issue”, “help-wanted” or “beginner-friendly”. These are designed to help you get your feet wet without feeling overwhelmed.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YoiitI9TaYghPZwn7Ik_4g.png" /><figcaption>#good-first-issue on GitHub</figcaption></figure><h3>Contributing to open-source: How to get started?</h3><h4>1. Code:</h4><p>If you encounter a problem within the tool and think you can help solve it, open a Pull Request and wait for feedback from the maintainers. Go ahead and tackle the problem.</p><p>This is a great start, as you will enjoy working on the project while having a sense of solving a problem and making an impact. This could be anything from fixing bugs, improving infrastructure to adding a feature.</p><h4>2. Documentation:</h4><p>If you’re unsure about how to offer a solution to a problem or suggest enhancements, consider helping to improve the documentation. Sometimes, users get frustrated by poorly written or organized docs, so your contribution will be highly appreciated!</p><p>Another tip: Consider adding examples or demos to documentation. Docs often lack practical examples, so creating and including these can be a significant contribution. Take the stage. 🌟</p><h4>3. Discussions:</h4><p>Connect with the community and participate in discussions! If you know answer to any usage questions, feel free to jump in and give a hand. Many projects have chat channels on communities on platforms like Slack or Discord where you can get involved.</p><h4>4. Testing:</h4><p>You can engage in beta testing of products or newly added features, noting and even fixing bugs as you find them. This proactive approach not only helps you stand out from other contributors but also significantly aids the maintainers. By testing early versions and reporting back, you provide essential feedback that can guide the final adjustments before a public release. Your contributions in this area can enhance the reliability and user experience of the software.</p><h4>More tips</h4><p>You can also contribute to new projects by sharing your ideas with like-minded people! Engaging with a community of enthusiasts who share your interests not only enhances the project but also enriches your own understanding and skills. Attend virtual meetups and participate in webinars or local events to network and learn more about open-source projects.</p><h4>Understanding open-source Code of Conduct and Licensing:</h4><p>Before you start, it’s important to understand the licensing associated with open-source projects. Knowing whether a project is under MIT, GPL, Apache, or another license can affect how you use and contribute to the software. Each license has different requirements and restrictions that can impact your contributions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/895/1*NN3-bozOPBX7AXbuI5GTlQ.png" /><figcaption>Hugging Face: Code of Conduct</figcaption></figure><blockquote>Amplify open-source by sharing your experiences and promoting projects through social media or blogs. Your interest and contribution will be noticed by open-source community and they will support you right back.</blockquote><p>Here are some platforms where you can find projects to contribute to in the open-source community:</p><ol><li><a href="https://github.com/"><strong>GitHub:</strong></a> The largest and most popular platform for hosting open-source projects. You can search for projects by language, topic, or label. Explore <a href="https://github.com/topics/good-first-issue">Good First Issues on GitHub</a> to find beginner-friendly opportunities.</li><li><a href="https://about.gitlab.com/"><strong>GitLab:</strong></a> Similar to GitHub, GitLab hosts a wide variety of open-source projects and is another great place to start looking for opportunities to contribute.</li></ol><p><em>Here are my selected open-source ML projects built on community feedback that you might consider contributing to:</em></p><ul><li><a href="https://github.com/huggingface"><strong>🤗Hugging Face</strong>:</a> A machine learning (ML) and data science platform that helps users build, deploy, and train machine learning models.</li><li><a href="https://github.com/aimhubio/aim"><strong>🚀Aim</strong>: </a>An open-source experiment tracking tool that logs training runs and AI metadata, and provides a supercharged UI to compare and observe them.</li><li><a href="https://github.com/run-llama/llama_index">🦙<strong>LlamaIndex</strong>:</a> An open-source tool specifically designed for building search and retrieval applications powered by large language models (LLMs).</li></ul><h3>Code contribution, technical setup:</h3><p>If you want to make a code contribution and aren’t sure how to technically go about it, you may find this helpful:</p><ol><li><strong>Set up your environment:</strong> Once you’ve selected a project, set up your development environment. This usually involves cloning the project repository to your local machine and installing any necessary dependencies.</li><li><strong>Understand the Contribution Guidelines:</strong> Before making any changes, read the project’s contribution guidelines if available. These guidelines will provide specifics about coding standards, branch naming conventions, and the process for submitting contributions. This can vary by each project and following these instructions is a must.</li><li><strong>Look for issues to tackle:</strong> Start with issues labeled as “good first issue” or “beginner-friendly” if you’re new. These tags are commonly used to indicate tasks that are suitable for newcomers.</li><li><strong>Fork and clone the Repository:</strong> Fork the repository to your own GitHub account and then clone it from your account to your local machine.</li><li><strong>Create a new branch:</strong> Always create a new branch for your changes. This keeps your modifications separate from the main project during development.</li><li><strong>Make your changes:</strong> Implement your changes in the new branch. Make sure you adhere to the coding standards and practices of the project.</li><li><strong>Test your changes:</strong> Run any existing tests to ensure you haven’t broken anything. If your changes are substantial, consider adding new tests that cover your changes. Test few times :))</li><li><strong>Commit your changes:</strong> Once you’re satisfied with your changes, commit them to your branch. Make sure your commit messages are clear and descriptive.</li><li><strong>Push changes to your fork:</strong> Push your changes to your fork on GitHub (or other platform).</li><li><strong>Submit a Pull Request (PR):</strong> From your fork, submit a pull to the original repository. Provide a clear description of what problems your changes solve and any additional context the maintainers might need.</li><li><strong>Participate in the review process:</strong> Respond to any comments or requests for changes from the project maintainers. This can involve making further modifications based on feedback.</li><li><strong>Get merged:</strong> Once your pull request is approved and merged, your changes will be incorporated into the project. Congratulations, you’ve successfully contributed!</li><li><strong>Clean up:</strong> After your PR is merged, you can clean up your branches and pull the latest changes from the original repository to your local setup.</li></ol><h3>That’s it! Not that hard, right?</h3><p>Learn by Doing: Don’t be afraid to make mistakes. The open-source community is generally understanding and supportive.</p><p>Always maintain kindness and patience in your interactions within a project. Many maintainers are often focused on resolving issues or work on these projects in their free time, so it might take some time for them to review your changes.</p><blockquote>If you’re looking to deepen your understanding of Machine Learning and MLOps and contribute to open-source project, we would love to have you join <a href="https://community.aimstack.io/">Aim Discord Community</a>. ✨</blockquote><p>Remember, all contributions are valuable, no matter how small they may seem. Let’s spread the love for open-source. Good luck on your journey! 🚀</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=211ad1f040a3" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>