New Developer Orientation

From Open Source Ecology
Jump to: navigation, search

Team Meetings

All Development Team meetings occur at 1 PM CST USA Time every Tuesday at

General Practices

Welcome to the Developer team. These are our general practices:

WEEKLY MEETINGS, GOOD STANDING, RECRUITING HELP AND NEW TEAM MEMBERS The development team will meet every Tuesday at 1 PM CST at the OSE Hangout. New developers will be assigned their first tasks. In case you miss the meeting, you can review a recorded video on the meeting log. It is good practice to prepare for this meeting by watching the videos from previous meetings so you are up to speed.To be in Excellent Standing, you have to complete the 120 hours in a 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.

Open source ecology is an open source network and movement. Open Source Ecology International is the nonprofit organization that coordinates the open source ecology effort. Everyone can participate by editing our wiki. 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. 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.

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 addresses the tens of hours that it would potentially take to download and configure all the software and libraries in common use by OSE. Instead, a single install, taking a few minutes of install time after download, is sufficient to download the entire operating system.This will be updated every quarter, so please update that as needed.

DOCUMENTATION AND ETIQUETTE 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 meticulously - using a Work Log - so we do not produce duplicate work and we may have accurate statistics to improve efficiency.

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. Include the date at the top of your log, and post with the newest work log updates at the top so that that your latest is readily visible without scrolling down. Include links to all your work, such as uploaded files or working documents. 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. We also teach each other, so you may be expected to publish a How-To on some topic that you have learned.

PIONEERING It is both our privilege and our challenge to make the road by walking. As we test technologies and open development processes--and break them--and evolve our practices, we enjoy each other’s good humor, problem solving, and pioneering attitudes.

New Developer's To-Do List

Welcome to the OSE Developer Team! It's time to get you set up. There are a lot of things to do so just take your time. If you have any questions contact Jozef (

Get Connected

We do a lot of our communications through online hangouts, text, email, and social media platforms. Let's get you connected.

  1. Go to the OSE Developers page and take a look at the bios of your new teammates. (You're going to post your bio in a little bit, but right now just take a look around.)
  2. If you have a smartphone, add the messaging apps WhatsApp and Signal, which we use for quick communications. They're in both the iTunes App store and Google Play, etc.
  3. Add your info on the OSE Developer's Contact Info page. Look up Jozef and shoot him a message. Once you find out who your teammates are in your first OSE Hangout, it's not a bad idea to add them to your contacts.
  4. Our public discussion venue is the OSE Workshops FB Group - Open Source Ecology Workshops Group. Please join. You can follow Open Source Ecology FB Page as well.
  5. Sign up to OSEmail for OSE news.
  6. Slack Channel

Calendar & Reminder Items

Take a look at the calendar and add the following items to remind yourself.

  1. First of all, you're in. Did you celebrate yet?
  2. Add your end date, listed in your welcome email.
  3. Add a reminder for your weekly meeting time. The main OSE development team will meet every Tuesday at 1:00 PM CST at our dedicated OSE Hangout. If there are changes to meetings times, you will be emailed. (Links below.)
  4. Add a reminder to submit your timesheet on Monday. (Instructions below.)

Wiki Items

Let's carve out some space for you on the OSE Wiki, and make sure you're set up right for you User Page, your Work Log, and on the OSE Developer Page. (Refer to Wiki 101 for help.)
User Page: This helps us learn about each other. It is a space for an informal resume & bio to help us allocate team roles, and tap the right people for input or to share skills. You can check out Jozef's here.

  1. Post your badge(s) at the top of your user page.
  2. Link to your work log.
  3. Add an informal resume of your experience, education, skills, and certifications.
  4. Add a bio if you would please.

Work Log Items.

  1. Take a quick look at Marcin Log, Lego Log, or Jozef Log as a samples of logs. (Publish early & often. Always link / embed files, even if you're not done. Put your newest work on top. Style-wise, keep it short and sweet like post-it notes on progress.)
  2. Review Best Practices for Logs.
  3. Add a Status Update Flag on top of your log. Look at the top of Marcin Log, Lego Log, or Jozef Log to see the green flag stating what is Done, To Do, or Blocked.
  4. Link to the following on top of your log (for quick reference):
    1. Wiki 101 if you might need it. (This is going through a heavy edit, but it is currently a repository of misc help links.)
    2. Timesheet link. This is how we submit time sheets every Monday.
    3. Google Hangouts link. This is where we meet.
    4. D3D for the general 3D printer project overview.
    5. Development Team Log. This is where we keep all our working files and link our captured meeting videos (if you happen to miss one).
    6. Your teammates' logs. At the first meeting you will be assigned to a team. Once you find out, refer to the Developer’s Page to find the links to their logs, and link to them on top of your page.
    7. Your User Page

OSE Developer Bio: Go to the OSE Developers page and post your own bio there. (If you're not sure how to format it, just take a look at what other developers did.) Add the following items:

  1. Profile picture attached in jpeg or png format
  2. A public email address for yourself
  3. A quote from you about why you are contributing to OSE
  4. A short bio or few sentences including your relevant skills
  5. Add your badge and reduce the size to match the size of others (250px).
  6. Link to your Work Log and User Page.

Take a Tour of OSE's Development Tools

The OSE Development Team uses a lot of tools for communication, design, and cloud documentation. You have already encountered most in the test. We regularly use Google Drive, Google Docs, Google Hangouts, Jitsi Meetup, Kdenlive, the OSE Wiki, Vokoscreen, the OSE Network, FreeCAD, and others. Begin to familiarize yourself with the tools and bookmark any help sources you will need to refer to. We mostly utilize external resources for help, but as we find good help resources we relocate them to our own help pages to compile our own tutorials: Google Drive 101, Google Docs 101, Wiki 101, Google Hangouts 101, FreeCAD 101, OSE Network 101, Vokoscreen 101, Kdenlive 101, and Scrum. We don't use any Scrum software, but we borrow the Scrum style of project management and use its vocabulary. Feel free to reach out to your teammates with questions, or contact HR.