-
Notifications
You must be signed in to change notification settings - Fork 6
solution 08 culture
This shows example reflection and triage output. Your response will be personal and different.
Reading the CODE_OF_CONDUCT.md and CONTRIBUTING.md files helped me understand that open source projects are communities, not just code. The contributing guide made it clear that you do not need to be an expert to participate -- filing a good issue is a contribution.
One thing I had not considered: accessibility is not just about the product. The way we write issues, name branches, and structure documentation affects whether people with disabilities can participate in the development process itself.
If your challenge asked you to evaluate an issue and recommend a label:
Issue: "The welcome page loads slowly on mobile"
Recommended label:
bugJustification: This describes unexpected behavior (slow loading) that affects the user experience. It is not a feature request because the page is supposed to load quickly. The
buglabel helps maintainers prioritize fixes.Additional label suggestion:
accessibility-- slow loading disproportionately affects users on assistive technology where each reload is more disruptive.
- Focus on CODE_OF_CONDUCT.md and what it means for inclusive collaboration
- Focus on CONTRIBUTING.md and what you learned about the contribution process
- Compare this project's guidelines to another open source project you have seen
The learning objective is understanding that open source has cultural norms, not just technical ones. Any thoughtful reflection that shows engagement with the governance and contribution documents is a success.
Use these official references when you need the current source of truth for facts in this chapter.
Use this map to verify facts for each major section in this file.
- Example reflection comment: GitHub Docs, home, GitHub Changelog
- Example triage recommendation: GitHub Docs, home, GitHub Changelog
- Alternate approaches: GitHub Docs, home, GitHub Changelog
- What matters: GitHub Docs, home, GitHub Changelog
- 00 Setup
- 01 Tools
- 02 GitHub
- 03 Repositories
- 04 Learning Room
- 05 Issues
- 06 Pull Requests
- 07 Merge Conflicts
- 08 Culture
- 09 Labels Milestones Projects
- 10 Day 1 Close
- 11 VS Code Interface
- 12 VS Code Accessibility
- 13 How Git Works
- 14 Git in Practice
- 15 Code Review
- 16 Copilot
- 17 Issue Templates
- 18 Fork and Contribute
- 19 Accessibility Agents
- 20 Build Your Agent
- 21 GitHub Accessibility and Open Source
- 22 What Comes Next
Use these official references when you need the current source of truth for the wiki navigation structure and the GitHub workflow concepts represented by these links.
- Start: GitHub Docs, home, GitHub Changelog
- Day 1: GitHub Docs, home, GitHub Changelog, About Git, GitHub flow, About pull requests
- Day 2: GitHub Docs, home, GitHub Changelog, About Git, GitHub flow, About pull requests
- Reference: GitHub Docs, home, GitHub Changelog
- Contributors: GitHub Docs, home, GitHub Changelog