Adrian's one of the BDFLs (I'm the other), so if he says "no" that stands.
Usually, we operate the way most open source projects do: "rough
consensus and working code". You've got the second ("working code") so
you need to work on the first, I think. Usually a strong consensus is
enough to override a committer's veto, even a BDFL veto, so if you can
show that this is a strong enough need, Adrian might drop his veto.
[For more on how we make decisions, see
https://docs.djangoproject.com/en/1.5/internals/contributing/bugs-and-features/#how-we-make-decisions]
Of course, I'm putting words in Adrian mouth, so this is all just a
guess. It's possible that he's really against this, in which case
you're basically SOL.
Adrian, if you're still following this thread... maybe want to weigh
in on how we might convince you to drop that veto?
Jacob
On Tue, Mar 26, 2013 at 8:17 AM, meric <meric...@gmail.com> wrote:
> Is the 'vote' a majority or a consensus must be achieved?
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to django-developers+unsubscr...@googlegroups.com.
> To post to this group, send email to django-developers@googlegroups.com.
> Visit this group at http://groups.google.com/group/django-developers?hl=en.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at http://groups.google.com/group/django-developers?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
