Working with the Community - Revision history

Germanvaleroelizondo: Added see also * Contributing to Moodle

2015-02-09T17:03:11Z

← Older revision		Revision as of 17:03, 9 February 2015
Line 120:		Line 120:
	* [[How to create a patch]].		* [[How to create a patch]].
	* [http://www.linux-mips.org/wiki/The_perfect_patch The perfect patch] as seen by the Linux kernel developers		* [http://www.linux-mips.org/wiki/The_perfect_patch The perfect patch] as seen by the Linux kernel developers
			* [[Contributing to Moodle]]

Poltawski: Moodle is accepting of everyone. But I don't think this statement should stay here, because it implies that using email/forums etc prevents discrimination. It does not. [I also have other problems with this statement being here]

2012-11-14T02:24:25Z

Moodle is accepting of everyone. But I don't think this statement should stay here, because it implies that using email/forums etc prevents discrimination. It does not. [I also have other problems with this statement being here]

← Older revision		Revision as of 02:24, 14 November 2012
Line 62:		Line 62:
	Another way the Moodle community is different than most traditional		Another way the Moodle community is different than most traditional
	software engineering work environments is the faceless nature of		software engineering work environments is the faceless nature of
	interaction~~. One benefit of using email, forums and the tracker as primary forms of~~		interaction.
	~~communication is the lack of discrimination based on gender or race.~~
	~~The Moodle work environment is accepting of women and minorities~~.

	The language barrier can cause problems for some people who are not		The language barrier can cause problems for some people who are not

Deraadt: /* Consider contributing your work as a Plugin */

2012-02-17T01:13:37Z

Consider contributing your work as a Plugin

← Older revision		Revision as of 01:13, 17 February 2012
Line 114:		Line 114:
	must be justified as being needed and useful.		must be justified as being needed and useful.

	==Consider contributing your work as a ~~Plugin~~==		==Consider contributing your work as a plugin==

	Help with improving core Moodle code ~~and standard plugins~~ is very welcome, however Moodle is designed to be modular, so ~~the change~~ you ~~might want to share might be possible in~~ a ~~single~~ Plugin. Plugins are shared through the [http://moodle.org/plugins Plugins repository]. There are many different [[Plugins\|kinds of plugins]] so check out the [[Guidelines_for_contributed_code\|guidelines for contributing]].		Help with improving core Moodle code is very welcome, however Moodle is designed to be modular, so you should consider sharing your idea as a Plugin. Plugins are shared through the [http://moodle.org/plugins Plugins repository]. There are many different [[Plugins\|kinds of plugins]], so check out the [[Guidelines_for_contributed_code\|guidelines for contributing]].

	==See also==		==See also==

Deraadt: A few updates and addition of contrib section

2012-02-17T01:09:03Z

A few updates and addition of contrib section

← Older revision		Revision as of 01:09, 17 February 2012
Line 1:		Line 1:
			So you'd like to contribute to Moodle? If you do, then thank you very much. The community appreciates your efforts.

			Here is a guide to help you work with the Moodle community.

			==What to expect==

	The goal of the Moodle community is to provide the best possible LMS there is. When you submit a patch (or new module, plugin or filter) for acceptance, it will be reviewed on its technical and educational merits and those alone. So, what should you be expecting?		The goal of the Moodle community is to provide the best possible LMS there is. When you submit a patch (or new module, plugin or filter) for acceptance, it will be reviewed on its technical and educational merits and those alone. So, what should you be expecting?

Line 37:		Line 43:
	* "This deletes 2000 lines of code."		* "This deletes 2000 lines of code."
	* "Here is a patch that explains what I am trying to describe."		* "Here is a patch that explains what I am trying to describe."
	* "I tested it on 5 different databases..."		* "I tested it on 4 different databases..."
	* "Here is a series of small patches that..."		* "Here is a series of small patches that..."
	* "This increases performance on typical machines..."		* "This increases performance on typical machines..."

	'''Bad''' things you should avoid saying:		'''Bad''' things you should avoid saying:
	* "This educational theory supports my use model, ~~even if~~ I ~~didn't test~~ it ~~with students~~"		* "This educational theory supports my use model, I feel it in my bones."
	* "We did it this way in WebCT/Blackboard, so therefore it must ~~begood~~..."		* "We did it this way in WebCT/Blackboard, so therefore it must be good..."
	* "I've being doing this for 20 years, so..."		* "I've being doing this for 20 years, so..."
	* "It makes this proprietary benchmark go faster"		* "It makes this proprietary benchmark go faster"
Line 56:		Line 62:
	Another way the Moodle community is different than most traditional		Another way the Moodle community is different than most traditional
	software engineering work environments is the faceless nature of		software engineering work environments is the faceless nature of
	interaction. One benefit of using email and ~~forums~~ as ~~the~~ primary forms of		interaction. One benefit of using email, forums and the tracker as primary forms of
	communication is the lack of discrimination based on gender or race.		communication is the lack of discrimination based on gender or race.
	The Moodle work environment is accepting of women and minorities		The Moodle work environment is accepting of women and minorities.
	~~because all you are is an email address. The international aspect also~~
	~~helps to level the playing field because you can't guess gender based on~~
	~~a person's name. A man may be named Andrea and a woman may be named Pat~~.

	The language barrier can cause problems for some people who are not		The language barrier can cause problems for some people who are not
	comfortable with English. A good grasp of the language can be needed in		comfortable with English. A good grasp of the language can be needed in
	order to get ideas across properly on forums, so it is		order to get ideas across properly on forums and in the tracker, so it is
	recommended that you check your ~~emails~~ to make sure ~~they make~~ sense in		recommended that you check your text to make sure it makes sense in
	English before sending ~~them~~.		English before sending.

	==Consider asking or discussing your proposal first==		==Consider asking or discussing your proposal first==
Line 91:		Line 94:
	The reasons for breaking things up are the following:		The reasons for breaking things up are the following:

	# Small patches increase the likelihood that your patches will be applied, since they don't take much time or effort to verify for correctness. A 5 line patch can be applied by a maintainer with barely a second glance. However, a 500 line patch may take hours to review for correctness (the time it takes is exponentially proportional to the size of the patch~~, or something~~). Small patches also make it very easy to debug when something goes wrong. It's much easier to back out patches one by one than it is to dissect a very large patch after it's been applied (and broken something).		# Small patches increase the likelihood that your patches will be applied, since they don't take much time or effort to verify for correctness. A 5 line patch can be applied by a maintainer with barely a second glance. However, a 500 line patch may take hours to review for correctness (the time it takes can be exponentially proportional to the size of the patch).
			# Small patches also make it very easy to debug when something goes wrong. It's much easier to back out patches one by one than it is to dissect a very large patch after it's been applied (and broken something).
	# It's important not only to send small patches, but also to rewrite and simplify (or simply re-order) patches before submitting them.		# It's important not only to send small patches, but also to rewrite and simplify (or simply re-order) patches before submitting them.

Line 109:		Line 113:
	the Moodle community know why they should add this change. New features		the Moodle community know why they should add this change. New features
	must be justified as being needed and useful.		must be justified as being needed and useful.

			==Consider contributing your work as a Plugin==

			Help with improving core Moodle code and standard plugins is very welcome, however Moodle is designed to be modular, so the change you might want to share might be possible in a single Plugin. Plugins are shared through the [http://moodle.org/plugins Plugins repository]. There are many different [[Plugins\|kinds of plugins]] so check out the [[Guidelines_for_contributed_code\|guidelines for contributing]].

	==See also==		==See also==

Deraadt: /* See also */

2011-06-10T08:14:01Z

Martinlanghoff: /* See also */

2008-10-14T06:13:37Z

Martinlanghoff: /* Differences between the Moodle community and corporate structures */

2008-03-21T16:34:33Z

Differences between the Moodle community and corporate structures

← Older revision		Revision as of 16:34, 21 March 2008
Line 33:		Line 33:

	'''Good''' things to say regarding your proposed changes:		'''Good''' things to say regarding your proposed changes:
			* "This works great with 9-year olds for learning X."
	* "This solves multiple problems."		* "This solves multiple problems."
	* "This deletes 2000 lines of code."		* "This deletes 2000 lines of code."
Line 41:		Line 42:

	'''Bad''' things you should avoid saying:		'''Bad''' things you should avoid saying:
			* "This educational theory supports my use model, even if I didn't test it with students"
	* "We did it this way in WebCT/Blackboard, so therefore it must begood..."		* "We did it this way in WebCT/Blackboard, so therefore it must begood..."
	* "I've being doing this for 20 years, so..."		* "I've being doing this for 20 years, so..."

Martinlanghoff at 16:32, 21 March 2008

2008-03-21T16:32:31Z

← Older revision		Revision as of 16:32, 21 March 2008
Line 1:		Line 1:
	The goal of the Moodle community is to provide the best possible LMS there is. When you submit a patch (or new module, plugin or filter) for acceptance, it will be reviewed on its technical merits and those alone. So, what should you be expecting?		The goal of the Moodle community is to provide the best possible LMS there is. When you submit a patch (or new module, plugin or filter) for acceptance, it will be reviewed on its technical and educational merits and those alone. So, what should you be expecting?

	* criticism		* criticism

TimHunt: /* See also */

2007-09-14T15:43:30Z

TimHunt at 12:51, 25 June 2007

2007-06-25T12:51:29Z

← Older revision		Revision as of 12:51, 25 June 2007
Line 107:		Line 107:
	the Moodle community know why they should add this change. New features		the Moodle community know why they should add this change. New features
	must be justified as being needed and useful.		must be justified as being needed and useful.

			==See also==

			* [[How to create a patch]].

	[[Category:Working with the Community]]		[[Category:Working with the Community]]

← Older revision		Revision as of 08:14, 10 June 2011
Line 114:		Line 114:
	* [[How to create a patch]].		* [[How to create a patch]].
	* [http://www.linux-mips.org/wiki/The_perfect_patch The perfect patch] as seen by the Linux kernel developers		* [http://www.linux-mips.org/wiki/The_perfect_patch The perfect patch] as seen by the Linux kernel developers
	~~[[Category:Working with the Community]]~~

← Older revision		Revision as of 06:13, 14 October 2008
Line 113:		Line 113:

	* [[How to create a patch]].		* [[How to create a patch]].
	* [http://www.~~zip.com~~.~~au/~akpm~~/~~linux~~/~~patches/stuff/tpp.txt~~ The perfect patch]		* [http://www.linux-mips.org/wiki/The_perfect_patch The perfect patch] as seen by the Linux kernel developers
	[[Category:Working with the Community]]		[[Category:Working with the Community]]

← Older revision		Revision as of 15:43, 14 September 2007
Line 111:		Line 111:

	* [[How to create a patch]].		* [[How to create a patch]].
			* [http://www.zip.com.au/~akpm/linux/patches/stuff/tpp.txt The perfect patch]
	[[Category:Working with the Community]]		[[Category:Working with the Community]]