From 25e7002ecdb171c987fe571a36f553b1fc1604a3 Mon Sep 17 00:00:00 2001 From: Angelica Willianto Date: Wed, 26 Nov 2025 19:25:47 +0800 Subject: [PATCH 1/2] docs: view scout approach to contribution guidelines --- .github/CONTRIBUTING.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/.github/CONTRIBUTING.md b/.github/CONTRIBUTING.md index 7889131..705a617 100644 --- a/.github/CONTRIBUTING.md +++ b/.github/CONTRIBUTING.md @@ -249,6 +249,10 @@ Once your PR is ready, assign reviewers and mark it as "ready to review." But be > [!NOTE] > When contributing, it's essential to report time accurately, including all stages of development (planning, implementation, QA). We encourage opening a PR at the start of your work, even during the planning or investigation phase. Programming and designing isn't just about writing code or creating designs; it also involves planning (40%) and QA (20-30%). +#### Scout approach + +If you ever have free time, be proactive and apply the scout approach: own the job, look for PRs that still need reviewers, and offer timely feedback so work keeps moving. + #### Code Quality and Reviews Aim for solutions that work correctly 99.9% of the time. Be independent and thorough in your QA - reviewers are not QA team members but are there for a final safety check. We expect contributors to deliver bug-free software, understanding that perfection is an ideal. Stand firm in your solutions and avoid unnecessary revisions based on subjective feedback. From 055309bb8c2006f44f4a2c65337572edc74c5feb Mon Sep 17 00:00:00 2001 From: Angelica Willianto Date: Wed, 26 Nov 2025 19:29:17 +0800 Subject: [PATCH 2/2] docs: update contribution guidelines for clarity and structure --- .github/CONTRIBUTING.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/.github/CONTRIBUTING.md b/.github/CONTRIBUTING.md index 705a617..f29730a 100644 --- a/.github/CONTRIBUTING.md +++ b/.github/CONTRIBUTING.md @@ -249,10 +249,10 @@ Once your PR is ready, assign reviewers and mark it as "ready to review." But be > [!NOTE] > When contributing, it's essential to report time accurately, including all stages of development (planning, implementation, QA). We encourage opening a PR at the start of your work, even during the planning or investigation phase. Programming and designing isn't just about writing code or creating designs; it also involves planning (40%) and QA (20-30%). -#### Scout approach +### Scout approach If you ever have free time, be proactive and apply the scout approach: own the job, look for PRs that still need reviewers, and offer timely feedback so work keeps moving. -#### Code Quality and Reviews +### Code Quality and Reviews Aim for solutions that work correctly 99.9% of the time. Be independent and thorough in your QA - reviewers are not QA team members but are there for a final safety check. We expect contributors to deliver bug-free software, understanding that perfection is an ideal. Stand firm in your solutions and avoid unnecessary revisions based on subjective feedback.