Re: Hello everyone I'm a new member

There is a chapter in the documentation on how to contribute to django. It should answer most of your questions. On 13 Dec 2017 3:10 am, "Asad Ahmed" wrote: > Hello everyone, > I'm new to open source community. I've been working on python and django > framework for few

Hello everyone I'm a new member

Hello everyone, I'm new to open source community. I've been working on python and django framework for few years now. I've done few projects based on them and ML. I'm planing for Gsoc. I would be really grateful if anyone can guide me on how to proceed for open source contribution on django.

Re: Proposal: make Model __unicode__() default to self.name

Hi Collin, On Tuesday, December 12, 2017 at 3:48:38 PM UTC+1, Collin Anderson wrote: > Yes, having a good __str__ is important, and thats why i think defaulting > it to the pk is good, because it's better than nothing. Yes, you'll still > want to override __str__ with something better (that

Re: Proposal: make Model __unicode__() default to self.name

Hi Alex, > I think __str__ is a more user/human-friendly thing, which I don't think can be generated automatically. Yes, having a good __str__ is important, and thats why i think defaulting it to the pk is good, because it's better than nothing. Yes, you'll still want to override __str__ with

Re: change commit message format to present tense?

I've read all your comments and I understand the "readability matters" arguments, but I think we're looking at it from a wrong angle. Commit message *is not a history record.* Commit *is a diff*, and commit message should be a *human version* of that diff. Please keep in mind that commits can