summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorAdrian Holovaty <adrian@holovaty.com>2014-01-13 10:32:09 -0600
committerAdrian Holovaty <adrian@holovaty.com>2014-01-13 10:32:09 -0600
commit660b7e70001209a53f0e51c66e2e19071f796d9f (patch)
treebf537a447b46720603b4384eb0fe1ed147c554e1 /docs
parent4f25d97404dc2a6faa5c9f467c246cb42b65b44c (diff)
Removed BDFL stuff from docs/internals/contributing/bugs-and-features.txt
Diffstat (limited to 'docs')
-rw-r--r--docs/internals/contributing/bugs-and-features.txt7
1 files changed, 2 insertions, 5 deletions
diff --git a/docs/internals/contributing/bugs-and-features.txt b/docs/internals/contributing/bugs-and-features.txt
index fe55b0897d..636bd27e57 100644
--- a/docs/internals/contributing/bugs-and-features.txt
+++ b/docs/internals/contributing/bugs-and-features.txt
@@ -160,16 +160,13 @@ by the core team if:
* There is no "-1" vote from any member of the core team.
-* The :ref:`BDFLs<django-bdfls>` haven't stepped in and executed their
- positive or negative veto.
-
When calling for a vote, the caller should specify a deadline by which
votes must be received. One week is generally suggested as the minimum
amount of time.
Since this process allows any core committer to veto a proposal, any "-1"
-votes (or BDFL vetos) should be accompanied by an explanation that explains
-what it would take to convert that "-1" into at least a "+0".
+votes should be accompanied by an explanation that explains what it would
+take to convert that "-1" into at least a "+0".
Whenever possible, these formal votes should be announced and held in
public on the |django-developers| mailing list. However, overly sensitive