Understanding Project Ownership: A GitHub Case Study

Article Summary

Many companies today use digital tools to manage their projects, like software code. GitHub, a big platform for software development, had a challenge. They had over 11,000 active projects without a clear owner. This meant that when security problems appeared, it was difficult and risky to fix them because nobody knew who was responsible. They spent too much time trying to find the right people to make decisions.

To solve this, GitHub started a project. They aimed to make sure every active project had an owner. First, they checked who owned projects that were already linked to specific services. Then, they asked teams and individuals to claim ownership of other projects. If a project did not get an owner after 30 days, it was put into storage. This storage step was safe because projects could be taken out of storage later if needed. The company also made a new rule: every new project must have an owner from the very beginning. This project took less than 45 days. Now, GitHub has about 3,000 active projects, and all of them have a clear owner. Many old, unused projects were moved to storage, which helps make their system safer and more organized. This shows how important clear ownership is for managing digital assets in a company.

Key Vocabulary

Comprehension Questions

1. What was the main problem GitHub faced with its repositories?

• They had too few projects to manage.
• They had too many projects without clear owners.
• They did not have enough storage space for their projects.
• Their projects were too old to be useful.

2. How long did GitHub's project to fix the ownership problem take?

• More than a year
• Exactly 30 days
• Less than 45 days
• Several months

3. Why was it risky to fix security issues for projects without clear owners?

• Because the projects were too old.
• Because they might change something important without knowing who to ask.
• Because it took too much time to find the security problem.
• Because the security problems were not very serious.

4. What was the purpose of putting unused projects into storage instead of deleting them?

• To save money on storage space.
• To make sure they could never be used again.
• To allow them to be accessed and used again if someone needed them.
• To make the system look cleaner without actually doing anything.

5. Do you think a 30-day grace period for assigning ownership is fair for employees in a large company? Why or why not?

• Yes, it gives enough time for everyone to act.
• No, it's too short for busy employees.
• Maybe, it depends on how well the company communicated the new rule.
• Only if the projects are very small and easy to manage.

Discussion Prompts

1. How do you currently keep track of tasks or projects in your team or company? Is there a clear owner for everything?

2. What problems can happen when nobody clearly owns a task, project, or piece of information at work?

3. How important is clear ownership in your company's projects? Can you give an example of when it was helpful or unhelpful?

Live Session Prep & Cheat Sheet

🎯 Speaking Targets (Vocabulary)

Try to use these target terms in your speaking turns:

• Repository
• Ownership
• Archived
• Custom properties
• Mitigate

⚙️ Grammar Target Formula

Expressing Past Obligation ('Had to') and Present Necessity ('Need to'): Past: Subject + had to + Base Verb. Present: Subject + need(s) to + Base Verb.

💬 Discussion Openers

Use these phrases to open or structure your arguments:

• In my opinion...
• What do you think about...?
• I agree because...
• I don't agree with that, actually.
• Could you explain more?

Teacher Notes

This lesson focuses on understanding the importance of clear ownership in project management, using GitHub's experience as an example. Encourage students to connect the concepts to their own workplaces. The grammar point helps express necessities and obligations in a professional context. Pay attention to correct usage of 'had to' vs 'need to' and proper sentence structure for B1 learners.

Speaking Class Facilitation Guide (Tutors/Moderators Only)

🎭 Role-Play Scenario

Situation: Your company is introducing a new policy that requires every active project to have a clear owner. If a project does not have an owner, it will be put into storage after a month.

Goal: The Project Manager must explain the new policy and calm the Team Member's concerns. The Team Member needs to understand the policy and feel their concerns are heard.

⚖️ Debate Prompt

{"side_a":["Yes, clear ownership improves organization and security.","It helps to know who is responsible for each task.","It prevents confusion and wasted time when problems appear."],"side_b":["No, it can create too much paperwork for small projects.","Sometimes projects are shared, and one owner is not suitable.","It might slow down new ideas or quick experiments."],"question":"Should all company projects always have a clear owner, even small or temporary ones?"}

💡 Discussion Facilitation Tips

Encourage students to use the vocabulary terms like 'ownership', 'repository', and 'archived'. Ask follow-up questions to prompt deeper thinking, such as 'Can you give an example from your own work?' Gently correct errors related to 'had to' and 'need to' during the discussion, perhaps by rephrasing correctly.

Session Blueprint

How do you currently keep track of tasks or projects in your team or company? Is there a clear owner for everything?