Re: Introduction

[Adam Johnson]

Try checking out an older commit and running the tests there. It may be
that this doesn't work in all situations on the current latest commit on
the master branch.

On Tue, 14 May 2019 at 14:25, Ruchit Vithani 
wrote:

> Hey Adam! I'm running tests same way as in that documentation. In tests
> directory, I used `python -m pip install -r requirements/py3.txt` and
> then `./runtests.py`. I tried this again, but output is same.
>
> --
> 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 post to this group, send email to django-developers@googlegroups.com.
> 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/25fc9f2b-71e9-4cd8-88e3-90695c0daee8%40googlegroups.com
> 
> .
> 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 django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
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/CAMyDDM39iOQE_fYuHphxCPzsJ1bHwmVdB9Hq_PpOU_gvONcAZQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Introduction

[Ruchit Vithani]

Hey Adam! I'm running tests same way as in that documentation. In tests 
directory, I used `python -m pip install -r requirements/py3.txt` and then `
./runtests.py`. I tried this again, but output is same.  

-- 
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 post to this group, send email to django-developers@googlegroups.com.
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/25fc9f2b-71e9-4cd8-88e3-90695c0daee8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Introduction

[Adam Johnson]

Hi Ruchit

You should not be trying to 'pip install' the tests module. There is no
tests module in Django's tree, there is a test directory that contains many
individual test modules: https://github.com/django/django/tree/master/tests .
You can see there's an i18n module in there.

>From your traceback, I think you may not be running the tests correctly
with runtests.py. It looks like you are invoking unittest directly. Are you
running as per
https://docs.djangoproject.com/en/dev/intro/contributing/#running-django-s-test-suite-for-the-first-time
 ?

Thanks,

Adam

On Tue, 14 May 2019 at 13:43, Ruchit Vithani 
wrote:

> I'm taking about this  requirements, which
> are described in the documentation.
>
> On Tuesday, May 14, 2019 at 6:09:34 PM UTC+5:30, Ruchit Vithani wrote:
>>
>> I've already installed requirements for tests. Before this, there was a
>> module `tests` which wasn't present, and I installed it using `pip3 install
>> tests`. This is the second module, which is not found. Am I missing
>> something? This is a link to traceback: https://dpaste.de/XYTB
>>
> --
> 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 post to this group, send email to django-developers@googlegroups.com.
> 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/597f3763-145c-49ce-b9d1-881a16d84ab0%40googlegroups.com
> 
> .
> 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 django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
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/CAMyDDM3C1XQdLEre402NZn0AgPecef6GW-P4qXdZbt6aTJCdkQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Introduction

[Ruchit Vithani]

I've already installed requirements for tests. Before this, there was a 
module `tests` which wasn't present, and I installed it using `pip3 install 
tests`. This is the second module, which is not found. Am I missing 
something? This is a link to traceback: https://dpaste.de/XYTB 

-- 
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 post to this group, send email to django-developers@googlegroups.com.
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/45af2cb9-2e7c-491b-b63f-178b211b457f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Introduction

[Ruchit Vithani]

I'm taking about this  requirements, which are 
described in the documentation. 

On Tuesday, May 14, 2019 at 6:09:34 PM UTC+5:30, Ruchit Vithani wrote:
>
> I've already installed requirements for tests. Before this, there was a 
> module `tests` which wasn't present, and I installed it using `pip3 install 
> tests`. This is the second module, which is not found. Am I missing 
> something? This is a link to traceback: https://dpaste.de/XYTB 
>

-- 
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 post to this group, send email to django-developers@googlegroups.com.
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/597f3763-145c-49ce-b9d1-881a16d84ab0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Introduction

[Ruchit Vithani]

I'm working now on ticket #30463 
, and I've figured out what 
the problem is. Here, when self._meta_ordering is called, it returns 
instances of OrderBy type and, when .join is called on that list, it throws 
an error saying: expected str instance but OrderBy found. One easy solution 
is already mentioned in the ticket, which suggests using "', '".join*([*str
*(*f*)* for f in self._meta_ordering*]**).  *But this causes a problem 
since we don't want quotes around OrderBy, and we do want quotes around 
anything inside F(), (i.e we want F('anything')). Moreover, we can not use ", 
".join instead of "', '".join  since we also want quotes around items if 
query expression is not used. 

So, the simple solution which came to my mind after thinking for some time 
was, to call one more string method on "', '".join*([*str*(*f*)* for f 
in self._meta_ordering*]**), * to replace `OrderBy with OrderBy and )' with 
). I'm not sure this is a cleaner solution to this problem, but any other 
solution did not come to my mind. Also, there will be a problem in 
replacement of F( ) with F(' '). I think we'll need to use regular 
expressions in this replacement. 

Any thoughts or comments on my solution? Or is there any better solution 
anyone can think of about this ticket?

-- 
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 post to this group, send email to django-developers@googlegroups.com.
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/a4762531-dd0c-4ece-9d8e-b07a35e2b7e0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Introduction

[Ruchit Vithani]

Thanks, Tobias, for a wonderful explanation. I sure will try to add 
documentation about 'Reproduced at:' in triaging workflow. But currently, 
I've claimed one easy picking ticket, so once I finish work on that, I'll 
come on to this documentation :)

-- 
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 post to this group, send email to django-developers@googlegroups.com.
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/a3c3d5f3-8b52-466b-aa5d-583127586f19%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Introduction

[Carlton Gibson]

Thank you Tobias. Good explanation.

An additional point I picked up from Tim is that if you have a Reproduced
at... but the bug is fixed on master then you have a starting point to git
bisect where the issue was fixed.

On Sat, 11 May 2019 at 15:28, Tobias Kunze  wrote:

> Hi Ruchit,
>
> On 19-05-10 23:19:16, Ruchit Vithani wrote:
> >I have following queries regarding tickets on Trac. In many of the
> tickets,
> >some people comment `Regression in` and `Reproduced at`, and both of them
> >link to some commit on GitHub. I could not understand what these links
> >specify.
>
> The "regression in" comments point to commits that have either
> introduced or re-introduced the issue in the ticket. Regressions are
> explained in the contributing documentation, including a guide on how to
> figure out which commit caused the regression:
> <
> https://docs.djangoproject.com/en/2.2/internals/contributing/triaging-tickets/#bisecting-a-regression
> >
>
> This is helpful because it gives you a start when trying to fix the
> issue. You can look at the causing commit, and figure out if this
> behaviour was intentional, if it was discussed in the ticket referenced
> in the commit, if it was accidental, etc. It also helps you to develop a
> fix that doesn't break anything else unintentionally. So even if you
> don't have the time or experience to find a fix, finding and noting
> which commit caused a regression can be very helpful.
>
> The 'reproduced at' comments are indeed not mentioned in the triage
> documentation – maybe you could add them?  Sometimes people add comments
> like that when they accept a ticket, for better documentation of why
> they decided to accept a ticket. There is a note about this workflow
> here:
> https://docs.djangoproject.com/en/2.2/internals/contributing/new-contributors/
>
> They can also be useful with old tickets: With more than a thousand
> open tickets, and most of them older than the last one or two releases,
> it's not always obvious that an issue still persists. (For instance, I
> recently came across a ticket that called for the introduction of
> template-based form rendering, which has been part of Django for some
> time now.) Adding a comment that the issue still persists currently (and
> linking to the tested commit for reference) can be helpful to show that
> an 8 year old bug is still relevant.
>
> I hope this helps,
> Tobias
>
> --
> 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 post to this group, send email to django-developers@googlegroups.com.
> 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/20190511132755.gmpmcetv33npqlji%40cordelia.localdomain
> .
> 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 django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
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/CAJwKpyRmus1j7xwz2NEjbzUYN1ncft0vu0uCqh6x8_xsebnCxA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Introduction

[Tobias Kunze]

Hi Ruchit,

On 19-05-10 23:19:16, Ruchit Vithani wrote:
>I have following queries regarding tickets on Trac. In many of the tickets, 
>some people comment `Regression in` and `Reproduced at`, and both of them 
>link to some commit on GitHub. I could not understand what these links 
>specify.

The "regression in" comments point to commits that have either
introduced or re-introduced the issue in the ticket. Regressions are
explained in the contributing documentation, including a guide on how to
figure out which commit caused the regression:
<https://docs.djangoproject.com/en/2.2/internals/contributing/triaging-tickets/#bisecting-a-regression>

This is helpful because it gives you a start when trying to fix the
issue. You can look at the causing commit, and figure out if this
behaviour was intentional, if it was discussed in the ticket referenced
in the commit, if it was accidental, etc. It also helps you to develop a
fix that doesn't break anything else unintentionally. So even if you
don't have the time or experience to find a fix, finding and noting
which commit caused a regression can be very helpful.

The 'reproduced at' comments are indeed not mentioned in the triage
documentation – maybe you could add them?  Sometimes people add comments
like that when they accept a ticket, for better documentation of why
they decided to accept a ticket. There is a note about this workflow
here: 
https://docs.djangoproject.com/en/2.2/internals/contributing/new-contributors/

They can also be useful with old tickets: With more than a thousand
open tickets, and most of them older than the last one or two releases,
it's not always obvious that an issue still persists. (For instance, I
recently came across a ticket that called for the introduction of
template-based form rendering, which has been part of Django for some
time now.) Adding a comment that the issue still persists currently (and
linking to the tested commit for reference) can be helpful to show that
an 8 year old bug is still relevant.

I hope this helps,
Tobias

-- 
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 post to this group, send email to django-developers@googlegroups.com.
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/20190511132755.gmpmcetv33npqlji%40cordelia.localdomain.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: PGP signature

Re: Introduction

[Ruchit Vithani]

I have following queries regarding tickets on Trac. In many of the tickets, 
some people comment `Regression in` and `Reproduced at`, and both of them 
link to some commit on GitHub. I could not understand what these links 
specify. I read this 

 documentation 
on Triage workflow, there is not anything mentioned about this yet on this 
page. It would be great if someone could tell me what those links specify, 
and if there is any link to documentation, which could be helpful, please 
mention. Thanks!

-- 
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 post to this group, send email to django-developers@googlegroups.com.
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/28af2017-ad64-4348-911b-31280f1afe91%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Introduction

[Ruchit Vithani]

Thanks! Carlton. Will surely check out those links. 

On Wednesday, May 8, 2019 at 5:46:33 PM UTC+5:30, Carlton Gibson wrote:
>
> Hi Ruchit, 
>
> Welcome aboard! 🙂
>
> There's a whole section on finding a ticket in the talk I gave at 
> DjangoCon Europe recently. Check it out: 
>
> https://www.youtube.com/watch?v=F4StlMFb5Ms
>
> In the Trac you can filter by component which helps: 
>
>
> https://code.djangoproject.com/query?status=assigned&status=new&component=contrib.admin&col=id&col=summary&col=status&col=owner&col=type&col=component&col=version&desc=1&order=id
>
> (That has the Admin selected, but you can change that.) 
>
> If you get into specific issues getting started email 
> django-core-mentorship 
>  and 
> we'll see if we can get you going. 
>
> Good luck. Have fun! 
>
> Carlton
>
> On Wednesday, 8 May 2019 13:59:36 UTC+2, Ruchit Vithani wrote:
>>
>> Hello developers! My name is Ruchit Vithani and I am a student at 
>> DA-IICT, Gandhinagar in India. I'm familiar with open source and I've also 
>> contributed to some projects.  I'd love to be a part of this awesome 
>> community and would like to contribute. I've read the contributing guide. 
>> Can someone guide me on what to do next? Also, please inform me if there 
>> are any other community platforms to chat and where should I pick my first 
>> ticket to work on. Thanks!
>>
>

-- 
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 post to this group, send email to django-developers@googlegroups.com.
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/7330c435-33ae-4c46-b3eb-359f2607c187%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Introduction

[Carlton Gibson]

Hi Ruchit, 

Welcome aboard! 🙂

There's a whole section on finding a ticket in the talk I gave at DjangoCon 
Europe recently. Check it out: 

https://www.youtube.com/watch?v=F4StlMFb5Ms

In the Trac you can filter by component which helps: 

https://code.djangoproject.com/query?status=assigned&status=new&component=contrib.admin&col=id&col=summary&col=status&col=owner&col=type&col=component&col=version&desc=1&order=id

(That has the Admin selected, but you can change that.) 

If you get into specific issues getting started email django-core-mentorship 
 and we'll 
see if we can get you going. 

Good luck. Have fun! 

Carlton

On Wednesday, 8 May 2019 13:59:36 UTC+2, Ruchit Vithani wrote:
>
> Hello developers! My name is Ruchit Vithani and I am a student at DA-IICT, 
> Gandhinagar in India. I'm familiar with open source and I've also 
> contributed to some projects.  I'd love to be a part of this awesome 
> community and would like to contribute. I've read the contributing guide. 
> Can someone guide me on what to do next? Also, please inform me if there 
> are any other community platforms to chat and where should I pick my first 
> ticket to work on. Thanks!
>

-- 
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 post to this group, send email to django-developers@googlegroups.com.
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/43b0b23f-793c-4a06-ab94-55aece5fe888%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Introduction

[Ruchit Vithani]

Hello developers! My name is Ruchit Vithani and I am a student at DA-IICT, 
Gandhinagar in India. I'm familiar with open source and I've also 
contributed to some projects.  I'd love to be a part of this awesome 
community and would like to contribute. I've read the contributing guide. 
Can someone guide me on what to do next? Also, please inform me if there 
are any other community platforms to chat and where should I pick my first 
ticket to work on. Thanks!

-- 
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 post to this group, send email to django-developers@googlegroups.com.
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/db352292-9886-4bc5-ace0-d688804de5da%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Introduction as a new member to django contributions mailing list

[Dylan Reinhold]

On the project home page https://www.djangoproject.com/  it has the link on
how to contribute.

https://docs.djangoproject.com/en/dev/internals/contributing

If you have a specific question feel free to ask, but this is a good
starting point.

Dylan

On Sat, Jan 26, 2019 at 10:51 AM Yemdjih Kaze Nasser 
wrote:

> Hello
> My names are Yemdjih Kaze Nasser and I am new to the mailing list and I
> would like to contribute the django organisations.
> Please can how can I get started
>
> --
> 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 post to this group, send email to django-developers@googlegroups.com.
> 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/50a23743-d915-429d-be51-271cc54d13eb%40googlegroups.com
> 
> .
> 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 django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
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/CAHtg44CJfsoKggmTphuj7jZGRRm09797%2BzUQ%3DiwbCwHKGWbYEw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Introduction as a new member to django contributions mailing list

[Yemdjih Kaze Nasser]

Hello
My names are Yemdjih Kaze Nasser and I am new to the mailing list and I 
would like to contribute the django organisations.
Please can how can I get started

-- 
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 post to this group, send email to django-developers@googlegroups.com.
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/50a23743-d915-429d-be51-271cc54d13eb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Introduction GSoC

[akki]

Also, if Django does participate in GSoC this year, they'll have an ideas page 
for it eventually similar to something like this - 
https://code.djangoproject.com/wiki/SummerOfCode2018.

The best thing that you can do today to improve your chances is start 
contributing!

-- 
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 post to this group, send email to django-developers@googlegroups.com.
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/6bccbc0f-347c-4a93-9dba-11fe2829da16%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Introduction GSoC

[oussama boumaad]

am sorry Noumbissi
you're a very welcome fellow .

On Jan 21 2019, at 9:42 am, Noumbissi Valere  wrote:
> Thanks Carlton.
>
> On Mon, Jan 21, 2019 at 9:38 AM Carlton Gibson  (mailto:carlton.gib...@gmail.com)> wrote:
> > Hi Folks.
> >
> > First off: can we please keep it civil. Let's offer positive responses 
> > where possible. Thanks
> >
> > There's no harm in people asking for help: there is a contributing guide, 
> > but if folks aren't finding it, perhaps we need a bigger sign-post.
> >
> > So...
> >
> > The place to begin is here: 
> > https://docs.djangoproject.com/en/dev/internals/contributing/
> >
> > See the Development Dashboard: https://dashboard.djangoproject.com
> >
> > Looking at Unreviewed Tickets on the issue tracker and helping to Triage 
> > them is super helpful.
> > That's a good place to get familiar.
> >
> > That doesn't make a GSoC project, so looking through Accepted tickets (take 
> > your time! 🙂)
> > would be a good place to look for ideas.
> >
> > I don't think we have a ready list of GSoC-scale project ideas we can point 
> > you to I'm afraid. (Anyone?)
> >
> > I hope that at least gets you started.
> >
> > Welcome aboard!
> >
> > Kind Regards,
> >
> > Carlton
> >
> >
> > --
> > 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 
> > (mailto:django-developers+unsubscr...@googlegroups.com).
> > To post to this group, send email to django-developers@googlegroups.com 
> > (mailto:django-developers@googlegroups.com).
> > 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/18569029-82a3-494c-ab06-6c0a958eb2b4%40googlegroups.com
> >  
> > (https://groups.google.com/d/msgid/django-developers/18569029-82a3-494c-ab06-6c0a958eb2b4%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 django-developers+unsubscr...@googlegroups.com 
> (mailto:django-developers+unsubscr...@googlegroups.com).
> To post to this group, send email to django-developers@googlegroups.com 
> (mailto:django-developers@googlegroups.com).
> 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/CAOwnGe7ziELM%2BTPs%2BoDhBifkKSQBeSyJG7%2BcdjEBqsinhszhMw%40mail.gmail.com
>  
> (https://groups.google.com/d/msgid/django-developers/CAOwnGe7ziELM%2BTPs%2BoDhBifkKSQBeSyJG7%2BcdjEBqsinhszhMw%40mail.gmail.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 django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
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/1548060306.local-b5c6d6cb-c621-v1.5.5-b7939d38%40getmailspring.com.
For more options, visit https://groups.google.com/d/optout.

Re: Introduction GSoC

[Noumbissi Valere]

Thanks Carlton.

On Mon, Jan 21, 2019 at 9:38 AM Carlton Gibson 
wrote:

> Hi Folks.
>
> First off: can we please keep it civil. Let's offer positive responses
> where possible. Thanks
>
> There's no harm in people asking for help: there is a contributing guide,
> but if folks aren't finding it, perhaps we need a bigger sign-post.
>
> So...
>
> The place to begin is here:
> https://docs.djangoproject.com/en/dev/internals/contributing/
>
> See the Development Dashboard: https://dashboard.djangoproject.com
>
> Looking at Unreviewed Tickets on the issue tracker and helping to Triage
> them is super helpful.
> That's a good place to get familiar.
>
> That doesn't make a GSoC project, so looking through Accepted tickets
> (take your time! 🙂)
> would be a good place to look for ideas.
>
> I don't think we have a ready list of GSoC-scale project ideas we can
> point you to I'm afraid. (Anyone?)
>
> I hope that at least gets you started.
>
> Welcome aboard!
>
> Kind Regards,
>
> Carlton
>
> --
> 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 post to this group, send email to django-developers@googlegroups.com.
> 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/18569029-82a3-494c-ab06-6c0a958eb2b4%40googlegroups.com
> 
> .
> 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 django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
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/CAOwnGe7ziELM%2BTPs%2BoDhBifkKSQBeSyJG7%2BcdjEBqsinhszhMw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Introduction GSoC

[Carlton Gibson]

Hi Folks. 

First off: can we please keep it civil. Let's offer positive responses 
where possible. Thanks 

There's no harm in people asking for help: there is a contributing guide, 
but if folks aren't finding it, perhaps we need a bigger sign-post.  

So...

The place to begin is 
here: https://docs.djangoproject.com/en/dev/internals/contributing/

See the Development Dashboard: https://dashboard.djangoproject.com

Looking at Unreviewed Tickets on the issue tracker and helping to Triage 
them is super helpful. 
That's a good place to get familiar. 

That doesn't make a GSoC project, so looking through Accepted tickets (take 
your time! 🙂) 
would be a good place to look for ideas. 

I don't think we have a ready list of GSoC-scale project ideas we can point 
you to I'm afraid. (Anyone?)

I hope that at least gets you started. 

Welcome aboard! 

Kind Regards,

Carlton

-- 
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 post to this group, send email to django-developers@googlegroups.com.
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/18569029-82a3-494c-ab06-6c0a958eb2b4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Introduction GSoC

[oussama boumaad]

Hello Noumbissi ,

I think you're skilled in python but you're not enough skilled in "" GOOGLEing" 
.
you can start with the officiel django tutorial.

https://docs.djangoproject.com/en/2.1/intro/tutorial01/
Best regards.
On Jan 21 2019, at 1:50 am, noumbissival...@gmail.com wrote:
> Hello Everyone! Am Noumbissi Valere, a student from Cameroon. Am skilled in 
> python and have used django to build some web apps. Am new to open source and 
> will love to contribute to django, hoping to participate for GSoC this Year. 
> Please can anyone help me on how to get started?
>
>
> --
> 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 
> (mailto:django-developers+unsubscr...@googlegroups.com).
> To post to this group, send email to django-developers@googlegroups.com 
> (mailto:django-developers@googlegroups.com).
> 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/5801f106-9beb-43d9-b8d0-7d1f91fb9a63%40googlegroups.com
>  
> (https://groups.google.com/d/msgid/django-developers/5801f106-9beb-43d9-b8d0-7d1f91fb9a63%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 django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
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/1548059179.local-7bed0a6d-af9e-v1.5.5-b7939d38%40getmailspring.com.
For more options, visit https://groups.google.com/d/optout.

Introduction GSoC

[noumbissivalere]

Hello Everyone! Am Noumbissi Valere, a student from Cameroon. Am skilled in 
python and have used django to build some web apps. Am new to open source 
and will love to contribute to django, hoping to participate for GSoC this 
Year. Please can anyone help me on how to get started?

-- 
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 post to this group, send email to django-developers@googlegroups.com.
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/5801f106-9beb-43d9-b8d0-7d1f91fb9a63%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

SCoC 2018 - introduction(librarie support django)

[amr anwar]

*it's not a proposal, I'll just say the main idea to get your great 
feedback then I'll write the Proposal if it's possible *

*the problem:*
when a user submits a Django Form, the entire page will be refreshed to get 
the response from the Server or show the response message
 - in login page for example-: it gives a really bad performance on the 
site 


*The traditional solution:*
the developer will need to write Js(jquery) code to write ajax request to 
the server  then  the server sends the response to it, finally the js will 
show the response message, refresh the page or redirect to another page

*What am I going to do ?:*
I'll handle all that flow in my library so the developer by just installing 
the library will be to do that by just using Django Forms & Django Messages 

*Why not just let the developers write JS Code in this **traditional way*
* : *
- for a lot of new python developers, they know python only, they don't 
want to get confused by learning new language to write a well-performance 
project 
- Save time
- write DRY FORMS  
__
-I want the library handle ajax request not only the Django Forms but right 
now, forms are the clear idea for me, if there is any other idea in this 
topic please tell me -
__
*about me :*
-I'm 21 backend web developer, in the third year in the university. I 
started to learn python web frameworks 1 year ago, I've finished Udacity 
full-stack web nanodegree, I've taken intern in an Egyptian startup as a 
Django developer. in these days I've made my first pull request to the 
Django repository it's a great feeling to learn and get a review from you.

- I'm still  junior as a developer but I'm a hard worker who always wants 
to be better and learn more and I have a dream to be Django core developer 
and help in improving the framework

- one of my previous project with TTD 
test: https://github.com/AmrAnwar/ToDoList_Django_Project  
__

I'll be waiting for your feedback and thanks

-- 
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 post to this group, send email to django-developers@googlegroups.com.
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/3460326d-9cb5-47e1-9a9c-c6145004c153%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

GSoC | Introduction

[Raju Jha]

Hello developers,
 I am Raju Jha from Delhi, India. I am a web developer with main focus on 
backend development using Django. It has been approx 2 years developing 
django apps and that makes be quite experienced with the tech.
I have chosen django as the organization because of reason that it has 
helped me (and of course every python web developer) to simplify the way 
web developing is and i want to contribute to its further development so 
that it can be more helpful for developers as it has been for ever.
My github handle : www.github.com/rajujha373

Regards, 
Raju Jha

-- 
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 post to this group, send email to django-developers@googlegroups.com.
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/67854cba-a993-4ff0-90a3-fe6d7bf8b82a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

GSoC 2018 Introduction

[baginda . achmad13]

Hello,

I'm Baginda Achmad Fadillah. I'm here because I want to be a participant in 
*Google 
Summer of Code 2018*. The reason of why I choose Django Software Foundation 
as my organization, is because I've already heard that thing before, so 
that's what makes me quite familiar with that. I've been chose the idea 
"Test framework cleanup", because I think it is more 'friendly' for me than 
the other ideas. Honestly, I didn't have many experience in Programming 
(like Python, etc.) and Web Development, but I really want to know more 
about them. I didn't know more about Django Software Foundation either, 
but, as soon as possible, I would like to learn about that.

I hope with some of my contributions later, it would make any kind of 
improvements for the project, and especially for this organization.

Best regards,
Baginda Achmad Fadillah

<
   The Idea : 
https://code.djangoproject.com/wiki/SummerOfCode2018#Testframeworkcleanup 
   My Github Account : https://github.com/bagindakarli
>

-- 
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 post to this group, send email to django-developers@googlegroups.com.
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/6411a75d-f022-4c32-b93b-0e82bbf0dc22%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Introduction : Somesh Chaturvedi

[Somesh Chaturvedi]

Sounds good. I'll join the group right away and look at all other 
possible ways of contribution you have mentioned. Thanks, Adam.

On Thursday, December 21, 2017 at 6:13:07 PM UTC+5:30, Somesh Chaturvedi 
wrote:
>
> Hi everyone,
>
> I have been using Django in my professional as well as personal projects 
> for the past 3 years now. I'd like to start contributing for Django now. I 
> have gone through the following documentation along with all its sub-docs. 
>
> https://docs.djangoproject.com/en/dev/internals/contributing/
>
> I would really appreciate if someone helps me with a head start. Thanks.
>
> Regards,
> Somesh Chaturvedi
>
>

-- 
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 post to this group, send email to django-developers@googlegroups.com.
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/2ff20cb1-d5cd-4f7d-b6b1-d991abaa84ec%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Introduction : Somesh Chaturvedi

[Adam Johnson]

Welcome Somesh,

There's actually a mailing list dedicated to first time contributors, where
you might get a bit more attention: https://groups.google.com/forum/#!forum/
django-core-mentorship

I'd suggest having a particular goal in mind where you'd like to contribute
- what areas of Django do you want to see improved? Also have a look
through the ticket tracker for a easy-pickings ticket to get involved in
the contribution process.

Also don't forget there are many more ways to contribute to Django than
just code, for example: helping a local community event, translating Django
or the docs, improving the docs, writing blog posts, contributing to one of
the many third party packages, or answering questions on Stack Overflow :)
:)

Adam

On 21 December 2017 at 10:58, Somesh Chaturvedi 
wrote:

> Hi everyone,
>
> I have been using Django in my professional as well as personal projects
> for the past 3 years now. I'd like to start contributing for Django now. I
> have gone through the following documentation along with all its sub-docs.
>
> https://docs.djangoproject.com/en/dev/internals/contributing/
>
> I would really appreciate if someone helps me with a head start. Thanks.
>
> Regards,
> Somesh Chaturvedi
>
> --
> 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 post to this group, send email to django-developers@googlegroups.com.
> Visit this group at https://groups.google.com/group/django-developers.
> To view this discussion on the web visit https://groups.google.com/d/ms
> gid/django-developers/0aeb1738-a3b8-438f-a042-d1b150268806%
> 40googlegroups.com
> 
> .
> 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 django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
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/CAMyDDM3fNqh9hzjHo6EzHY6Viiu7sTKU9uynVJgodr%3DxE5g_jw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Introduction : Somesh Chaturvedi

[Somesh Chaturvedi]

Hi everyone,

I have been using Django in my professional as well as personal projects 
for the past 3 years now. I'd like to start contributing for Django now. I 
have gone through the following documentation along with all its sub-docs. 

https://docs.djangoproject.com/en/dev/internals/contributing/

I would really appreciate if someone helps me with a head start. Thanks.

Regards,
Somesh Chaturvedi

-- 
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 post to this group, send email to django-developers@googlegroups.com.
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/0aeb1738-a3b8-438f-a042-d1b150268806%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Introduction for GSoC 2017

[Tim Graham]

Welcome! It's a bit late to be starting on a successful proposal, 
especially if you haven't contributed to Django before, but good luck. I'm 
not sure if you were looking for anything specific in reply to your intro?

On Monday, March 13, 2017 at 9:52:34 AM UTC-4, Gunpreet Ahuja wrote:
>
> Greetings,
> I am a Masters in Engineering student at Concordia University, Canada. I 
> wish to participate in GSoC 2017. This is my first time and I want to 
> contribute in this project.
> I have worked on various projects which include three android applications 
> named a Textile app, Dawn-to-Dusk (a weather application) and Styllax (a 
> wallpaper application). As far as python/django is concerned, I have 
> contributed to the project LibreHatti during our undergraduate training. 
> The project is entirely based on django framework for python. Besides 
> this, I have also worked a data mining project named SocioDAvIS that 
> utilizes Facebook data set and Twitter streaming API data to predict 
> different trends using R language. The database systems utilized in these 
> projects being MySQL and SQLite3.
> In addition to this, I have participated in Google Student Ambassador program 
> (being listed among the top 400 selected students) and have been a core 
> team member of Google Student Club, co-convener at Linux User Group, 
> Ludhiana and a member of Android Student Club at my college during my 
> undergraduate course. I have worked on Git, Vim, Latex, Doxygen and have 
> had a hand on Windows, Linux and Mac Operating Systems. During my 
> undergraduate studies only, I won a C++/JAVA event that involved building 
> an algorithm to solve a given problem.
> As for now, I have working on a JAVA project for metrics analysis of source 
> codes. I am currently on the way to polish my python/django skills 
> further.
>
> Regards,
> Gunpreet Ahuja
> gunpreetahuja.wordpress.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 post to this group, send email to django-developers@googlegroups.com.
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/4044c631-d6a2-441c-907e-2e62d1efc232%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Introduction for GSoC 2017

[Gunpreet Ahuja]

Greetings,
I am a Masters in Engineering student at Concordia University, Canada. I 
wish to participate in GSoC 2017. This is my first time and I want to 
contribute in this project.
I have worked on various projects which include three android applications 
named a Textile app, Dawn-to-Dusk (a weather application) and Styllax (a 
wallpaper application). As far as python/django is concerned, I have 
contributed to the project LibreHatti during our undergraduate training. 
The project is entirely based on django framework for python. Besides this, 
I have also worked a data mining project named SocioDAvIS that utilizes 
Facebook data set and Twitter streaming API data to predict different 
trends using R language. The database systems utilized in these projects 
being MySQL and SQLite3.
In addition to this, I have participated in Google Student Ambassador program 
(being listed among the top 400 selected students) and have been a core 
team member of Google Student Club, co-convener at Linux User Group, 
Ludhiana and a member of Android Student Club at my college during my 
undergraduate course. I have worked on Git, Vim, Latex, Doxygen and have 
had a hand on Windows, Linux and Mac Operating Systems. During my 
undergraduate studies only, I won a C++/JAVA event that involved building 
an algorithm to solve a given problem.
As for now, I have working on a JAVA project for metrics analysis of source 
codes. I am currently on the way to polish my python/django skills further.

Regards,
Gunpreet Ahuja
gunpreetahuja.wordpress.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 post to this group, send email to django-developers@googlegroups.com.
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/a881af38-00c2-44db-aeb3-b8e7a2ad87ea%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Introduction GSoC 2017

[Tim Graham]

Hi, Have you read the wiki page? 
https://code.djangoproject.com/wiki/SummerOfCode2017 It contains getting 
started tips. If so, please be more specific with your questions.

On Monday, March 6, 2017 at 7:25:31 AM UTC-5, sahil jain wrote:
>
> Hello Everyone
> I am a sophomore major in computer science and engineering.
> I would like to contribute to django .
> I am interested in project Replace form media class for GSoC 2017
> I have been working with django for more than year. 
>
> Please suggest where to begin with,
>
> Regards
> Sahil Jain
>

-- 
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 post to this group, send email to django-developers@googlegroups.com.
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/6ecbd3f8-5cfb-4b35-87c8-0755915da392%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Introduction GSoC 2017

[sahil jain]

Hello Everyone
I am a sophomore major in computer science and engineering.
I would like to contribute to django .
I am interested in project Replace form media class for GSoC 2017
I have been working with django for more than year. 

Please suggest where to begin with,

Regards
Sahil Jain

-- 
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 post to this group, send email to django-developers@googlegroups.com.
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/d62e3695-5f63-475f-891d-cd1fdc9b7e5b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [GSOC] Introduction and task proposal

[Daniel Pyrathon]

Hi Josh,

Sorry for getting back now. I have just finished my exam session, so I will 
be trying out the djangocore-box VM.

Regards,
Daniel Pyrathon

On Thursday, March 27, 2014 5:45:36 AM UTC+1, Josh Smeaton wrote:
>
> If you haven't already got all your databases installed on your 
> development machine, I *highly* recommend checking out 
> https://github.com/jphalip/djangocore-box. It's a vagrant VM environment 
> that already has MySQL, PostgreSQL, and SQLite installed (plus most GIS 
> installations), along with various versions of python. Unfortunately it 
> doesn't have Oracle - but being able to run tests on 3/4 databases is 
> especially handy.
>
> Josh
>
> On Thursday, 27 March 2014 11:14:35 UTC+11, Russell Keith-Magee wrote:
>>
>>
>> Hi Daniel,
>>
>> Nope - other than "cross your fingers" that your proposal is accepted :-)
>>
>> But seriously…
>>
>> If you haven't already, I'd suggest reading Django's contribution docs, 
>> and getting your development environment set up. Make sure you can run 
>> Django's test suite. If you're particularly enthused, try your hand at 
>> working on a patch for an open ticket so you can get used to the toolchain 
>> and the review process. That way you'll be up to speed with Django's 
>> development process, so when the GSoC period starts, you'll be comfortable 
>> with our basic process, so you'll just have to deal with the actual GSoC 
>> work.
>>
>> Yours,
>> Russ Magee %-)
>>
>> On Wed, Mar 26, 2014 at 7:22 PM, Daniel Pyrathon wrote:
>>
>>> Hi all,
>>>
>>> It's been a while since I submitted my GSOC proposal. Although I am 
>>> currently under exams, is there anything you would recommend me to do at 
>>> this point (other than hope that my proposal is successful)?
>>>
>>> Thanks,
>>> Daniel Pyrathon
>>>
>>>
>>> On Thursday, March 20, 2014 6:05:40 AM UTC, Russell Keith-Magee wrote:
>>>

 For the benefit of those reading along at home; I gave some revised 
 notes and had a conversation with Daniel on IRC a couple of hours ago.

 Yours,
 Russ Magee %-)


 On Thu, Mar 20, 2014 at 4:10 AM, Daniel Pyrathon wrote:

> Hi!
>
> Thanks for all the comments yesterday. They really helped me make the 
> proposal stronger.
> I have changed to proposal to reflect the changes. Would anyone like 
> to have a look and, possibly, comment more?
>
> https://docs.google.com/document/d/1yp2_skqkxyrc0egdRv6ofnRGCI9nmvxDFB
> kCXgy0Jwo/edit#heading=h.wyxx4xxijubt
>
> Thanks,
> Dan
>
> On Wednesday, March 19, 2014 7:32:10 AM UTC, Aymeric Augustin wrote:
>
>> On 19 mars 2014, at 06:27, Zach Borboa  wrote: 
>>
>> > Curious, how do you get REPL shell access to the server with 
>> DEBUG=True with a vanilla Django deployment? 
>>
>> That part of the discussion was about adding the werkzeug interactive 
>> debugger to Django’s default error page. 
>>
>> -- 
>> Aymeric. 
>>
>>
>>
>>
>>  -- 
> 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 django-develop...@googlegroups.com.
> To post to this group, send email to django-d...@googlegroups.com.
>
> 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/16264cb7-3f44-434d-865a-
> 8c33baa4d921%40googlegroups.com
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

  -- 
>>> 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 django-develop...@googlegroups.com.
>>> To post to this group, send email to django-d...@googlegroups.com.
>>> 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/ad5d6016-2c6a-45b4-91c8-0e4500befc74%40googlegroups.com
>>> .
>>>
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>

-- 
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 django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at http://groups.google.com/group/django-developers.
To view this disc

Re: [GSOC] Introduction and task proposal

[Josh Smeaton]

If you haven't already got all your databases installed on your development 
machine, I *highly* recommend checking out 
https://github.com/jphalip/djangocore-box. It's a vagrant VM environment 
that already has MySQL, PostgreSQL, and SQLite installed (plus most GIS 
installations), along with various versions of python. Unfortunately it 
doesn't have Oracle - but being able to run tests on 3/4 databases is 
especially handy.

Josh

On Thursday, 27 March 2014 11:14:35 UTC+11, Russell Keith-Magee wrote:
>
>
> Hi Daniel,
>
> Nope - other than "cross your fingers" that your proposal is accepted :-)
>
> But seriously…
>
> If you haven't already, I'd suggest reading Django's contribution docs, 
> and getting your development environment set up. Make sure you can run 
> Django's test suite. If you're particularly enthused, try your hand at 
> working on a patch for an open ticket so you can get used to the toolchain 
> and the review process. That way you'll be up to speed with Django's 
> development process, so when the GSoC period starts, you'll be comfortable 
> with our basic process, so you'll just have to deal with the actual GSoC 
> work.
>
> Yours,
> Russ Magee %-)
>
> On Wed, Mar 26, 2014 at 7:22 PM, Daniel Pyrathon 
> 
> > wrote:
>
>> Hi all,
>>
>> It's been a while since I submitted my GSOC proposal. Although I am 
>> currently under exams, is there anything you would recommend me to do at 
>> this point (other than hope that my proposal is successful)?
>>
>> Thanks,
>> Daniel Pyrathon
>>
>>
>> On Thursday, March 20, 2014 6:05:40 AM UTC, Russell Keith-Magee wrote:
>>
>>>
>>> For the benefit of those reading along at home; I gave some revised 
>>> notes and had a conversation with Daniel on IRC a couple of hours ago.
>>>
>>> Yours,
>>> Russ Magee %-)
>>>
>>>
>>> On Thu, Mar 20, 2014 at 4:10 AM, Daniel Pyrathon wrote:
>>>
 Hi!

 Thanks for all the comments yesterday. They really helped me make the 
 proposal stronger.
 I have changed to proposal to reflect the changes. Would anyone like to 
 have a look and, possibly, comment more?

 https://docs.google.com/document/d/1yp2_skqkxyrc0egdRv6ofnRGCI9nmvxDFB
 kCXgy0Jwo/edit#heading=h.wyxx4xxijubt

 Thanks,
 Dan

 On Wednesday, March 19, 2014 7:32:10 AM UTC, Aymeric Augustin wrote:

> On 19 mars 2014, at 06:27, Zach Borboa  wrote: 
>
> > Curious, how do you get REPL shell access to the server with 
> DEBUG=True with a vanilla Django deployment? 
>
> That part of the discussion was about adding the werkzeug interactive 
> debugger to Django’s default error page. 
>
> -- 
> Aymeric. 
>
>
>
>
>  -- 
 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 django-develop...@googlegroups.com.
 To post to this group, send email to django-d...@googlegroups.com.

 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/16264cb7-3f44-434d-865a-
 8c33baa4d921%40googlegroups.com
 .

 For more options, visit https://groups.google.com/d/optout.

>>>
>>>  -- 
>> 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 django-develop...@googlegroups.com .
>> To post to this group, send email to 
>> django-d...@googlegroups.com
>> .
>> 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/ad5d6016-2c6a-45b4-91c8-0e4500befc74%40googlegroups.com
>> .
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
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 django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
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/70eba10d-cd77-4579-ad3c-ac4be8da6849%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [GSOC] Introduction and task proposal

[Russell Keith-Magee]

Hi Daniel,

Nope - other than "cross your fingers" that your proposal is accepted :-)

But seriously...

If you haven't already, I'd suggest reading Django's contribution docs, and
getting your development environment set up. Make sure you can run Django's
test suite. If you're particularly enthused, try your hand at working on a
patch for an open ticket so you can get used to the toolchain and the
review process. That way you'll be up to speed with Django's development
process, so when the GSoC period starts, you'll be comfortable with our
basic process, so you'll just have to deal with the actual GSoC work.

Yours,
Russ Magee %-)

On Wed, Mar 26, 2014 at 7:22 PM, Daniel Pyrathon  wrote:

> Hi all,
>
> It's been a while since I submitted my GSOC proposal. Although I am
> currently under exams, is there anything you would recommend me to do at
> this point (other than hope that my proposal is successful)?
>
> Thanks,
> Daniel Pyrathon
>
>
> On Thursday, March 20, 2014 6:05:40 AM UTC, Russell Keith-Magee wrote:
>
>>
>> For the benefit of those reading along at home; I gave some revised notes
>> and had a conversation with Daniel on IRC a couple of hours ago.
>>
>> Yours,
>> Russ Magee %-)
>>
>>
>> On Thu, Mar 20, 2014 at 4:10 AM, Daniel Pyrathon wrote:
>>
>>> Hi!
>>>
>>> Thanks for all the comments yesterday. They really helped me make the
>>> proposal stronger.
>>> I have changed to proposal to reflect the changes. Would anyone like to
>>> have a look and, possibly, comment more?
>>>
>>> https://docs.google.com/document/d/1yp2_skqkxyrc0egdRv6ofnRGCI9nmvxDFB
>>> kCXgy0Jwo/edit#heading=h.wyxx4xxijubt
>>>
>>> Thanks,
>>> Dan
>>>
>>> On Wednesday, March 19, 2014 7:32:10 AM UTC, Aymeric Augustin wrote:
>>>
 On 19 mars 2014, at 06:27, Zach Borboa  wrote:

 > Curious, how do you get REPL shell access to the server with
 DEBUG=True with a vanilla Django deployment?

 That part of the discussion was about adding the werkzeug interactive
 debugger to Django's default error page.

 --
 Aymeric.




  --
>>> 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 django-develop...@googlegroups.com.
>>> To post to this group, send email to django-d...@googlegroups.com.
>>>
>>> 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/16264cb7-3f44-434d-865a-
>>> 8c33baa4d921%40googlegroups.com
>>> .
>>>
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>  --
> 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 django-developers+unsubscr...@googlegroups.com.
> To post to this group, send email to django-developers@googlegroups.com.
> 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/ad5d6016-2c6a-45b4-91c8-0e4500befc74%40googlegroups.com
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
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/CAJxq849CfFVLdgWD_Q3d-%2Bpk4%3DMX%3DWLzd%2BqNbQZHOZ%2Bumg_tjA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [GSOC] Introduction and task proposal

[Daniel Pyrathon]

Hi all,

It's been a while since I submitted my GSOC proposal. Although I am 
currently under exams, is there anything you would recommend me to do at 
this point (other than hope that my proposal is successful)?

Thanks,
Daniel Pyrathon

On Thursday, March 20, 2014 6:05:40 AM UTC, Russell Keith-Magee wrote:
>
>
> For the benefit of those reading along at home; I gave some revised notes 
> and had a conversation with Daniel on IRC a couple of hours ago.
>
> Yours,
> Russ Magee %-)
>
>
> On Thu, Mar 20, 2014 at 4:10 AM, Daniel Pyrathon 
> 
> > wrote:
>
>> Hi!
>>
>> Thanks for all the comments yesterday. They really helped me make the 
>> proposal stronger.
>> I have changed to proposal to reflect the changes. Would anyone like to 
>> have a look and, possibly, comment more?
>>
>>
>> https://docs.google.com/document/d/1yp2_skqkxyrc0egdRv6ofnRGCI9nmvxDFBkCXgy0Jwo/edit#heading=h.wyxx4xxijubt
>>
>> Thanks,
>> Dan
>>
>> On Wednesday, March 19, 2014 7:32:10 AM UTC, Aymeric Augustin wrote:
>>
>>> On 19 mars 2014, at 06:27, Zach Borboa  wrote: 
>>>
>>> > Curious, how do you get REPL shell access to the server with 
>>> DEBUG=True with a vanilla Django deployment? 
>>>
>>> That part of the discussion was about adding the werkzeug interactive 
>>> debugger to Django’s default error page. 
>>>
>>> -- 
>>> Aymeric. 
>>>
>>>
>>>
>>>
>>>  -- 
>> 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 django-develop...@googlegroups.com .
>> To post to this group, send email to 
>> django-d...@googlegroups.com
>> .
>> 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/16264cb7-3f44-434d-865a-8c33baa4d921%40googlegroups.com
>> .
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
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 django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
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/ad5d6016-2c6a-45b4-91c8-0e4500befc74%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [GSOC] Introduction and task proposal

[Russell Keith-Magee]

For the benefit of those reading along at home; I gave some revised notes
and had a conversation with Daniel on IRC a couple of hours ago.

Yours,
Russ Magee %-)


On Thu, Mar 20, 2014 at 4:10 AM, Daniel Pyrathon  wrote:

> Hi!
>
> Thanks for all the comments yesterday. They really helped me make the
> proposal stronger.
> I have changed to proposal to reflect the changes. Would anyone like to
> have a look and, possibly, comment more?
>
>
> https://docs.google.com/document/d/1yp2_skqkxyrc0egdRv6ofnRGCI9nmvxDFBkCXgy0Jwo/edit#heading=h.wyxx4xxijubt
>
> Thanks,
> Dan
>
> On Wednesday, March 19, 2014 7:32:10 AM UTC, Aymeric Augustin wrote:
>
>> On 19 mars 2014, at 06:27, Zach Borboa  wrote:
>>
>> > Curious, how do you get REPL shell access to the server with DEBUG=True
>> with a vanilla Django deployment?
>>
>> That part of the discussion was about adding the werkzeug interactive
>> debugger to Django's default error page.
>>
>> --
>> Aymeric.
>>
>>
>>
>>
>>  --
> 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 django-developers+unsubscr...@googlegroups.com.
> To post to this group, send email to django-developers@googlegroups.com.
> 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/16264cb7-3f44-434d-865a-8c33baa4d921%40googlegroups.com
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
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/CAJxq84_pBSmYKX2w-c1JDcAxtPjuwUsxdHstAHJYpZeWhK2DNg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [GSOC] Introduction and task proposal

[Daniel Pyrathon]

Hi!

Thanks for all the comments yesterday. They really helped me make the 
proposal stronger.
I have changed to proposal to reflect the changes. Would anyone like to 
have a look and, possibly, comment more?

https://docs.google.com/document/d/1yp2_skqkxyrc0egdRv6ofnRGCI9nmvxDFBkCXgy0Jwo/edit#heading=h.wyxx4xxijubt

Thanks,
Dan

On Wednesday, March 19, 2014 7:32:10 AM UTC, Aymeric Augustin wrote:
>
> On 19 mars 2014, at 06:27, Zach Borboa > 
> wrote: 
>
> > Curious, how do you get REPL shell access to the server with DEBUG=True 
> with a vanilla Django deployment? 
>
> That part of the discussion was about adding the werkzeug interactive 
> debugger to Django’s default error page. 
>
> -- 
> Aymeric. 
>
>
>
>
>

-- 
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 django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
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/16264cb7-3f44-434d-865a-8c33baa4d921%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [GSOC] Introduction and task proposal

[Aymeric Augustin]

On 19 mars 2014, at 06:27, Zach Borboa  wrote:

> Curious, how do you get REPL shell access to the server with DEBUG=True with 
> a vanilla Django deployment?

That part of the discussion was about adding the werkzeug interactive debugger 
to Django's default error page.

-- 
Aymeric.




-- 
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 django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
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/0BA238DA-E4BE-4ACB-A5ED-C405ED190DEF%40polytechnique.org.
For more options, visit https://groups.google.com/d/optout.

Re: [GSOC] Introduction and task proposal

[Zach Borboa]

2) Security implications. Unfortunately, more than one site has been 
> launched with debug=True accidentally left on; all you need to do then is 
> stimulate a server error, and you have REPL shell access to the server. 
> This strikes me as a remarkably effective foot-gun :-) Before you get too 
> involved in the implementation, I'd want to know the security issues have 
> been locked down.
>

Curious, how do you get REPL shell access to the server with DEBUG=True 
with a vanilla Django deployment?

-- 
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 django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
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/363c7b06-5a62-453d-9253-68bcb24b4398%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [GSOC] Introduction and task proposal

[Daniel Pyrathon]

Hi all,

As promised, I have been working on the formalizing Meta task.
I apologize to not have posted in the last days, but I have come back with 
my proposal. I want to post this now to the community, in order to gain 
feedback and re-iterate.

Formalizing Meta

Enabling users to build custom stores that work well with Django


https://docs.google.com/document/d/1yp2_skqkxyrc0egdRv6ofnRGCI9nmvxDFBkCXgy0Jwo/edit#

Kind regards,
Daniel

On Tuesday, March 11, 2014 10:48:43 PM UTC, Daniel Pyrathon wrote:
>
> Hi Russel,
>
> Sorry for getting back now (I did not have notifications set up!). Thank 
> you very much for the suggestions, I will have a look at models/options.py 
> right away.
>
> Regards,
> Daniel Pyrathon
>
> On Thursday, March 6, 2014 12:03:04 AM UTC, Russell Keith-Magee wrote:
>>
>> Hi Daniel,
>>
>> On Wed, Mar 5, 2014 at 11:48 PM, Daniel Pyrathon wrote:
>>
>>> Hi,
>>>
>>> My name is Daniel Pyrathon. I am currently a third year BSc student in 
>>> Computer Science at the University of Plymouth. 
>>>
>>> I love programming and I have always been active in the Open Source 
>>> community (especially Python). In the past years I have written lots of 
>>> Python, Javascript, Ruby, Java, and I am currently using C++ for many 
>>> university projects. I have attended the last 3 EuroPython conferences and 
>>> I have been a staff member of the conference for the last 2 years.
>>>
>>> I am currently looking for a way to contribute to Django. Working on 
>>> Django would increase my knowledge of the framework as well as let me share 
>>> my own experience.
>>>
>>> Reading the ideas list I found 2 of them that are very interesting for 
>>> me, and so the reason behind this post is not only to present myself but 
>>> also to discuss their feasibility.
>>>
>>> Formalizing the Meta object
>>>
>>> This task is very challenging because it digs in the internals of 
>>> Django. I feel that I could learn a lot from it because I am very committed 
>>> to refactoring and write most of my code in TDD. I have also experience 
>>> with backwards compatibility. 
>>>
>>> Do you have any resources (code) I should read to get up to date and to 
>>> understand better how it is currently implemented?
>>>
>>
>> Unfortunately not; at least, not other than just trying to untangle the 
>> mess that is django/db/models/options.py and the things that depend on it 
>> (ModelForms and Admin in particular). This project really is the very model 
>> of untangling a ball of string. The reason it's listed as a potential 
>> project is specifically *because* there are no resources we can point you 
>> at.
>>
>> If, after looking at the code, you feel it's a little "thin" for 12 
>> weeks, one way to bulk it out is to build a proof of concept alternate 
>> implementation of Meta. Aside from the "it would be good to document this" 
>> aspect, the practical reason for wanting to formalise Meta is that it would 
>> allow people to build duck-typed implementations of Meta. If you can build 
>> an alternate implementation of the Meta interface, then you should be able 
>> to deploy your "duck" into a Django project and build a ModelForm, or 
>> browse it in Admin.
>>
>> So, for example, you could build a wrapper around a NoSQL store, or 
>> around an LDAP or email store, that *looked* like a Django model from the 
>> outside. This means you could view your NoSQL data, or LDAP records, or 
>> emails in Admin without needing to go through a SQL database. 
>>
>> The aim of proof of concept wouldn't be to commit something to Django's 
>> core - it would be to build an external, standalone proof-of-concept, 
>> demonstrating that your documentation was complete and correct. Depending 
>> on what backend you choose, it might turn into a fully viable project on 
>> it's own.
>>  
>>
>>> Improved error reporting
>>>
>>> The idea of making people’s lives better by improving error messages is 
>>> fundamental. There would be a lot to discuss: what type of imports would we 
>>> want to mask? I have read BetterErrorMessages and would be happy to get 
>>> started soon. My idea behind this task would be to expand on this ticket: 
>>> what would be great is to add a web console with live REPL support, similar 
>>> to what Werkzeug debugger does. This could be a great starting point and 
>>> would lead to a better use of Django.
>>>
>>
>> This is an interesting idea; however, I see two problems:
>>
>> 1) It would involve reinventing the wheel. Werkzeug exists, and does its 
>> job well; a GSoC project to "duplicate Werkzeug" doesn't strike me as a 
>> good use of GSoC resources. However, a project to integrate Werkzeug's live 
>> debugging capabilities into Django might be more viable.
>>
>> 2) Security implications. Unfortunately, more than one site has been 
>> launched with debug=True accidentally left on; all you need to do then is 
>> stimulate a server error, and you have REPL shell access to the server. 
>> This strikes me as a rema

Re: [GSOC] Introduction and task proposal

[Daniel Pyrathon]

Hi Russel,

Sorry for getting back now (I did not have notifications set up!). Thank 
you very much for the suggestions, I will have a look at models/options.py 
right away.

Regards,
Daniel Pyrathon

On Thursday, March 6, 2014 12:03:04 AM UTC, Russell Keith-Magee wrote:
>
> Hi Daniel,
>
> On Wed, Mar 5, 2014 at 11:48 PM, Daniel Pyrathon 
> 
> > wrote:
>
>> Hi,
>>
>> My name is Daniel Pyrathon. I am currently a third year BSc student in 
>> Computer Science at the University of Plymouth. 
>>
>> I love programming and I have always been active in the Open Source 
>> community (especially Python). In the past years I have written lots of 
>> Python, Javascript, Ruby, Java, and I am currently using C++ for many 
>> university projects. I have attended the last 3 EuroPython conferences and 
>> I have been a staff member of the conference for the last 2 years.
>>
>> I am currently looking for a way to contribute to Django. Working on 
>> Django would increase my knowledge of the framework as well as let me share 
>> my own experience.
>>
>> Reading the ideas list I found 2 of them that are very interesting for 
>> me, and so the reason behind this post is not only to present myself but 
>> also to discuss their feasibility.
>>
>> Formalizing the Meta object
>>
>> This task is very challenging because it digs in the internals of Django. 
>> I feel that I could learn a lot from it because I am very committed to 
>> refactoring and write most of my code in TDD. I have also experience with 
>> backwards compatibility. 
>>
>> Do you have any resources (code) I should read to get up to date and to 
>> understand better how it is currently implemented?
>>
>
> Unfortunately not; at least, not other than just trying to untangle the 
> mess that is django/db/models/options.py and the things that depend on it 
> (ModelForms and Admin in particular). This project really is the very model 
> of untangling a ball of string. The reason it's listed as a potential 
> project is specifically *because* there are no resources we can point you 
> at.
>
> If, after looking at the code, you feel it's a little "thin" for 12 weeks, 
> one way to bulk it out is to build a proof of concept alternate 
> implementation of Meta. Aside from the "it would be good to document this" 
> aspect, the practical reason for wanting to formalise Meta is that it would 
> allow people to build duck-typed implementations of Meta. If you can build 
> an alternate implementation of the Meta interface, then you should be able 
> to deploy your "duck" into a Django project and build a ModelForm, or 
> browse it in Admin.
>
> So, for example, you could build a wrapper around a NoSQL store, or around 
> an LDAP or email store, that *looked* like a Django model from the outside. 
> This means you could view your NoSQL data, or LDAP records, or emails in 
> Admin without needing to go through a SQL database. 
>
> The aim of proof of concept wouldn't be to commit something to Django's 
> core - it would be to build an external, standalone proof-of-concept, 
> demonstrating that your documentation was complete and correct. Depending 
> on what backend you choose, it might turn into a fully viable project on 
> it's own.
>  
>
>> Improved error reporting
>>
>> The idea of making people’s lives better by improving error messages is 
>> fundamental. There would be a lot to discuss: what type of imports would we 
>> want to mask? I have read BetterErrorMessages and would be happy to get 
>> started soon. My idea behind this task would be to expand on this ticket: 
>> what would be great is to add a web console with live REPL support, similar 
>> to what Werkzeug debugger does. This could be a great starting point and 
>> would lead to a better use of Django.
>>
>
> This is an interesting idea; however, I see two problems:
>
> 1) It would involve reinventing the wheel. Werkzeug exists, and does its 
> job well; a GSoC project to "duplicate Werkzeug" doesn't strike me as a 
> good use of GSoC resources. However, a project to integrate Werkzeug's live 
> debugging capabilities into Django might be more viable.
>
> 2) Security implications. Unfortunately, more than one site has been 
> launched with debug=True accidentally left on; all you need to do then is 
> stimulate a server error, and you have REPL shell access to the server. 
> This strikes me as a remarkably effective foot-gun :-) Before you get too 
> involved in the implementation, I'd want to know the security issues have 
> been locked down.
>  
>
>> Said this, I have to be very honest. I have never contributed to Django 
>> up till now and I want to hear your feedback on which proposal would suit 
>> me best. However I learn a lot through experience and I am attracted by 
>> new and challenging tasks.
>>
>
> My suggestion would be that the Meta project is probably better suited to 
> a newcomer. The Error reporting project is a little vague - it relies on 
> someone having a bit of experience with Django to k

Re: Introduction

[Russell Keith-Magee]

Hi Naman,

All the details for Django's GSoC program can be found on our wiki page:

https://code.djangoproject.com/wiki/SummerOfCode2014

That page has a bunch of suggestions for projects, and details of what we
expect of applicants.

If you've got any more questions, let us know!

Yours,
Russ Magee %-)


On Sat, Mar 8, 2014 at 3:21 PM, Naman Gupta wrote:

> I am Naman from New Delhi India, pursuing Btech Computer Sceinces and
> Engg. from IIITD. I was looking forward to work in Django Project for the
> GSoC.
> I am a completely new and require guidance for what do I have to do. I
> have read the documentation and have completed the official django tutorial.
>
> Thanks and Regards,
> Naman
> naman13...@iiitd.ac.in
>
> --
> 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 django-developers+unsubscr...@googlegroups.com.
> To post to this group, send email to django-developers@googlegroups.com.
> 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/2a7469c6-2a0a-4f2c-865e-b1cd0beba45b%40googlegroups.com
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
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/CAJxq848u11_Ba-1NkuH5bqcQDrASPYewR3oqFQa%2BwBxinwBojA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Introduction

[Naman Gupta]

I am Naman from New Delhi India, pursuing Btech Computer Sceinces and Engg. 
from IIITD. I was looking forward to work in Django Project for the GSoC.
I am a completely new and require guidance for what do I have to do. I have 
read the documentation and have completed the official django tutorial.

Thanks and Regards,
Naman
naman13...@iiitd.ac.in

-- 
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 django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
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/2a7469c6-2a0a-4f2c-865e-b1cd0beba45b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [GSOC] Introduction and task proposal

[Russell Keith-Magee]

Hi Daniel,

On Wed, Mar 5, 2014 at 11:48 PM, Daniel Pyrathon  wrote:

> Hi,
>
> My name is Daniel Pyrathon. I am currently a third year BSc student in
> Computer Science at the University of Plymouth.
>
> I love programming and I have always been active in the Open Source
> community (especially Python). In the past years I have written lots of
> Python, Javascript, Ruby, Java, and I am currently using C++ for many
> university projects. I have attended the last 3 EuroPython conferences and
> I have been a staff member of the conference for the last 2 years.
>
> I am currently looking for a way to contribute to Django. Working on
> Django would increase my knowledge of the framework as well as let me share
> my own experience.
>
> Reading the ideas list I found 2 of them that are very interesting for me,
> and so the reason behind this post is not only to present myself but also
> to discuss their feasibility.
>
> Formalizing the Meta object
>
> This task is very challenging because it digs in the internals of Django.
> I feel that I could learn a lot from it because I am very committed to
> refactoring and write most of my code in TDD. I have also experience with
> backwards compatibility.
>
> Do you have any resources (code) I should read to get up to date and to
> understand better how it is currently implemented?
>

Unfortunately not; at least, not other than just trying to untangle the
mess that is django/db/models/options.py and the things that depend on it
(ModelForms and Admin in particular). This project really is the very model
of untangling a ball of string. The reason it's listed as a potential
project is specifically *because* there are no resources we can point you
at.

If, after looking at the code, you feel it's a little "thin" for 12 weeks,
one way to bulk it out is to build a proof of concept alternate
implementation of Meta. Aside from the "it would be good to document this"
aspect, the practical reason for wanting to formalise Meta is that it would
allow people to build duck-typed implementations of Meta. If you can build
an alternate implementation of the Meta interface, then you should be able
to deploy your "duck" into a Django project and build a ModelForm, or
browse it in Admin.

So, for example, you could build a wrapper around a NoSQL store, or around
an LDAP or email store, that *looked* like a Django model from the outside.
This means you could view your NoSQL data, or LDAP records, or emails in
Admin without needing to go through a SQL database.

The aim of proof of concept wouldn't be to commit something to Django's
core - it would be to build an external, standalone proof-of-concept,
demonstrating that your documentation was complete and correct. Depending
on what backend you choose, it might turn into a fully viable project on
it's own.


> Improved error reporting
>
> The idea of making people's lives better by improving error messages is
> fundamental. There would be a lot to discuss: what type of imports would we
> want to mask? I have read BetterErrorMessages and would be happy to get
> started soon. My idea behind this task would be to expand on this ticket:
> what would be great is to add a web console with live REPL support, similar
> to what Werkzeug debugger does. This could be a great starting point and
> would lead to a better use of Django.
>

This is an interesting idea; however, I see two problems:

1) It would involve reinventing the wheel. Werkzeug exists, and does its
job well; a GSoC project to "duplicate Werkzeug" doesn't strike me as a
good use of GSoC resources. However, a project to integrate Werkzeug's live
debugging capabilities into Django might be more viable.

2) Security implications. Unfortunately, more than one site has been
launched with debug=True accidentally left on; all you need to do then is
stimulate a server error, and you have REPL shell access to the server.
This strikes me as a remarkably effective foot-gun :-) Before you get too
involved in the implementation, I'd want to know the security issues have
been locked down.


> Said this, I have to be very honest. I have never contributed to Django up
> till now and I want to hear your feedback on which proposal would suit me
> best. However I learn a lot through experience and I am attracted by new
> and challenging tasks.
>

My suggestion would be that the Meta project is probably better suited to a
newcomer. The Error reporting project is a little vague - it relies on
someone having a bit of experience with Django to know when the errors that
are being returned are unhelpful. A "green" Django user *could* do this,
but they're going to spend a lot more time trying to find problems that
need to be fixed.

Approaching the project from the Werkzeug angle is an interesting idea, but
you're not starting with a pre-blessed project -- your first step is to
convince the core team that the idea is worth pursuing. Given the
compressed timeframe for submitting applications, it might not be possib

[GSOC] Introduction and task proposal

[Daniel Pyrathon]

Hi,

My name is Daniel Pyrathon. I am currently a third year BSc student in 
Computer Science at the University of Plymouth. 

I love programming and I have always been active in the Open Source 
community (especially Python). In the past years I have written lots of 
Python, Javascript, Ruby, Java, and I am currently using C++ for many 
university projects. I have attended the last 3 EuroPython conferences and 
I have been a staff member of the conference for the last 2 years.

I am currently looking for a way to contribute to Django. Working on Django 
would increase my knowledge of the framework as well as let me share my own 
experience.

Reading the ideas list I found 2 of them that are very interesting for me, 
and so the reason behind this post is not only to present myself but also 
to discuss their feasibility.

Formalizing the Meta object

This task is very challenging because it digs in the internals of Django. I 
feel that I could learn a lot from it because I am very committed to 
refactoring and write most of my code in TDD. I have also experience with 
backwards compatibility. 

Do you have any resources (code) I should read to get up to date and to 
understand better how it is currently implemented?

Improved error reporting

The idea of making people’s lives better by improving error messages is 
fundamental. There would be a lot to discuss: what type of imports would we 
want to mask? I have read BetterErrorMessages and would be happy to get 
started soon. My idea behind this task would be to expand on this ticket: 
what would be great is to add a web console with live REPL support, similar 
to what Werkzeug debugger does. This could be a great starting point and 
would lead to a better use of Django.

Said this, I have to be very honest. I have never contributed to Django up 
till now and I want to hear your feedback on which proposal would suit me 
best. However I learn a lot through experience and I am attracted by new 
and challenging tasks.
Also, it would be nice if I could have some suggestions on what to read and 
if there are some specific parts of the code I should be directed to.

Please let me know,
Daniel Pyrathon

-- 
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 django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
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/0b1cc1e7-063a-48ea-9c92-eaa0344d396d%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Introduction to GSOC 2014

[Vinay Raghavan]

Hi, I'm Vinay Raghavan. I'm a self- taught programmer and currently 
pursuing BE. in Electronics and Communication.

I am interested in working on the project "Test framework cleanup".
I have about 5 months experience of developing information mining web 
applications using Django during my internship. Information mining happens 
to be one of my favorite fields.


-- 
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 django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
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/0886dc84-9046-4e46-9fd9-448b3a0a8541%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Introduction

[Harjot Mann]

Hello Django-developers,

My name is Harjot Kaur Mann. I am working on Django from last one year. I 
am an active member on Django-users mailing list. Now I want to work on 
DJango as developer. 
I have worked on two projects one was my six weeks training project, it was 
used to manage the DMC records of students. Other is related to 
Automate the work of an organization. Now I am going to start a new project 
which is the Sports Database Management using this wonderful framework. 
Looking forward to work with you all.

Thanks

-- 
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 django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
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/1bd4ce41-d117-4796-9aa5-13df06629b0a%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Introduction

[Jasvir Singh]

On Saturday, October 12, 2013 7:53:38 PM UTC+5:30, Daniele Procida wrote:

> In particular you might want to choose something straightforward to begin 
> with, so look for tickets marked as "easy pickings": <
> https://code.djangoproject.com/query?

 

>
> You have probably already done so, but if not, take a look at <
> https://docs.djangoproject.com/en/1.5/internals/contributing/> 
>

Thanks Daniele.
I think I have to start with some video tutorials after which I'll try 
tickets as you suggested.

--
Jasvir Singh  

-- 
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 django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
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/e1248be5-757d-4480-a51a-9876e4fa444d%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Introduction

[Daniele Procida]

On Sat, Oct 12, 2013, Jasvir Singh  wrote:

>I am Jasvir Singh, a student of Computer Science.
>5-6 months ago, I started working on django and found it is a really
>efficient tool.
>Now I want to do some development for django.
>
>Can anyone please suggest me some task/project to do.

Hi Jasvir. If you'd like to contribute to Django itself, why not have a look at 
the ticket tracker: ?

In particular you might want to choose something straightforward to begin with, 
so look for tickets marked as "easy pickings": 
.

>May I start with making some video tutorials, in which I'll explain
>how to make a poll or blog application?

That too could be a valuable contribution to the community, though it will 
probably be more work, and will probably benefit fewer people.

You have probably already done so, but if not, take a look at 


Regards,

Daniele

-- 
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 django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
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/20131012142338.1774804393%40smtp.ntlworld.com.
For more options, visit https://groups.google.com/groups/opt_out.

Introduction

[Jasvir Singh]

Hello everyone.

I am Jasvir Singh, a student of Computer Science.
5-6 months ago, I started working on django and found it is a really
efficient tool.
Now I want to do some development for django.

Can anyone please suggest me some task/project to do.
May I start with making some video tutorials, in which I'll explain
how to make a poll or blog application?
-- 

Jasvir Singh Grewal
Blog:http://jasvirsinghgrewal91.wordpress.com/

-- 
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 django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
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/CAN_O85s3xHDLTNpEM5U3AXx%3DDw6iiT6j%3DHTNLKHMRSXGARgDxw%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.

[GSoC] An Introduction about me

[Madhusudan C.S]

Hi all,
   This is an introduction about myself. Since Jacob said,
"And if we don't know them at all, it's hard to trust they'll
get things done." I am writing my involvement in Django and
other FOSS communities in general here to let you all know
something about me. Hope this helps you people to tell me
what I need to learn and how to go about the idea I am
interested in.

I have been interested in contributing to Django even before
GSoC ever flashed to me. In January or so, I badly felt the
need for Multiple Primary Key support (Ticket #373) and
pinged David Crammer about it on #django-dev, since he had
done some work on it. Back then I started to read the Django
ORM code, but could not write any code after that. Thanks to
University coursework :(

Later from early March I have been trying to contribute
something to Django. (I am free from then and will be
mostly free henceforth and totally free in Summer without
any other commitments.) I have had some discussions about
fixing ticket #8161 on django-devel list (http://is.gd/obr2)
but unfortunately it was fixed. So was looking for few other
things and I thought I will apply for GSoC as Django student
since I felt it lowers the barrier to get started. I am
mostly interested in ORM related ideas since I have read
most of django.db.* code. (I am sorry, I am not claiming I
am very well versed in Django ORM, but I have a fair idea of
how the code is written and structured). I am searching for
other ORM related ideas from the ticket list. I will get
back to you all whenever I find I something interesting.

I am involved in FOSS communities from 3 years now and have
Python experience of around 1.25 years. I have contributed
few patches to projects like Melange
(http://code.google.com/p/soc/source/browse/trunk/AUTHORS,
the app on which this year GSoC is run, built on Django),
KDE Step (http://is.gd/oci7), GNUSim8085(worked for Windows
port), RTEMS and quite a few other FOSS projects.


-- 
Thanks and regards,
 Madhusudan.C.S

Blogs at: www.madhusudancs.info
Official Email ID: madhusu...@madhusudancs.info

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en
-~--~~~~--~~--~--~---

Re: Introduction to CRM

[bedros]

thanks man, I was looking for more information about how CRM works.

On May 21, 4:04 am, Ankur <[EMAIL PROTECTED]> wrote:
> Hi All,
>
> I just found a link which seems to be quite informative about CRM.
>
> Just try the link below to have a look at it.
>
> http://www.quazen.com/Business/Management/Introduction-to-CRM.25530
>
> This contains the basics of CRM. I really loved this article.
>
> Thanks,
> Ankur


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en
-~--~~~~--~~--~--~---

Introduction to CRM

[Ankur]

Hi All,

I just found a link which seems to be quite informative about CRM.

Just try the link below to have a look at it.

http://www.quazen.com/Business/Management/Introduction-to-CRM.25530

This contains the basics of CRM. I really loved this article.

Thanks,
Ankur


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en
-~--~~~~--~~--~--~---

Short Introduction to smart work

[Shortcut Weebly]

  ShortIntroduction 

Well, cut short, Shortcut takes you to those ultimate, hand picked,
genuine sites 
that add bucks to your pocket, without any strings attached!

What you will find here:
Links to time-tested and transparent websites leading you to earn
money by
something as simple as referring it to other people (Posting it in groups,
via e-mail,
blogs, chat, etc...), something that this website does.

What you won't find in here:
Any irritating ads popping up, forums, blogs, anything that deviates
from the
website's intention.
Any hi-funda stuff. Things are pretty simple here and won't take
much of your time
to getting used to and/or to attain fast growth.


You may visit our links to sign up for them and instantly start
getting paid.
Of course hard work and dedication are essential for success
but thats not the case with Shortcut!..

Smart work and a bit of time will take you heights...

So enjoy and all the best to you.


 Visit shortcut.weebly.com


Please do not mark this message as spam rather delete or discard
it.
We hate spams as much as you do, this message is only for your
interest .

Thank You for reading so patiently. And sorry coz we came in without
knocking your door !!

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en
-~--~~~~--~~--~--~---

Short Introduction to smart work

[Shortcut Weebly]

  ShortIntroduction 

Well, cut short, Shortcut takes you to those ultimate, hand picked,
genuine sites 
that add bucks to your pocket, without any strings attached!

What you will find here:
Links to time-tested and transparent websites leading you to earn
money by
something as simple as referring it to other people (Posting it in groups,
via e-mail,
blogs, chat, etc...), something that this website does.

What you won't find in here:
Any irritating ads popping up, forums, blogs, anything that deviates
from the
website's intention.
Any hi-funda stuff. Things are pretty simple here and won't take
much of your time
to getting used to and/or to attain fast growth.


You may visit our links to sign up for them and instantly start
getting paid.
Of course hard work and dedication are essential for success
but thats not the case with Shortcut!..

Smart work and a bit of time will take you heights...

So enjoy and all the best to you.


Click here to visit shortcut.weebly.com



Please do not mark this message as spam rather delete or discard
it.
We hate spams as much as you do, this message is only for your
interest .

Thank You for reading so patiently. And sorry coz we came in without
knocking your door !!

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en
-~--~~~~--~~--~--~---

Re: introduction

[Luke Plant]

Andy Shaw wrote:

> PS: would Luke's GenericForeignKey allow for inline editing, assuming it
> was to be adopted? Personally I'd much rather be able to alter a row's
> permissions on its own admin page than have to switch table.

There would have to be very specialised support for it.  I haven't been
following carefully, but I imagine the permissions systems won't affect
existing tables, or the model definitions, so there is no way for a
model to know it has a GenericForeignKey pointed at it -- precisely
because it is generic and no relationship exists at the database level.
 (I currently have a utility method to add the relevant descriptor
attributes to models, but you have to call it manually, and it doesn't
even appear in the models field list (MyModel._meta.fields))

Luke


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-developers
-~--~~~~--~~--~--~---

Re: introduction

[Chris L]

Thanks everyone for the ideas, I've updated the wiki page. Please take
a look if you have a moment and let me know.

Thanks,

Chris


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-developers
-~--~~~~--~~--~--~---

Re: introduction

[Andy Shaw]

Hi Chris,

The implementation detailed on the wiki appears to give the granularity
that several people around here (including myself) have been looking
for, minus the various points that have already been brought up. An
ACL-type solution as opposed to UNIX-style permissions certainly seems
more flexible. My concern is that there's no details suggesting
precisely how to implement one of the more common scenarios: when you
want to specify that users can only have certain permissions for rows
they've created themselves. An example of this would be your forum -
apart from moderators, you only want users to be able to edit their own
posts.

Clearly, with the given proposal, it would be possible (and necessary)
to create a new permission row for each data row the user generates.
This is not especially hard, but a straightforward generic mechanism for
doing this would be nice (which is to say, a mechanism that allows the
admin system to generate the appropriate permissions when a user creates
a new row).

There might be one or two other similar situations the want considering,
but this is my personal bugber at the moment. Anyway, looking good.

-Andy

PS: would Luke's GenericForeignKey allow for inline editing, assuming it
was to be adopted? Personally I'd much rather be able to alter a row's
permissions on its own admin page than have to switch table.

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-developers
-~--~~~~--~~--~--~---

Re: introduction

[Ian Holsman]

one more nit to add to my growing pile,
while I use integer's as my keys (which is they  default django way),  
others override this and use strings and other weird things.
I'm not sure how my previous suggestion would work when you take that  
kind of thing into account.

On 28/05/2006, at 9:04 AM, Ian Holsman wrote:

>
> Hi Chris... great write up.
>
> my only thought was: why do you need multiple tables to store the row
> level permissions?
>
> Luke has recently submitted a 'GenericForeignKey' in
> http://files.lukeplant.fastmail.fm/public/python/ 
> lp_tagging_app_0.1.zip
>
> which may be of interest. it would allow you to store all the
> information in  a single table then. (it stores the content-type of
> the table as well)
>
> other questions to ponder:
>
> are you going to allow 'blanket' permissions user/group X is allowed
> to do Y on ALL rows?
> are you going to allow negativity ? ie.. person X is NOT allowed to
> see row Y.
>
> regards
> Ian
>
> On 28/05/2006, at 4:47 AM, Chris L wrote:
>
>>
>> Hi Ian,
>>
>> Wrote up a summary on the wiki page:
>> http://code.djangoproject.com/wiki/RowLevelPermissions
>>
>> Please let me know what you think, if anyone else has any input  
>> please
>> let me know.
>>
>> Right now, I'm working through the source code in more depth then my
>> previous exploration of it, and will be modifying the wiki page to
>> expand and modify what is written there during my journey into it.  
>> Any
>> mistakes you notice, please let me know.
>>
>> Thanks,
>>
>> Chris
>>
>>
>>>
>
>
> >


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-developers
-~--~~~~--~~--~--~---

Re: introduction

[oggie rob]

> How do you deal with those permissions in the generic and admin views?

To be clearer, I meant: How do you deal with those permissions in the
generic and admin *list* views?

 -rob


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-developers
-~--~~~~--~~--~--~---

Re: introduction

[oggie rob]

Hi Chris,
I have a little feedback if you are interested. [Just so you know, I'm
a "heavy user" of Django but have yet to make a substancial
contribution to the project]

In general I think your proposal is fine but I have a few points:
-Lots of tables there! Can you acheive the same without the extra
tables? I would guess you can come pretty close. I think by narrowing
your functionality to *only* deal with the example you provided you can
greatly simplify your implementation and the management of the db.
-(Somewhat contrary to the suggestion above!) An alternative approach
for the group-level changes: a new permission type that allows you to
assign a group that can access that object. i.e. permissionA = access
for every user in groupA. Then every user that belongs to groupA can
access objects created by any user in groupA. You would then,
obviously, add the permission to groupA only
-How do you deal with those permissions in the generic and admin views?
You may need to change the returned lists to show only those things
that the user has created? I'm not sure. I know it would be an issue in
the admin pages but the generic lists might be used in various ways
(and perhaps the option to choose would be nice).

Anyway, that's just what came to me when I was looking. Thanks for
taking this on!

 -rob


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-developers
-~--~~~~--~~--~--~---

Re: introduction

[Honza Král]

I think that multiple tables are better because its easier to manage -
you can use foreign keys inside the DB, thus it can be faster and
clearer plus its easier to drop a table than delete many rows.

I gave this feature a lot of thought (I thought of applying for it
myself ;) ), here are some of my ideas (feel completely free to ignore
them ;) ):

Use the category-level permissions as a default, when row-level
permissions are not set. If they are, they override the generic (so
that you can say, that CODERS can modify all PROJECTS, except project
X).

The problem with this approach is that it is not compatible with
django's auth subsystem where you cannot (please correct me if I am
wrong) revoke a privilege once a user has gained it (via group), you
can only grant, so that the user ends up with the strongest privileges
posiible for him.

It would be great if you could also specify a negative permission (as
Ian proposes), so that the hierarchy would be:
GROUP(s) - USER - GROUP(s) (row level) - USER (row level)
and the rightmost permission applicable for a given object (row) would
be used, be it positive or negative.

Honza

On 5/28/06, Ian Holsman <[EMAIL PROTECTED]> wrote:
>
> Hi Chris... great write up.
>
> my only thought was: why do you need multiple tables to store the row
> level permissions?
>
> Luke has recently submitted a 'GenericForeignKey' in
> http://files.lukeplant.fastmail.fm/public/python/lp_tagging_app_0.1.zip
>
> which may be of interest. it would allow you to store all the
> information in  a single table then. (it stores the content-type of
> the table as well)
>
> other questions to ponder:
>
> are you going to allow 'blanket' permissions user/group X is allowed
> to do Y on ALL rows?
> are you going to allow negativity ? ie.. person X is NOT allowed to
> see row Y.
>
> regards
> Ian
>
> On 28/05/2006, at 4:47 AM, Chris L wrote:
>
> >
> > Hi Ian,
> >
> > Wrote up a summary on the wiki page:
> > http://code.djangoproject.com/wiki/RowLevelPermissions
> >
> > Please let me know what you think, if anyone else has any input please
> > let me know.
> >
> > Right now, I'm working through the source code in more depth then my
> > previous exploration of it, and will be modifying the wiki page to
> > expand and modify what is written there during my journey into it. Any
> > mistakes you notice, please let me know.
> >
> > Thanks,
> >
> > Chris
> >
> >
> > >
>
>
> >
>


-- 
Honza Král
E-Mail: [EMAIL PROTECTED]
ICQ#:   107471613
Phone:  +420 606 678585

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-developers
-~--~~~~--~~--~--~---

Re: introduction

[Ian Holsman]

Hi Chris... great write up.

my only thought was: why do you need multiple tables to store the row  
level permissions?

Luke has recently submitted a 'GenericForeignKey' in
http://files.lukeplant.fastmail.fm/public/python/lp_tagging_app_0.1.zip

which may be of interest. it would allow you to store all the  
information in  a single table then. (it stores the content-type of  
the table as well)

other questions to ponder:

are you going to allow 'blanket' permissions user/group X is allowed  
to do Y on ALL rows?
are you going to allow negativity ? ie.. person X is NOT allowed to  
see row Y.

regards
Ian

On 28/05/2006, at 4:47 AM, Chris L wrote:

>
> Hi Ian,
>
> Wrote up a summary on the wiki page:
> http://code.djangoproject.com/wiki/RowLevelPermissions
>
> Please let me know what you think, if anyone else has any input please
> let me know.
>
> Right now, I'm working through the source code in more depth then my
> previous exploration of it, and will be modifying the wiki page to
> expand and modify what is written there during my journey into it. Any
> mistakes you notice, please let me know.
>
> Thanks,
>
> Chris
>
>
> >


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-developers
-~--~~~~--~~--~--~---

Re: introduction

[Chris L]

Hi Ian,

Wrote up a summary on the wiki page:
http://code.djangoproject.com/wiki/RowLevelPermissions

Please let me know what you think, if anyone else has any input please
let me know.

Right now, I'm working through the source code in more depth then my
previous exploration of it, and will be modifying the wiki page to
expand and modify what is written there during my journey into it. Any
mistakes you notice, please let me know.

Thanks,

Chris


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-developers
-~--~~~~--~~--~--~---

Re: introduction

[Ian Holsman]

Hi Chris.

why not post your idea onto the list.

it's much easier to critique something than wave hands around.
you might also want to set up a wiki page on say http:// 
code.djangoproject.com/wiki/RowLevelPermissions or something

I've my own thoughts, but I'd rather see what you have than dictate it.

regards
Ian
On 27/05/2006, at 11:15 AM, Chris L wrote:

>
> Guess I'll just continue this thread. My name is Chris, another one of
> the SoC students.
>
> I'm working on per row permissions, so if anyone has any ideas on it,
> please let me know. I have my own idea, but what I think works  
> might be
> horribly wrong for everyone else. Not to say that my idea sucks. ;) So
> I want to get an idea of what other developers and users of Django are
> thinking for this feature.
>
> Otherwise, a bit about me, I'm Canadian, living outside Toronto.
> Entering my last year of University in Computer Science with a math
> minor.
>
> Really looking forward to this summer and the project.
>
> Cheers,
>
> Chris
> [EMAIL PROTECTED]
>
>
> >


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-developers
-~--~~~~--~~--~--~---

Re: introduction

[Chris L]

Guess I'll just continue this thread. My name is Chris, another one of
the SoC students.

I'm working on per row permissions, so if anyone has any ideas on it,
please let me know. I have my own idea, but what I think works might be
horribly wrong for everyone else. Not to say that my idea sucks. ;) So
I want to get an idea of what other developers and users of Django are
thinking for this feature.

Otherwise, a bit about me, I'm Canadian, living outside Toronto.
Entering my last year of University in Computer Science with a math
minor.

Really looking forward to this summer and the project.

Cheers,

Chris
[EMAIL PROTECTED]


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-developers
-~--~~~~--~~--~--~---

introduction

[public]

hey all,

i'm derek, one of the SoC selectees. just
thought i'd pop my head in and say hi. :)

-- derek anderson
http://kered.org/


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-developers
-~--~~~~--~~--~--~---