Community Project Handbook - Revision history

TimRiker at 21:35, 17 November 2022

2022-11-17T21:35:57Z

← Older revision		Revision as of 21:35, 17 November 2022
Line 1:		Line 1:
	~~{{Other languages/Community_Project_Handbook}}~~
	{{communityprojecthandbook}}		{{communityprojecthandbook}}
	The Community Project Handbook provides guidance to project leaders, volunteers, and other community members engaged in the Tech community effort. This handbook compiles an ongoing set of principles and best practices intended to demystify, improve, and advance community projects. Because this is a wiki, you can add your own tips and experiences to this ongoing, growing handbook.		The Community Project Handbook provides guidance to project leaders, volunteers, and other community members engaged in the Tech community effort. This handbook compiles an ongoing set of principles and best practices intended to demystify, improve, and advance community projects. Because this is a wiki, you can add your own tips and experiences to this ongoing, growing handbook.

TimRiker at 19:12, 2 February 2022

2022-02-02T19:12:47Z

← Older revision		Revision as of 19:12, 2 February 2022
Line 1:		Line 1:
	{{Other languages/Community_Project_Handbook}}		{{Other languages/Community_Project_Handbook}}
	{{communityprojecthandbook}}		{{communityprojecthandbook}}
	The Community Project Handbook provides guidance to project leaders, volunteers, and other community members engaged in the ~~LDSTech~~ community effort. This handbook compiles an ongoing set of principles and best practices intended to demystify, improve, and advance community projects. Because this is a wiki, you can add your own tips and experiences to this ongoing, growing handbook.		The Community Project Handbook provides guidance to project leaders, volunteers, and other community members engaged in the Tech community effort. This handbook compiles an ongoing set of principles and best practices intended to demystify, improve, and advance community projects. Because this is a wiki, you can add your own tips and experiences to this ongoing, growing handbook.

	==Project manager role==		==Project manager role==

Wlhunag: Undo mistakes

2012-08-25T13:04:53Z

Undo mistakes

← Older revision		Revision as of 13:04, 25 August 2012
Line 1:		Line 1:
	{{Other languages/Community_Project_Handbook}}		{{Other languages/Community_Project_Handbook}}
	{{communityprojecthandbook}}		{{communityprojecthandbook}}
	社群專案手冊提供指引給專案領袖、志願者以及其他在LDSTech社群付出努力的社群成員們。本手冊不斷的收集最實用的原則和經驗來釐清和協助推動社群專案。因為這是一個wiki，所以你可以添加自己的技巧和經驗到這持續增添的手冊中。		The Community Project Handbook provides guidance to project leaders, volunteers, and other community members engaged in the LDSTech community effort. This handbook compiles an ongoing set of principles and best practices intended to demystify, improve, and advance community projects. Because this is a wiki, you can add your own tips and experiences to this ongoing, growing handbook.
	~~==專案經理的角色==~~
	本手冊的核心有兩個部份：一個是寫給專案經理們，而另一個則是給志願者們看的。你會注意到寫給專案經理的指示排在寫給志願者的指示之前。此編排是有原因的。其中一個重要的原因是：社群專案不會因為缺乏人才而失敗。專案的成敗有賴於''專案經理的帶領，協調志願者所付出的努力'''。

	~~要獲得成功，~~'''~~專案經理必須了解，這些兼職的志願者來自世界各地，有著不同的興趣、背景和時間安排，而且經常有所變動~~'''~~。因此，如上所述，管理社群專案的規則，大大不同於管理教會辦公室內，領薪水職員的那些內部專案。這也是撰寫本手冊的原因。~~		==Project manager role==
	~~==志願者的角色==~~		At the heart of the handbook are two main sections: one for project managers, and one for volunteers. You'll notice that the instruction for project managers appears before the instruction for volunteers. There's a purpose behind this arrangement. The number one reason community projects fail is not due to lack of volunteer resources or talent. A project's failure or success depends on ''how the project manager guides the project and volunteer efforts''.
	同樣的，志願者也需要了解社群專案是需要主動參與的。太多的專案因為志願者加入後等著專案經理分配任務，而停滯不前。雖然專案經理應該一一歡迎新加入的志願者，但是你也要知道，你若需要愈多的支援和指導，專案經理就會因為你的加入而要花費更多的心力。

	~~有時候，假如專案經理在支援志願者方面付出太多心力的話，他就會開始思考社群的價值。因此，~~'''~~對志願者來說，很重要的是要主動、自我引導，即使沒有特定指示，也願意付出貢獻~~'''~~。大部分的專案在他們的 wiki 頁面上都有相當充分的資訊，並且在 JIRA 上面有一串問題有待解決。直接投入並開始行動吧，不需要等人來邀請！~~		To be successful, '''project managers need to understand the dynamics of managing remotely located, part-time volunteers with varying interests, backgrounds, and schedules.''' As such, the rules for managing community projects differ significantly from managing internal projects with on-site, paid employees. Hence the justification for this guide.

	==~~變化與彈性~~==		==Volunteer role==
	當然，並非全部的專案都用一樣的模式來進行。有些專案可能不太依循這邊講到的原則來進行。另外，像是測試中的那些專案，有著數百位志願者參與，如果要一一歡迎新加入的志願者，那也是不實際的。		Likewise, volunteers also need to understand the dynamics of community projects. Too many projects stagnate with volunteers who join and wait to be engaged. While project managers should reach out and welcome new volunteers, recognize that the more hand-holding and guidance you need, the more management overhead your participation requires.

	儘管如此，這些原則與方針適用於大部分的專案，並且可以幫助你和志願者們付出努力時得到成功。當你學到管理你的專案的更好方法時，請分享你的方法，以便其他的專案經理和志願者們能夠成功。		At some point, if the management overhead is too high, project managers begin to question the value of the community effort. Therefore '''it is critical that volunteers be proactive, self-guiding, and willing to step up even when not specifically directed to do so.''' Most projects should have ample information on their wiki pages and a list of items to tackle in JIRA. Don't wait for an invitation—jump in and act.

			==Variations and flexibility==
			We recognize that not all projects are run the same way, of course. Some projects may not rely on many of these principles. Others, such as testing projects, which have hundreds of volunteers, will not find it practical to reach out and individually welcome new volunteers.

			Even so, these principles and guidelines apply generally and will help you be successful with your community endeavors. As you learn how to better manage your projects, please share what works for you so that others—both project managers and volunteers—can benefit.

Wlhunag at 11:27, 25 August 2012

2012-08-25T11:27:27Z

← Older revision		Revision as of 11:27, 25 August 2012
Line 1:		Line 1:
			{{Other languages/Community_Project_Handbook}}
	{{communityprojecthandbook}}		{{communityprojecthandbook}}
	The Community Project Handbook provides guidance to project leaders, volunteers, and other community members engaged in the LDSTech community effort. This handbook compiles an ongoing set of principles and best practices intended to demystify, improve, and advance community projects. Because this is a wiki, you can add your own tips and experiences to this ongoing, growing handbook.		社群專案手冊提供指引給專案領袖、志願者以及其他在LDSTech社群付出努力的社群成員們。本手冊不斷的收集最實用的原則和經驗來釐清和協助推動社群專案。因為這是一個wiki，所以你可以添加自己的技巧和經驗到這持續增添的手冊中。
			==專案經理的角色==
			本手冊的核心有兩個部份：一個是寫給專案經理們，而另一個則是給志願者們看的。你會注意到寫給專案經理的指示排在寫給志願者的指示之前。此編排是有原因的。其中一個重要的原因是：社群專案不會因為缺乏人才而失敗。專案的成敗有賴於''專案經理的帶領，協調志願者所付出的努力'''。

	~~==Project manager role==~~		要獲得成功，'''專案經理必須了解，這些兼職的志願者來自世界各地，有著不同的興趣、背景和時間安排，而且經常有所變動'''。因此，如上所述，管理社群專案的規則，大大不同於管理教會辦公室內，領薪水職員的那些內部專案。這也是撰寫本手冊的原因。
	~~At the heart of the handbook are two main sections: one for project managers, and one for volunteers. You~~'~~ll notice that the instruction for project managers appears before the instruction for volunteers. There~~'~~s a purpose behind this arrangement. The number one reason community projects fail is not due to lack of volunteer resources or talent. A project~~'~~s failure or success depends on~~ ''~~how the project manager guides the project and volunteer efforts~~''.		==志願者的角色==
			同樣的，志願者也需要了解社群專案是需要主動參與的。太多的專案因為志願者加入後等著專案經理分配任務，而停滯不前。雖然專案經理應該一一歡迎新加入的志願者，但是你也要知道，你若需要愈多的支援和指導，專案經理就會因為你的加入而要花費更多的心力。

	~~To be successful,~~ '''~~project managers need to understand the dynamics of managing remotely located, part-time volunteers with varying interests, backgrounds, and schedules.~~''' ~~As such, the rules for managing community projects differ significantly from managing internal projects with on-site, paid employees. Hence the justification for this guide.~~		有時候，假如專案經理在支援志願者方面付出太多心力的話，他就會開始思考社群的價值。因此，'''對志願者來說，很重要的是要主動、自我引導，即使沒有特定指示，也願意付出貢獻'''。大部分的專案在他們的 wiki 頁面上都有相當充分的資訊，並且在 JIRA 上面有一串問題有待解決。直接投入並開始行動吧，不需要等人來邀請！

	==~~Volunteer role~~==		==變化與彈性==
	Likewise, volunteers also need to understand the dynamics of community projects. Too many projects stagnate with volunteers who join and wait to be engaged. While project managers should reach out and welcome new volunteers, recognize that the more hand-holding and guidance you need, the more management overhead your participation requires.		當然，並非全部的專案都用一樣的模式來進行。有些專案可能不太依循這邊講到的原則來進行。另外，像是測試中的那些專案，有著數百位志願者參與，如果要一一歡迎新加入的志願者，那也是不實際的。

	At some point, if the management overhead is too high, project managers begin to question the value of the community effort. Therefore '''it is critical that volunteers be proactive, self-guiding, and willing to step up even when not specifically directed to do so.''' Most projects should have ample information on their wiki pages and a list of items to tackle in JIRA. Don't wait for an invitation—jump in and act.		儘管如此，這些原則與方針適用於大部分的專案，並且可以幫助你和志願者們付出努力時得到成功。當你學到管理你的專案的更好方法時，請分享你的方法，以便其他的專案經理和志願者們能夠成功。

	~~==Variations and flexibility==~~
	We recognize that not all projects are run the same way, of course. Some projects may not rely on many of these principles. Others, such as testing projects, which have hundreds of volunteers, will not find it practical to reach out and individually welcome new volunteers.

	Even so, these principles and guidelines apply generally and will help you be successful with your community endeavors. As you learn how to better manage your projects, please share what works for you so that others—both project managers and volunteers—can benefit.

Minsonbt: /* Variations and flexibility */

2012-04-17T20:19:52Z

Variations and flexibility

← Older revision		Revision as of 20:19, 17 April 2012
Line 15:		Line 15:
	We recognize that not all projects are run the same way, of course. Some projects may not rely on many of these principles. Others, such as testing projects, which have hundreds of volunteers, will not find it practical to reach out and individually welcome new volunteers.		We recognize that not all projects are run the same way, of course. Some projects may not rely on many of these principles. Others, such as testing projects, which have hundreds of volunteers, will not find it practical to reach out and individually welcome new volunteers.

	Even so, these principles and guidelines apply generally and will help you be successful with your community endeavors. As you learn how to better manage your projects, please share what works for you so that ~~others -- both~~ project managers and ~~volunteers -- can~~ benefit.		Even so, these principles and guidelines apply generally and will help you be successful with your community endeavors. As you learn how to better manage your projects, please share what works for you so that others—both project managers and volunteers—can benefit.

Minsonbt: /* Volunteer role */

2012-04-17T20:18:02Z

Volunteer role

← Older revision		Revision as of 20:18, 17 April 2012
Line 10:		Line 10:
	Likewise, volunteers also need to understand the dynamics of community projects. Too many projects stagnate with volunteers who join and wait to be engaged. While project managers should reach out and welcome new volunteers, recognize that the more hand-holding and guidance you need, the more management overhead your participation requires.		Likewise, volunteers also need to understand the dynamics of community projects. Too many projects stagnate with volunteers who join and wait to be engaged. While project managers should reach out and welcome new volunteers, recognize that the more hand-holding and guidance you need, the more management overhead your participation requires.

	At some point, if the management overhead is too high, project managers begin to question the value of the community effort. Therefore '''it is critical that volunteers be proactive, self-guiding, and willing to step up even when not specifically directed to do so.''' Most projects should have ample information on their wiki pages and a list of items to tackle in JIRA. Don't wait for an ~~invitation -- jump~~ in and act.		At some point, if the management overhead is too high, project managers begin to question the value of the community effort. Therefore '''it is critical that volunteers be proactive, self-guiding, and willing to step up even when not specifically directed to do so.''' Most projects should have ample information on their wiki pages and a list of items to tackle in JIRA. Don't wait for an invitation—jump in and act.

	==Variations and flexibility==		==Variations and flexibility==

Minsonbt: /* Project managers role */

2012-04-17T20:16:58Z

Project managers role

← Older revision		Revision as of 20:16, 17 April 2012
Line 2:		Line 2:
	The Community Project Handbook provides guidance to project leaders, volunteers, and other community members engaged in the LDSTech community effort. This handbook compiles an ongoing set of principles and best practices intended to demystify, improve, and advance community projects. Because this is a wiki, you can add your own tips and experiences to this ongoing, growing handbook.		The Community Project Handbook provides guidance to project leaders, volunteers, and other community members engaged in the LDSTech community effort. This handbook compiles an ongoing set of principles and best practices intended to demystify, improve, and advance community projects. Because this is a wiki, you can add your own tips and experiences to this ongoing, growing handbook.

	==Project ~~managers~~ role==		==Project manager role==
	At the heart of the handbook are two main sections: one for project managers, and one for volunteers. You'll notice that the instruction for project managers appears before the instruction for volunteers. There's a purpose behind this arrangement. The number one reason community projects fail is not due to lack of volunteer resources or talent. A project's failure or success depends on ''how the project manager guides the project and volunteer efforts''.		At the heart of the handbook are two main sections: one for project managers, and one for volunteers. You'll notice that the instruction for project managers appears before the instruction for volunteers. There's a purpose behind this arrangement. The number one reason community projects fail is not due to lack of volunteer resources or talent. A project's failure or success depends on ''how the project manager guides the project and volunteer efforts''.

Johnsonth: broke up content with subheads

2012-04-05T19:36:12Z

broke up content with subheads

← Older revision		Revision as of 19:36, 5 April 2012
Line 2:		Line 2:
	The Community Project Handbook provides guidance to project leaders, volunteers, and other community members engaged in the LDSTech community effort. This handbook compiles an ongoing set of principles and best practices intended to demystify, improve, and advance community projects. Because this is a wiki, you can add your own tips and experiences to this ongoing, growing handbook.		The Community Project Handbook provides guidance to project leaders, volunteers, and other community members engaged in the LDSTech community effort. This handbook compiles an ongoing set of principles and best practices intended to demystify, improve, and advance community projects. Because this is a wiki, you can add your own tips and experiences to this ongoing, growing handbook.

			==Project managers role==
	At the heart of the handbook are two main sections: one for project managers, and one for volunteers. You'll notice that the instruction for project managers appears before the instruction for volunteers. There's a purpose behind this arrangement. The number one reason community projects fail is not due to lack of volunteer resources or talent. A project's failure or success depends on ''how the project manager guides the project and volunteer efforts''.		At the heart of the handbook are two main sections: one for project managers, and one for volunteers. You'll notice that the instruction for project managers appears before the instruction for volunteers. There's a purpose behind this arrangement. The number one reason community projects fail is not due to lack of volunteer resources or talent. A project's failure or success depends on ''how the project manager guides the project and volunteer efforts''.

	To be successful, '''project managers need to understand the dynamics of managing remotely located, part-time volunteers with varying interests, backgrounds, and schedules.''' As such, the rules for managing community projects differ significantly from managing internal projects with on-site, paid employees. Hence the justification for this guide.		To be successful, '''project managers need to understand the dynamics of managing remotely located, part-time volunteers with varying interests, backgrounds, and schedules.''' As such, the rules for managing community projects differ significantly from managing internal projects with on-site, paid employees. Hence the justification for this guide.

			==Volunteer role==
	Likewise, volunteers also need to understand the dynamics of community projects. Too many projects stagnate with volunteers who join and wait to be engaged. While project managers should reach out and welcome new volunteers, recognize that the more hand-holding and guidance you need, the more management overhead your participation requires.		Likewise, volunteers also need to understand the dynamics of community projects. Too many projects stagnate with volunteers who join and wait to be engaged. While project managers should reach out and welcome new volunteers, recognize that the more hand-holding and guidance you need, the more management overhead your participation requires.

	At some point, if the management overhead is too high, project managers begin to question the value of the community effort. Therefore '''it is critical that volunteers be proactive, self-guiding, and willing to step up even when not specifically directed to do so.''' Most projects should have ample information on their wiki pages and a list of items to tackle in JIRA. Don't wait for an invitation -- jump in and act.		At some point, if the management overhead is too high, project managers begin to question the value of the community effort. Therefore '''it is critical that volunteers be proactive, self-guiding, and willing to step up even when not specifically directed to do so.''' Most projects should have ample information on their wiki pages and a list of items to tackle in JIRA. Don't wait for an invitation -- jump in and act.

			==Variations and flexibility==
	We recognize that not all projects are run the same way, of course. Some projects may not rely on many of these principles. Others, such as testing projects, which have hundreds of volunteers, will not find it practical to reach out and individually welcome new volunteers.		We recognize that not all projects are run the same way, of course. Some projects may not rely on many of these principles. Others, such as testing projects, which have hundreds of volunteers, will not find it practical to reach out and individually welcome new volunteers.

	Even so, these principles and guidelines apply generally and will help you be successful with your community endeavors. As you learn how to better manage your projects, please share what works for you so that others -- both project managers and volunteers -- can benefit.		Even so, these principles and guidelines apply generally and will help you be successful with your community endeavors. As you learn how to better manage your projects, please share what works for you so that others -- both project managers and volunteers -- can benefit.

Jcarroll: Formatting only: Added emphasis to key points

2012-03-18T12:56:42Z

Formatting only: Added emphasis to key points

← Older revision		Revision as of 12:56, 18 March 2012
Line 4:		Line 4:
	At the heart of the handbook are two main sections: one for project managers, and one for volunteers. You'll notice that the instruction for project managers appears before the instruction for volunteers. There's a purpose behind this arrangement. The number one reason community projects fail is not due to lack of volunteer resources or talent. A project's failure or success depends on ''how the project manager guides the project and volunteer efforts''.		At the heart of the handbook are two main sections: one for project managers, and one for volunteers. You'll notice that the instruction for project managers appears before the instruction for volunteers. There's a purpose behind this arrangement. The number one reason community projects fail is not due to lack of volunteer resources or talent. A project's failure or success depends on ''how the project manager guides the project and volunteer efforts''.

	To be successful, project managers need to understand the dynamics of managing remotely located, part-time volunteers with varying interests, backgrounds, and schedules. As such, the rules for managing community projects differ significantly from managing internal projects with on-site, paid employees. Hence the justification for this guide.		To be successful, '''project managers need to understand the dynamics of managing remotely located, part-time volunteers with varying interests, backgrounds, and schedules.''' As such, the rules for managing community projects differ significantly from managing internal projects with on-site, paid employees. Hence the justification for this guide.

	Likewise, volunteers also need to understand the dynamics of community projects. Too many projects stagnate with volunteers who join and wait to be engaged. While project managers should reach out and welcome new volunteers, recognize that the more hand-holding and guidance you need, the more management overhead your participation requires.		Likewise, volunteers also need to understand the dynamics of community projects. Too many projects stagnate with volunteers who join and wait to be engaged. While project managers should reach out and welcome new volunteers, recognize that the more hand-holding and guidance you need, the more management overhead your participation requires.

	At some point, if the management overhead is too high, project managers begin to question the value of the community effort. Therefore it is critical that volunteers be proactive, self-guiding, and willing to step up even when not specifically directed to do so. Most projects should have ample information on their wiki pages and a list of items to tackle in JIRA. Don't wait for an invitation -- jump in and act.		At some point, if the management overhead is too high, project managers begin to question the value of the community effort. Therefore '''it is critical that volunteers be proactive, self-guiding, and willing to step up even when not specifically directed to do so.''' Most projects should have ample information on their wiki pages and a list of items to tackle in JIRA. Don't wait for an invitation -- jump in and act.

	We recognize that not all projects are run the same way, of course. Some projects may not rely on many of these principles. Others, such as testing projects, which have hundreds of volunteers, will not find it practical to reach out and individually welcome new volunteers.		We recognize that not all projects are run the same way, of course. Some projects may not rely on many of these principles. Others, such as testing projects, which have hundreds of volunteers, will not find it practical to reach out and individually welcome new volunteers.

	Even so, these principles and guidelines apply generally and will help you be successful with your community endeavors. As you learn how to better manage your projects, please share what works for you so that others -- both project managers and volunteers -- can benefit.		Even so, these principles and guidelines apply generally and will help you be successful with your community endeavors. As you learn how to better manage your projects, please share what works for you so that others -- both project managers and volunteers -- can benefit.

Johnsonth: moved Community Project Handbook overview to Community Project Handbook: want easier link

2012-03-15T05:51:26Z

moved Community Project Handbook overview to Community Project Handbook: want easier link

← Older revision	Revision as of 05:51, 15 March 2012
(No difference)