Show pageOld revisionsBacklinksBack to top This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong. ====== First Contact Team ====== At the %%EuroBSDCon%% 2015 Dev Summit Recruiting session, the idea was raised to have a team of people who would be potential new contributors first contacts in the community. Rather than suggesting that they send a mail to a mailing list which might go unanswered, the idea is to identify a team of %%FreeBSD%% community members who are best suited to onboarding potential new contributors and shepherding them into the project. ===== Goals ===== * Attract more people to the project * Ensure that people who do attempt to contribute receive feedback instead of crickets * Ensure that the feedback first time contributors receive is positive * Extend the idea of 'Doc Sprints' online * Develop a high quality onboarding guide ===== Tools ===== * %%WebRTC%% (talky.io, appear.in, etc) * Google Hangouts (do they work on %%FreeBSD%%?) * Mumble (voice only, some people may want to avoid video, or not have the bandwidth for video hangouts) * IRC (put up a page somewhere with mibbit, a javascript IRC client that allows people to join IRC without installing anything) ===== People ===== * AllanJude ==== Onboarding ==== * Signup for Bugzilla * Signup for Phabricator (why is this separate? What happened to the idea of SSO via github etc?) ==== Outstanding Tasks ==== * Integrate automatic build testing of patches into Phabricator * Generate more documentation on getting started, that isn't from the 90s ==== Resources ==== * DanLangille's "Contributing to Open Source" workshop * Brian Callah's Lab on [[https://github.com/rcos/CSCI2961-01/blob/master/Labs/Lab4.Md|contributing documentation patches to Open Source]] ---- {{tag>Community Team}} firstcontactteam.txt Last modified: 2018/04/15 15:06by MateuszPiotrowski