Let me rephrase -- Where do I voice support that I too would like this 
feature? Here, on the DEP pull request, on the original ticket?

I get that there is a difference between core devs voting and non core devs 
voicing support, and that +1 from a core dev is a vote whereas +1 from a 
non-core user is an expression of support.  That wasn't the question.  The 
question is about how to most effectively join the chorus so core devs know 
that people do care about this when they cast their votes.

T

On Tuesday, April 29, 2014 10:24:12 PM UTC-4, Florian Apolloner wrote:
>
> Technically I'd think only core devs would vote. So neither here or there 
> would make a diff imo.
>
> P.S.: That said I am not sure we have a formal policy on how we act on 
> DEPs yet (or maybe I should just read DEP 001 more carefully ;))
>
> Cheers,
> Florian
>
> On Wednesday, April 30, 2014 4:02:26 AM UTC+2, ted wrote:
>>
>> Now that there is a DEP, where do we voice our support (cast +1 votes)? 
>>  Here, on the DEP pull request, on the original ticket?
>>
>> T
>>
>> On Wednesday, April 16, 2014 10:14:25 PM UTC-4, Loic Bistuer wrote:
>>>
>>> On Thursday, April 17, 2014 5:47:10 AM UTC+7, Josh Smeaton wrote:
>>>>
>>>> And for the last month or so a patch has existed and feedback has been 
>>>> requested. Performance was one of the concerns mentioned, so download 
>>>> Curtis' patch, and test that it works for your use case. He has asked for 
>>>> feedback a number of times. Unless you try it out, I fear that you won't 
>>>> be 
>>>> seeing multi-line tags.
>>>>
>>>
>>> My thought exactly.
>>>
>>> I intend to review the patch, benchmark it, and work on improvements if 
>>> need be, but that's no replacement for extensive community testing. This 
>>> patch doesn't stand a chance unless the latter has happened since we can't 
>>> risk breaking all the templates out there; the diff may look small, but 
>>> it's a significant change to the parsing algorithm.
>>>
>>> Decision making in Django goes by "rough consensus and working code". 
>>> The DEP process that Curtis started is the right way to work constructively 
>>> on "rough consensus", but people who really want this feature need to play 
>>> their part in coming up with "working code" and the code needs to be well 
>>> tested to be considered as working.
>>>
>>> If you want this feature, please try the patch against your own projects 
>>> and report your findings. The DEP is also awaiting community feedback.
>>>
>>> -- 
>>> Loic
>>>
>>>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/ef2dc161-3e90-45a9-a1b1-0ab7c61bf41c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to