¿Es un nuevo colaborador y no sabe qué hacer? ¿Quiere ayudar pero simplemente no sabe cómo empezar? Esta sección es para usted.
Get up and running!
Si es un nuevo colaborador de Django, el :doc: tutorial /intro/contributing le dará una introducción a las herramientas y el flujo de trabajo.
This page contains more general advice on ways you can contribute to Django, and how to approach that.
Si usted está buscando una referencia sobre cómo hacer contribuciones, consulte la documentación Submitting contributions.
Start with these steps to discover Django’s development process.
Si un ‘ticket no revisado’ informa de un bug, intente reproducirlo. Si puede reproducirlo y si parece válido, indique que usted corroboró el bug y acepta el ticket. Asegúrese de que el ticket se archive en el área del componente correcto. Considere escribir un parche que añada una prueba para el comportamiento del bug, incluso si usted no corrige el bug. Vea más en :ref: ‘Cómo puedo ayudar con la clasificación’ para más información.
This will help you build familiarity with the codebase and processes. Mark the appropriate flags if a patch needs docs or tests. Look through the changes a patch makes, and keep an eye out for syntax that is incompatible with older but still supported versions of Python. Run the tests and make sure they pass. Where possible and relevant, try them out on a database other than SQLite. Leave comments and feedback!
Oftentimes the codebase will change between a patch being submitted and the time it gets reviewed. Make sure it still applies cleanly and functions as expected. Updating a patch is both useful and important! See more on Submitting contributions.
Django’s documentation is great but it can always be improved. Did you find a typo? Do you think that something should be clarified? Go ahead and suggest a documentation patch! See also the guide on Writing documentation.
Nota
La página de informes contiene enlaces a muchas consultas Trac útiles, incluyendo varias que son útiles para clasificar tickets y revisar parches como se sugirió anteriormente.
El código que escribe pertenece a usted o su jefe. Si su contribución es más de una o dos líneas de código, es necesario firmar el ALC. Consulte las “preguntas frecuentes sobre el Acuerdo de Licencia del Colaborador” para una explicación más detallada.
Como principiante en un proyecto grande, es fácil experimentar frustración. Estos son algunos consejos para hacer su trabajo en Django más útil y gratificante.
This should be something that you care about, that you are familiar with or that you want to learn about. You don’t already have to be an expert on the area you want to work on; you become an expert through your ongoing contributions to the code.
Trac isn’t an absolute; the context is just as important as the words. When reading Trac, you need to take into account who says things, and when they were said. Support for an idea two years ago doesn’t necessarily mean that the idea will still have support. You also need to pay attention to who hasn’t spoken – for example, if an experienced contributor hasn’t been recently involved in a discussion, then a ticket may not have the support required to get into Django.
Es más fácil recibir comentarios y sugerencias sobre un problema pequeño que sobre uno grande. Vea los tickets presa fácil.
This means getting someone else to confirm that a bug is real before you fix the issue, and ensuring that there’s consensus on a proposed feature before you go implementing it.
Sometimes it can be scary to put your opinion out to the world and say «this ticket is correct» or «this patch needs work», but it’s the only way the project moves forward. The contributions of the broad Django community ultimately have a much greater impact than that of any one person. We can’t do it without you!
If you’re really not certain if a ticket is ready, don’t mark it as such. Leave
a comment instead, letting others know your thoughts. If you’re mostly certain,
but not completely certain, you might also try asking on the
#contributing-getting-started
channel in the Django Discord server to
see if someone else can confirm your suspicions.
Concéntrese en uno o dos tickets, analícelos de principio a fin y repita el proceso. La táctica de la escopeta consistente en aceptar muchos tickets y dejar de lado algunos termina haciendo más daño que bien.
When we say «PEP 8, and must have docs and tests», we mean it. If a patch doesn’t have docs and tests, there had better be a good reason. Arguments like «I couldn’t find any existing tests of this feature» don’t carry much weight. While it may be true, that means you have the extra-important job of writing the very first tests for that feature, not that you get a pass from writing tests altogether.
It’s not always easy for your ticket or your patch to be reviewed quickly. This isn’t personal. There are a lot of tickets and pull requests to get through.
Keeping your patch up to date is important. Review the ticket on Trac to ensure that the Needs tests, Needs documentation, and Patch needs improvement flags are unchecked once you’ve addressed all review comments.
Remember that Django has an eight-month release cycle, so there’s plenty of time for your patch to be reviewed.
Finally, a well-timed reminder can help. See contributing code FAQ for ideas here.
may 07, 2025