How to join the LimeSurvey project team/en - Revision history

FuzzyBot: Updating to match new version of source page

2017-01-30T09:15:02Z

Updating to match new version of source page

← Older revision		Revision as of 11:15, 30 January 2017
Line 16:		Line 16:
	*Real life comes first - but give us a small notice if and for how long you will be gone.		*Real life comes first - but give us a small notice if and for how long you will be gone.
	*Developers come and go in an open source project - that is absolutely normal. However if you leave the project please give us a notice and tell us how far you are, what you did and if there are things still to do so that someone else can pick up your work.		*Developers come and go in an open source project - that is absolutely normal. However if you leave the project please give us a notice and tell us how far you are, what you did and if there are things still to do so that someone else can pick up your work.
	*Attend to the developers meeting which take place every ~~Monday~~ on 22:00 Berlin time on the channel #limesurvey-team on irc.freenode.org (ask Carsten Schmitz for the password - see below)		*Attend to the developers meeting which take place every Tuesday on 14:30 Berlin time in the channel #limesurvey-team on irc.freenode.org (ask Carsten Schmitz for the password - see below)

	==First steps==		==First steps==

FuzzyBot: Importing a new version from external source

2013-10-11T06:40:59Z

Importing a new version from external source

← Older revision		Revision as of 08:40, 11 October 2013
Line 39:		Line 39:

	To ensure this quality we are mentoring new developers using the following steps:		To ensure this quality we are mentoring new developers using the following steps:
	# At first we only assign a small tasks to the new developer. What task is assigned will be decided together with the new developer.		# At first we only assign small tasks to the new developer. What task is assigned will be decided together with the new developer.
	# The developer sends the code to the mentor for review.		# The developer sends the code to the mentor for review.
	# If the mentor is satisfied with the code quality the developer may commit the code to the repository.		# If the mentor is satisfied with the code quality the developer may commit the code to the repository.

FuzzyBot: Importando nueva versión desde fuente externa

2013-10-11T06:40:37Z

Importando nueva versión desde fuente externa

← Older revision		Revision as of 08:40, 11 October 2013
Line 34:		Line 34:
	==Additional information for new developers==		==Additional information for new developers==

	LimeSurvey contains ~~alot~~ of old and mess code - but by now we strictly pay attention to coding guidelines which are very important.		LimeSurvey contains a lot of old and mess code - but by now we strictly pay attention to coding guidelines which are very important.

	Coding Guidelines and Generic Code Implementation will help you and any developers working on your code at a later time by easier understanding your code and making it more modular.		Coding Guidelines and Generic Code Implementation will help you and any developers working on your code at a later time by easier understanding your code and making it more modular.

FuzzyBot: Bezig met het importeren van een nieuwe versie uit een externe bron

2013-09-04T11:18:25Z

Bezig met het importeren van een nieuwe versie uit een externe bron

← Older revision		Revision as of 13:18, 4 September 2013
Line 30:		Line 30:
	## Tell us in what area you would like to help (coding, patching, support etc.)		## Tell us in what area you would like to help (coding, patching, support etc.)
	# Carsten Schmitz will get back to you as soon as possible. He is a very nice guy and will give you an introduction and will provide more information on the next steps.		# Carsten Schmitz will get back to you as soon as possible. He is a very nice guy and will give you an introduction and will provide more information on the next steps.
	# Visit the [http://www.limesurvey.org/~~index.php~~/~~Live~~-~~Chat.html~~ official ~~Lime Survey~~ IRC Channel] and SAY HELLO TO US!<br />([irc://irc.freenode.net/limesurvey])		# Visit the [http://www.limesurvey.org/en/community-services/live-chat official LimeSurvey IRC Channel] and SAY HELLO TO US!<br />([irc://irc.freenode.net/limesurvey])

	==Additional information for new developers==		==Additional information for new developers==

FuzzyBot: Importing a new version from external source

2013-06-13T00:02:19Z

Importing a new version from external source

← Older revision	Revision as of 02:02, 13 June 2013
(No difference)

FuzzyBot: Importing a new version from external source

2013-06-13T00:02:19Z

Importing a new version from external source

← Older revision		Revision as of 02:02, 13 June 2013
Line 22:		Line 22:
	If you agree to the above points please follow these steps:		If you agree to the above points please follow these steps:
	#Create a personal account on the limesurvey.org website here (if you don't have one): [http://www.limesurvey.org/en/component/comprofiler/registers]		#Create a personal account on the limesurvey.org website here (if you don't have one): [http://www.limesurvey.org/en/component/comprofiler/registers]
	#Create a personal account on ~~sourceforge.net~~ here (if you don't have one): [https://~~sourceforge~~.~~net~~/~~account/registration~~/]		#Create a personal account on gitHub here (if you don't have one): [https://github.com/signup/free]
	#Make sure you subscribe to the limesurvey-developer mailing list at [~~https~~://sourceforge.net/~~mail~~/?~~group_id~~=~~74605~~]. If you want to get notified of any changes in the development source code then subscribe to the limesurvey-~~csv~~ list too.		#Make sure you subscribe to the limesurvey-developer mailing list at [http://sourceforge.net/p/limesurvey/mailman/?source=navbar]. If you want to get notified of any changes in the development source code then subscribe to the limesurvey-git list too.
	#If you use a Windows System get the ~~Subversion~~ client ~~TortoiseSVN~~ to access the source code ~~in the repository on sf.net~~. You can download it from [http://~~tortoisesvn~~.~~sourceforge~~.~~net~~/~~downloads~~]		#If you use a Windows System get the Git client SmartGit (there are others but we recommend this one) to access the source code gitHub. You can download it from [http://www.syntevo.com/smartgithg/]
	#Introduce yourself on the limesurvey-developer mailing list and provide the following information:		#Introduce yourself on the limesurvey-developer mailing list and provide the following information:
	## A short resume (so we can see what your background is)		## A short resume (so we can see what your background is)

C schmitz: Text replace - "
" to "
"

2013-05-23T07:12:32Z

Text replace - " " to " "

← Older revision		Revision as of 09:12, 23 May 2013
Line 30:		Line 30:
	## Tell us in what area you would like to help (coding, patching, support etc.)		## Tell us in what area you would like to help (coding, patching, support etc.)
	# Carsten Schmitz will get back to you as soon as possible. He is a very nice guy and will give you an introduction and will provide more information on the next steps.		# Carsten Schmitz will get back to you as soon as possible. He is a very nice guy and will give you an introduction and will provide more information on the next steps.
	# Visit the [http://www.limesurvey.org/index.php/Live-Chat.html official Lime Survey IRC Channel] and SAY HELLO TO US!<br/>([irc://irc.freenode.net/limesurvey])		# Visit the [http://www.limesurvey.org/index.php/Live-Chat.html official Lime Survey IRC Channel] and SAY HELLO TO US!<br />([irc://irc.freenode.net/limesurvey])

	==Additional information for new developers==		==Additional information for new developers==

C schmitz: Text replace - "
" to "
"

2013-05-23T07:12:31Z

Text replace - " " to " "

← Older revision		Revision as of 09:12, 23 May 2013
Line 20:		Line 20:
	==First steps==		==First steps==

	~~<span class="mw-translate-fuzzy">~~
	If you agree to the above points please follow these steps:		If you agree to the above points please follow these steps:
	#Create a personal account on the limesurvey.org website here (if you don't have one): [http://www.limesurvey.org/en/component/comprofiler/registers]		#Create a personal account on the limesurvey.org website here (if you don't have one): [http://www.limesurvey.org/en/component/comprofiler/registers]
Line 31:		Line 30:
	## Tell us in what area you would like to help (coding, patching, support etc.)		## Tell us in what area you would like to help (coding, patching, support etc.)
	# Carsten Schmitz will get back to you as soon as possible. He is a very nice guy and will give you an introduction and will provide more information on the next steps.		# Carsten Schmitz will get back to you as soon as possible. He is a very nice guy and will give you an introduction and will provide more information on the next steps.
	# Visit the [http://www.limesurvey.org/index.php/Live-Chat.html official Lime Survey IRC Channel] and SAY HELLO TO US!<br />([irc://irc.freenode.net/limesurvey])		# Visit the [http://www.limesurvey.org/index.php/Live-Chat.html official Lime Survey IRC Channel] and SAY HELLO TO US!<br/>([irc://irc.freenode.net/limesurvey])
	~~</span>~~

	==Additional information for new developers==		==Additional information for new developers==
Line 50:		Line 48:
	Giving support is a specialty since you are interacting with lots of different persons, friendly and not so friendly, strict or sloppy, eager or calm.		Giving support is a specialty since you are interacting with lots of different persons, friendly and not so friendly, strict or sloppy, eager or calm.

	~~<span class="mw-translate-fuzzy">~~
	Therefore we have a special request to persons who give support in the channel or forums:		Therefore we have a special request to persons who give support in the channel or forums:
	*'''Don't be caught by support burnout'''. It's nearly impossible to answer every technical question that is asked in the forum. In many cases, the problem doesn't lie in the technical aspects of the question; cultural barriers may get in the way of communication, or it may be difficult to explain to a newbie just where to begin. When you try to answer every question, regardless of difficulty, you set yourself up for support burnout. <br />Support burnout is nearly always accompanied by the feeling that you're losing control of your time, that the people you've set out to help are making unreasonable demands. The problem is that you're taking on too much responsibility; but it begins to appear instead that the problem is the end user who's asking for help.<br />Different people react to support burnout in different ways. Some offer malicious advice, some insist that every question a newbie asks should be answered with a URL or by lists of manual references. <br />Such arbitrary rule sets tend to grow longer over time, because they don't solve the real problem. You can't answer every question, and you shouldn't try. Be gentle, be courteous, be flexible and be as patient and helpful as you can - but let someone else try to answer questions that you find too frustrating. Don't try to be a superhuman support machine. Also leave room for user-to-user help. If you support every user and answer every question you do not necessarily boost the community thinking because too much activity takes away any other user motivation to help.		*'''Don't be caught by support burnout'''. It's nearly impossible to answer every technical question that is asked in the forum. In many cases, the problem doesn't lie in the technical aspects of the question; cultural barriers may get in the way of communication, or it may be difficult to explain to a newbie just where to begin. When you try to answer every question, regardless of difficulty, you set yourself up for support burnout. <br />Support burnout is nearly always accompanied by the feeling that you're losing control of your time, that the people you've set out to help are making unreasonable demands. The problem is that you're taking on too much responsibility; but it begins to appear instead that the problem is the end user who's asking for help.<br />Different people react to support burnout in different ways. Some offer malicious advice, some insist that every question a newbie asks should be answered with a URL or by lists of manual references. <br />Such arbitrary rule sets tend to grow longer over time, because they don't solve the real problem. You can't answer every question, and you shouldn't try. Be gentle, be courteous, be flexible and be as patient and helpful as you can - but let someone else try to answer questions that you find too frustrating. Don't try to be a superhuman support machine. Also leave room for user-to-user help. If you support every user and answer every question you do not necessarily boost the community thinking because too much activity takes away any other user motivation to help.
	~~</span>~~

C schmitz: Text replace - "
" to "
"

2013-05-23T07:11:55Z

Text replace - " " to " "

← Older revision		Revision as of 09:11, 23 May 2013
Line 31:		Line 31:
	## Tell us in what area you would like to help (coding, patching, support etc.)		## Tell us in what area you would like to help (coding, patching, support etc.)
	# Carsten Schmitz will get back to you as soon as possible. He is a very nice guy and will give you an introduction and will provide more information on the next steps.		# Carsten Schmitz will get back to you as soon as possible. He is a very nice guy and will give you an introduction and will provide more information on the next steps.
	# Visit the [http://www.limesurvey.org/index.php/Live-Chat.html official Lime Survey IRC Channel] and SAY HELLO TO US!<br/>([irc://irc.freenode.net/limesurvey])		# Visit the [http://www.limesurvey.org/index.php/Live-Chat.html official Lime Survey IRC Channel] and SAY HELLO TO US!<br />([irc://irc.freenode.net/limesurvey])
	</span>		</span>

Line 52:		Line 52:
	<span class="mw-translate-fuzzy">		<span class="mw-translate-fuzzy">
	Therefore we have a special request to persons who give support in the channel or forums:		Therefore we have a special request to persons who give support in the channel or forums:
	*'''Don't be caught by support burnout'''. It's nearly impossible to answer every technical question that is asked in the forum. In many cases, the problem doesn't lie in the technical aspects of the question; cultural barriers may get in the way of communication, or it may be difficult to explain to a newbie just where to begin. When you try to answer every question, regardless of difficulty, you set yourself up for support burnout. <br/>Support burnout is nearly always accompanied by the feeling that you're losing control of your time, that the people you've set out to help are making unreasonable demands. The problem is that you're taking on too much responsibility; but it begins to appear instead that the problem is the end user who's asking for help.<br/>Different people react to support burnout in different ways. Some offer malicious advice, some insist that every question a newbie asks should be answered with a URL or by lists of manual references. <br/>Such arbitrary rule sets tend to grow longer over time, because they don't solve the real problem. You can't answer every question, and you shouldn't try. Be gentle, be courteous, be flexible and be as patient and helpful as you can - but let someone else try to answer questions that you find too frustrating. Don't try to be a superhuman support machine. Also leave room for user-to-user help. If you support every user and answer every question you do not necessarily boost the community thinking because too much activity takes away any other user motivation to help.		*'''Don't be caught by support burnout'''. It's nearly impossible to answer every technical question that is asked in the forum. In many cases, the problem doesn't lie in the technical aspects of the question; cultural barriers may get in the way of communication, or it may be difficult to explain to a newbie just where to begin. When you try to answer every question, regardless of difficulty, you set yourself up for support burnout. <br />Support burnout is nearly always accompanied by the feeling that you're losing control of your time, that the people you've set out to help are making unreasonable demands. The problem is that you're taking on too much responsibility; but it begins to appear instead that the problem is the end user who's asking for help.<br />Different people react to support burnout in different ways. Some offer malicious advice, some insist that every question a newbie asks should be answered with a URL or by lists of manual references. <br />Such arbitrary rule sets tend to grow longer over time, because they don't solve the real problem. You can't answer every question, and you shouldn't try. Be gentle, be courteous, be flexible and be as patient and helpful as you can - but let someone else try to answer questions that you find too frustrating. Don't try to be a superhuman support machine. Also leave room for user-to-user help. If you support every user and answer every question you do not necessarily boost the community thinking because too much activity takes away any other user motivation to help.
	</span>		</span>

FuzzyBot: Importing a new version from external source

2013-04-11T22:01:07Z

Importing a new version from external source

← Older revision		Revision as of 00:01, 12 April 2013
Line 50:		Line 50:
	Giving support is a specialty since you are interacting with lots of different persons, friendly and not so friendly, strict or sloppy, eager or calm.		Giving support is a specialty since you are interacting with lots of different persons, friendly and not so friendly, strict or sloppy, eager or calm.

			<span class="mw-translate-fuzzy">
	Therefore we have a special request to persons who give support in the channel or forums:		Therefore we have a special request to persons who give support in the channel or forums:
	*'''Don't be caught by support burnout'''. It's nearly impossible to answer every technical question that is asked in the forum. In many cases, the problem doesn't lie in the technical aspects of the question; cultural barriers may get in the way of communication, or it may be difficult to explain to a newbie just where to begin. When you try to answer every question, regardless of difficulty, you set yourself up for support burnout. <br/>Support burnout is nearly always accompanied by the feeling that you're losing control of your time, that the people you've set out to help are making unreasonable demands. The problem is that you're taking on too much responsibility; but it begins to appear instead that the problem is the end user who's asking for help.<br/>Different people react to support burnout in different ways. Some offer malicious advice, some insist that every question a newbie asks should be answered with a URL or by lists of manual references. <br/>Such arbitrary rule sets tend to grow longer over time, because they don't solve the real problem. You can't answer every question, and you shouldn't try. Be gentle, be courteous, be flexible and be as patient and helpful as you can - but let someone else try to answer questions that you find too frustrating. Don't try to be a superhuman support machine. Also leave room for user-to-user help. If you support every user and answer every question you do not necessarily boost the community thinking because too much activity takes away any other user motivation to help.		*'''Don't be caught by support burnout'''. It's nearly impossible to answer every technical question that is asked in the forum. In many cases, the problem doesn't lie in the technical aspects of the question; cultural barriers may get in the way of communication, or it may be difficult to explain to a newbie just where to begin. When you try to answer every question, regardless of difficulty, you set yourself up for support burnout. <br/>Support burnout is nearly always accompanied by the feeling that you're losing control of your time, that the people you've set out to help are making unreasonable demands. The problem is that you're taking on too much responsibility; but it begins to appear instead that the problem is the end user who's asking for help.<br/>Different people react to support burnout in different ways. Some offer malicious advice, some insist that every question a newbie asks should be answered with a URL or by lists of manual references. <br/>Such arbitrary rule sets tend to grow longer over time, because they don't solve the real problem. You can't answer every question, and you shouldn't try. Be gentle, be courteous, be flexible and be as patient and helpful as you can - but let someone else try to answer questions that you find too frustrating. Don't try to be a superhuman support machine. Also leave room for user-to-user help. If you support every user and answer every question you do not necessarily boost the community thinking because too much activity takes away any other user motivation to help.
			</span>

How to join the LimeSurvey project team/en - Revision history

FuzzyBot: Updating to match new version of source page

FuzzyBot: Importing a new version from external source

FuzzyBot: Importando nueva versión desde fuente externa

FuzzyBot: Bezig met het importeren van een nieuwe versie uit een externe bron

FuzzyBot: Importing a new version from external source

FuzzyBot: Importing a new version from external source

C schmitz: Text replace - "" to ""

C schmitz: Text replace - "" to ""

C schmitz: Text replace - "" to ""

FuzzyBot: Importing a new version from external source

C schmitz: Text replace - "
" to "
"

C schmitz: Text replace - "
" to "
"

C schmitz: Text replace - "
" to "
"