Re: getting started with contributions

['Adam Johnson' via Django developers (Contributions to Django itself)]

Welcome!

There are many different ways to contribute to Django - the forum,
blogging, translating, documenting, writing code, and more. Our
Contributing Guide can help you get started with many of these:
https://docs.djangoproject.com/en/stable/internals/contributing/

If you’re looking to work with the code base (for documentation or code),
check out the “Advice for New Contributors” section:
https://docs.djangoproject.com/en/stable/internals/contributing/new-contributors/
. Then see if you can work through the “Writing Your First Patch” tutorial:
https://docs.djangoproject.com/en/stable/intro/contributing/ .

If you get stuck or have questions, post back here or in the “Mentorship”
section on the forum:
https://forum.djangoproject.com/c/internals/mentorship/10

Hope that helps,

Adam

On Mon, 3 Jan 2022 at 22:51, Ayush  wrote:

> Did you look at the issue tracker? Choose the "Easy Pickings" Tickets
>  from there
> that will help you get familiar with django but before writing any actual
> code or documentation you must know what's going on in here if you don't
> then freecodecamp django
>  video will help
> you understand how django is used, moreover, go and look at the video "Django
> in depth"  by James Bennett
> which was made to help you understand how Django internally works. Once you
> complete all this then you would have enough knowledge to pick any "Ticket"
> and start contributing.
>
> Thanks!
>
> On Mon, 3 Jan 2022 at 19:38, Vanshita Rathore <
> vanshita.rathor...@gmail.com> wrote:
>
>> Respected sir/madam
>>
>> My name is vanshita rathore  currently a undergraduate at NIT bhopal
>> India . I'm new to open source contributions but I'm well aware of python
>> and have great interest in web development.  I would love to contribute to
>> this organization could you guide me on how to get started.
>>
>> Hoping to hear from you soon .
>>
>> Regards
>>
>> Vanshita rathore
>>
>> --
>> 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 django-developers+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/django-developers/64680db3-c210-4e4c-a468-eedc30d76a42n%40googlegroups.com
>> 
>> .
>>
> --
> 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 django-developers+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/django-developers/CADZYoLcGJxNf9q17g0uvAmap1FrAgfLiKv-XWdG1%3Dv-6FeBOvg%40mail.gmail.com
> 
> .
>

-- 
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 django-developers+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/CAMyDDM0%2BaXhHSTP3eYoxRBH%3Dh2ga69q3j%2Bv-5H5XMT%3DSYejQWA%40mail.gmail.com.

Django security releases issued: 4.0.1, 3.2.11, and 2.2.26

[Carlton Gibson]

Details are available on the Django project weblog:

https://www.djangoproject.com/weblog/2022/jan/04/security-releases/

-- 
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 django-developers+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/CAJwKpyRqsW8dtfD0KNuHoztipNZ-D9tbyqo1npsOv60fjeE%3DBw%40mail.gmail.com.

Implementation of view permission in Django admin

[Gagan Deep]

Hello everyone! 


I have been looking into the implementation of ModelAdmin and how it 
processes the view only permission. While rendering a ModelAdmin for a user 
with view-only permission, the ModelAdmin disregard widget defined for the 
field and uses the AdminReadonlyField 

 to 
display the information. 


This implementation makes it difficult to customize the rendering of the 
object information. An example use case is rendering map for GeoJSON 
coordinates in django-lealet 
. 


I have already read discussions in 
https://code.djangoproject.com/ticket/17295 ticket and also checked related 
discussions on this mailing list. I couldn't find a discussion on how 
ModelAdmins that use custom forms (or widgets for fields) could be 
supported for view-only permission. 


Will adding support for customizing the rendering of ModelAdmin for users 
with view-only permissions be useful for Django? 


Best, 

Gagan Deep 

-- 
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 django-developers+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/b85b8330-3180-46e4-9b46-1b3cd8124295n%40googlegroups.com.

Re: Django security releases issued: 4.0.1, 3.2.11, and 2.2.26

[SJ Postmus]

Hi!

I have a question regarding the fix for CVE-2021-45116. In this fix the 
resolving logic for 'paths' passed to dictsort is simplified to no longer 
support indexing into lists, nor to support method-calls on objects.

The explanation here is that:
> Due to leveraging the Django Template Language's variable resolution logic, 
> the dictsort template filter was potentially vulnerable to information 
> disclosure or unintended method calls, if passed a suitably crafted key.

Unfortunately (at least for us), this breaks the case where dictsort was used 
with a static argument that looked up a callable. A quick code search showed 
that the pattern dictsort.*get​ 
(https://github.com/search?q=%22dictsort.*get%22&type=Code) is less used than I 
would expect it to be used, but used nonetheless.

On the other hand, searching publicly viewable code for cases where dictsort 
gets a dynamic value yields very little results: 
https://grep.app/search?q=dictsort%3A%5B%5E%22%270-9%5D®exp=true&case=true, 
only one which I can recognize as a Django template: 
https://github.com/crodas/Haanga/blob/develop/tests/assert_templates/regroup.tpl#L3
 .

Since the previous behaviour of allowing callables was in place already in 
2005, (I could find 
https://github.com/django/django/commit/ed114e15106192b22ebb78ef5bf5bce72b419d13#diff-e05e2e8efbf1fa5eea1ffee16cc8b740cba7b1bff746b2e55cebf968a0983f2cR192,
 where the filter is introduced), I would argue that even though it may not 
have been explicitly documented that this syntax allows callables, I don't 
think it's far fetched to consider it to always have supported.

However, before creating a ticket, I was wondering what the sentiment of 
django-developers is here. My own sentiments are summarized by what's also 
mentioned in the announcement blogpost.

>  As a reminder, all untrusted user input should be validated before use.

As an example, even with the change, {% for user in users|dictsort:"password" 
%} would still be supported, which is still be counted as potential information 
disclosure.

Kind regards,
Sjoerd Job Postmus


From: django-developers@googlegroups.com  
on behalf of Carlton Gibson 
Sent: 04 January 2022 11:03
To: django-annou...@googlegroups.com ; Django 
developers (Contributions to Django itself) 
; django-us...@googlegroups.com 

Subject: Django security releases issued: 4.0.1, 3.2.11, and 2.2.26

Details are available on the Django project weblog:

https://www.djangoproject.com/weblog/2022/jan/04/security-releases/


--
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 
django-developers+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/CAJwKpyRqsW8dtfD0KNuHoztipNZ-D9tbyqo1npsOv60fjeE%3DBw%40mail.gmail.com.

-- 
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 django-developers+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/AM9PR09MB5089BF8C4FCCDDAA46216E76AB4A9%40AM9PR09MB5089.eurprd09.prod.outlook.com.

Re: getting started with contributions

[Vijayant Shrivastav]

Hi Adam,

I also want to start my contribution journey, can I follow up the same
details.

Thanks and Regards
Vijayant

On Tue, Jan 4, 2022 at 3:31 PM 'Adam Johnson' via Django developers
(Contributions to Django itself)  wrote:

> Welcome!
>
> There are many different ways to contribute to Django - the forum,
> blogging, translating, documenting, writing code, and more. Our
> Contributing Guide can help you get started with many of these:
> https://docs.djangoproject.com/en/stable/internals/contributing/
>
> If you’re looking to work with the code base (for documentation or code),
> check out the “Advice for New Contributors” section:
> https://docs.djangoproject.com/en/stable/internals/contributing/new-contributors/
> . Then see if you can work through the “Writing Your First Patch” tutorial:
> https://docs.djangoproject.com/en/stable/intro/contributing/ .
>
> If you get stuck or have questions, post back here or in the “Mentorship”
> section on the forum:
> https://forum.djangoproject.com/c/internals/mentorship/10
>
> Hope that helps,
>
> Adam
>
> On Mon, 3 Jan 2022 at 22:51, Ayush  wrote:
>
>> Did you look at the issue tracker? Choose the "Easy Pickings" Tickets
>>  from there
>> that will help you get familiar with django but before writing any actual
>> code or documentation you must know what's going on in here if you don't
>> then freecodecamp django
>>  video will help
>> you understand how django is used, moreover, go and look at the video "Django
>> in depth"  by James Bennett
>> which was made to help you understand how Django internally works. Once you
>> complete all this then you would have enough knowledge to pick any "Ticket"
>> and start contributing.
>>
>> Thanks!
>>
>> On Mon, 3 Jan 2022 at 19:38, Vanshita Rathore <
>> vanshita.rathor...@gmail.com> wrote:
>>
>>> Respected sir/madam
>>>
>>> My name is vanshita rathore  currently a undergraduate at NIT bhopal
>>> India . I'm new to open source contributions but I'm well aware of python
>>> and have great interest in web development.  I would love to contribute to
>>> this organization could you guide me on how to get started.
>>>
>>> Hoping to hear from you soon .
>>>
>>> Regards
>>>
>>> Vanshita rathore
>>>
>>> --
>>> 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 django-developers+unsubscr...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/django-developers/64680db3-c210-4e4c-a468-eedc30d76a42n%40googlegroups.com
>>> 
>>> .
>>>
>> --
>> 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 django-developers+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/django-developers/CADZYoLcGJxNf9q17g0uvAmap1FrAgfLiKv-XWdG1%3Dv-6FeBOvg%40mail.gmail.com
>> 
>> .
>>
> --
> 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 django-developers+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/django-developers/CAMyDDM0%2BaXhHSTP3eYoxRBH%3Dh2ga69q3j%2Bv-5H5XMT%3DSYejQWA%40mail.gmail.com
> 
> .
>

-- 
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 django-developers+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/CAJ5Uwx%2BXt9R%2B3jDM1NvNveS%2BOTsWcc-tA7Dw8gMKs4n4OkOjAw%40mail.gmail.com.

Re: getting started with contributions

[Vanshita Rathore]

Thank you for your time , I will get started as soon as possible .

On Tue, 4 Jan 2022, 04:24 Ayush,  wrote:

> Did you look at the issue tracker? Choose the "Easy Pickings" Tickets
>  from there
> that will help you get familiar with django but before writing any actual
> code or documentation you must know what's going on in here if you don't
> then freecodecamp django
>  video will help
> you understand how django is used, moreover, go and look at the video "Django
> in depth"  by James Bennett
> which was made to help you understand how Django internally works. Once you
> complete all this then you would have enough knowledge to pick any "Ticket"
> and start contributing.
>
> Thanks!
>
> On Mon, 3 Jan 2022 at 19:38, Vanshita Rathore <
> vanshita.rathor...@gmail.com> wrote:
>
>> Respected sir/madam
>>
>> My name is vanshita rathore  currently a undergraduate at NIT bhopal
>> India . I'm new to open source contributions but I'm well aware of python
>> and have great interest in web development.  I would love to contribute to
>> this organization could you guide me on how to get started.
>>
>> Hoping to hear from you soon .
>>
>> Regards
>>
>> Vanshita rathore
>>
>> --
>> 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 django-developers+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/django-developers/64680db3-c210-4e4c-a468-eedc30d76a42n%40googlegroups.com
>> 
>> .
>>
> --
> 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 django-developers+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/django-developers/CADZYoLcGJxNf9q17g0uvAmap1FrAgfLiKv-XWdG1%3Dv-6FeBOvg%40mail.gmail.com
> 
> .
>

-- 
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 django-developers+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/CAKeqoBrmykYRvdCeZ4_zvUk9ProcSfi%2Ba1R4wtKN3ob4jpz%2BOg%40mail.gmail.com.

Re: Django security releases issued: 4.0.1, 3.2.11, and 2.2.26

[Florian Apolloner]

Hi,

On Tuesday, January 4, 2022 at 2:09:18 PM UTC+1 Sjoerd Job Postmus wrote:

> Unfortunately (at least for us), this breaks the case where dictsort was 
> used with a static argument that looked up a callable. A quick code search 
> showed that the pattern dictsort.*get​ (
> https://github.com/search?q=%22dictsort.*get%22&type=Code) is less used 
> than I would expect it to be used, but used nonetheless. 
>

I expected as much; literally every security fix nowadays will break some 
code. Sorry about that. You can change it to a property or write your own 
filter I guess.

On the other hand, searching publicly viewable code for cases where 
> dictsort gets a dynamic value yields very little results: 
> https://grep.app/search?q=dictsort%3A%5B%5E%22%270-9%5D®exp=true&case=true,
>  
> only one which I can recognize as a Django template: 
> https://github.com/crodas/Haanga/blob/develop/tests/assert_templates/regroup.tpl#L3
>  .
>

Yes, that said there is no easy way for a template filter to determine 
whether it is a variable or a literal (I'd say it is simply impossible). 
Our first approach would have been to limit only those values provided via 
variables… I do not think that is possible in a nice way though and 
probably to much for a security patch.

Since the previous behaviour of allowing callables was in place already in 
> 2005, (I could find 
> https://github.com/django/django/commit/ed114e15106192b22ebb78ef5bf5bce72b419d13#diff-e05e2e8efbf1fa5eea1ffee16cc8b740cba7b1bff746b2e55cebf968a0983f2cR192,
>  
> where the filter is introduced), I would argue that even though it may not 
> have been explicitly documented that this syntax allows callables, I don't 
> think it's far fetched to consider it to always have supported.
>

I would argue that the Django team always said that the documentation is 
the public API. Everything else works by luck. I even went as far as 
supporting lookups on objects (ie a list of objects as opposed to a list of 
dicts) because I assumed that people would use that often (and the docs 
clearly say this filter is for dicts).

However, before creating a ticket, I was wondering what the sentiment of 
> django-developers is here. My own sentiments are summarized by what's also 
> mentioned in the announcement blogpost.
>

>From a security PoV I think this is not going to fly. The main issue here 
is that dictsort should perform a rather limited subset of normal template 
variable resolution -- if we were going to support callables again we'd 
have to also support `alter_data` etc (which is forbidden in templates) and 
then we are basically back to what the previous code did. We opted for the 
most limited subset possible while allowing a relatively wide range of code 
to keep working, I don't think adding more features to that filter is 
feasible.
 

> >  As a reminder, all untrusted user input should be validated before use.
>
> As an example, even with the change, {% for user in 
> users|dictsort:"password" %} would still be supported, which is still be 
> counted as potential information disclosure.
>

There is a massive difference though. Being able to sort by every index 
inside the password means that you need to control far less password hashes 
than in your example to get a useful result. To be honest I do not think it 
is very realistic to use that attack on the password; but it might be 
usable for shorter api  tokens or so that you can also view in plaintext.

 I hope that helps.

Cheers,
Florian

-- 
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 django-developers+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/6ee7a4a3-f0b3-451e-a250-71b2a31b4722n%40googlegroups.com.

Re: Django security releases issued: 4.0.1, 3.2.11, and 2.2.26

['Adam Johnson' via Django developers (Contributions to Django itself)]

>
> I would argue that the Django team always said that the documentation is
> the public API. Everything else works by luck.


I agree with Florian, this is Django’s policy. To go against it and restore
the undocumented behaviour requires a strong case, perahps that many users
were affected or there’s no reasonable workaround. IMO there's a  good
workaround here: perform the sorting step in your view, rather than
template.

On Tue, 4 Jan 2022 at 15:45, Florian Apolloner 
wrote:

> Hi,
>
> On Tuesday, January 4, 2022 at 2:09:18 PM UTC+1 Sjoerd Job Postmus wrote:
>
>> Unfortunately (at least for us), this breaks the case where dictsort was
>> used with a static argument that looked up a callable. A quick code search
>> showed that the pattern dictsort.*get​ (
>> https://github.com/search?q=%22dictsort.*get%22&type=Code) is less used
>> than I would expect it to be used, but used nonetheless.
>>
>
> I expected as much; literally every security fix nowadays will break some
> code. Sorry about that. You can change it to a property or write your own
> filter I guess.
>
> On the other hand, searching publicly viewable code for cases where
>> dictsort gets a dynamic value yields very little results:
>> https://grep.app/search?q=dictsort%3A%5B%5E%22%270-9%5D®exp=true&case=true,
>> only one which I can recognize as a Django template:
>> https://github.com/crodas/Haanga/blob/develop/tests/assert_templates/regroup.tpl#L3
>>  .
>>
>
> Yes, that said there is no easy way for a template filter to determine
> whether it is a variable or a literal (I'd say it is simply impossible).
> Our first approach would have been to limit only those values provided via
> variables… I do not think that is possible in a nice way though and
> probably to much for a security patch.
>
> Since the previous behaviour of allowing callables was in place already in
>> 2005, (I could find
>> https://github.com/django/django/commit/ed114e15106192b22ebb78ef5bf5bce72b419d13#diff-e05e2e8efbf1fa5eea1ffee16cc8b740cba7b1bff746b2e55cebf968a0983f2cR192,
>> where the filter is introduced), I would argue that even though it may not
>> have been explicitly documented that this syntax allows callables, I don't
>> think it's far fetched to consider it to always have supported.
>>
>
> I would argue that the Django team always said that the documentation is
> the public API. Everything else works by luck. I even went as far as
> supporting lookups on objects (ie a list of objects as opposed to a list of
> dicts) because I assumed that people would use that often (and the docs
> clearly say this filter is for dicts).
>
> However, before creating a ticket, I was wondering what the sentiment of
>> django-developers is here. My own sentiments are summarized by what's also
>> mentioned in the announcement blogpost.
>>
>
> From a security PoV I think this is not going to fly. The main issue here
> is that dictsort should perform a rather limited subset of normal template
> variable resolution -- if we were going to support callables again we'd
> have to also support `alter_data` etc (which is forbidden in templates) and
> then we are basically back to what the previous code did. We opted for the
> most limited subset possible while allowing a relatively wide range of code
> to keep working, I don't think adding more features to that filter is
> feasible.
>
>
>> >  As a reminder, all untrusted user input should be validated before use.
>>
>> As an example, even with the change, {% for user in
>> users|dictsort:"password" %} would still be supported, which is still be
>> counted as potential information disclosure.
>>
>
> There is a massive difference though. Being able to sort by every index
> inside the password means that you need to control far less password hashes
> than in your example to get a useful result. To be honest I do not think it
> is very realistic to use that attack on the password; but it might be
> usable for shorter api  tokens or so that you can also view in plaintext.
>
>  I hope that helps.
>
> Cheers,
> Florian
>
> --
> 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 django-developers+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/django-developers/6ee7a4a3-f0b3-451e-a250-71b2a31b4722n%40googlegroups.com
> 
> .
>

-- 
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 django-developers+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-develo

Re: getting started with contributions

[Vanshita Rathore]

Hello Adam
This helps a lot I will get started as soon as possible  and ask for your
guidance along the way
Regards
Vanshita

On Tue, 4 Jan 2022, 15:31 'Adam Johnson' via Django developers
(Contributions to Django itself), 
wrote:

> Welcome!
>
> There are many different ways to contribute to Django - the forum,
> blogging, translating, documenting, writing code, and more. Our
> Contributing Guide can help you get started with many of these:
> https://docs.djangoproject.com/en/stable/internals/contributing/
>
> If you’re looking to work with the code base (for documentation or code),
> check out the “Advice for New Contributors” section:
> https://docs.djangoproject.com/en/stable/internals/contributing/new-contributors/
> . Then see if you can work through the “Writing Your First Patch” tutorial:
> https://docs.djangoproject.com/en/stable/intro/contributing/ .
>
> If you get stuck or have questions, post back here or in the “Mentorship”
> section on the forum:
> https://forum.djangoproject.com/c/internals/mentorship/10
>
> Hope that helps,
>
> Adam
>
> On Mon, 3 Jan 2022 at 22:51, Ayush  wrote:
>
>> Did you look at the issue tracker? Choose the "Easy Pickings" Tickets
>>  from there
>> that will help you get familiar with django but before writing any actual
>> code or documentation you must know what's going on in here if you don't
>> then freecodecamp django
>>  video will help
>> you understand how django is used, moreover, go and look at the video "Django
>> in depth"  by James Bennett
>> which was made to help you understand how Django internally works. Once you
>> complete all this then you would have enough knowledge to pick any "Ticket"
>> and start contributing.
>>
>> Thanks!
>>
>> On Mon, 3 Jan 2022 at 19:38, Vanshita Rathore <
>> vanshita.rathor...@gmail.com> wrote:
>>
>>> Respected sir/madam
>>>
>>> My name is vanshita rathore  currently a undergraduate at NIT bhopal
>>> India . I'm new to open source contributions but I'm well aware of python
>>> and have great interest in web development.  I would love to contribute to
>>> this organization could you guide me on how to get started.
>>>
>>> Hoping to hear from you soon .
>>>
>>> Regards
>>>
>>> Vanshita rathore
>>>
>>> --
>>> 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 django-developers+unsubscr...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/django-developers/64680db3-c210-4e4c-a468-eedc30d76a42n%40googlegroups.com
>>> 
>>> .
>>>
>> --
>> 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 django-developers+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/django-developers/CADZYoLcGJxNf9q17g0uvAmap1FrAgfLiKv-XWdG1%3Dv-6FeBOvg%40mail.gmail.com
>> 
>> .
>>
> --
> 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 django-developers+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/django-developers/CAMyDDM0%2BaXhHSTP3eYoxRBH%3Dh2ga69q3j%2Bv-5H5XMT%3DSYejQWA%40mail.gmail.com
> 
> .
>

-- 
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 django-developers+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/CAKeqoBr%2BD3zqiPsMWRGc7ZtUL6iE%2B3%3DQvjuJL6w86cwAoPRu6Q%40mail.gmail.com.