I had a chance to read all of the articles you guys pointed out and
they helped tremendously. I'll take a look at some tickets and the
documentation on how I should go about fixing/submitting later today
(after some sleep and class).
I really feel like I have a much better idea now, so thank you
On Mon, 2007-02-12 at 06:56 +, zbelzer wrote:
> Hi all.
>
> I've been learning about and working with Django for a little while
> now and I have decided that I would like to help contribute to the
> project and community. I'm decent with python, but I still find that
> looking through the ent
Thanks everyone!
I'll look into all your suggestions tonight after work (I'm so sick of
PHP).
I appreciate the help,
Zach
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this
zbelzer wrote:
> Hi all.
>
> I've been learning about and working with Django for a little while
> now and I have decided that I would like to help contribute to the
> project and community. I'm decent with python, but I still find that
> looking through the entire code base is pretty intimidatin
Hi,
I'd like to add that you can learn a lot by looking into the existing
tickets, and try to follow what they do. Some areas are hard to follow,
others quite easy, poke a bit around to find what you like.
It would be a great contribution if you could look into the approved
tickets that need tes
On 2/12/07, zbelzer <[EMAIL PROTECTED]> wrote:
> The question I have is where does one begin on figuring out how things
> work in detail (behind the scenes) and where I should start in trying
> to contribute. Do I try to follow the execution of something like
> syncdb or do I start somewhere else?
Hi all.
I've been learning about and working with Django for a little while
now and I have decided that I would like to help contribute to the
project and community. I'm decent with python, but I still find that
looking through the entire code base is pretty intimidating and trying
to follow the
