|
| 1 | +--- |
| 2 | +title: GSoC Application Guide |
| 3 | +nav_order: |
| 4 | +parent: GSoC |
| 5 | +layout: default |
| 6 | +permalink: "/gsoc-application-guide" |
| 7 | +lang: en |
| 8 | +--- |
| 9 | + |
| 10 | + |
| 11 | +# 📖 Google Summer of Code (GSoC) Application Guide |
| 12 | + |
| 13 | +🚀 **Want to write a strong GSoC proposal?** Follow this guide to increase your chances of being selected as a contributor for **BIRDS Open Source**! |
| 14 | + |
| 15 | +--- |
| 16 | + |
| 17 | +## 🏆 What Makes a Strong Proposal? |
| 18 | +A great GSoC proposal should: |
| 19 | +✅ Clearly define the **problem** and how your project will solve it |
| 20 | +✅ Demonstrate your **understanding** of the project scope |
| 21 | +✅ Show a **realistic timeline** with milestones |
| 22 | +✅ Highlight your **skills** and **past experience** |
| 23 | +✅ Include a plan for **testing, documentation, and community engagement** |
| 24 | + |
| 25 | +--- |
| 26 | + |
| 27 | +## ✍️ **How to Structure Your Proposal** |
| 28 | + |
| 29 | +### 1️⃣ **Personal Information** |
| 30 | +- Full Name |
| 31 | +- GitHub/Portfolio Link |
| 32 | +- Email & Preferred Contact Method |
| 33 | +- Timezone & Available Working Hours |
| 34 | + |
| 35 | +### 2️⃣ **Synopsis** |
| 36 | +- **What is your project about?** (1-2 sentences) |
| 37 | +- **Why is it important?** |
| 38 | +- **What problem does it solve?** |
| 39 | + |
| 40 | +### 3️⃣ **Benefits to the Community** |
| 41 | +- How will this project **help BIRDS Open Source**? |
| 42 | +- How will it **benefit the open-source space community**? |
| 43 | +- How will the final output be **used after GSoC**? |
| 44 | + |
| 45 | +### 4️⃣ **Deliverables & Milestones** |
| 46 | +- **List the key goals and features** you aim to complete |
| 47 | +- **Break your timeline into 3 phases**: |
| 48 | + - **Community Bonding Period**: Research, setup, first contributions |
| 49 | + - **Phase 1**: Develop core functionality, initial testing |
| 50 | + - **Phase 2**: Expand features, refine implementation |
| 51 | + - **Final Phase**: Complete, test, and document |
| 52 | + |
| 53 | +### 5️⃣ **Technical Details** |
| 54 | +- **What technologies will you use?** (Languages, frameworks, tools) |
| 55 | +- **How will you implement your solution?** |
| 56 | +- **Any potential challenges, and how will you overcome them?** |
| 57 | + |
| 58 | +### 6️⃣ **Previous Experience** |
| 59 | +- **Have you contributed to open source before?** (Not mandatory but helpful) |
| 60 | +- **Relevant projects you've worked on** (GitHub links if possible) |
| 61 | +- **Why are you interested in BIRDS Open Source & space projects?** |
| 62 | + |
| 63 | +### 7️⃣ **Commitment & Availability** |
| 64 | +- How many hours per week can you dedicate? |
| 65 | +- Do you have any **other commitments** during GSoC? |
| 66 | + |
| 67 | +--- |
| 68 | + |
| 69 | +## 🎯 **Tips for Writing a Strong Proposal** |
| 70 | +✅ **Be Clear & Concise** – Get to the point, avoid unnecessary details |
| 71 | +✅ **Show Initiative** – Try contributing before applying (fix a bug, improve docs) |
| 72 | +✅ **Engage with Mentors** – Ask questions, discuss ideas before submission |
| 73 | +✅ **Be Realistic** – Propose a plan you can complete within GSoC’s timeframe |
| 74 | +✅ **Format Properly** – Use bullet points, headings, and paragraphs for readability |
| 75 | + |
| 76 | +--- |
| 77 | + |
| 78 | +## 📅 **Next Steps** |
| 79 | +📌 **Join Our Community** – Ask mentors for feedback on your draft |
| 80 | +📌 **Submit Early** – Avoid last-minute issues! |
| 81 | +📌 **Follow Up** – Stay engaged and show your enthusiasm |
| 82 | + |
| 83 | +📨 **Need Help? Contact Us!** |
| 84 | +📌 **GitHub Discussions:** [BIRDS Open Source](https://github.com/BIRDSOpenSource) |
| 85 | +📌 **Email:** birds_opensource@lean-sat.org |
| 86 | + |
| 87 | +🚀 **We look forward to your application! Good luck!** |
0 commit comments