Por outro lado, antes de reportar um “bug” ou requerer uma nova funcionalidade no ticket tracker, considere estes pontos:
\nVerifique se alguém já relatou o bug ou solicitou sua funcionalidade fazendo consultas customizadas no rastreador de tickets
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.
Relatos de bugs bem escritos são incrivelmente úteis. Porém, existe uma certa quantidade de sobrecarga envolvida em trabalhar com qualquer sistema de rastreamento de bugs de modo que a sua ajuda em manter nosso rastreador de tickets o mais eficiente possível é muito apreciada. Em particular:
\nLeia a FAQ para saber se o seu problema não é uma questão recorrente.
Do ask on Django Forum or the Django Discord server first if\nyou’re not sure if what you’re seeing is a bug.
Do write complete, reproducible, specific bug reports. You must\ninclude a clear, concise description of the problem, and a set of\ninstructions for replicating it. Add as much debug information as you can:\ncode snippets, test cases, exception backtraces, screenshots, etc. A nice\nsmall test case is the best way to report a bug, as it gives us a\nhelpful way to confirm the bug quickly.
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.
Para entender o ciclo de vida do seu ticket uma vez que você o tenha criado, veja Triagem de tickets.
\nSe a sua nova funcionalidade ou bug tem a ver com qualquer coisa visual, existem mais algumas regras para seguir:
\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.
Se o problema for muito difícil de mostrar usando uma imagem, considere capturar um breve screencast. Se o seu software permitir isso, capture somente a área relevante da tela.
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.
Screencasts não absolvem você de outras boas práticas ao reportar um bug. Certifique-se de incluir URLs, trechos de código, e instruções passo-a-passo sobre como reproduzir o comportamento exibido nas screenshots.
Certifique-se de incluir a tag UI/UX no ticket para que outras partes interessadas no problema possam encontrá-lo.
Nós estamos sempre tentando deixar o Django melhor, e as suas solicitações por novas funcionalidades são uma peça chave nesse processo. Aqui vão algumas dicas sobre como fazer uma solicitação de forma eficiente.
\nMake sure the feature actually 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.
First request the feature on the Django Forum, not in the ticket tracker.\nIt’ll get read more closely and reach a larger audience. This is even more\nimportant for large-scale feature requests. We like to discuss any big\nchanges to Django’s core before actually working on them.
Descreva claramente e de forma concisa qual é a funcionalidade que você não encontrou e como você gostaria que ela fosse implementada. Se possível inclua códigos como exemplos (código que não funciona é válido).
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.
If there’s a consensus agreement on the feature, then it’s appropriate to\ncreate a ticket. Include a link to the discussion in the ticket description.
\nAs with most open-source projects, code talks. If you are willing to write the\ncode for the feature yourself or, even better, if you’ve already written it,\nit’s much more likely to be accepted. Fork Django on GitHub, create a feature\nbranch, and show us your work!
\nVeja também: Documentando novas funcionalidades.
\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 strive for a rough consensus. To that end, we’ll often\nhave informal votes on the Django Forum about a feature. In these votes we\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: “Eu adorei a ideia e estou fortemente comprometido com ela.”
+0: “Por mim OK.”
-0: “Não me animou, mas eu não vou ficar no caminho.”
-1: “Eu definitivamente não gostei e ficaria realmente chateado de ver essa ideia virando realidade.”
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.
\nHowever, consensus is not always possible. If consensus cannot be reached, or\nif the discussion toward a consensus fizzles out without a concrete decision,\nthe decision may be deferred to the steering council.
\nInternally, the steering council will use the same voting mechanism. A\nproposition will be considered carried if:
\nThere are at least three “+1” votes from members of the steering council.
There is no “-1” vote from any member of the steering council.
Votos devem ser submetidos dentro de uma semana.
\nSince this process allows any steering council member to veto a proposal, a\n“-1” vote should be accompanied by an explanation of what it would take to\nconvert that “-1” into at least a “+0”.
\nVotes on technical matters should be announced and held in public on the\nDjango Forum.
\n