Page History

...

• Please be sure to share your plans with the DSpace community on the 'dspace-devel' list (or via one of the weekly Developer MeetingMeetings) before embarking on any sizable development effort. This will ensure you achieve your goals in a way that is consistent with the DSpace architecture and plans of the rest of the community. This will minimize the chances of a scenario where you have invested a large amount of time and effort into a body of code that does not fit in with the DSpace architecture or the consensus of the community, meaning that you need to spend further time refactoring your code or worse, 'forking' the code.
• Develop incrementally; try and implement and contribute a basic form of your feature as soon as possible, rather than aiming to implement a complete and 'polished' solution. This will help ensure you're on the right track with regards to the rest of the DSpace community and platform. The sooner your code is part of the core code base, the less time you will have to spend 'chasing' the main code base, i.e. keeping your changes up-to-date with that core code base.
• Obtain the DSpace code using Subversion. This will make code management much easier. It's very simple to do; see Guide to Developing with DSpace.
• Read ContributionGuidelines to ensure you are following DSpace conventions. This page also gives you a sense of the DSpace Code Approval processes.

...