<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
    <id>https://borr.dev/blog/</id>
    <title>The Borr Project Blog</title>
    <updated>2025-12-24T00:00:00.000Z</updated>
    <generator>https://github.com/jpmonette/feed</generator>
    <link rel="alternate" href="https://borr.dev/blog/"/>
    <subtitle>The Borr Project Blog</subtitle>
    <icon>https://borr.dev/img/favicon.ico</icon>
    <entry>
        <title type="html"><![CDATA[First 6 Months of The BORR Project]]></title>
        <id>https://borr.dev/blog/first-six-months-of-borr/</id>
        <link href="https://borr.dev/blog/first-six-months-of-borr/"/>
        <updated>2025-12-24T00:00:00.000Z</updated>
        <summary type="html"><![CDATA[The BORR Project started out as a community fork of OSSU to rebuild the community where people can come together, geek out, and support one another in a peer learning environment for computer science and math. Six months in, we’re excited to share our progress.]]></summary>
        <content type="html"><![CDATA[<p>The BORR Project started out as a community fork of OSSU to rebuild the community where people can come together, geek out, and support one another in a peer learning environment for computer science and math. Six months in, we’re excited to share our progress.</p>
<h3 class="anchor anchorTargetHideOnScrollNavbar_vjPI" id="repos--discord-community">Repos &amp; Discord Community<a href="https://borr.dev/blog/first-six-months-of-borr/#repos--discord-community" class="hash-link" aria-label="Direct link to Repos &amp; Discord Community" title="Direct link to Repos &amp; Discord Community" translate="no">​</a></h3>
<ul>
<li class="">We launched a new Docusaurus-based website. Compared to a GitHub README, it offers a significantly better user experience and allows us to organize supplementary information without clutter. Recent additions include progress tracking (inspired by The Odin Project) and global search.</li>
<li class="">Our Discord server leverages new community features like onboarding, forums, event channels, and AutoMod. We also recently activated our server tag.</li>
<li class="">Despite having only 91 members (at the time of writing), we observed <strong>27% more activity</strong> in public channels over the last 6 months compared to the OSSU server.</li>
<li class="">We held active cohort meetings with consistent participation and organized a server event around the CodinGame Summer Challenge.</li>
<li class="">We launched our Study Hall, which gave home to numerous public study sessions and quite a few teamworks.</li>
<li class="">Because puzzle solving is fun, we also organized an event around Advent of Code 2025. Being our most popular event at this point, it proved to be nicely balanced between competition and collaboration.</li>
<li class="">We have started working on formalizing the governance structure of the project, and drafting the bylaws of the project. We are aiming for a governance structure that is open and collaborative, while not being too bureaucratic. We are taking inspiration from several prominent open source projects.</li>
</ul>
<h3 class="anchor anchorTargetHideOnScrollNavbar_vjPI" id="curriculum">Curriculum<a href="https://borr.dev/blog/first-six-months-of-borr/#curriculum" class="hash-link" aria-label="Direct link to Curriculum" title="Direct link to Curriculum" translate="no">​</a></h3>
<ul>
<li class="">We promptly addressed issues with courses affected by Coursera's removal of the audit option by identifying alternative resources.</li>
<li class="">We have seen familiar and new faces contributing to our repos, streamlining resource suggestions and fixes. The Preschool Math curriculum, for instance, received a complete overhaul.</li>
<li class="">We avoid a strict "lecture-only" policy, embracing books, articles, and other formats. For example, we recommend <em>Dive into Systems</em> combined with <em>CS<!-- -->:APP</em> lectures and labs as our primary resource, keeping the <em>CS<!-- -->:APP</em> textbook as an optional supplement since it is not free. This approach, suggested before students start <a class="" href="https://borr.dev/computer-science/systems/ostep/">OSTEP</a>, helps students plan their studies effectively in the systems programming section.</li>
<li class="">The curriculum is actively maintained with frequent contributions on GitHub regarding courses, issues, and research suggestions. We've also added supplemental resources to many courses.</li>
<li class="">We have started the work of moving the CS curriculum to CS2023 guidelines, from the older CS2013 guidelines. We are having discussions on this topic in <a href="https://discord.com/channels/1385616874200371350/1444728546760069242" target="_blank" rel="noopener noreferrer" class="">a dedicated channel on the discord server</a>.</li>
</ul>
<h2 class="anchor anchorTargetHideOnScrollNavbar_vjPI" id="roadmap-for-the-next-6-months">Roadmap for the Next 6 Months<a href="https://borr.dev/blog/first-six-months-of-borr/#roadmap-for-the-next-6-months" class="hash-link" aria-label="Direct link to Roadmap for the Next 6 Months" title="Direct link to Roadmap for the Next 6 Months" translate="no">​</a></h2>
<p>Beyond gathering user feedback and adapting to community needs, our key goals for the next half-year include:</p>
<ul>
<li class="">Developing comprehensive "Setting Up Your Development Environment" guides, inspired by The Odin Project.</li>
<li class="">Creating a showcase board for students to share their curriculum work and projects.</li>
<li class="">Hosting more server events and group activities.</li>
<li class="">Completing the formalization of the governance structure and the bylaws.</li>
<li class="">Organizing focus groups (tutors, website maintainers, curriculum maintainers, etc.) and assigning roles.</li>
<li class="">And marketing! We plan to announce the Borr Project on Reddit, Hacker News, and the wider internet to acquire more users.</li>
</ul>
<p>Join us in building a place where we can all geek out and learn together!</p>]]></content>
        <author>
            <name>Rohit M</name>
        </author>
    </entry>
    <entry>
        <title type="html"><![CDATA[Announcing Borr Project]]></title>
        <id>https://borr.dev/blog/announcing-borr-project/</id>
        <link href="https://borr.dev/blog/announcing-borr-project/"/>
        <updated>2025-06-24T00:00:00.000Z</updated>
        <summary type="html"><![CDATA[A Community-Driven Evolution of OSSU]]></summary>
        <content type="html"><![CDATA[<h2 class="anchor anchorTargetHideOnScrollNavbar_vjPI" id="a-community-driven-evolution-of-ossu">A Community-Driven Evolution of OSSU<a href="https://borr.dev/blog/announcing-borr-project/#a-community-driven-evolution-of-ossu" class="hash-link" aria-label="Direct link to A Community-Driven Evolution of OSSU" title="Direct link to A Community-Driven Evolution of OSSU" translate="no">​</a></h2>
<p>For years, the Open-Source Society University (OSSU) Computer Science curriculum has been an invaluable resource, positively impacting countless lives. It fostered a vibrant community, rich with industry professionals, academics, and engaged students who collaborated and learned together. However, over time, the OSSU community has faced challenges, leading to a decline in collaboration and engagement. Many of the individuals who contributed significantly to its strength have moved on, and the current administrative structure has introduced friction and delays.</p>
<p>We believe in the power of open education and the strength of a truly collaborative community. That's why we, a group of former OSSU staff members and active community contributors, are excited to announce the <strong>Borr Project</strong>—a fork designed to revitalize and advance the OSSU computer science curriculum, both academically and as a community.</p>
<!-- -->
<h2 class="anchor anchorTargetHideOnScrollNavbar_vjPI" id="our-vision-for-borr-project">Our Vision for Borr Project<a href="https://borr.dev/blog/announcing-borr-project/#our-vision-for-borr-project" class="hash-link" aria-label="Direct link to Our Vision for Borr Project" title="Direct link to Our Vision for Borr Project" translate="no">​</a></h2>
<p>The core of Borr Project's vision is a commitment to <strong>decentralized, collaborative leadership</strong>. Unlike the current single-director model, Borr Project will adopt an open-source governance structure, drawing inspiration from other successful projects. This means:</p>
<ul>
<li class=""><strong>Community-led Development</strong>: Decisions and initiatives will be driven by the community, fostering a more responsive and agile environment.</li>
<li class=""><strong>Reduced Bureaucracy</strong>: We aim to minimize unnecessary processes, empowering contributors to implement meaningful changes efficiently.</li>
<li class=""><strong>Enhanced Collaboration</strong>: We will actively cultivate an environment where new ideas can flourish and diverse contributions are welcomed and encouraged.</li>
</ul>
<h2 class="anchor anchorTargetHideOnScrollNavbar_vjPI" id="moving-forward-key-initiatives-and-future-plans">Moving Forward: Key Initiatives and Future Plans<a href="https://borr.dev/blog/announcing-borr-project/#moving-forward-key-initiatives-and-future-plans" class="hash-link" aria-label="Direct link to Moving Forward: Key Initiatives and Future Plans" title="Direct link to Moving Forward: Key Initiatives and Future Plans" translate="no">​</a></h2>
<p>Our immediate focus for Borr Project includes a number of key initiatives to improve the learning experience and rebuild a thriving community:</p>
<ul>
<li class=""><strong>Revitalized Online Presence</strong>: We're developing a proper, user-friendly website using Docusaurus, featuring improved SEO and accessibility, to make the curriculum more discoverable and navigable.</li>
<li class=""><strong>Richer Learning Resources</strong>:<!-- -->
<ul>
<li class="">Creating video content showcasing projects built throughout the curriculum.<!-- -->
<ul>
<li class="">Expanding and refining course pages for greater clarity and depth.</li>
<li class="">Developing comprehensive "Setting Up Your Development Environment" guides, similar to The Odin Project's excellent resources.</li>
<li class="">Adding extra practice problems with automated checks (e.g., using check50) for a more interactive learning experience.</li>
</ul>
</li>
</ul>
</li>
<li class=""><strong>Rebuilding Community Engagement</strong>: We're excited to re-introduce and expand community initiatives that were previously difficult to implement, such as:<!-- -->
<ul>
<li class="">Regular online community meet-ups and events.<!-- -->
<ul>
<li class="">Collaborative projects and study groups.</li>
<li class="">Mentorship opportunities and avenues for peer support.</li>
</ul>
</li>
</ul>
</li>
</ul>
<p>These are just a few of the many ideas our collective of former OSSU staff and contributors are eager to bring to life. We believe in empowering the community to shape the future of open-source computer science education.</p>
<h2 class="anchor anchorTargetHideOnScrollNavbar_vjPI" id="our-commitment">Our Commitment<a href="https://borr.dev/blog/announcing-borr-project/#our-commitment" class="hash-link" aria-label="Direct link to Our Commitment" title="Direct link to Our Commitment" translate="no">​</a></h2>
<p>Before embarking on this new path, we, as former staff, did raise our concerns regarding the direction and administrative structure of OSSU with its leadership. Ultimately, these discussions did not lead to the necessary changes. With no active moderators currently present in the OSSU community, we, the former staff who remain committed to the original spirit of open-source education, have come together to establish Borr Project.</p>
<p>We invite all former OSSU community members, new learners, and anyone passionate about accessible, high-quality computer science education to join us. The Borr Project is a fresh start, built on the principles of collaboration, innovation, and community empowerment.</p>
<p>Stay tuned for updates as we build Borr Project together!</p>]]></content>
        <author>
            <name>Pulkit Krishna</name>
        </author>
    </entry>
</feed>