Versions Compared

Old Version 31

changes.mady.by.user Tim Donohue

Saved on

compared with

New Version 32

changes.mady.by.user Tim Donohue

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

First, you must make your code available to the DSpace Committers Group for review. This can be in the form of a patch (usually posted to our DSpace Issue Tracking SystemTracker). Alternatively, you may provide us with downloadable version or read-only access to your SVN or CVS code repository. In either case, you should create a new Issue in our DSpace Issue Tracker. This ensures that the DSpace Developers are notified of your contribution, and acts as a place for us to comment on the work or make suggestions for improvements.

Info
titleCode Standards

Code contributions that meet certain standards are much more likely to be accepted immediately. For a list of our current standards, please read through the Code Contribution Standards section below.

Info
titleOur recommended way to make code available

The best way to inform us of your code contribution is by entering a new issue into our DSpace Issue Tracking SystemTracker. You should upload any files to that new issue, or provide links to where the code can be obtained. We will then review & comment on your code in that same area (and it will automatically send you an email with our comments).
For Larger Initiatives: If you are building out a much larger project, we will also gladly provide you with a space in our DSpace SVN Sandbox to develop and/or share your work. Just ask us!

...