Welcome Email

From Open Source Ecology
Revision as of 14:25, 28 June 2017 by Richard White (talk | contribs)
Jump to navigation Jump to search

SUBJECT LINE: Welcome to the Open Source Ecology Development Team


This email will be your reference to the processes and platforms used by the development team. Please star or archive this email.


Congratulations ________________,

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 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 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.

To get an overview of the development work of Open Source Ecology, please review our Crash Course here: http://opensourceecology.org/wiki/OSE_Crash_Course

.

OUR CURRENT PROJECT: OPEN SOURCE 3D PRINTER

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_Log


YOUR WORK LOG AND COLLABORATION PRINCIPLES

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 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.
  • Please fill out your timesheet by Monday's meeting every week - as we track development time so we can increase our team velocity.
  • 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.
  • 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


WEEKLY MEETINGS, GOOD STANDING, AND RECRUITING NEW TEAM MEMBERS

The development team will meet every Monday at 11:00 AM CST at the OSE Hangout - please bookmark it as that is where all of our team meetings take place:

https://hangouts.google.com/hangouts/_/event/cfvdskolaipjgki95aoufjf3l50?hl=en&authuser=0

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 sometimes uses http://opensourceecology.org/wiki/Scrumy - which is a backlog of tasks and their completion.

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.


OSE LINUX 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.

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


ETIQUETTE

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.

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.


TELL YOUR FRIENDS

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.

TEAM BIO PAGE

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

We are requesting the following:

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

Please send bio information to hr@opensourceecology.org

Sincerely,

Marcin Jakubowski Founder Open Source Ecology

Richard White HR Generalist in Training

Retrieved from "https://wiki.opensourceecology.org/index.php?title=Welcome_Email&oldid=154770"