x

Main chapters

  1. LimeSurvey Cloud vs LimeSurvey CE
  2. LimeSurvey Cloud - Quick start guide
  3. LimeSurvey CE - Installation
  4. How to design a good survey (Guide)
  5. Getting started
  6. LimeSurvey configuration
  7. Introduction - Surveys
  8. View survey settings
  9. View survey menu
  10. View survey structure
  11. Introduction - Questions
  12. Introduction - Question Groups
  13. Introduction - Surveys - Management
  14. Survey toolbar options
  15. Multilingual survey
  16. Quick start guide - ExpressionScript
  17. Advanced features
  18. General FAQ
  19. Troubleshooting
  20. Workarounds
  21. License
  22. Version change log
  23. Plugins - Advanced
 Actions

How to contribute new features

From LimeSurvey Manual

Revision as of 16:20, 24 September 2010 by Mazi (talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Contribution process

We are always encouraging users to contribute new features they have developed. If you are planning to code a stunning new feature and you want it to be implemented at the core so you are future save when updating later, please proceed as follows:

  1. Use the latest SVN version for your development
  2. Open a new ticket at our bugtracker at the "user patches" section with a speaking title.
  3. Describe your feature as detailed as possible and tell us about the implementation details (what code you want to add, which files you are planning to change, which GUI parts have to be extended, ...)
  4. We will then assign the ticket to one of our developers and discuss your approach. It's important to tell us about your plans before you start coding because otherwise you might take the wrong way when implementing new features so we might have to say "Sorry, we can't take that one (because of security problems or what so ever)".
  5. Once implementation details were discussed just start coding and create a .diff patch afterwards. Attach this patch to the bugtracker ticket and ask for a developer to review your coding.
  6. There might be some further discussions about implementation details but once this was solved, your feature will be available in the next new version.

Useful links