The FAQ is at: https://github.com/django/django/tree/master/docs/faq Depending on how much content there is, it might make more sense to add the questions on the CSRF reference page instead: https://github.com/django/django/blob/master/docs/ref/csrf.txt Please read the contributing documentation about claiming tickets: https://docs.djangoproject.com/en/dev/internals/contributing/writing-code/submitting-patches/#claiming-tickets
p.s. I think it's better to use the django-core-mentorship mailing list to get help about the basics of contributing. Thanks! On Tuesday, February 2, 2016 at 4:14:08 PM UTC-5, Vivek unni wrote: > > I wanted to start with a documentation ticket while I get myself > acquainted with the code base. I have seen the thread referenced and I can > make relevant questions and answers from it . These questions and answers > will go to the FAQ page regarding why Django's CSRF protection isn't > vulernable. Where do I start writing the documentation and how can I claim > the ticket ? Some examples will help. > Thanks in advance. > -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" 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 https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/fa19bbdf-47b8-4fdd-904e-917b2ac465ee%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
