角色與責任
透過集合功能整理內容
你可以依據偏好儲存及分類內容。
關於 GSoC 計畫中，各角色的預期要求，常常出現許多問題。許多機構不斷發展
這個情況也相當多元本說明文件旨在實現所有參與組織的期望標準。
個別機構可能具有其他角色和責任。詳情請洽詢機構管理員。
GSoC 貢獻者責任
...給導師
- 提交品質工作 (程式碼)
- 定期告知工作已完成、您打算採取的後續行動，以及阻礙
- 有任何因素造成你無法達成目標時請求協助
- 讓大家知道你今天還活著
- 明顯超前工作範圍時，重新評估工作範圍
- 與你的導師「和」廣大的社群溝通交流
- 盡早在工作能力降低 (例如家庭、健康、其他工作) 時通知工作量
- 聆聽並回覆意見回饋
...給機構組織管理員
- 出現下列情況時請通知對方
- 與任何導師或社群成員互動的問題
- 與您工作或工作計畫變動有關的重大意見
導師責任
...給您的機構管理員
- 說明時間安排和互動期望
- 盡早在指導能力減少 (例如家人、健康、休假) 時發出通知
- 在 GSoC 貢獻者有問題時收到通知
- 缺乏通訊、活動、瀏覽權限 (MIA) 或進度
- 違反參與者協議的行為 (例如抄襲、騷擾、詐欺)
- 身體不適或卸任
- 正式評估 GSoC 貢獻者參與情形
- 請先與管理員和 GSoC 貢獻者溝通交流，再嘗試失敗
...供 GSoC 貢獻者參與
- 協助和/或教導 GSoC 貢獻者如何
- 成為社群的一分子
- 更有效率地與開放式溝通
- 與貴機構偏好的通訊管道 (IRC、Slack 等) 合作
- 使用貴機構的版本管控系統
- 提出好問題，並且獲得問題的解答
- 提供有說服力的技術論點和建設性討論
- 正確提供作者資訊及選取開放原始碼授權的方式
- 激勵自己並保持工作效率
- 解決棘手的技術問題
- 隨時掌握進度，以便 GSoC 貢獻者瞭解他們的狀態
- 定期溝通交流：
- 提供具建設性的意見、耐心等待並保持尊重
- 建立實際可行的工作目標和時程期望
- 在明顯超前或落後使用 GSoC 貢獻者重新評估範圍
- 與開發人員和社群合作，協助他們接受 GSoC 貢獻者工作
機構管理員的責任
...對 Google
- 框架機構參與情況、機構選擇條件和機構專屬作業程序
- 提交機構申請並擔任機構代表
- 擔任 Google 的溝通聯絡
- 在 36 小時內回覆 Google 洽詢的所有問題
- 檢舉《參與者協議》違規情形 (例如騷擾、抄襲、詐欺)
- 回報 GSoC 貢獻者解除權
- 確保符合所有期限 (例如運算單元要求、輔導評估、建立機構付款帳戶)
- 挑選並邀請值得信賴、有能力且合格的導師
- 提供並維護足夠的專案構想
- 監督所有導師和 GSoC 貢獻者的活動，確保實現責任
- 回覆 Google 的 GSoC 問卷調查 (包括 GSoC 貢獻者留存率等問題)
...給導師
- 框架機構參與情況、輔導者需求條件、失敗流程和程序
- 在計畫開始前告知導師期望的事項
- 說明 GSoC 貢獻者選擇、繼續參與和關閉政策
- 為運算單元分配提供選取條件
- 說明《參與者協議》違反與失敗的處理方式
- 持續評估導師與 GSoC 貢獻者的互動
- 讓導師知道需要更多專案構想
- 在計畫前後持續與導師定期溝通
- 務必提供充分且適當的輔導服務，特別是在假日附近
...供 GSoC 貢獻者參與
- 向 GSoC 協作者說明聯絡機構管理員的方式、時間和原因
- 確保已引進 GSoC 貢獻者完成適當整合
- 說明特定機構的需求 (例如時間、程式碼、通訊、授權)
- 傳達特定機構組織的期望 (例如行為、最佳做法、瀏覽權限)
- 說明期限、接受條件和失敗/關閉政策
- 監控通訊內容，確保所有不當行為都獲得解決
- 事先通知 GSoC 貢獻者可能故障或關閉
特別感謝資深 GSoC 和 GCI 機構管理員 Sean、Terri、Hong Phuc、Valorie 和 Mario，他們與 Google 計畫管理員共同將這份文件放在一起。
除非另有註明，否則本頁面中的內容是採用創用 CC 姓名標示 4.0 授權。詳情請參閱《Google Developers 網站政策》。Java 是 Oracle 和/或其關聯企業的註冊商標。
上次更新時間：2025-07-25 (世界標準時間)。
[null,null,["上次更新時間：2025-07-25 (世界標準時間)。"],[[["\u003cp\u003eThis documentation aims to standardize expectations for Google Summer of Code (GSoC) participants across all organizations, covering contributors, mentors, and organization administrators.\u003c/p\u003e\n"],["\u003cp\u003eContributors are expected to submit quality work, communicate regularly with their mentor and community, and be proactive in addressing challenges or changes in their work capacity.\u003c/p\u003e\n"],["\u003cp\u003eMentors are responsible for guiding contributors, providing regular feedback, facilitating their integration into the community, and escalating any issues to the organization administrator.\u003c/p\u003e\n"],["\u003cp\u003eOrganization administrators oversee the GSoC program for their organization, ensuring compliance with Google's guidelines, managing communication, and supporting both mentors and contributors.\u003c/p\u003e\n"],["\u003cp\u003eWhile this document provides a baseline, individual organizations may have additional roles and responsibilities, so contributors should consult their organization administrator for any specific requirements.\u003c/p\u003e\n"]]],["GSoC Contributors are responsible for submitting quality work, communicating progress and blockers, and informing about reduced capacity. Mentors must guide contributors, track their progress, provide feedback, and communicate regularly. Organization Administrators oversee all participants, ensure expectations are met, handle communication with Google, and set policies for participation, selection, and dismissal. They also manage mentors, contributor integration, and ensure deadlines are followed.\n"],null,["# Roles and Responsibilities\n\nThere are always a lot of questions about what the expectations are for each\nrole in the GSoC program. Organizations have developed their own, and\nthis has resulted in wide variation. This documentation aims to standardize\nexpectations across all participating organizations.\n\nIndividual organizations may have additional roles and responsibilities. Talk to\nyour Organization Administrator for more information.\n\nGSoC Contributor Responsibilities\n---------------------------------\n\n### ...to your Mentor\n\n- Submit quality work (code)\n- Regularly communicate work completed, what you intend to do next, and blockers\n - Ask for help when something is preventing you from achieving a goal\n - Give indication that you are alive and working daily\n- Re-evaluate work scope when significantly ahead of expectations\n- Communicate with your mentor AND the broader community\n- Inform when work capacity will be reduced, as early as possible (e.g., family, health, other work)\n- Listen and respond to feedback\n\n### ...to the Org Admin\n\n- Let them know when there are\n - Interaction issues with any mentor or community member\n - Significant disagreements involving your work or changes to your work plan\n\nMentor Responsibilities\n-----------------------\n\n### ...to your Org Admin\n\n- Communicate availability and interaction expectations\n- Inform when mentoring capacity will be reduced, as early as possible (e.g., family, health, vacation)\n- Inform when there is an issue with a GSoC contributor\n - Lacking communication, activity, visibility (MIA), or progress\n - Participant Agreement violations (e.g., plagiarism, harassment, fraud)\n - Bad fit or stepping down\n- Formally evaluate GSoC contributor participation\n - Communicate with admin and GSoC contributor before failing\n\n### ...to your GSoC contributors\n\n- Help and/or teach the GSoC contributor how to\n - be a part of your community\n - communicate more effectively and in the open\n - work with your org's preferred communication channel (IRC, Slack, etc)\n - use your org's version control system\n - ask good questions and get answers to their questions\n - provide convincing technical argument and constructive discussion\n - give attribution correctly and how to select an open source license\n - be independently motivated and productive\n - solve difficult technical problems\n- Keep track of their progress, keep GSoC contributor informed as to their status\n- Communicate on a regular basis:\n - At least twice a week or better\n- Give constructive feedback, be patient, and be respectful\n- Establish realistic work objectives and timeline expectations\n- Re-evaluate scope with GSoC contributor when significantly ahead of or behind expectations\n- Work with devs and community to facilitate acceptance of GSoC contributor work\n\nOrg Admin Responsibilities\n--------------------------\n\n### ...to Google\n\n- Frame org participation, org selection criteria, and org-specific operating procedures\n- Submit the org application and be the org's representative\n- Serve as communication liaison with Google\n - Respond to any inquiries from Google within 36 hours\n - Report Participant Agreement violations (e.g., harassment, plagiarism, fraud)\n - Report GSoC contributor withdrawal\n- Ensure all deadlines are met (e.g., slot requests, mentor evaluations, org payment account creation)\n- Select and invite trusted, capable, and qualified mentors\n- Provide and maintain an adequate list of project ideas\n- Oversee activity of all mentors and GSoC contributors ensuring responsibilities are being met\n- Respond to Google's survey post GSoC (with questions around GSoC contributor retention, etc.)\n\n### ...to your Mentors\n\n- Frame org participation, mentor requirements, failure process, and procedure\n- Communicate mentor expectations before the program starts\n- Communicate GSoC contributor selection, continued participation, and dismissal policy\n - Provide selection criteria for slot allocations\n - Describe how Participant Agreement violations and failure will be handled\n- Continuously evaluate mentor interaction with GSoC contributors\n - Recognize conflicts of interest, interpersonal issues, and replace as necessary\n- Let mentors know when more project ideas are needed\n- Maintain regular communication with mentors before and during the program\n- Ensure adequate and appropriate mentoring coverage, particularly near holidays\n\n### ...to your GSoC contributors\n\n- Let GSoC contributors know how, when, and why to contact the org admin\n- Ensure GSoC contributors are introduced and become appropriately integrated\n- Communicate org-specific requirements (e.g., time, coding, communication, licensing)\n- Communicate org-specific expectations (e.g., behavior, best practices, visibility)\n- Communicate deadlines, acceptance criteria, and failure/dismissal policy\n- Monitor communications and ensure inappropriate behavior is addressed\n- Ensure GSoC contributors at risk of failure or dismissal are notified in advance\n\nSpecial thanks to Sean, Terri, Hong Phuc, Valorie, and Mario, veteran GSoC and\nGCI Organization Administrators, for working with Google's Program\nAdministrators to put this document together."]]
