{"title":"Submitting contributions","version":"5.2","locale":"ko","docname":"internals/contributing/writing-code/submitting-patches","url":"/ko/5.2/internals/contributing/writing-code/submitting-patches/","canonical":"https://djangodocs.dev/ko/5.2/internals/contributing/writing-code/submitting-patches/","summary":"We’re always grateful for contributions to Django’s code. Indeed, bug reports with associated contributions will get fixed far more quickly than those…","html":"

Submitting contributionsLink to this heading#

\n

We’re always grateful for contributions to Django’s code. Indeed, bug reports\nwith associated contributions will get fixed far more quickly than those\nwithout a solution.

\n
\n

오타 수정 및 사소한 문서 변경 사항입니다.Link to this heading#

\n

설명서에서 단어를 변경하는 등 매우 사소한 문제를 수정하는 경우 패치를 제공하는 기본 방법은 Trac 티켓 없이 GitHub 풀 요청을 사용하는 것입니다.

\n

pull 요청을 사용하는 방법에 대한 자세한 내용은 :doc:’working-with-git’을 참조하십시오.

\n
\n
\n

티켓을 “청구하기”Link to this heading#

\n

전 세계에 수백 명의 기여자가 있는 오픈소스 프로젝트에서는 작업이 중복되지 않고 기여자가 최대한 효과적으로 작업할 수 있도록 커뮤니케이션을 효율적으로 관리하는 것이 중요합니다.

\n

따라서 우리의 정책은 특정 버그나 기능이 작업 중임을 다른 개발자에게 알리기 위해 티켓을 “청구”하는 기여자를 위한 것입니다.

\n

원하는 기여가 확인되었고 이를 수정할 수 있는 능력이 있는 경우(코딩 능력, Django 내부 지식 및 시간 가용성으로 측정됨) 다음 단계를 수행하여 해당 기여를 청구합니다.

\n\n\n
\n

티켓 청구인의 책임입니다.Link to this heading#

\n

티켓을 수령한 후에는 적시에 해당 티켓을 처리해야 할 책임이 있습니다. 만약 여러분이 그것을 할 시간이 없다면, 그것을 청구하지 않거나, 애초에 청구하지 마세요!

\n

If there’s no sign of progress on a particular claimed ticket for a week or\ntwo, another developer may ask you to relinquish the ticket claim so that it’s\nno longer monopolized and somebody else can claim it.

\n

티켓을 수령했는데 코딩하는 데 오랜 시간(일 또는 몇 주)이 걸리는 경우 티켓에 댓글을 달아 모든 사용자를 최신 상태로 유지하십시오. 정기적인 업데이트를 제공하지 않고 진행 상황 보고서 요청에 응답하지 않으면 티켓에 대한 청구가 취소될 수 있습니다.

\n

항상 그렇듯이, 더 많은 의사소통이 덜 소통하는 것보다 더 낫습니다!

\n
\n
\n

어떤 표를 구해야 합니까?Link to this heading#

\n

어떤 경우에는 티켓을 청구하는 단계를 거치는 것이 지나치기도 합니다.

\n

In the case of small changes, such as typos in the documentation or small bugs\nthat will only take a few minutes to fix, you don’t need to jump through the\nhoops of claiming tickets. Submit your changes directly and you’re done!

\n

It is always acceptable, regardless whether someone has claimed it or not, to\nlink proposals to a ticket if you happen to have the changes ready.

\n
\n
\n
\n

Contribution styleLink to this heading#

\n

최소한 다음 요구 사항을 충족하는 기여가 있는지 확인하십시오.

\n\n

When you think your work is ready to be reviewed, send a GitHub pull\nrequest.\nIf you can’t send a pull request for some reason, you can also use patches in\nTrac. When using this style, follow these guidelines.

\n\n

작업 제출 방법과 상관없이 다음 단계를 따르십시오.

\n\n
\n
\n

Contributions which require community feedbackLink to this heading#

\n

A wider community discussion is required when a patch introduces new Django\nfunctionality and makes some sort of design decision. This is especially\nimportant if the approach involves a deprecation\nor introduces breaking changes.

\n

The following are different approaches for gaining feedback from the community.

\n
\n

The new feature ideas trackerLink to this heading#

\n

If you have an idea for a new feature, please create a new proposal (or join an\nexisting discussion) following the process for suggesting new features. You should explain the need for the change, go into\ndetails of the approach and discuss alternatives.

\n
\n
\n

The Django ForumLink to this heading#

\n

You can propose a change (that is not a new feature idea) on the\nDjango Forum. You should explain the need for the change, go into details of\nthe approach and discuss alternatives.

\n

Please include a link to such discussions in your contributions.

\n
\n
\n

Third party packageLink to this heading#

\n

Django does not accept experimental features. All features must follow our\ndeprecation policy. Hence, it can\ntake months or years for Django to iterate on an API design.

\n

If you need user feedback on a public interface, it is better to create a\nthird-party package first. You can iterate on the public API much faster, while\nalso validating the need for the feature.

\n

Once this package becomes stable and there are clear benefits of incorporating\naspects into Django core, the next step is to propose its inclusion by\nfollowing the process for suggesting new features.

\n
\n
\n

Django Enhancement Proposal (DEP)Link to this heading#

\n

Similar to Python’s PEPs, Django has Django Enhancement Proposals or DEPs. A\nDEP is a design document which provides information to the Django community, or\ndescribes a new feature or process for Django. They provide concise technical\nspecifications of features, along with rationales. DEPs are also the primary\nmechanism for proposing and collecting community input on major new features.

\n

Before considering writing a DEP, it is recommended to first open a discussion\nfollowing the process for suggesting new features.\nThis allows the community to provide feedback and helps refine the proposal.\nOnce the DEP is ready the Steering Council votes on\nwhether to accept it.

\n

Some examples of DEPs that have been approved and fully implemented:

\n\n
\n
\n
\n

기능을 사용Link to this heading#

\n

Django의 코드가 더 이상 사용되지 않는 몇 가지 이유가 있습니다.

\n\n

:ref:’감가상각 정책’에서 설명한 것처럼 기능을 사용하지 않는 Django의 첫 번째 릴리스(‘’A’)입니다.B’’)는 사용되지 않는 기능이 호출될 때 “제거된 장고 XX 경고”(여기서 XX는 기능이 제거될 장고 버전)를 발생시켜야 합니다. 테스트 범위가 양호하다고 가정하면, 경고가 활성화된 상태에서 :ref:’test Suite’를 실행하면 이러한 경고가 오류로 변환됩니다. ‘’’와 - 와 runtests.py’’’’입니다. 따라서 “RemovedInDjangoXXWarning”을 추가할 때 테스트를 실행할 때 발생하는 경고를 제거하거나 침묵시켜야 합니다.

\n

첫 번째 단계는 Django가 사용하지 않는 동작의 사용을 제거하는 것입니다. 그런 다음 테스트 또는 클래스 수준에서 “ignore_warnings” 데코레이터를 사용하여 권장되지 않는 동작을 실제로 테스트하는 테스트에서 경고를 음소거할 수 있습니다.

\n
    \n

  1. 특정 테스트의 경우:

    \n
    Code
    from django.test import ignore_warnings\nfrom django.utils.deprecation import RemovedInDjangoXXWarning\n\n\n@ignore_warnings(category=RemovedInDjangoXXWarning)\ndef test_foo(self): ...\n
    \n
    2. \n

  2. 전체 테스트 사례의 경우:

    \n
    Code
    from django.test import ignore_warnings\nfrom django.utils.deprecation import RemovedInDjangoXXWarning\n\n\n@ignore_warnings(category=RemovedInDjangoXXWarning)\nclass MyDeprecatedTests(unittest.TestCase): ...\n
    \n
    3. \n
\n

You should also add a test for the deprecation warning:

\n
Code
from django.utils.deprecation import RemovedInDjangoXXWarning\n\n\ndef test_foo_deprecation_warning(self):\n    msg = "Expected deprecation message"\n    with self.assertWarnsMessage(RemovedInDjangoXXWarning, msg) as ctx:\n        # invoke deprecated behavior\n        ...\n    self.assertEqual(ctx.filename, __file__)\n
\n

It’s important to include a RemovedInDjangoXXWarning comment above code\nwhich has no warning reference, but will need to be changed or removed when the\ndeprecation ends. This could include hooks which have been added to keep the\nprevious behavior, or standalone items that are unnecessary or unused when the\ndeprecation ends. For example:

\n
Code
import warnings\nfrom django.utils.deprecation import RemovedInDjangoXXWarning\n\n\n# RemovedInDjangoXXWarning.\ndef old_private_helper():\n    # Helper function that is only used in foo().\n    pass\n\n\ndef foo():\n    warnings.warn(\n        "foo() is deprecated.",\n        category=RemovedInDjangoXXWarning,\n        stacklevel=2,\n    )\n    old_private_helper()\n    ...\n
\n

마지막으로 Django의 문서에는 다음과 같은 몇 가지 업데이트가 있습니다.

\n
    \n

  1. 기존 기능이 문서화된 경우 ‘’를 사용하여 문서에서 사용되지 않는 것으로 표시합니다. 사용되지 않음: A입니다.B’ 주석입니다. 해당되는 경우 간단한 설명과 업그레이드 경로에 대한 참고 사항을 포함합니다.

    2. \n

  2. 권장되지 않는 동작에 대한 설명과 적용 가능한 업그레이드 경로가 있다면 현재 릴리스 정보(‘’docs/releases/A’.B.txt”)를 “A.B에서 사용되지 않는 기능입니다” 헤드에 추가합니다.

    3. \n

  3. 제거될 코드를 설명하는 항목을 해당 버전의 사용 중지 타임라인(docs/internals/deprecation.txt)에 추가합니다.

    4. \n
\n

이 단계를 완료하면 더 이상 사용되지 않습니다. 각 :term:’feature release’에서 새 버전과 일치하는 모든 “RemovedInDjangoXXWarning”s가 제거된다.

\n
\n
\n

Testing with a Django projectLink to this heading#

\n

It’s important to test local changes using a Django project. This allows\nensuring that the changes behave as expected in a real environment, especially\nfor user-facing features such as templates, forms, or the admin.

\n

To do this:

\n
    \n

  1. Create a virtual environment and install the cloned copy of Django in\neditable mode.

    2. \n

  2. Set up a Django project outside the source tree (you can use the first\npart of the tutorial for guidance).

    3. \n
\n

With this setup, any changes made to the Django checkout will take effect\nimmediately in the test project, allowing manual testing of contributions\nagainst a new or existing app.

\n
\n
\n

JavaScript contributionsLink to this heading#

\n

For information on JavaScript contributions, see the JavaScript 패치\ndocumentation.

\n
\n
\n

Optimization patchesLink to this heading#

\n

Patches aiming to deliver a performance improvement should provide benchmarks\nshowing the before and after impact of the patch and sharing the commands for\nreviewers to reproduce.

\n
\n

django-asv benchmarksLink to this heading#

\n

django-asv monitors the performance of Django code over time. These\nbenchmarks can be run on a pull request by labeling the pull request with\nbenchmark. Adding to these benchmarks is highly encouraged.

\n
\n
\n
\n

Contribution checklistLink to this heading#

\n

Use this checklist to review a pull request. If this contribution would not be\nconsidered trivial, first ensure it has an accepted\nticket before proceeding with the review.

\n

If the pull request passes all the criteria below and is not your own, please\nset the “Triage Stage” on the corresponding Trac ticket to “Ready for checkin”.\nIf you’ve left comments for improvement on the pull request, please tick the\nappropriate flags on the Trac ticket based on the results of your review:\n“Patch needs improvement”, “Needs documentation”, and/or “Needs tests”. As time\nand interest permits, mergers do final reviews of “Ready for checkin” tickets\nand will either commit the changes or bump it back to “Accepted” if further\nwork needs to be done.

\n

If you’re looking to become a member of the triage & review team, doing\nthorough reviews of contributions is a great way to earn trust.

\n

Looking for a patch to review? Check out the “Patches needing review” section\nof the Django Development Dashboard.

\n

Looking to get your pull request reviewed? Ensure the Trac flags on the ticket\nare set so that the ticket appears in that queue.

\n
\n

문서Link to this heading#

\n\n
\n
\n

버그Link to this heading#

\n\n
\n
\n

새로운 특징들Link to this heading#

\n\n
\n
\n

기능을 사용Link to this heading#

\n

:ref:’decrating-a-feature’ 가이드를 참조하십시오.

\n
\n
\n

모든 코드가 변경됩니다.Link to this heading#

\n\n
\n
\n

모든 티켓들Link to this heading#

\n\n
\n
","rootId":"submitting-contributions","toc":[{"title":"오타 수정 및 사소한 문서 변경 사항입니다.","anchor":"typo-fixes-and-trivial-documentation-changes","children":[]},{"title":"티켓을 “청구하기”","anchor":"claiming-tickets","children":[{"title":"티켓 청구인의 책임입니다.","anchor":"ticket-claimers-responsibility","children":[]},{"title":"어떤 표를 구해야 합니까?","anchor":"which-tickets-should-be-claimed","children":[]}]},{"title":"Contribution style","anchor":"contribution-style","children":[]},{"title":"Contributions which require community feedback","anchor":"contributions-which-require-community-feedback","children":[{"title":"The new feature ideas tracker","anchor":"the-new-feature-ideas-tracker","children":[]},{"title":"The Django Forum","anchor":"the-django-forum","children":[]},{"title":"Third party package","anchor":"third-party-package","children":[]},{"title":"Django Enhancement Proposal (DEP)","anchor":"django-enhancement-proposal-dep","children":[]}]},{"title":"기능을 사용","anchor":"deprecating-a-feature","children":[]},{"title":"Testing with a Django project","anchor":"testing-with-a-django-project","children":[]},{"title":"JavaScript contributions","anchor":"javascript-contributions","children":[]},{"title":"Optimization patches","anchor":"optimization-patches","children":[{"title":"django-asv benchmarks","anchor":"django-asv-benchmarks","children":[]}]},{"title":"Contribution checklist","anchor":"contribution-checklist","children":[{"title":"문서","anchor":"documentation","children":[]},{"title":"버그","anchor":"bugs","children":[]},{"title":"새로운 특징들","anchor":"new-features","children":[]},{"title":"기능을 사용","anchor":"id3","children":[]},{"title":"모든 코드가 변경됩니다.","anchor":"all-code-changes","children":[]},{"title":"모든 티켓들","anchor":"all-tickets","children":[]}]}],"breadcrumbs":[{"docname":"internals/index","title":"Django internals","url":"/ko/5.2/internals/"},{"docname":"internals/contributing/index","title":"장고에 기여하기","url":"/ko/5.2/internals/contributing/"},{"docname":"internals/contributing/writing-code/index","title":"Contributing code","url":"/ko/5.2/internals/contributing/writing-code/"}],"prev":{"docname":"internals/contributing/writing-code/index","title":"Contributing code","url":"/ko/5.2/internals/contributing/writing-code/"},"next":{"docname":"internals/contributing/writing-code/unit-tests","title":"유닛 테스트","url":"/ko/5.2/internals/contributing/writing-code/unit-tests/"},"formats":{"html":"/ko/5.2/internals/contributing/writing-code/submitting-patches/","markdown":"/ko/5.2/internals/contributing/writing-code/submitting-patches.md","json":"/ko/5.2/internals/contributing/writing-code/submitting-patches.json"},"source":"https://github.com/django/django/blob/stable/5.2.x/docs/internals/contributing/writing-code/submitting-patches.txt","official":"https://docs.djangoproject.com/ko/5.2/internals/contributing/writing-code/submitting-patches/","inVersions":["6.1","6.0","5.2","5.1","5.0","4.2","4.1","4.0","3.2","3.1","3.0","2.2","2.1","2.0","1.11"],"inLocales":["en","sv","zh-hans","ga","fr","ja","id","it","pt-br","ko","es","el","pl"]}