update FAQ

Author: andibraeu

.gitignore

@@ -8,6 +8,10 @@ _site/
 .jekyll-cache/
 .jekyll-metadata
 vendor
+gems
+specifications
+cache
+extensions
 _projects/*.yaml
 # GitBook rules
 # Node rules:

_faq/001_will_freifunk_apply_for_gsoc2021.md

@@ -1,5 +1,5 @@
 ---
-question: "Will freifunk apply for Google Summer of Code 2025?"
+question: "Will freifunk apply for Google Summer of Code 2026?"
 order: 1
 ---
-Yes, freifunk will apply as an organization for Google Summer of Code - 2025. You might read the [GSoC Timeline](https://developers.google.com/open-source/gsoc/timeline) to get an idea of how things will proceed.
+Yes, freifunk will apply as an organization for Google Summer of Code - 2026. You might read the [GSoC Timeline](https://developers.google.com/open-source/gsoc/timeline) to get an idea of how things will proceed.

_faq/004_how_to_write_a_proposal.md

@@ -11,3 +11,4 @@ We have some notes you should keep in mind for your proposal:
 * Refine and break down your milestones (maybe into stories), also together with the mentor.
 * Try to estimate what stories you can work on within the GSoC period. Please keep in mind that we have 3 kinds of projects: large with 350 hours, medium with 175 hours and small with 90 hours over 10 weeks.
 * Use our application template to introduce yourself and describe your project. The resulting document you should upload to the Google Summer of Code program website.
+* If there are some beginner issues or tasks, you can use them as a showcase

_faq/005_contact_to_mentors.md

@@ -5,3 +5,5 @@ order: 5
 We act as an umbrella organization, so there are a bunch of possibilities to contact mentors. Most of our mentors can be contacted via GitHub. Please try to contact your mentor first!
 
 If you're in doubt or don't know the project location, ask our [international mailing list](https://lists.freifunk.net/mailman/listinfo/wlanware-freifunk.net) or at [matrix](https://matrix.to/#/!DmXQbxcSxGYgXDYrBs:bau-ha.us?via=bau-ha.us). Please keep in mind that people there don't know the projects or your ideas in detail!
+
+**Please note:** Our mentors are volunteers who contribute their time and expertise on a voluntary basis in their free time. They do not receive any payment for their mentoring work.

_faq/008_what_did_you_achieve.md

@@ -4,4 +4,6 @@ order: 8
 ---
 We attended Google Summer of Code first in 2009. Over 15 years, we completed a lot of valuable projects, won many new contributors and community members that help us to grow and continue our work.
 
-You can find a list of completed projects since 2020 at our [completed projects page](https://projects.freifunk.net/#/completed).
+You can find a list of completed projects since 2020 at our [completed projects page](https://projects.freifunk.net/#/completed).
+
+Our contributors have also written blog posts about their GSoC experiences. You can read all GSoC-related blog posts at [blog.freifunk.net/tag/gsoc/](https://blog.freifunk.net/tag/gsoc/).

_faq/009_eligibility.md

@@ -0,0 +1,18 @@
+---
+question: "Who can apply for Google Summer of Code?"
+order: 9
+---
+Google Summer of Code has specific eligibility requirements that are set by Google. These requirements typically include:
+
+* You must be at least 18 years old at the time of registration
+* You must be a student or new to open source software and software development
+* You must be eligible to work in the country where you will reside during the program
+
+Please check the [official GSoC eligibility requirements](https://developers.google.com/open-source/gsoc/faq#eligibility) on Google's website for the most current and detailed information, as these requirements may change from year to year.
+
+In addition to Google's requirements, we expect applicants to have:
+* Basic technical skills relevant to the project they're applying for
+* Motivation and commitment to work on the project
+* Good communication skills in English
+* Willingness to learn and collaborate with the community
+

_faq/010_project_sizes.md

@@ -0,0 +1,16 @@
+---
+question: "What are the different project sizes (90h, 175h, 350h)?"
+order: 10
+---
+Google Summer of Code offers three project sizes, which are defined by Google:
+
+* **Small projects**: 90 hours over 10 weeks
+* **Medium projects**: 175 hours over 10 weeks  
+* **Large projects**: 350 hours over 10 weeks
+
+The project size is determined by the scope and complexity of the work. When you look at our project ideas, each project will indicate its size. You should choose a project size that matches your availability and the project's requirements.
+
+The hours should be distributed evenly over the 10-week coding period, or you can discuss a different schedule with your mentor. Projects can also be extended or completed faster if needed, but this should be coordinated with your mentor.
+
+Please refer to [Google's official documentation](https://developers.google.com/open-source/gsoc/faq#project-sizes) for the most current information about project sizes and stipends.
+

_faq/013_expectations.md

@@ -0,0 +1,36 @@
+---
+question: "What are the expectations during GSoC?"
+order: 13
+---
+During Google Summer of Code, we have several expectations for our contributors:
+
+**Time Commitment:**
+* Hours should be distributed evenly over the 10-week coding period, or coordinated with your mentor
+* Projects can be extended or completed faster if needed, but this should be discussed with your mentor
+
+**Communication:**
+* Regular updates to your mentor (at least one meeting per week is the minimum expectation)
+* Active participation in community discussions
+* Regular communication about progress, challenges, and questions
+
+**Blog Posts:**
+We expect three blog posts during the program:
+* **Beginning**: An introductory post about yourself and your project
+* **Midterm**: A midterm evaluation post summarizing your progress
+* **Final**: A final blog post describing what you achieved
+
+**Meetings:**
+* Regular one-on-one meetings with your mentor (schedule to be discussed personally)
+* Participation in joint meetings with all GSoC projects (these are organized for all contributors)
+
+**Code Quality:**
+* Write clean, well-documented code
+* Include tests where appropriate
+* Follow the project's coding standards and best practices
+* Respond to code review feedback promptly
+
+**Community Engagement:**
+* Be respectful and collaborative
+* Ask questions when you need help
+* Share your knowledge and experiences
+

_faq/015_not_selected.md

@@ -0,0 +1,26 @@
+---
+question: "What if I'm not selected for GSoC?"
+order: 15
+---
+Not being selected for Google Summer of Code doesn't mean you can't contribute to our projects!
+
+**You can still contribute:**
+* All our projects are open source and welcome contributions
+* You can work on issues, submit pull requests, and participate in discussions
+* Many contributors started without GSoC and became valuable community members
+
+**Important difference:**
+* If you contribute outside of GSoC, you cannot expect formal mentoring
+* Our mentors volunteer their time specifically for GSoC participants
+* We don't have the capacity to provide structured mentoring for all contributors
+
+**Other opportunities:**
+* You can apply again next year if you're still eligible
+* Some projects have other mentorship programs or initiatives
+* Contributing now will strengthen your application for future GSoC rounds
+
+**Getting started:**
+* Check out our [projects page](https://projects.freifunk.net/#/projects) for open issues
+* Join our [community channels](https://projects.freifunk.net/#/faq/007_how_to_get_in_touch_with_the_community) to introduce yourself
+* Start with small contributions to get familiar with the codebase
+

resources/css/coala.css

@@ -844,3 +844,18 @@ a.chip i {
   text-indent: 1em;
   box-shadow: 0 6px 10px 0 rgba(0, 0, 0, 0.14), 0 1px 18px 0 rgba(0, 0, 0, 0.12), 0 3px 5px -1px rgba(0, 0, 0, 0.3) !important;
 }
+
+/* Hidden AI prompt: visible to machines (when copying) but not to humans */
+.ai-prompt {
+  position: absolute;
+  left: -9999px;
+  width: 1px;
+  height: 1px;
+  overflow: hidden;
+  opacity: 0;
+  pointer-events: none;
+  user-select: text; /* Allow text selection for copying */
+  -webkit-user-select: text;
+  -moz-user-select: text;
+  -ms-user-select: text;
+}