Getting Started with the DJango Developer Community

Greetings to all!

I want to start bringing my benefits to the django community.
I have already read the guides on getting started, and I would like to know how you can take tickets and work on them.

For example, now I would like to do the right thing and fix the outdated code in Django that was talked about in Tibet #34709, will it be possible for me to start this work or is this ticket already closed?

Thank you in advance for your answer and help!

1 Like

Hi @abdulaev-sh-m that’s great to hear! Welcome! :wave:
The ticket you’re reffering to (#34709 (charset should be ignored for the application/x-www-form-urlencoded content type.) – Django) is not the best ticket as Mariusz created the ticket and assigned himself to it just a couple of days ago, so it is likely it is already being worked on.
If you need a ticket suggestion, this ticket is not a bad one for a first ticket: #34657 (Testing assertions `assertContains` and `assertInHTML` should output the haystack on failure) – Django

Look forward to seeing what you end up doing! :tada:
If you like discord, you can also go to the #contribing-getting-started channel: Discord. That might be a little quicker to get responses on small questions you might have :+1:

1 Like

Greetings, @sarahboyce !

Thank you for your help in selecting the ticket, I fixed the flaw mentioned in the ticket and sent the PR!)

Which ticket would you recommend I do next?

Thank you for your help!

Awesome! I have left a comment on the PR with the next steps. Also note that there is a patch review checklist here: Submitting patches | Django documentation | Django
As this is a change to a feature you need to make sure that you do everything in the “New features”, “All code changes” and “All tickets” sections.

First I would focus on getting the test suite passing and having the changes covered by test cases. :+1:

1 Like

Hello @sarahboyce!

I updated the PR and it passed all the tests.

Please tell me which issues should I work on more?

I’ve added some minor comments on the PR, well done for getting the tests passing! I would focus on resolving PR comments and trying to get an approval before picking up a next ticket but you can always take a look at open tickets and pick up another one if you like?

Können Sie mir auch ähnlich schwierige Themen empfehlen, an denen ich arbeiten kann, vergleichbar mit dem, was in diesem Thema erwähnt wurde? Ich bin ein junger Django Entwickler, der sich jedoch verbessern möchte.

— Original post from google translate —
Can you also recommend similar difficult topics for me to work on, comparable to what was mentioned in this topic? I’m a young Django developer who wants to improve

— From google translate —
Sie werden wahrscheinlich mehr Antworten auf Ihre Frage erhalten, wenn Sie auf Englisch posten.

(Tut mir leid, ich persönlich habe keine Empfehlungen für Sie. Ich würde vorschlagen, dass Sie die offenen Tickets durchsehen, um zu sehen, was Ihrer Meinung nach für Sie in der Lage sein könnte. Sie sollten auch Writing your first patch for Django | Django documentation | Django )

— The original English —
You’re likely going to get more responses to your question if you post in English.

(Sorry, I personally don’t have any recommendations for you. I would suggest you look through the open tickets to see what you think you may be able to handle. You’ll also want to read Writing your first patch for Django | Django documentation | Django )

1 Like

Ich denke, #34988 (Makemigrations shouldn't prompt for default values for non-nullable fields of other apps.) – Django ist leicht zu verstehen, aber schwer zu lösen.
Aber normalerweise würde ich für Ihr erstes Ticket etwas Einfacheres vorschlagen.

To reiterate what Ken said, we’re a global community but our communication is mostly in English. Ticket comments, pull requests, reviews will be in English :+1:

1 Like