Yep, and encourage new people to the list to actively contribute!

One thing springs to mind, an agile / crystal process 'game', which encourages all parties to contribute ideas within a time frame (usually half an hour to a hour), without prejudice or discouragement. This gets lots of good and bad ideas out into the open, which can then be whittled down. Without the openness, contributors are put off, no ideas flow...

Just my 2 pennies (yep, i'm in the UK :-))


On 31 Aug 2010, at 18:24, stefanw wrote:

Hello,

I guess the most interesting point in this discussion is:

After a while that I spent time to develop new tags and filters
especially for
new projects, I began to think a way to implement a template engine
that
would let me no more write sort of "plugins" like tags and filters, a
thing that
really bother me.

The template language is great, it's design decisions are sensible,
but writing filters and tags is too complex and time-consuming.
Unnecessarily so, as wrappers around creating template tags have shown
(e.g. django-templatetag-sugar by Alex Gaynor). If people don't see a
documented way of easily bringing features to their templates, they
may switch the template engine or, well, start patching the template
engine.
Bottom line: we need to improve the template tag creation.

Cheers
Stefan

--
You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com . To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com . For more options, visit this group at http://groups.google.com/group/django-developers?hl=en .


--
You received this message because you are subscribed to the Google Groups "Django 
developers" group.
To post to this group, send email to django-develop...@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Reply via email to