Page History

...

•  Create a ticket in the DSpace Issue Tracker (describe your contribution, how to use it, and perhaps some use cases)
•  Submit your code. It is HIGHLY recommended to do so via a GitHub Pull Request (see Development with Git), which references your newly created ticket by number (e.g. DS-1234).  If you are uncomfortable with Git/GitHub, you may instead attach a patch to the ticket you created. But, be warned that patch files may not receive a thorough review until we find a volunteer to create a Pull Request on your behalf. (In the end, we need a Pull Request for all code changes – so if you can create it, that speeds up the review process)
  
•  Review your own code. Does it follow our Contribution Checklist? Does it need Documentation? If you are using any third party tools/APIs, do they all have an acceptable Open Source License (see Licensing of Contributions). The Committers will also be reviewing these aspects of your code, and will also let you know if they notice any issues.
  
•  Respond to feedback. If the Committers ask questions or make suggestions for changes, please try to be responsive. The Committers are all volunteers and are trying to help as best we can, but the process moves more quickly if you can try to be responsive as well.
•  Help rework/update code as needed. If suggestions for changes are made, if you can rework the code, it speeds up the process. If you submitted your code as a Pull Request, you can just quickly add changes/updates to the branch linked to from your Pull Request.
•  Ask questions. If there is a long delay in the Committers responding, or if you aren't sure of the status of your workcontribution, please ask. We'd be glad to explain whether the delay is just cause because we are all busy, or if there's something else we are waiting on.
  

...