Launch CS section

Author: pulkitkrishna00

blog/2025/06/24-announcing-borr-project.md

@@ -0,0 +1,45 @@
+---
+title: Announcing Borr Project
+slug: announcing-borr-project
+authors: pulkitkrishna
+---
+
+## A Community-Driven Evolution of OSSU
+
+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.
+
+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 **Borr Project**—a fork designed to revitalize and advance the OSSU computer science curriculum, both academically and as a community. 
+
+
+## Our Vision for Borr Project
+
+The core of Borr Project's vision is a commitment to **decentralized, collaborative leadership**. Unlike the current single-director model, Borr Project will adopt an open-source governance structure, drawing inspiration from other successful projects. This means:
+
+- **Community-led Development**: Decisions and initiatives will be driven by the community, fostering a more responsive and agile environment.
+- **Reduced Bureaucracy**: We aim to minimize unnecessary processes, empowering contributors to implement meaningful changes efficiently.
+- **Enhanced Collaboration**: We will actively cultivate an environment where new ideas can flourish and diverse contributions are welcomed and encouraged.
+
+## Moving Forward: Key Initiatives and Future Plans
+
+Our immediate focus for Borr Project includes a number of key initiatives to improve the learning experience and rebuild a thriving community:
+
+- **Revitalized Online Presence**: We're developing a proper, user-friendly website using Docusaurus, featuring improved SEO and accessibility, to make the curriculum more discoverable and navigable.
+- **Richer Learning Resources**:
+  - Creating video content showcasing projects built throughout the curriculum.
+    - Expanding and refining course pages for greater clarity and depth.
+    - Developing comprehensive "Setting Up Your Development Environment" guides, similar to The Odin Project's excellent resources.
+    - Adding extra practice problems with automated checks (e.g., using check50) for a more interactive learning experience.
+- **Rebuilding Community Engagement**: We're excited to re-introduce and expand community initiatives that were previously difficult to implement, such as:
+  - Regular online community meet-ups and events.
+    - Collaborative projects and study groups.
+    - Mentorship opportunities and avenues for peer support.
+
+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.
+
+## Our Commitment
+
+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.
+
+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.
+
+Stay tuned for updates as we build Borr Project together!

blog/authors.yml

@@ -0,0 +1,5 @@
+pulkitkrishna:
+  name: Pulkit Krishna
+  url: https://github.com/pulkitkrishna00
+  image_url: https://avatars.githubusercontent.com/u/72264063
+  page: true

docs/coc.md

@@ -0,0 +1,91 @@
+## Code of Conduct
+
+Thank you for being a part of the Borr project. We value your participation and want everyone to have an enjoyable and fulfilling experience. Accordingly, all participants are expected to follow this Code of Conduct, and to show respect, understanding, and consideration to one another. Thank you for helping make this a welcoming, friendly community for everyone.
+
+If you witness or experience any behavior that violates our Code of Conduct, please do not hesitate to report it to our community moderators. Together, let’s ensure a safe and inclusive environment for all members.
+
+## Scope
+
+This Code of Conduct applies to all the Borr project community spaces, including, but not limited to:
+- This server
+- The GitHub organization
+
+Communication channels and private conversations that are normally out of scope may be considered in scope if a Borr Project participant is being stalked or harassed. Social media conversations may be considered in-scope if the incident occurred under a Borr Project related hashtag, or when an official Borr Project account on social media is tagged, or within any other discussion about the Borr Project. The Borr Project reserves the right to take actions against behaviors that happen in any context, if they are deemed to be relevant to the Borr project and its participants.
+
+All participants in the Borr Project community spaces are subject to the Code of Conduct. This includes the Borr Project admins and GitHub Organization Owners. This also includes volunteers, maintainers, leaders, contributors, contribution reviewers, issue reporters, server members, and anyone participating in discussion in the Borr project community spaces.
+
+## Reporting an Incident
+
+If you believe that someone is violating the Code of Conduct, or have any other concerns, please contact the moderators in private threads in the [discord server](https://discord.gg/uR2QS36pdH) or by sending a message to modmail bot.
+
+## Our Standards
+
+The Borr Project community is dedicated to providing a positive experience for everyone, regardless of:
+- age
+- body size
+- caste
+- citizenship
+- disability
+- education
+- ethnicity
+- familial status
+- gender expression
+- gender identity
+- genetic information
+- immigration status
+- level of experience
+- nationality
+- personal appearance
+- pregnancy
+- race
+- religion
+- sex characteristics
+- sexual orientation
+- sexual identity
+- socio-economic status
+- tribe
+- veteran status
+
+### Community Guidelines
+
+Examples of behavior that contributes to creating a positive environment include:
+
+- **Be friendly.** Use welcoming and inclusive language.
+- **Be empathetic.** Be respectful of differing viewpoints and experiences.
+- **Be respectful.** When we disagree, we do so in a polite and constructive manner.
+- **Be considerate.** Remember that decisions are often a difficult choice between competing priorities. Focus on what is best for the community. Keep discussions around technology choices constructive and respectful.
+- **Be patient and generous.** If someone asks for help it is because they need it. When documentation is available that answers the question, politely point them to it. If the question is off-topic, suggest a more appropriate online space to seek help.
+- **Try to be concise.** Read the discussion before commenting in order to not repeat a point that has been made.
+
+### Inappropriate Behavior
+
+Community members asked to stop any inappropriate behavior are expected to comply immediately.
+
+We want all participants in the Borr Project community have the best possible experience they can. In order to be clear what that means, we’ve provided a list of examples of behaviors that are inappropriate for the Borr Project community spaces:
+
+- **Deliberate intimidation, stalking, or following.**
+- **Sustained disruption of online discussion, talks, or other events**. Sustained disruption of events, online discussions, or meetings, including talks and presentations, will not be tolerated. This includes ‘Talking over’ or ‘heckling’ event speakers or influencing crowd actions that cause hostility in event sessions. Sustained disruption also includes drinking alcohol to excess or using recreational drugs to excess, or pushing others to do so.
+- **Harassment of people who don’t drink alcohol or other legal substances.** We do not tolerate derogatory comments about those who abstain from alcohol or other legal substances. We do not tolerate pushing people to drink, talking about their abstinence or preferences to others, or pressuring them to drink – physically or through jeering.
+
+#### Safety versus Comfort
+
+The GNOME community prioritizes marginalized people’s safety over privileged people’s comfort, for example in situations involving:
+
+- “Reverse”-isms, including “reverse racism,” “reverse sexism,” and “cisphobia”
+- Reasonable communication of boundaries, such as “leave me alone,” “go away,” or “I’m not discussing this with you.”
+- Criticizing racist, sexist, cissexist, or otherwise oppressive behavior or assumptions
+- Communicating boundaries or criticizing oppressive behavior in a “tone” you don’t find congenial
+
+The examples listed above are not against the Code of Conduct.
+
+Outreach and diversity efforts directed at under-represented groups are permitted under the code of conduct. For example, a social event for women would not be classified as being outside the Code of Conduct under this provision.
+
+Basic expectations for conduct are not covered by the “reverse-ism clause” and would be enforced irrespective of the demographics of those involved. For example, racial discrimination will not be tolerated, irrespective of the race of those involved. Nor would unwanted sexual attention be tolerated, whatever someone’s gender or sexual orientation. Members of our community have the right to expect that participants in the project will uphold these standards.
+
+##  License
+
+The Borr Project Code of Conduct is licensed under a [Creative Commons Attribution Share-Alike 3.0 Unported License](http://creativecommons.org/licenses/by-sa/3.0/)
+
+## Attribution
+
+- The Borr Project Code of Conduct was forked from the [GNOME Project Code of Conduct](https://conduct.gnome.org/).

docs/computer-science/borrproject.webp

@@ -0,0 +1,9 @@
+---
+sidebar_position: 2
+---
+
+# Course Pages
+
+import DocCardList from '@theme/DocCardList';
+
+<DocCardList />

docs/computer-science/coursepages/automatic-parentheses.png

@@ -0,0 +1,42 @@
+# Introduction to CS
+
+This course will introduce you to the world of computer science and programming, giving you a flavor of the material to come. If you finish the course wanting more, Computer Science is likely for you!
+
+This course has been developed by MIT and is available on [MIT's OCW](https://ocw.mit.edu) platform.
+
+> Introduction to Computer Science and Programming in Python is intended for students with little or no programming experience. It aims to provide students with an understanding of the role computation can play in solving problems and to help students, regardless of their major, feel justifiably confident of their ability to write small programs that allow them to accomplish useful goals. The class uses the Python programming language.
+
+**Course Link:** [https://ocw.mit.edu/courses/6-100l-introduction-to-cs-and-programming-using-python-fall-2022/pages/material-by-lecture/](https://ocw.mit.edu/courses/6-100l-introduction-to-cs-and-programming-using-python-fall-2022/pages/material-by-lecture/)
+
+The course has been designed to accommodate people completely new to programming. However, if you find the course difficult to follow, you can try doing one of the [Intro to Programming courses](../intro-programming) and then return to this course.
+
+## Instructions
+
+1. Open the [course link](https://ocw.mit.edu/courses/6-100l-introduction-to-cs-and-programming-using-python-fall-2022/pages/material-by-lecture/) given above. You will see a list of Lectures.
+2. Clicking on the link of a particular lecture will present all the materials from that lecture to you.
+3. Work through all the course lectures as given in the link above. Watch the videos, do the finger exercises, and then solve the problem sets.
+4. You are not supposed to complete the problem sets as soon as they appear on a lecture page. You are supposed to start thinking about it from that point. The actual due dates, according to the [course calendar](https://ocw.mit.edu/courses/6-100l-introduction-to-cs-and-programming-using-python-fall-2022/pages/calendar/) are:
+
+   - PSET 0 - Before lecture 1
+   - PSET 1 - Before lecture 9
+   - PSET 2 - Before lecture 12
+   - PSET 3 - Before lecture 16
+   - PSET 4 - Before lecture 20
+   - PSET 5 - Before lecture 25
+
+6. There are links to solution of finger exercises on each lecture page. Match your answers to the given solutions to grade yourself.
+7. Each problem set come with a script and instructions to check your solution. Use them to grade yourself.
+8. You don't need to install the full Anaconda distribution to do this course. See the notes section below for more information.
+9. If you are stuck somewhere, feel free to ask questions. You can join the Borr Project chat for this course here: [https://discord.gg/JM8WwGedwW](https://discord.gg/JM8WwGedwW).
+
+## Notes
+
+1. You don't need to install the full anaconda package to do this course. You can just download the Spyder IDE from here: [https://github.com/spyder-ide/spyder/releases/latest](https://github.com/spyder-ide/spyder/releases/latest). It comes bundles with python as well as some popular scientific python libraries (all the libraries which this course uses are included), but it is not as large or complex as the full anaconda distribution. You don't need to set up python separately or anything.
+2. You can use VS Code, or any text editor/IDE you prefer. If you are using a text editor/IDE other than Spyder/Anaconda, you should note that the course sometimes ask you to run some additional statements after running a python file. To do so, run `python -i file.py`. Then you can run additional statements. 
+3. You won't get any certificate for doing this course. If you really want a certificate, you need to do the faster instructor-paced [6.00.1x course on Edx](https://www.edx.org/course/introduction-to-computer-science-and-programming-7) on Edx. Certificate of an introductory course like this is not very valuable, so unless you are absolutely sure, we recommend you to do the 6.100L course linked above instead.
+4. If for some reason you want to do the OCW version of the faster paced 6.0001 course, you can do that here: [https://ocw.mit.edu/courses/6-0001-introduction-to-computer-science-and-programming-in-python-fall-2016/](https://ocw.mit.edu/courses/6-0001-introduction-to-computer-science-and-programming-in-python-fall-2016/).
+5. The course mentions the textbook [Introduction to Computation and Programming Using Python, third edition](https://mitpress.mit.edu/9780262542364/introduction-to-computation-and-programming-using-python/) as required reading. As with any course listed on the Borr Project, please remember: All paid additions should be considered optional. You will not fail this course if you do not read the textbook. "The book and the course lectures parallel each other, though there is more detail in the book about some topics." You are not missing out on enough for it to matter.
+
+## Extra Practice
+
+1. [https://introcomp.mit.edu/spring25/practice](https://introcomp.mit.edu/spring25/practice)