Welcome Email - Revision history

Marcin at 19:13, 18 November 2017

2017-11-18T19:13:13Z

← Older revision		Revision as of 19:13, 18 November 2017
Line 4:		Line 4:
	'''This email will be your reference to key information and New Developer Orientation. Please star or archive this email.'''		'''This email will be your reference to key information and New Developer Orientation. Please star or archive this email.'''

	Congratulations ~~[_________________________],~~		Congratulations!

	You have passed the FreeCAD Test with a score of ~~[insert score]~~. Please find your OSE FreeCAD Badge, you can add it to your LinkedIn page and Resume.		You have passed the FreeCAD Test with a score of _________________. Please find your OSE FreeCAD Badge, you can add it to your LinkedIn page and Resume.

	Welcome to the Open Source Ecology development team. We are very excited to have you aboard. As you know our vision here at Open Source Ecology is to build a new economy that is more innovative, efficient and democratic through open source collaboration and distributive enterprise. This is an ambitious and noble undertaking so congratulations and thanks for your time and energy.		Welcome to the Open Source Ecology development team. We are very excited to have you aboard. As you know our vision here at Open Source Ecology is to build a new economy that is more innovative, efficient and democratic through open source collaboration and distributive enterprise. This is an ambitious and noble undertaking so congratulations and thanks for your time and energy.

Marcin at 18:35, 18 November 2017

2017-11-18T18:35:46Z

← Older revision		Revision as of 18:35, 18 November 2017
Line 11:		Line 11:

	START DATE		START DATE
	Your official start date is the date of you posting your FreeCAD Test - which is _________________________. This marks the first day of your participation - for 12 weekly team meetings (90-day development cycles). We release a product at the end of every 90-day cycle. At the point of having completed 12 weeks - which would be on _________________________- you will have the option to continue. This assumes that you have completed your 120 hours - though you can complete a cycle sooner or later depending on how many hours you put in per week. After each completed cycle you will have a chance to participate in a Performance Development meeting with HR. The Performance Development Meeting is where we take an opportunity to learn from you how we could make the development process better - and how you could get more out of the process. If you have completed your weekly task assignments to a good degree through the development cycle, you will receive a star on your badge: a mark of having completed a full development cycle successfully.		Your official start date is the date of you posting your [[FreeCAD Test]] - which is _________________________. This marks the first day of your participation - for 12 weekly team meetings (90-day development cycles). We release a product at the end of every 90-day cycle. At the point of having completed 12 weeks - which would be on _________________________- you will have the option to continue. This assumes that you have completed your 120 hours - though you can complete a cycle sooner or later depending on how many hours you put in per week. After each completed cycle you will have a chance to participate in a Performance Development meeting with HR. The Performance Development Meeting is where we take an opportunity to learn from you how we could make the development process better - and how you could get more out of the process. If you have completed your weekly task assignments to a good degree through the development cycle, you will receive a star on your badge: a mark of having completed a full development cycle successfully.

	TELL YOUR FRIENDS		TELL YOUR FRIENDS

JMikler at 05:56, 14 July 2017

2017-07-14T05:56:38Z

Show changes

Richard White at 14:25, 28 June 2017

2017-06-28T14:25:27Z

← Older revision		Revision as of 14:25, 28 June 2017
Line 12:		Line 12:
	Welcome to the Open Source Ecology development team. We are very excited to have you aboard. As you know our vision here at Open Source Ecology is to build a new economy that is more innovative, efficient and democratic through open source collaboration and distributive enterprise. This is an ambitious and noble undertaking so congratulations and thanks for your time and energy.		Welcome to the Open Source Ecology development team. We are very excited to have you aboard. As you know our vision here at Open Source Ecology is to build a new economy that is more innovative, efficient and democratic through open source collaboration and distributive enterprise. This is an ambitious and noble undertaking so congratulations and thanks for your time and energy.

	Your official start date is the date of you posting your FreeCAD Test - which is _________________. This marks the first day of your participation - for 12 weekly team meetings (90-day development cycles). We release a product at the end of every 90-day cycle. At the point of having completed 12 weeks - which would be on __________________ - you will have the option to continue. This assumes that you have completed your 120 hours - though you can complete a cycle sooner or later ~~dependig~~ on how many hours you put in per week. After each completed cycle - you will have a chance to participate in a Performance Development meeting with HR. The Performance Development Meeting is where we take an opportunity to learn from you how we could make the development process better - and how you could get more out of the process. If you have completed your weekly task assignments to a good degree through the development cycle - you will receive a star on your badge - a mark of having completed a full development cycle successfully.		Your official start date is the date of you posting your FreeCAD Test - which is _________________. This marks the first day of your participation - for 12 weekly team meetings (90-day development cycles). We release a product at the end of every 90-day cycle. At the point of having completed 12 weeks - which would be on __________________ - you will have the option to continue. This assumes that you have completed your 120 hours - though you can complete a cycle sooner or later depending on how many hours you put in per week. After each completed cycle - you will have a chance to participate in a Performance Development meeting with HR. The Performance Development Meeting is where we take an opportunity to learn from you how we could make the development process better - and how you could get more out of the process. If you have completed your weekly task assignments to a good degree through the development cycle - you will receive a star on your badge - a mark of having completed a full development cycle successfully.

	The nature of this experience is that we are a development and learning community. We teach each other, as we develop a tribe of high-performing team members. One way we teach each other is by making video instructionals using Kdenlive- a core part of our education/training work.		The nature of this experience is that we are a development and learning community. We teach each other, as we develop a tribe of high-performing team members. One way we teach each other is by making video instructionals using Kdenlive- a core part of our education/training work.

Marcin at 19:02, 13 May 2017

2017-05-13T19:02:26Z

← Older revision		Revision as of 19:02, 13 May 2017
Line 10:		Line 10:
	You have passed the FreeCAD Test with a score of _________. Please find your OSE FreeCAD Badge - which you can post on your log, or you can add it to your Resume.		You have passed the FreeCAD Test with a score of _________. Please find your OSE FreeCAD Badge - which you can post on your log, or you can add it to your Resume.

	Welcome to the Open Source Ecology development team. We are very excited to have you aboard. As you know our vision here at Open Source Ecology is to build a new economy that is more innovative, efficient and democratic through open source collaboration and distributive enterprise. This is an ambitious and noble undertaking so congratulations and thanks for ~~devoting~~ your time and energy.		Welcome to the Open Source Ecology development team. We are very excited to have you aboard. As you know our vision here at Open Source Ecology is to build a new economy that is more innovative, efficient and democratic through open source collaboration and distributive enterprise. This is an ambitious and noble undertaking so congratulations and thanks for your time and energy.

	Your official start date is the date of you posting your FreeCAD Test - which is _________________. This marks the first day of your participation - for 12 weekly team meetings (90-day development cycles). We release a product at the end of every 90-day cycle. At the point of having completed 12 weeks - which would be on __________________ - you will have the option to continue. ~~You~~ will have a chance to participate in a Performance Development meeting with HR. The Performance Development Meeting is where we take an opportunity to learn from you how we could make the development process better - and how you could get more out of the process. If you have completed your weekly task assignments to a good degree through the development cycle - you will receive a star on your badge - a mark of having completed a full development cycle successfully.		Your official start date is the date of you posting your FreeCAD Test - which is _________________. This marks the first day of your participation - for 12 weekly team meetings (90-day development cycles). We release a product at the end of every 90-day cycle. At the point of having completed 12 weeks - which would be on __________________ - you will have the option to continue. This assumes that you have completed your 120 hours - though you can complete a cycle sooner or later dependig on how many hours you put in per week. After each completed cycle - you will have a chance to participate in a Performance Development meeting with HR. The Performance Development Meeting is where we take an opportunity to learn from you how we could make the development process better - and how you could get more out of the process. If you have completed your weekly task assignments to a good degree through the development cycle - you will receive a star on your badge - a mark of having completed a full development cycle successfully.

	The nature of this experience is that we are a development and learning community. We teach each other, as we develop a tribe of high-performing team members. One way we teach each other is by making video instructionals using Kdenlive- a core part of our education/training work.		The nature of this experience is that we are a development and learning community. We teach each other, as we develop a tribe of high-performing team members. One way we teach each other is by making video instructionals using Kdenlive- a core part of our education/training work.
Line 24:		Line 24:
	Once you have familiarized yourself with Open Source Ecology’s core objectives it is time to dive into our current project: The 3D Printer. For updated information related to the 3D Printer please refer to this page:		Once you have familiarized yourself with Open Source Ecology’s core objectives it is time to dive into our current project: The 3D Printer. For updated information related to the 3D Printer please refer to this page:

	http://opensourceecology.org/wiki/~~D3D~~		http://opensourceecology.org/wiki/D3D_Log


Line 31:		Line 31:
	You should already have your Work Log set up. If not, please see http://opensourceecology.org/wiki/Emmanouil_Log as an example:		You should already have your Work Log set up. If not, please see http://opensourceecology.org/wiki/Emmanouil_Log as an example:

	Include the date at the top, and post with the newest updates at the top		*Include the date at the top, and post with the newest updates at the top
	Include links to all your work, such as uploaded files or working documents		*Include links to all your work, such as uploaded files or working documents
	Post other team members' logs on top for ease of collaboration (see team members at http://opensourceecology.org/wiki/D3D) *Post a link to the http://opensourceecology.org/wiki/Timesheet on top of your log.		*Post other team members' logs on top for ease of collaboration (see team members at http://opensourceecology.org/wiki/D3D)
	Please fill out your timesheet by Monday's meeting every week - as we track development time so we can increase our team velocity.		*Post a link to the http://opensourceecology.org/wiki/Timesheet on top of your log.
	Please link to http://opensourceecology.org/wiki/D3D and http://opensourceecology.org/wiki/D3D_Meeting_Log on the top of your log. The meeting log contains recordings of past meetings for review.		*Please fill out your timesheet by Monday's meeting every week - as we track development time so we can increase our team velocity.
	Post the badges that you have earned at the top of your log (so far the OSE FreeCAD Badge)		*Please link to http://opensourceecology.org/wiki/D3D and http://opensourceecology.org/wiki/D3D_Meeting_Log on the top of your log. The meeting log contains recordings of past meetings for review.
	OSE Network - ~~we are using~~ the OSE Network 3D Printer Group as the official discussion thread ~~for the 3D Printer group~~.		*Post the badges that you have earned at the top of your log (so far the OSE FreeCAD Badge)
			*OSE Network - please begin posting to the OSE Network 3D Printer Group as the official discussion thread -
			http://network.opensourceecology.org/groups/profile/676151284687970315/activity


Line 48:		Line 50:
	The format for each team meeting is:		The format for each team meeting is:

	Everyone is assigned tasks during the Monday meeting. In case you miss the meeting, you can review it at http://opensourceecology.org/wiki/D3D_Meeting_Log . It is good practice to prepare for this meeting by watching the videos from previous meetings so you are up to speed. New developers will also be assigned tasks at their first meeting. The D3D Meeting Log ~~includes~~ http://opensourceecology.org/wiki/Scrumy - which is a backlog of tasks and their completion.		Everyone is assigned tasks during the Monday meeting. In case you miss the meeting, you can review it at http://opensourceecology.org/wiki/D3D_Meeting_Log . It is good practice to prepare for this meeting by watching the videos from previous meetings so you are up to speed. New developers will also be assigned tasks at their first meeting. The D3D Meeting Log sometimes uses http://opensourceecology.org/wiki/Scrumy - which is a backlog of tasks and their completion.

	To be in Excellent Standing, you have to ~~contribute a minimum of 100~~ hours in ~~the 12-week Development Cycle~~, for which you will receive a star on your badge. You are allowed and encouraged to recruit a co-worker - who is not part of team meetings but who works with you on completing tasks - and who can participate in the team meeting for you if you are not available. Recruiting a co-worker allows you to reduce your workload as an OSE Developer - while helping others to participate without having passed the official OSE FreeCAD Test. Working in pairs helps keep momentum - and it also helps to develop your leadership skills.		To be in Excellent Standing, you have to complete the 120 hours in a developement cycle, for which you will receive a star on your badge. You are allowed and encouraged to recruit a co-worker - who is not part of team meetings but who works with you on completing tasks - and who can participate in the team meeting for you if you are not available. Recruiting a co-worker allows you to reduce your workload as an OSE Developer - while helping others to participate without having passed the official OSE FreeCAD Test. Working in pairs helps keep momentum - and it also helps to develop your leadership skills.


Line 56:		Line 58:

	By now you should have the OSE Linux Live USB working. This common operating system helps the entire team to collaborate seamlessly with zero barriers. This will be updated every quarter, so please update that as needed. Instructions for installing are at http://opensourceecology.org/wiki/OSE_Linux - please read this page so you are clear about the reasons why we are all using a live USB.		By now you should have the OSE Linux Live USB working. This common operating system helps the entire team to collaborate seamlessly with zero barriers. This will be updated every quarter, so please update that as needed. Instructions for installing are at http://opensourceecology.org/wiki/OSE_Linux - please read this page so you are clear about the reasons why we are all using a live USB.

	~~Link to download OSE Linux and Instructions for creating a Live USB - http://opensourceecology.org/wiki/OSE_Linux~~

	Open Source Ecology is an open design platform where many people build off each others' ideas. It is imperative that we document and log our work - using a Work Log - meticulously so we do not produce duplicate work and we may have accurate statistics to improve efficiency. Here are the best practices for keeping your log - http://opensourceecology.org/wiki/Daily_Log_of_Tasks		Open Source Ecology is an open design platform where many people build off each others' ideas. It is imperative that we document and log our work - using a Work Log - meticulously so we do not produce duplicate work and we may have accurate statistics to improve efficiency. Here are the best practices for keeping your log - http://opensourceecology.org/wiki/Daily_Log_of_Tasks
Line 75:		Line 75:
	'''TELL YOUR FRIENDS'''		'''TELL YOUR FRIENDS'''

	Open Source Ecology is an open source~~, non-profit, volunteer network~~. The scope of our mission is vast and it requires massive engagement from committed members across the globe. ~~We feel the organization will~~ have ~~a greater opportunity~~ to grow if our current team members actively recruit additional members. If you identify and invite a new team member that ends up joining as an OSE Developer - you will be awarded the OSE Recruiting Badge.		Open source ecology is an open source network and movement. Open Source Ecology (with capitals) International is the nonprofit organization that coordinates the open source ecology effort. Everyone can participate by editing our wiki. Dedicated developers are recruited to the OSE Developer team. The scope of our mission is vast and it requires massive engagement from committed members across the globe. People who participate as OSE Developers can subsequently receive training to run teams as Process Managers. Once they have trained as effective Process Managers, they qualify to start recognized OSE Chapters. These Chapters work on the Roadmap and priorities of OSE in conjunction with OSE International. OSE can grow if our current team members actively recruit additional members. If you identify and invite a new team member that ends up joining as an OSE Developer - you will be awarded the OSE Recruiting Badge.


	Please update your LinkedIn and Facebook page about being selected to the development team. Share the team’s accomplishments on social media as we reach milestones. Tell your friends and family what you are doing. It will take mass mobilization in order to successfully scale our organization and form it into the distributive enterprise of shared prosperity that we all envision.		Please update your LinkedIn and Facebook page about being selected to the development team. Share the team’s accomplishments on social media as we reach milestones. Tell your friends and family what you are doing. It will take mass mobilization in order to successfully scale our organization and form it into the distributive enterprise of shared prosperity that we all envision.
Line 82:		Line 81:
	'''TEAM BIO PAGE'''		'''TEAM BIO PAGE'''

	We are putting together a bio page for each member of the Development Team.		We are putting together a bio page for each member of the Development Team. You can view an example here:
	You can view an example here
	http://opensourceecology.org/wiki/OSE_Developers#OSE_Developer_Team		http://opensourceecology.org/wiki/OSE_Developers#OSE_Developer_Team

	We are requesting the following:		We are requesting the following:

	*Profile ~~pic~~ attached in jpeg or png format		*Profile picture attached in jpeg or png format
	*Email, LinkedIn page, website (optional)		*Email, LinkedIn page, website (optional)
	*A quote from yourself about why you are contributing to OSE		*A quote from yourself about why you are contributing to OSE
Line 95:		Line 94:
	Please send bio information to hr@opensourceecology.org		Please send bio information to hr@opensourceecology.org

	Sincerely		Sincerely,

			Marcin Jakubowski
			Founder Open Source Ecology

	~~Marcin Jakubowski Founder Open Source Ecology~~ Richard White HR Generalist in Training		Richard White
			HR Generalist in Training

Richard White at 01:21, 4 May 2017

2017-05-04T01:21:04Z

← Older revision		Revision as of 01:21, 4 May 2017
Line 88:		Line 88:
	We are requesting the following:		We are requesting the following:

	1. Profile pic attached in jpeg or png format		*Profile pic attached in jpeg or png format
	2. Email, LinkedIn page, website (optional)		*Email, LinkedIn page, website (optional)
	3. A quote from yourself about why you are contributing to OSE		*A quote from yourself about why you are contributing to OSE
	~~4. 4.~~ A short bio or few sentences including your relevant skills.		*A short bio or few sentences including your relevant skills.

	Please send bio information to hr@opensourceecology.org		Please send bio information to hr@opensourceecology.org

Richard White at 01:20, 4 May 2017

2017-05-04T01:20:10Z

← Older revision		Revision as of 01:20, 4 May 2017
Line 82:		Line 82:
	'''TEAM BIO PAGE'''		'''TEAM BIO PAGE'''

	~~Lastly~~		We are putting together a bio page for each member of the Development Team.
			You can view an example here
			http://opensourceecology.org/wiki/OSE_Developers#OSE_Developer_Team

	~~Thank~~ you,		We are requesting the following:

			1. Profile pic attached in jpeg or png format
			2. Email, LinkedIn page, website (optional)
			3. A quote from yourself about why you are contributing to OSE
			4. 4. A short bio or few sentences including your relevant skills.

			Please send bio information to hr@opensourceecology.org

	Sincerely		Sincerely

	Marcin Jakubowski Founder Open Source Ecology Richard White HR Generalist in Training		Marcin Jakubowski Founder Open Source Ecology Richard White HR Generalist in Training

Richard White at 01:16, 4 May 2017

2017-05-04T01:16:48Z

← Older revision		Revision as of 01:16, 4 May 2017
Line 31:		Line 31:
	You should already have your Work Log set up. If not, please see http://opensourceecology.org/wiki/Emmanouil_Log as an example:		You should already have your Work Log set up. If not, please see http://opensourceecology.org/wiki/Emmanouil_Log as an example:

	Include date on top, and post with newest updates on top		Include the date at the top, and post with the newest updates at the top
	Include links to all your work, such as uploaded files or working documents		Include links to all your work, such as uploaded files or working documents
	Post other team members' logs on top for ease of collaboration (see team members at http://opensourceecology.org/wiki/D3D) *Post a link to the http://opensourceecology.org/wiki/Timesheet on top of your log.		Post other team members' logs on top for ease of collaboration (see team members at http://opensourceecology.org/wiki/D3D) *Post a link to the http://opensourceecology.org/wiki/Timesheet on top of your log.
Line 57:		Line 57:
	By now you should have the OSE Linux Live USB working. This common operating system helps the entire team to collaborate seamlessly with zero barriers. This will be updated every quarter, so please update that as needed. Instructions for installing are at http://opensourceecology.org/wiki/OSE_Linux - please read this page so you are clear about the reasons why we are all using a live USB.		By now you should have the OSE Linux Live USB working. This common operating system helps the entire team to collaborate seamlessly with zero barriers. This will be updated every quarter, so please update that as needed. Instructions for installing are at http://opensourceecology.org/wiki/OSE_Linux - please read this page so you are clear about the reasons why we are all using a live USB.

	Link to download OSE Linux and Instructions for creating a Live USB - http://opensourceecology.org/wiki/~~OSE Live USB]]~~		Link to download OSE Linux and Instructions for creating a Live USB - http://opensourceecology.org/wiki/OSE_Linux

	Open Source Ecology is an open design platform where many people build off each others' ideas. It is imperative that we document and log our work - using a Work Log - meticulously so we do not produce duplicate work and we may have accurate statistics to improve efficiency. Here are the best practices for keeping your log - http://opensourceecology.org/wiki/Daily_Log_of_Tasks		Open Source Ecology is an open design platform where many people build off each others' ideas. It is imperative that we document and log our work - using a Work Log - meticulously so we do not produce duplicate work and we may have accurate statistics to improve efficiency. Here are the best practices for keeping your log - http://opensourceecology.org/wiki/Daily_Log_of_Tasks
Line 79:		Line 79:

	Please update your LinkedIn and Facebook page about being selected to the development team. Share the team’s accomplishments on social media as we reach milestones. Tell your friends and family what you are doing. It will take mass mobilization in order to successfully scale our organization and form it into the distributive enterprise of shared prosperity that we all envision.		Please update your LinkedIn and Facebook page about being selected to the development team. Share the team’s accomplishments on social media as we reach milestones. Tell your friends and family what you are doing. It will take mass mobilization in order to successfully scale our organization and form it into the distributive enterprise of shared prosperity that we all envision.

			'''TEAM BIO PAGE'''

			Lastly

	Thank you,		Thank you,

Richard White at 18:13, 23 April 2017

2017-04-23T18:13:49Z

← Older revision		Revision as of 18:13, 23 April 2017
Line 10:		Line 10:
	You have passed the FreeCAD Test with a score of _________. Please find your OSE FreeCAD Badge - which you can post on your log, or you can add it to your Resume.		You have passed the FreeCAD Test with a score of _________. Please find your OSE FreeCAD Badge - which you can post on your log, or you can add it to your Resume.

	Welcome to the Open Source Ecology development team. We are very excited to have you aboard. As you know our vision here at Open Source Ecology is to build a new economy that is more innovative, efficient and democratic through open source collaboration and distributive enterprise. This is an ambitious and noble undertaking so congratulations and ~~thank you~~ for devoting your time and energy.		Welcome to the Open Source Ecology development team. We are very excited to have you aboard. As you know our vision here at Open Source Ecology is to build a new economy that is more innovative, efficient and democratic through open source collaboration and distributive enterprise. This is an ambitious and noble undertaking so congratulations and thanks for devoting your time and energy.

	Your official start date is the date of you posting your FreeCAD Test - which is _________________. This marks the first day of your participation - for 12 weekly team meetings (90 day development cycles). We release a product at the end of every 90 day cycle. At the point of having completed 12 weeks - which would be on __________________ - you will have the option to continue. You will have a chance to participate in a Performance Development meeting with HR. The Performance Development Meeting is where we take an opportunity to learn from you how we could make the development process better - and how you could get more out of the process. If you have completed your weekly task assignments to a good degree through the development cycle - you will receive a star on your badge - a mark of having completed a full development cycle successfully.		Your official start date is the date of you posting your FreeCAD Test - which is _________________. This marks the first day of your participation - for 12 weekly team meetings (90-day development cycles). We release a product at the end of every 90-day cycle. At the point of having completed 12 weeks - which would be on __________________ - you will have the option to continue. You will have a chance to participate in a Performance Development meeting with HR. The Performance Development Meeting is where we take an opportunity to learn from you how we could make the development process better - and how you could get more out of the process. If you have completed your weekly task assignments to a good degree through the development cycle - you will receive a star on your badge - a mark of having completed a full development cycle successfully.

	The nature of this experience is that we are a development and learning community. We teach each other, as we develop a tribe of high-performing team members. One way we teach each other is by making video instructionals using Kdenlive- a core part of our education/training work.		The nature of this experience is that we are a development and learning community. We teach each other, as we develop a tribe of high-performing team members. One way we teach each other is by making video instructionals using Kdenlive- a core part of our education/training work.
Line 48:		Line 48:
	The format for each team meeting is:		The format for each team meeting is:

	Everyone is assigned tasks during the Monday meeting. In case you miss the meeting, you can review it at http://opensourceecology.org/wiki/D3D_Meeting_Log . It is good practice to prepare for this meeting by watching the videos from previous meetings so you are up to speed. New developers will also be assigned tasks at their first meeting. The D3D Meeting Log includes http://opensourceecology.org/wiki/Scrumy - which is a backlog ~~for~~ tasks and their completion.		Everyone is assigned tasks during the Monday meeting. In case you miss the meeting, you can review it at http://opensourceecology.org/wiki/D3D_Meeting_Log . It is good practice to prepare for this meeting by watching the videos from previous meetings so you are up to speed. New developers will also be assigned tasks at their first meeting. The D3D Meeting Log includes http://opensourceecology.org/wiki/Scrumy - which is a backlog of tasks and their completion.

	To be in Excellent Standing, you have to contribute a minimum of 100 hours in the 12 week Development Cycle, for which you will receive a star on your badge. You are allowed and encouraged to recruit a co-worker - who is not part of team meetings but who works with you on completing tasks - and who can participate in the team meeting for you if you are not available. Recruiting a co-worker allows you to reduce your ~~work load~~ as an OSE Developer - while helping others to participate without having passed the official OSE FreeCAD Test. Working in pairs helps keep momentum - and it also helps to develop your leadership skills.		To be in Excellent Standing, you have to contribute a minimum of 100 hours in the 12-week Development Cycle, for which you will receive a star on your badge. You are allowed and encouraged to recruit a co-worker - who is not part of team meetings but who works with you on completing tasks - and who can participate in the team meeting for you if you are not available. Recruiting a co-worker allows you to reduce your workload as an OSE Developer - while helping others to participate without having passed the official OSE FreeCAD Test. Working in pairs helps keep momentum - and it also helps to develop your leadership skills.


Line 65:		Line 65:
	'''ETIQUETTE'''		'''ETIQUETTE'''

	Email Etiquette - do not send files over email. Upload them to the wiki, and send links in email. This way, the world has access to your work, as we work openly, and anyone in the world can collaborate.		Email Etiquette - do not send files over email. Upload them to the wiki, and send links in an email. This way, the world has access to your work, as we work openly, and anyone in the world can collaborate.

	Publishing Etiquette - “Publish Early and Often.” Do not wait until you finish something to upload a file to the wiki - upload immediately after you finish working on something on a daily basis. Use the version history on the wiki to “Upload a new version of the the file.” The reason is immediate access by others - as we typically encourage others to pick up work and continue it in a tag-team fashion - including even the cooperation of people who are not on the official team. The reasons for Publish Early and Often are 3-fold: (1) improved team morale as it is visible that work is being done, (2) immediate ability to collaborate, (3) not losing work - in case your computer crashes or something happens to the developer - the work is still available to others. The only thing to watch out for is that anyone who continues the work also uploads their work immediately - so that it is clear that updates were made. The developer is responsible for checking the latest uploaded file on a regular basis - to make sure they are working on the latest version. This process is an important culture point for effective remote collaboration by large teams.		Publishing Etiquette - “Publish Early and Often.” Do not wait until you finish something to upload a file to the wiki - upload immediately after you finish working on something on a daily basis. Use the version history on the wiki to “Upload a new version of the the file.” The reason is immediate access by others - as we typically encourage others to pick up work and continue it in a tag-team fashion - including even the cooperation of people who are not on the official team. The reasons for Publish Early and Often are 3-fold: (1) improved team morale as it is visible that work is being done, (2) immediate ability to collaborate, (3) not losing work - in case your computer crashes or something happens to the developer - the work is still available to others. The only thing to watch out for is that anyone who continues the work also uploads their work immediately - so that it is clear that updates were made. The developer is responsible for checking the latest uploaded file on a regular basis - to make sure they are working on the latest version. This process is an important culture point for effective remote collaboration by large teams.

	Team Etiquette - we are a learning community, and we create an encouraging learning environment for team members. We pride ourselves on a positive team spirit, and an open mind for learning. We pull together toward common goals - so that morale is high - based on clearly visible results.		Team Etiquette - we are a learning community, and we create an encouraging learning environment for team members. We pride ourselves on a positive team spirit and an open mind for learning. We pull together toward common goals - so that morale is high - based on clearly visible results.


Line 82:		Line 82:
	Thank you,		Thank you,

	~~Sincerly~~		Sincerely

	Marcin Jakubowski Founder Open Source Ecology Richard White HR Generalist in Training		Marcin Jakubowski Founder Open Source Ecology Richard White HR Generalist in Training

Richard White at 18:04, 23 April 2017

2017-04-23T18:04:36Z

← Older revision		Revision as of 18:04, 23 April 2017
Line 38:		Line 38:
	Post the badges that you have earned at the top of your log (so far the OSE FreeCAD Badge)		Post the badges that you have earned at the top of your log (so far the OSE FreeCAD Badge)
	OSE Network - we are using the OSE Network 3D Printer Group as the official discussion thread for the 3D Printer group.		OSE Network - we are using the OSE Network 3D Printer Group as the official discussion thread for the 3D Printer group.


	'''WEEKLY MEETINGS, GOOD STANDING, AND RECRUITING NEW TEAM MEMBERS'''		'''WEEKLY MEETINGS, GOOD STANDING, AND RECRUITING NEW TEAM MEMBERS'''