Computer Science · Class 11

Active learning ideas

Open Source Software and Licensing

When students actively engage with open-source concepts through debates, case studies, and real-world examples, they move beyond memorisation to grapple with ethical and practical dilemmas. Hands-on activities make licensing principles tangible, helping students see how these rules shape software ecosystems around them.

• CBSE Learning Outcomes
• CBSE: Society, Law and Ethics - IPR and E-Waste - Class 11

• 30–50 min
• Pairs → Whole Class
• 4 activities

Activity 01

• World Café
• 45 min · Small Groups

Debate Format: Open Source vs Proprietary

Divide class into two teams to argue for open source or proprietary software using prepared points on innovation, cost, and security. Each team presents for 5 minutes, followed by rebuttals and a class vote. Conclude with a summary of key differences.

Compare the principles of open-source software with proprietary software.

Facilitation Tip

During the debate, assign roles explicitly to ensure every student participates, including roles that argue for hidden costs of open source and proprietary software's limitations in customisation.

What to look for

Pose this question: 'Imagine you are starting a new software company. Would you choose an open-source or proprietary model? Justify your decision by citing at least two benefits and two challenges of your chosen model, referencing specific licenses where applicable.'

• Understand
• Apply
• Analyze
• Social Awareness
• Relationship Skills

Activity 02

• World Café
• 30 min · Pairs

Licence Matching: Case Study Analysis

Provide excerpts from GPL, MIT, and Apache licences alongside software scenarios. In pairs, students match licences to scenarios and justify choices. Discuss as a class which licence best fits Indian software firms.

Explain the benefits and challenges associated with open-source development.

Facilitation Tip

For the licence matching activity, provide students with actual licence texts first, then let them analyse real-world projects like Firefox or LibreOffice to see licences in action.

What to look for

Provide students with short descriptions of two software scenarios: one requiring extensive customisation and another needing a stable, widely supported platform. Ask them to identify which scenario might benefit more from open-source software and explain why, referencing license types.

• Understand
• Apply
• Analyze
• Social Awareness
• Relationship Skills

Activity 03

• World Café
• 50 min · Small Groups

Project Hunt: Real-World OSS Examples

Students research and present one open source project like Ubuntu or Mozilla Firefox, noting its licence, contributors, and impact. Groups compile findings into a shared class poster. Include challenges faced by developers.

Evaluate the role of open-source software in fostering innovation and collaboration.

Facilitation Tip

In the role play, give students licence summaries upfront so they focus on negotiation strategies rather than licence details during the simulation.

What to look for

On a slip of paper, ask students to write down one key difference between the GPL and MIT licenses and one example of a well-known open-source project they learned about.

• Understand
• Apply
• Analyze
• Social Awareness
• Relationship Skills

Activity 04

• Role Play
• 35 min · Small Groups

Role Play: Contributor Negotiation

Assign roles as developer, user, and licensor in a scenario where code is shared. Groups negotiate terms under different licences, then perform skits. Debrief on collaboration benefits.

Compare the principles of open-source software with proprietary software.

What to look for

Pose this question: 'Imagine you are starting a new software company. Would you choose an open-source or proprietary model? Justify your decision by citing at least two benefits and two challenges of your chosen model, referencing specific licenses where applicable.'

• Apply
• Analyze
• Evaluate
• Social Awareness
• Self-Awareness

A few notes on teaching this unit

Teachers find success when they start with students' existing assumptions and use the activities as evidence-checking exercises. Avoid lecturing on licence terms; instead, let students discover constraints and freedoms through structured analysis. Research shows that peer discussions about real projects like Linux or Blender help students grasp the balance between freedom and responsibility in open source.

By the end of these activities, students will articulate clear differences between licences, justify choices using evidence, and demonstrate how community collaboration impacts software quality. They will also recognise both the strengths and limitations of open-source models in real-world contexts.

---

Watch Out for These Misconceptions

• During the debate on open source vs proprietary, listen for statements claiming open-source software is always free. Use the Licence Matching activity materials to redirect by asking students to examine project donation pages or service offerings.

  During the debate, pause discussions when this claim arises and refer students to the Licence Matching activity materials, where they can see that projects like GIMP rely on paid services or donations, making the 'free' claim inaccurate.

• During the Licence Matching activity, expect some students to assume all open-source licences permit unrestricted commercial use. Use the Debate Format activity to redirect by asking students to compare GPL's 'copyleft' clause with MIT's permissiveness.

  During the Licence Matching activity, guide students back to the Debate Format activity by asking them to revisit licence clauses they discussed, such as GPL's requirement to share derivative works, to correct the assumption of unrestricted use.

• During the Project Hunt activity, some students may claim open-source software lacks quality because it is 'amateur'. Use the Role Play activity to redirect by asking them to analyse bug trackers or contribution guidelines from projects they researched.

  During the Project Hunt activity, if this claim arises, steer students toward the Role Play activity by referencing how projects like the Linux kernel or Blender use structured contribution processes and peer reviews to maintain high standards.

---

Methods used in this brief

• World Café
• Role Play