> I'm sorry. Please accept my apologies and let me rephrase that without > spam-fighting-induced frustration: > > "Other than reducing spam, Django as a project will benefit from this > change be freeing core dev time and energy currently used to delete > spam manually and tweak a feeble anti-spam plugin. Core dev time > and energy are often cited as bottlenecks in the Django development > process." > > Other advantages have been put forward; I won't rehash them.
+1 It would also enable us to unify access controls too I think? I think we could just pull permissions from GitHub? --- Donald Stufft PGP: 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA -- 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/5A2D0897-B9FE-4043-A6DE-BB5D26507360%40stufft.io. For more options, visit https://groups.google.com/d/optout.
