Before reporting a bug on the ticket tracker consider these points:
\nCheck that someone hasn’t already filed the bug report by searching or\nrunning custom queries in the ticket tracker.
Don’t use the ticket system to ask support questions. Use the Django Forum\nor the Django Discord server for that.
Don’t reopen issues that have been marked „wontfix” without finding consensus\nto do so on the Django Forum.
Don’t use the ticket tracker for lengthy discussions, because they’re\nlikely to get lost. If a particular ticket is controversial, please move the\ndiscussion to the Django Forum.
Dobrze napisane raporty błędów są niesamowicie pomocne. Jednakże w pracy z jakimkolwiek systemem zgłaszania błędów zawsze jest pewien koszt, więc doceniona zostanie twoja pomoc w utrzymaniu systemu tak użytecznym jak to możliwe. W szczególności:
\nPrzeczytaj FAQ, aby zobaczyć czy twoje zgłoszenie nie jest dobrze znanym pytaniem.
Do ask on Django Forum or the Django Discord server first if\nyou’re not sure if what you’re seeing is a bug.
Pisz kompletne, odtwarzalne, konkretne zgłoszenia błędów. Musisz zawrzeć czytelny, zwarty opis problemu i zestaw instrukcji, jak go odtworzyć. Dodaj tak dużo informacji debugowania jak możesz: skrawki kodu, testy, ślad powrotny wyjątku, zrzut ekranu i tym podobne. Ładny mały test jest najlepszym sposobem na zgłoszenie błędu, jako że szybko i w pomocny sposób pozwala potwierdzić błąd.
Don’t post to Django Forum only to announce that you have filed a\nbug report. All the tickets are mailed to another list, django-updates,\nwhich is tracked by developers and interested community members; we see them\nas they are filed.
Aby zrozumieć cykl życia zgłoszenia po jego stworzeniu, przejdź do Triaging tickets.
\nIf your bug impacts anything visual in nature, there are a few additional\nguidelines to follow:
\nInclude screenshots in your ticket which are the visual equivalent of a\nminimal test case. Show off the issue, not the crazy customizations\nyou’ve made to your browser.
If the issue is difficult to show off using a still image, consider\ncapturing a brief screencast. If your software permits it, capture only\nthe relevant area of the screen.
If you’re offering a patch that changes the look or behavior of Django’s\nUI, you must attach before and after screenshots/screencasts.\nTickets lacking these are difficult for triagers to assess quickly.
Screenshots don’t absolve you of other good reporting practices. Make sure\nto include URLs, code snippets, and step-by-step instructions on how to\nreproduce the behavior visible in the screenshots.
Make sure to set the UI/UX flag on the ticket so interested parties can\nfind your ticket.
If the issue relates to accessibility, please link to the relevant\naccessibility standard if applicable.
Zawsze próbujemy ulepszać Django, a wasze prośby o funkcjonalności są kluczową tego częścią. Tutaj jest kilka porad jak najefektywniej zgłaszać prośbę:
\nEvaluate whether the feature idea requires changes in Django’s core. If your\nidea can be developed as an independent application or module — for\ninstance, you want to support another database engine — we’ll probably\nsuggest that you develop it independently. Then, if your project gathers\nsufficient community support, we may consider it for inclusion in Django.
Propose the feature in the new feature ideas GitHub project (not in the\nticket tracker) by creating a new item in the Idea column. This is where\nthe community and the Steering Council evaluate new\nideas for the Django ecosystem. This step is especially important for large\nor complex proposals. We prefer to discuss any significant changes to\nDjango’s core before any development begins. In some cases, a feature may be\nbetter suited as a third-party package, where it can evolve independently of\nDjango’s release cycle.
Describe clearly and concisely what the missing feature is and how you’d\nlike to see it implemented. Include example code (non-functional is OK)\nif possible.
Explain why you’d like the feature. Explaining a minimal use case will help\nothers understand where it fits in, and if there are already other ways of\nachieving the same thing.
See also: Documenting new features.
\nReports of a performance regression, or suggested performance optimizations,\nshould provide benchmarks and commands for the ticket triager to reproduce.
\nSee the django-asv benchmarks for more details of Django’s existing\nbenchmarks.
\nWhenever possible, we aim for rough consensus. Emoji reactions are used on\nissues within the new feature ideas GitHub project to track community\nfeedback. The following meanings are assigned to each reaction:
\n👍: I support this feature and would use it
👎: I oppose this feature or believe it would cause issues for me or Django
😕: I have no strong opinion on this feature
🎉: This feature seems like a straightforward and beneficial addition
The Steering Council will regularly review the ideas\nin the project, moving those with community support through the following\nstages:
\nIdea
Approved - Idea refinement - Team creation
In progress
Working solution - Review - Feedback
Needs maintainer (Django only)
Done
Occasionally, discussions on feature ideas or the direction of Django may take\nplace on the Django Forum. These discussions may include informal votes, which\nfollow the voting style invented by Apache and used on Python itself, where\nvotes are given as +1, +0, -0, or -1.\nRoughly translated, these votes mean:
\n+1: „I love the idea and I’m strongly committed to it.”
+0: „Sounds OK to me.”
-0: „I’m not thrilled, but I won’t stand in the way.”
-1: „I strongly disagree and would be very unhappy to see the idea turn\ninto reality.”
Although these votes are informal, they’ll be taken very seriously. After a\nsuitable voting period, if an obvious consensus arises we’ll follow the votes.
\n