Note:

If you want to create a new page for developers, you should create it on the Moodle Developer Resource site.

Contracting: Difference between revisions

From MoodleDocs
No edit summary
 
 
(3 intermediate revisions by one other user not shown)
Line 1: Line 1:
If you really need some changes made to Moodle you have a few options.
If you really need some changes made to Moodle and can't do the work yourself you have a few ways to pay for it.


===Moodle.com===
===Moodle.com===


One of the major sources of income for the Moodle project is contracting work done by core Moodle developers via Moodle.com.  See http://moodle.com/development for details about getting a quote for work done.  Work done this way has a very high chance of being included in Moodle core distribution, and will thus be maintained into the future.  Not only that, but you are directly supporting the Moodle project in the best way!
One of the major sources of income for the Moodle project is contracting work done by core Moodle developers via Moodle.com.  See http://moodle.com/development for details about getting a quote for work done.  Work done this way has a very high chance of being included in Moodle core distribution to benefit the community, and will thus be maintained into the future.  Not only that, but you are directly supporting the Moodle project in the best possible way!
 
===Module maintainers===
 
If your changes involve improvements to an existing module (eg Hotpot, Quiz, Assignments) etc, then think about contracting that developer directly to work on those features.  Many of the maintainers work for free on their modules, and really appreciate the chance to get paid for it.  And, again, the code is very likely to be included in future versions of Moodle for all to use and help maintain.
 
===Your own developers===
 
Possibly you have your own development team, or have found someone else with the skills to develop PHP code.  If you do develop extensions to Moodle this way, please try as hard as possible to implement the changes as a module (Moodle has about 20 different types of plugins).  Ask for design advice on moodle.org if you need it, and think about publishing the module on the [http://moodle.org/modules Moodle Modules] listing.  As a self-contained module your work has the best chance of remaining compatible with future Moodle releases.
 
===Your own time===
 
Even if you can't write code, there's a lot you can do in the community to help get things done.  Write a detailed functional specification, test new features, create mock screenshots of the final product, engage the community in discussions about the idea, file feature requests in the [http://tracker.moodle.org/ Moodle Tracker].  Things like this maximise the possibility of finding other volunteers to get that feature written.

Latest revision as of 03:50, 3 November 2006

If you really need some changes made to Moodle and can't do the work yourself you have a few ways to pay for it.

Moodle.com

One of the major sources of income for the Moodle project is contracting work done by core Moodle developers via Moodle.com. See http://moodle.com/development for details about getting a quote for work done. Work done this way has a very high chance of being included in Moodle core distribution to benefit the community, and will thus be maintained into the future. Not only that, but you are directly supporting the Moodle project in the best possible way!

Module maintainers

If your changes involve improvements to an existing module (eg Hotpot, Quiz, Assignments) etc, then think about contracting that developer directly to work on those features. Many of the maintainers work for free on their modules, and really appreciate the chance to get paid for it. And, again, the code is very likely to be included in future versions of Moodle for all to use and help maintain.

Your own developers

Possibly you have your own development team, or have found someone else with the skills to develop PHP code. If you do develop extensions to Moodle this way, please try as hard as possible to implement the changes as a module (Moodle has about 20 different types of plugins). Ask for design advice on moodle.org if you need it, and think about publishing the module on the Moodle Modules listing. As a self-contained module your work has the best chance of remaining compatible with future Moodle releases.

Your own time

Even if you can't write code, there's a lot you can do in the community to help get things done. Write a detailed functional specification, test new features, create mock screenshots of the final product, engage the community in discussions about the idea, file feature requests in the Moodle Tracker. Things like this maximise the possibility of finding other volunteers to get that feature written.