角色和职责
使用集合让一切井井有条
根据您的偏好保存内容并对其进行分类。
对于 GSoC 计划中每个角色的预期是什么，总是存在很多问题。组织已经发展了自己的组织，这带来了广泛的变化。本文档旨在实现所有参与组织的预期标准化。
各个组织可能还具有其他角色和责任。如需了解详情，请与您的组织管理员联系。
GSoC 贡献者的职责
...给你的导师
- 提交高质量作品（代码）
- 定期传达已完成的工作、您打算做什么以及阻碍因素
- 在阻碍您实现目标时寻求帮助
- 表明你还活着并且每天都工作
- 当远远超出预期时，重新评估工作范围
- 与导师和更广泛的社区沟通
- 尽早在工作能力将降低时发出通知（例如，家庭、健康、其他工作）
- 听取和回复反馈
...组织管理员
- 如果有，请告知客户
- 与任何导师或社区成员的互动问题
- 涉及你的工作或工作计划的重大分歧
导师的职责
...组织管理员
- 传达对可用性和互动的预期
- 当指导能力将降低时（例如家庭、健康、休假）提供相关信息
- 在 GSoC 贡献者出现问题时通知
- 缺乏沟通、活动、可见性 (MIA) 或进度
- 违反参与者协议的行为（例如抄袭、骚扰、欺诈）
- 不合适或降级
- 正式评估 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 的项目管理员合作编写本文档。
如未另行说明，那么本页面中的内容已根据知识共享署名 4.0 许可获得了许可。有关详情，请参阅 Google 开发者网站政策。Java 是 Oracle 和/或其关联公司的注册商标。
最后更新时间 (UTC)：2025-07-25。
[null,null,["最后更新时间 (UTC)：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."]]
