On Wednesday, April 16, 2014 10:36:00 AM UTC+7, Adrian Holovaty wrote: > > Hey, may I suggest writing this up using our new DEP process? I don't mean > to make people jump through hoops, but it would be useful for people like > me who haven't been following the issue and don't want to wade through > dozens of mailing-list messages, comment threads, patches, etc. >
I agree, DEP seems to be the best tool for this kind of proposals and design decisions. Even more so now that Curtis volunteered to write it :P Note that me asking for a DEP doesn't mean I necessarily support the idea > of multiline tags -- the point of a DEP is to collect and organize thoughts > in one place, not to be a "we will definitely do this" feature plan. > Understood, a DEP can be accepted or rejected. On Wednesday, April 16, 2014 10:48:22 AM UTC+7, Curtis Maloney wrote: > I'm happy to coalesce this into a DEP... is there a format template I can > follow? > I believe https://github.com/django/deps/blob/master/deps/0001.rst serves as a template? Thanks for offering to work on it. -- 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 [email protected]. To post to this group, send email to [email protected]. 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/07a50d8f-4b4b-4917-aa31-662c0376943d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
