Hi Tom! Thank you so much for taking time out and answering my queries. However, I'm still unclear about how to move ahead with all the guidelines suggested by you. I would be extremely grateful if you could guide me a bit more with respect to all your suggestions.
On Friday, 22 September 2017 14:51:46 UTC+5:30, Tom Forbes wrote: > > Hey Heba, > For a few popular packages on Github it could be as simple as making a > merge request and changing their tox.ini or travis.yml file. Once the > django 2.0 alpha is published on PyPi (sometime very soon) you could make a > merge request to run the projects tests with the alpha, and inspect the CI > output for any failures, then fix those. Alternatively, clone each project > and run the tests locally (but this can get tiring for lots of individual > different projects). > > For example, django-reversion has a tox.ini here: > https://github.com/etianen/django-reversion/blob/master/tox.ini - If you > make a merge request to that project adding Django 2.0 alpha to the `deps` > section (line ~16) and the `test` section (line 4) it will run the tests on > Travis CI and report any failures. You could post on the django-users > mailing list for some ideas of what packages to make changes for (and for > more help with specific things like tox/travis), but I would recommend: > django-reversion, django-mptt, silk and django-debug-toolbar: > > https://github.com/etianen/django-reversion/blob/master/tox.ini > https://github.com/django-mptt/django-mptt/blob/master/tox.ini > https://github.com/jazzband/silk/blob/master/.travis.yml > https://github.com/jazzband/django-debug-toolbar/blob/master/tox.ini > > An initial merge request testing on Django 2.0 alpha is the first step, > then fixing any issues that are discovered is the next (and harder) one. > > On Thu, Sep 21, 2017 at 6:55 PM, Heba Khan <[email protected] > <javascript:>> wrote: > >> Can you suggest a way of how to test Django projects ad third party >> packages please? >> >> On Thursday, 21 September 2017 21:00:36 UTC+5:30, Adam Johnson wrote: >>> >>> There's a whole documentation page on this: >>> https://docs.djangoproject.com/en/dev/internals/contributing/ >>> >>> There aren't many easy pickings tickets, plus most of the effort right >>> now is being put into features for the 2.0 feature freeze. I'd suggest the >>> biggest contribution you can make right now is testing Django projects or >>> third party packages with 2.0 and finding bugs or helping them become >>> compatible. >>> >>> On 21 September 2017 at 15:17, Heba Khan <[email protected]> wrote: >>> >>>> Hello! >>>> >>>> I'm an undergrad student of B.Tech. in Computer Science and we've been >>>> assigned a project to contribute in an open source project. My team >>>> members >>>> and I decided to pick Django since it is one of the most well known and >>>> widely used open source projects. We need help in deciding what >>>> contributions to make to the repository and how to go about it. Please >>>> keep >>>> the following in mind: >>>> >>>> 1. We're students with Intermediate coding skills and intermediate >>>> knowledge of Python along with a good hold on HTML, CSS, JavaScript and >>>> JQuery. >>>> 2. We need some easy contribution ideas which can be executed in a >>>> short span of time. >>>> 3. We will be needing guidance and future help from the community as >>>> well. >>>> >>>> Thank you 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/236511d3-54de-441a-a423-57cc01143be0%40googlegroups.com >>>> >>>> <https://groups.google.com/d/msgid/django-developers/236511d3-54de-441a-a423-57cc01143be0%40googlegroups.com?utm_medium=email&utm_source=footer> >>>> . >>>> For more options, visit https://groups.google.com/d/optout. >>>> >>> >>> >>> >>> -- >>> Adam >>> >> -- >> 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] <javascript:>. >> To post to this group, send email to [email protected] >> <javascript:>. >> 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/c3feb2a3-4cec-4ac2-9bc1-e61e90165913%40googlegroups.com >> >> <https://groups.google.com/d/msgid/django-developers/c3feb2a3-4cec-4ac2-9bc1-e61e90165913%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> >> For more options, visit https://groups.google.com/d/optout. >> > > On Friday, 22 September 2017 14:51:46 UTC+5:30, Tom Forbes wrote: > > Hey Heba, > For a few popular packages on Github it could be as simple as making a > merge request and changing their tox.ini or travis.yml file. Once the > django 2.0 alpha is published on PyPi (sometime very soon) you could make a > merge request to run the projects tests with the alpha, and inspect the CI > output for any failures, then fix those. Alternatively, clone each project > and run the tests locally (but this can get tiring for lots of individual > different projects). > > For example, django-reversion has a tox.ini here: > https://github.com/etianen/django-reversion/blob/master/tox.ini - If you > make a merge request to that project adding Django 2.0 alpha to the `deps` > section (line ~16) and the `test` section (line 4) it will run the tests on > Travis CI and report any failures. You could post on the django-users > mailing list for some ideas of what packages to make changes for (and for > more help with specific things like tox/travis), but I would recommend: > django-reversion, django-mptt, silk and django-debug-toolbar: > > https://github.com/etianen/django-reversion/blob/master/tox.ini > https://github.com/django-mptt/django-mptt/blob/master/tox.ini > https://github.com/jazzband/silk/blob/master/.travis.yml > https://github.com/jazzband/django-debug-toolbar/blob/master/tox.ini > > An initial merge request testing on Django 2.0 alpha is the first step, > then fixing any issues that are discovered is the next (and harder) one. > > On Thu, Sep 21, 2017 at 6:55 PM, Heba Khan <[email protected] > <javascript:>> wrote: > >> Can you suggest a way of how to test Django projects ad third party >> packages please? >> >> On Thursday, 21 September 2017 21:00:36 UTC+5:30, Adam Johnson wrote: >>> >>> There's a whole documentation page on this: >>> https://docs.djangoproject.com/en/dev/internals/contributing/ >>> >>> There aren't many easy pickings tickets, plus most of the effort right >>> now is being put into features for the 2.0 feature freeze. I'd suggest the >>> biggest contribution you can make right now is testing Django projects or >>> third party packages with 2.0 and finding bugs or helping them become >>> compatible. >>> >>> On 21 September 2017 at 15:17, Heba Khan <[email protected]> wrote: >>> >>>> Hello! >>>> >>>> I'm an undergrad student of B.Tech. in Computer Science and we've been >>>> assigned a project to contribute in an open source project. My team >>>> members >>>> and I decided to pick Django since it is one of the most well known and >>>> widely used open source projects. We need help in deciding what >>>> contributions to make to the repository and how to go about it. Please >>>> keep >>>> the following in mind: >>>> >>>> 1. We're students with Intermediate coding skills and intermediate >>>> knowledge of Python along with a good hold on HTML, CSS, JavaScript and >>>> JQuery. >>>> 2. We need some easy contribution ideas which can be executed in a >>>> short span of time. >>>> 3. We will be needing guidance and future help from the community as >>>> well. >>>> >>>> Thank you 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/236511d3-54de-441a-a423-57cc01143be0%40googlegroups.com >>>> >>>> <https://groups.google.com/d/msgid/django-developers/236511d3-54de-441a-a423-57cc01143be0%40googlegroups.com?utm_medium=email&utm_source=footer> >>>> . >>>> For more options, visit https://groups.google.com/d/optout. >>>> >>> >>> >>> >>> -- >>> Adam >>> >> -- >> 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] <javascript:>. >> To post to this group, send email to [email protected] >> <javascript:>. >> 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/c3feb2a3-4cec-4ac2-9bc1-e61e90165913%40googlegroups.com >> >> <https://groups.google.com/d/msgid/django-developers/c3feb2a3-4cec-4ac2-9bc1-e61e90165913%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> >> For more options, visit https://groups.google.com/d/optout. >> > > -- 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/b3da4793-9e77-47ad-9f41-44d627149d8e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
