Developer Vetting Process

From Open Source Ecology
Revision as of 18:16, 13 June 2013 by Marcin (talk | contribs) (Created page with "#Before anything else - add disclaimer in our signatures that our communications IP is open source. We work openly, and privileged and confidential information shall be addres...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search
  1. Before anything else - add disclaimer in our signatures that our communications IP is open source. We work openly, and privileged and confidential information shall be addressed not in email, but other media such as phone.
  2. First - find out whether the person is willing to work on site or remotely.
  3. Second - find out how much time they have available for OSE contributions, and whether that is volunteer or paid.
  4. Third - assess for their contribution type - what skills/offers they have
    1. Resume
    2. Documented work samples
    3. References for what other projects they worked on
  5. Fourth - bring them into community.
    1. Tech team culturing survey
    2. Executive Team Advisor
    3. Mentor or coach
    4. Forums or communication channels
  6. Fifth - bring in the True Fans Network + 1 Day in 2 Hours + OSE Chapters online
  7. Start OSE Credit Score - badges connected specifically to 1 Day in 2 Hours for OSE Skills Badges, and Contributor Badges for specific contribution performance.
Retrieved from "https://wiki.opensourceecology.org/index.php?title=Developer_Vetting_Process&oldid=96415"