Make sure that you have written unit tests and docstrings for all code which has changed in your patch. For more details about what will be considered an acceptable patch, see the "Development Process" section below.

Attach the output of 'svn diff' to a ticket in the tracker and assign it the 'review' keyword so that a core developer will notice it and review it. Don't be discouraged if it is not immediately accepted! To keep the quality of Twisted high, almost all patches are rejected on their initial submission. Check back to see if the patch has been re-assigned to you for further work.

Finally, if your patch is good, it will be applied to trunk and included as part of the next release.

If you are interested in contributing to Twisted for the first time, consider working on an existing ticket rather than contributing a new feature. Fixes for existing problems or implementations of already-requested features will generally take priority over new ideas.

If you want to become a developer, it is important to understand that all your contributions (including those initial patches you send to the bug tracker) will have to be licenced under the ​MIT licence.