Week 10 — Discussion (Adaptive Learning) · "Open Source vs. Proprietary: Should Code Be Free or Owned?"

Course: Introduction to Computer Science — CS1 / Programming Fundamentals in Python (CSCI 1101) · Silver Oak University (fictional sample) · Prof. Okafor
Objective: Objective 6 (collections — the week's technical anchor) · computing ethics: intellectual property · SLO B (reason clearly and weigh evidence)
This is Discussion 10 of 15 · Discussions group = 10% of the grade · Worth 20 points
Format: adaptive learning — instead of writing a post cold, you'll think it through in a real-time dialogue with your own AI, then post the short summary the AI writes with you (plus a link to your chat).

Evenhandedness note (read before you start). This is a genuine, unsettled debate with thoughtful people and real-world success on both sides — Linux and Wikipedia are open; Photoshop and the software running most businesses are proprietary; many companies (and the Python you're learning on) blend the two. Your job is to weigh the trade-offs and present the major positions fairly, not to crown a single "right answer." You'll take a personal position — that's expected — but a strong post represents the other side honestly too. (Factual matters — e.g., what an open-source license actually permits — should be stated accurately, not "both-sided" into mush.)

Part 1 — Student Instructions (read this first)

What this is. You'll wrestle with one of computing's oldest live arguments — should software be free and open, or owned and sold? — in a back-and-forth conversation with an AI chatbot. The AI's job is to draw out and challenge your thinking and make you argue the other side too — it will not write your post for you. When you've reasoned it through, it produces a short summary you post to the class.

How to run it (about 15–20 minutes):
1. Open any approved AI chatbot — Gemini, Claude, or ChatGPT (free versions are fine).
2. Copy everything in the box below and paste it as one single message.
3. Have the conversation. Answer honestly and push back — the better you engage, the better your summary.

A tie-in to this week's code: the Python you're learning on — and most of the libraries you'll ever use — are open source, free to read and build on. Meanwhile the apps you pay for are proprietary. You're standing in the middle of this debate every time you open the editor. Bring a concrete example you actually use.

What to submit. When the AI gives you the DISCUSSION SUMMARY, copy it and your conversation's share link, and post both to the Week 10 discussion board as your initial post by Friday, Nov 6. Then reply to two classmates by Sunday, Nov 8 — engage someone whose position differs from yours, and add a consideration they didn't raise (don't just agree or dismiss).

Integrity note. The dialogue and the analysis are yours; the posted summary must reflect your reasoning, in your own words. (This is an adaptive-learning activity — you complete it with an approved chatbot, per the course AI policy.)

Part 2 — The Discussion-Partner Prompt (copy everything in the box)

⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ COPY EVERYTHING BELOW THIS LINE ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯

You are my discussion partner for Week 10 of Introduction to Computer Science (CSCI 1101) at Silver Oak University. We are going to have a real, balanced back-and-forth about a computing-ethics question: should software be free and open (open source) or owned and sold (proprietary)? Your job is to draw out and challenge MY thinking through conversation, make me argue both sides fairly, and never write my discussion post for me.

THE QUESTION WE'RE EXPLORING
Software can be open source (anyone can read, use, modify, and share the code — e.g., Linux, Firefox, Python and its libraries, Wikipedia's software) or proprietary (the code is owned, closed, and sold or licensed — e.g., Photoshop, Windows, most commercial apps and games). The arguable question: should code be free/open or owned/sold — and when? I should take a reasoned position, but I must genuinely engage the trade-offs on both sides.

THE TRADE-OFFS TO DRAW OUT (use these privately to steer — do NOT read them to me as a checklist; bring them in as questions and counterpoints):
- The case FOR open/free: transparency (anyone can inspect the code for bugs or backdoors), collaboration and faster improvement, learning (beginners can read real code — like the Python I'm learning on), avoiding lock-in, equ/access for people who can't pay, and "many eyes" security.
- The case FOR proprietary/owned: developers and companies need to get paid to sustain the work, funded full-time teams and support, the incentive to invest in big/risky projects, accountability (a company to call when it breaks), and protecting an investment.
- The honest complications: lots of open-source projects are underfunded and maintained by unpaid volunteers (real burnout/sustainability problem); lots of "free" software monetizes your data or attention instead of charging money; and most of the real world is a blend (open-source foundations under paid products; "freemium"; companies that sell support for free software). "Free" can mean free-as-in-price or free-as-in-freedom — those are different.

HOW TO RUN THE DIALOGUE
- Open by greeting me warmly (2–3 sentences), asking my FIRST NAME, and asking ONE question that gets me to say which side I lean toward and why — using a piece of software I actually use as an example. (If I never give my name, keep going, but ask before the summary.)
- Exactly ONE question per message, then stop and wait. Never stack questions.
- Build on MY words: quote or paraphrase what I said, then go deeper — ask for a concrete example, or for who pays for the thing I'm praising.
- Make me argue the other side at least once: whatever position I take, ask me to make the strongest honest case for the opposite view (if I favor open source, ask how the maintainers eat; if I favor proprietary, ask about transparency, lock-in, and the student who can't afford the tool).
- Stay balanced and factual: don't push your own verdict, and present both sides as held by reasonable people. But if I state something factually wrong about what a license permits or what "open source" means, correct it kindly — don't "both-sides" a fact.
- Keep YOUR messages short; I should be doing most of the thinking and talking.

ENGAGEMENT GUARDS
- Don't accept a one-word or low-effort answer and move on — gently probe for the reasoning first ("Say more — who funds the thing you're calling free?").
- Don't lecture, and don't hand me my position or sentences I can paste as my post. If I ask you to "just write it," redirect with a question that helps me write it myself.
- If I go completely off-topic, give a brief friendly answer (a sentence or two) and then, IN THE SAME MESSAGE, steer us back.
- Until the summary, EVERY message must end with a question or a clear prompt to continue.
- Don't just agree with me — if my argument ignores an obvious cost or benefit on the other side, name it kindly and ask me to address it.

THE EXIT CONDITION
After at least 5 substantive exchanges AND once I have (a) stated a reasoned position with a concrete software example, (b) made the strongest honest case for the opposing side, (c) engaged at least one of the "honest complications" (funding/sustainability, data-as-payment, or the blended reality), and (d) refined or qualified my position in light of the trade-offs — whichever happens LAST — tell me we've had a good discussion and you'll summarize. Don't stop earlier; don't drag well past it.

THE DISCUSSION SUMMARY — produce it in EXACTLY this format, drawn ONLY from what I actually said (never invent a position I didn't take):
WEEK 10 DISCUSSION SUMMARY — Open Source vs. Proprietary
Student: [name] | Date: ___
My position (and the software example I used): ___
The strongest case for the OTHER side (in my words): ___
A real complication I weighed (funding / data-as-payment / blended reality): ___
Where I landed after weighing the trade-offs: ___
Then say, verbatim: "Copy this summary AND your share link to this chat, and post both to the Week 10 discussion board as your initial post — then reply to two classmates, ideally someone who landed differently." End with one genuine sentence about something I reasoned well.

GETTING STARTED
Begin now: greet me, ask my first name, and ask your opening question.

⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ COPY EVERYTHING ABOVE THIS LINE ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯

Participation rubric (instructor) — 20 points

Grading note (Prof. Okafor): the posted artifact is the AI-written summary + the chat share link; spot-check a few links against the summary. The thing to reward is genuine weighing of both sides — a one-sided rant (in either direction) or a "both are fine, who cares" shrug both miss the point. The strongest posts name who pays and who benefits.

Canvas placement block

canvas_object    = DiscussionTopic
title            = "Week 10 Discussion — Open Source vs. Proprietary (adaptive)"
assignment_group = "Discussions"
points_possible  = 20
grading_type     = points
discussion_type  = adaptive
due_offset_days  = 3     # initial post (AI summary + chat share link)
reply_offset_days = 5    # two peer replies
published        = true
submission_note  = "Initial post = the AI discussion summary + the chat share link; then reply to two classmates (ideally someone who landed differently)."
provenance       = "~ Prof. Okafor's edition · Fall 2026 · built with thecoursemaker.com"

Traditional variant — for comparison. This sample course is configured adaptive learning, so its actual Week-10 discussion is the BYOAI-dialogue version in G-discussion-week-10.md. This file shows the same Week-10 topic built the traditional way — an instructor-posted prompt where students write their own post and reply to peers — so you can see both formats side by side. (Choosing discussion_type = traditional at course setup generates this style instead.)

Course: Introduction to Computer Science — CS1 / Programming Fundamentals in Python (CSCI 1101) · Silver Oak University (fictional sample) · Prof. Okafor
Objective: Objective 6 (collections — the week's technical anchor) · computing ethics: intellectual property · SLO B (reason clearly and weigh evidence)
Discussion 10 of 15 · Discussions group = 10% of the grade · Worth 20 points

Evenhandedness note (read before you post). This is a real, unsettled debate with thoughtful people and major success stories on both sides — Linux, Firefox, Wikipedia, and the Python you're learning on are open; Photoshop, Windows, and most commercial apps are proprietary; and a huge share of the real world blends the two. Present the major positions and trade-offs fairly and take a reasoned stand — don't pretend there's one obvious answer, and don't "both-sides" a plain fact (e.g., what an open-source license actually lets you do). A strong post argues its side and represents the other side honestly.

The Discussion

This week you've been working with the collections that make real software possible — and nearly every tool you used to do it (Python, its libraries, the online editor) is open source: free to read, use, and build on. Meanwhile, the apps you pay for are proprietary: owned, closed, and sold. That contrast is one of computing's longest-running ethical debates, and it's worth your thinking.

Your initial post (by Friday, Nov 6 — about 150–200 words). Take a position on the question and defend it while fairly representing the other side:

• The question: Should software be free and open (open source) or owned and sold (proprietary) — and when?
• Make your case with a concrete example. Name a real piece of software you actually use (open or proprietary) and use it to ground your argument.
• Weigh the trade-offs — name at least one cost and one benefit on each side. For open/free: transparency, collaboration, learning, access, avoiding lock-in — but also the real problem that many open projects are underfunded and run by unpaid volunteers. For proprietary/owned: developers and companies get paid to sustain the work, fund full-time teams, and stay accountable — but at the cost of closed code, lock-in, and price barriers.
• Acknowledge the messy middle. "Free" can mean free-of-cost or free-as-in-freedom; lots of "free" apps actually charge you in data and attention; and most real systems blend open foundations with paid products. Where do you land after weighing all that?

Replies (by Sunday, Nov 8). Reply to at least two classmates — and make at least one of them someone whose position differs from yours. Add a consideration they didn't raise (e.g., who funds the "free" tool they praised, or the transparency cost of the proprietary tool they defended). One or two solid sentences each. Disagree respectfully; the goal is sharper thinking, not winning.

What a strong post looks like: "I lean open-source: I learned to code partly by reading real Python libraries, which I couldn't do with closed software, and 'many eyes' can catch security bugs. But I won't pretend it's free of cost — someone has to maintain these projects, and a lot of maintainers burn out doing it unpaid, which is a genuine weakness. The proprietary side has a real point: paid teams ship polished, supported tools and have someone accountable when things break. Where I land: open by default for infrastructure and learning, but I don't begrudge paying for proprietary apps when the funding keeps good software alive — and I'd want 'free' apps to be honest about whether I'm paying with my data."

Why this matters: as a programmer you'll constantly choose which to use, build, or contribute to — and these choices have real consequences for users, security, and who can participate. Thinking clearly about the trade-offs now makes you a more responsible developer later.

Integrity & AI note. Write your post in your own words — that's the point of the exercise. You may use an approved chatbot (Gemini, Claude, or ChatGPT) to brainstorm or check a fact, but the post you submit must be your own thinking; if AI helped, add a one-line note saying which tool and how. (Note: this is the traditional format. In this course's actual adaptive discussion, working through the argument with the chatbot — and being pushed to argue both sides — is the activity; see G-discussion-week-10.md.)

Participation rubric — 20 points

Grading note (Prof. Okafor): you read and grade each student's posted writing + their two replies against this rubric — the traditional flow. Reward genuine two-sided weighing; a one-sided rant (either direction) or a "whatever, both are fine" shrug both fall short. (The adaptive version instead has students submit an AI-dialogue summary + chat link.)

Canvas placement block

canvas_object    = DiscussionTopic
title            = "Week 10 Discussion — Open Source vs. Proprietary (traditional)"
assignment_group = "Discussions"
points_possible  = 20
grading_type     = points
discussion_type  = traditional
due_offset_days  = 3     # initial post
reply_offset_days = 5    # two peer replies
published        = true
submission_note  = "Students write an original initial post and reply to two classmates (at least one with a differing view) in the Canvas discussion."
provenance       = "~ Prof. Okafor's edition · Fall 2026 · built with thecoursemaker.com"