Governance on Django Commons

Django Commons Governance

Mon, 01 Jan 0001 00:00:00 +0000

For Django Commons to function effectively, we need trusted volunteers to step up and take responsibility for certain aspects that require ongoing attention and a certain level of trust from our community. These volunteers are organized into teams, each with a specific focus.

Relation to the Django Software Foundation

Django Commons is an independent initiative from the Django Software Foundation (DSF). We are here for the third-party packages that complement Django. We are here as a community for and by Django users.

Project Maintenance Governance

Mon, 01 Jan 0001 00:00:00 +0000

Overview

Django Commons creates the conditions for maintainership to transfer smoothly so that when maintainers step back, the community has a clear path to step in.

This document will outline the various states a project can be in, how a project transitions between them, and where support is provided.

Maintenance States

Healthy

A project has a responsive maintainer, clear ownership, regular releases, and an active repository.

Dormant

A project has an unresponsive maintainer, a lack of forward compatibility, and potentially community complaints.

Response Timeframes

Mon, 01 Jan 0001 00:00:00 +0000

The table below defines the timeframes in which we expect a maintainer to respond to a reported security vulnerability. For the purposes of ‘responsiveness’ an acknowledgement is sufficient. There isn’t an expectation that a fix will be implemented within the time frames below.

CVE Level	Timeframe
Critical	1 week
High	2 weeks
Medium	4 weeks
Low	8 weeks
None	16 weeks