Skip to content

Add Google Summer of Code Working Group charter. #63

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
tim-schilling wants to merge 2 commits into
base: main
Choose a base branch
from
Draft

Add Google Summer of Code Working Group charter. #63

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
4cd5df8
Add Google Summer of Code Working Group charter.
tim-schilling Dec 12, 2025
e87c599
Add line about coordinating with the Django community
tim-schilling Dec 16, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
62 changes: 62 additions & 0 deletions active/google-summer-of-code.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,62 @@
# Google Summer of Code Working Group

## Scope of responsibilities

This working group coordinates and organizes Django's participating with [Google Summer of Code (GSoC)](https://summerofcode.withgoogle.com/).

The goal of the group is to support and facilitate Django's participation in Google Summer of Code as an organization.

Delegated responsibilities:
- Communicate and coordinate with GSoC officials on behalf of the Django community.
- Identify projects and mentors for Django projects across the community.
- Communicate and coordinate with prospective mentees and mentors.
- Communicate and coordinate with Django community regarding GSoC.

## Initial membership

- Chair: Bhuvnesh Sharma
- Co-Chair: Apoorv Garg
- Board Liaison:
- Steering Council Liaison:
Comment on lines +19 to +20
Copy link
Contributor

@nanorepublica nanorepublica Jan 1, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@tim-schilling a question popped into my header while reading your year in review.

Are some of the working groups/teams meant to report to just the Steering Council or is the board always included?

I ask this here as it would seem from an outside perspective GSoC is more technical in nature over requiring much from the board?

Copy link
Member Author

@tim-schilling tim-schilling Jan 3, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

From my understanding / perspective it is a and/or situation depending on the use case. GSoC and Djangonaut Space (if you think of it as a contributor WG) both are relevant to the technical aspect of Django. However, more of them are about community building which is the Board's purview.

So I think GSoC would report to the board, but would need a SC liaison for helping with project selection. Though that's not a strong preference.

Copy link
Contributor

@nanorepublica nanorepublica Jan 3, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That makes sense. More broadly is there a case to be made for some WG's to only have a SC liaison and no board liaison?

Copy link
Member Author

@tim-schilling tim-schilling Jan 3, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes. I'd imagine if we had a dedicated team for handling the new-features repo (no plans atm), that'd be entirely in the SC's domain. Or a dedicated team that managed a particular component.

Concretely, the mergers, releases, triage and review teams, likely all will be SC domain rather than board domain.

- Other members:

## Future membership

Anyone who has interest in Django, coordinating community members and/or encouraging contributions to Django is welcome to join. We welcome all experience levels.

### Expressing Interest

Send one of the WG members a message on Discord or the Forum. A form will be made available in a public space with the following questions:

* Usernames on the Forum/Discord.
* Why they want to join.
* What experience and skills they bring to the WG.

### Membership Conditions

- New members may self-nominate.
- Members will serve for a one year term. At the end of this term, they need to opt into staying involved to keep being a member of the group.
- New members will get approved by existing members of the WG.
- If any member wishes to leave the group before the end of their term, they can do so by notifying the group.
- Members can propose a vote on removing a member from the working group. This needs 50%+1 agreement.

### Roles in within WG

- Chair/Co-chair: The chair and co-chair are responsible for coordinating the community for the GSoC program.
- Board Liaison: Must be an active Board member; may be the same as Chair/Co-Chair.
- Steering Council Liaison: Must be an active Steering Council member; may be the same as Chair/Co-Chair.

## Budget

No budget is required at this time. This will be reviewed at least annually.
Any changes to the budget may be requested from the board.

## Comms

Discussions will take place on the [Django Discord](https://chat.djangoproject.com) in the private #gsoc-organization channel.

## Reporting

An annual report will be produced highlighting the GSoC project(s) of the year. There may be one per project that is written by the mentees.

The program's documentation and notes will be maintained in Django's Google Drive folder, [Google Summer of Code (GSoC)](https://drive.google.com/drive/folders/1g-j683JwHlIFMTR_E4_NM1_ykRfvq_nA?usp=drive_link).