GSoC Admin Expectations (Changelog)

Tue Feb 6 00:20:52 PST 2024, a

In GSoC, Organization Administrators have the responsiblity of making sure the organization's involvement in the program goes smoothly, that appropriate communication is happening, and some administrivia. Here's what to expect from your org admins.

This year, the primary admin is Anthony Sorace; the backup mentor is Paul Lalonde. You can reach the admins at gsoc-admin@p9f.org.

Like all participants, Organization Admins will abide by the Plan 9 Code of Conduct and all applicable GSoC policies.

Admins will complete all the required forms, registration materials, organization profiles, and so on, in a timely manner.

Admins will follow at least the weekly project reports from contributors and mentors to ensure work is progressing. In the event that these aren't coming in as expected, admins will contact the mentors first, and then the contributors if necessary.

Admins will actively contact each mentor on a weekly basis to ensure that all's going well. In the event of problems, admins will take corrective action, most likely communicating with the backup mentor(s) and then the contributors. The schedule for this may be adjusted based on the work schedule decided by the mentor and contributor, given the more flexible hours introduced in GSoC 2021 and expanded in 2024.

Admins will check in with contributors at the beginning of the community bonding period, the beginning of the code period, once before midterm, and once a week or so before the suggested "pencils down" date, to ensure their communications with their mentors are going well. Admins will not try to inject themselves into the contributor-mentor relationship, but should make sure the contributor is having a productive and enjoyable time.

Admins will check completion of contributor and mentor midterm and final reviews and will provide gentle reminders of unfinished forms as the deadlines near.

In the event both the primary and backup mentors become unavailable, org admins will be prepared to either find another suitable mentor from the community or, as a last resort, serve as an intermediary to the community generally.

In all cases above, actions to be performed by "admins" will be expected of the primary admin, with the backup following along well enough to pick up tasks in case the primary gets hit by a bus or goes awol.

Tue Feb 6 00:13:45 PST 2024, a

This year, the primary admin is Anthony Sorace; the backup mentor is Paul Lalonde. You can reach the admins at gsoc-admin@p9f.org.

Like all participants, Organization Admins will abide by the Plan 9 Code of Conduct and all applicable GSoC policies.

Admins will complete all the required forms, registration materials, organization profiles, and so on, in a timely manner.

Admins will follow at least the weekly project reports from contributors and mentors to ensure work is progressing. In the event that these aren't coming in as expected, admins will contact the mentors first, and then the contributors if necessary.

Admins will actively contact each mentor on a weekly basis to ensure that all's going well. In the event of problems, admins will take corrective action, most likely communicating with the backup mentor(s) and then the contributors. The schedule for this may be adjusted based on the work schedule decided by the mentor and contributor, given the more flexible hours introduced in GSoC 2021 and expanded in 2024.

Admins will check in with contributors at the beginning of the community bonding period, the beginning of the code period, once before midterm, and once a week or so before the suggested "pencils down" date, to ensure their communications with their mentors are going well. Admins will not try to inject themselves into the contributor-mentor relationship, but should make sure the contributor is having a productive and enjoyable time.

Admins will check completion of contributor and mentor midterm and final reviews and will provide gentle reminders of unfinished forms as the deadlines near.

In the event both the primary and backup mentors become unavailable, org admins will be prepared to either find another suitable mentor from the community or, as a last resort, serve as an intermediary to the community generally.

In all cases above, actions to be performed by "admins" will be expected of the primary admin, with the backup following along well enough to pick up tasks in case the primary gets hit by a bus or goes awol.

Fri Mar 26 22:12:17 PDT 2021, a

This year, the primary admin is Anthony Sorace; the backup mentor is Jeff Sickel.

Organization admins will complete all the required forms, registration materials, organization profiles, and so on, in a timely manner.

Admins will follow at least the weekly project reports from students and mentors to ensure work is progressing. In the event that these aren't coming in as expected, admins will contact the mentors first, and then the students if necessary.

Admins will actively contact each mentor on a weekly basis to ensure that all's going well. In the event of problems, admins will take corrective action, most likely communicating with the backup mentor(s) and then the students. The schedule for this may be adjusted based on the work schedule decided by the mentor and student, given the revised hours for GSoC 2021.

Admins will check in with students at the beginning of the community bonding period, the beginning of the code period, once before midterm, and once a week or so before the suggested "pencils down" date, to ensure their communications with their mentors are going well. Admins will not try to inject themselves into the student-mentor relationship, but should make sure the student is having a productive and enjoyable time.

Admins will check completion of student and mentor midterm and final reviews and will provide gentle reminders of unfinished forms as the deadlines near.

In the event both the primary and backup mentors become unavailable, org admins will be prepared to either find another suitable mentor from the community or, as a last resort, serve as an intermediary to the community generally.

In all cases above, actions to be performed by "admins" will be expected of the primary admin, with the backup following along well enough to pick up tasks in case the primary gets hit by a bus or goes awol.