Dev-squad GitHubGitHubGitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/ triage: Thursdays 07:00 UTC
The roster of Guides consists of experienced Training Team members. It would make sense for Faculty members to participate, but it is not required of them. Training Team members that have a Training Contributor badge, and have been contributing consistently to the team for at least 6 months could also qualify as Guides.
For initial launch of the program, Guides were chosen from existing Faculty members (preferably part or full-time sponsored, since they can maintain their commitment and access). An application form for experienced contributors that are interested in becoming Guides has since been created. Applications are reviewed by Faculty members.
When a new contributor joins the #Training channel, they are greeted with an automated message that includes offering them the option to be matched with a Training Team Guide. If interested, they are instructed to fill out the interest form in order to be matched with a Guide.
During the weekly Training Team meetings, the Welcome Committee can also remind the new channel joinees that they can join the Guide Program, and share the application form with them.
There will be more pathways for new contributors to learn about the Guide Program, but for the initial launch of the program, we are starting with SlackSlackSlack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/.-based introductions.
Once new contributors have completed the interest form, this information will be used to match them with Guides. The following factors are considered in order of priority:
Time zone in UTC
Language(s) they are comfortable conversing in
Area(s) of contribution that they are interested in
Form submissions are stored in a spreadsheet that Administrators and Guides review to identify suitable pairings. Admins can help assign Guides to contributors, or Admins can volunteer themselves. Note that Guides should take on no more than 4 new contributors at once.
It is recommended that Guides interact individually with the new contributors that they are paired with. However, Guides can opt to form small cohorts (up to 4 people) if they are able to arrange suitable methods of communication and synchronous connection times.
Regular check-ins between Guides and new contributors can be brief, as they will also be in constant contact via asynchronous Direct Messages (DMs) on Slack. However, keep in mind that it is important to leave space for the new contributor to communicate any questions or concerns during each check-in. It is recommended to have check-ins at least weekly, but the Guide and contributor can plan a schedule that works best for them.
If a Faculty Admin assigned the pairing, they introduce the Guide and the new contributor to each other via Slack DM. If the Guide is a Faculty member, they can introduce themselves.
The Guide and new contributor discuss the cadence for their regular check-in meetings and set up a schedule. Synchronous check-ins are preferred, but if schedules do not allow, asynchronous check-ins on Slack are also acceptable.
Before their first check-in, the Guide confirms if the contributor has valid WordPress.orgWordPress.orgThe community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ and GitHubGitHubGitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/ accounts, and shares the Getting Started guide with them.
The Guide asks the new contributor if they have reviewed the Getting Started Guide, completed the steps, and if they have any questions.
Bonus: if the contributor has decided which area(s) of contribution they want to pursue, they complete the onboarding process for that area together.
The Guide advises the new contributor to attend the next Training Team meeting (Coffee Hour optional) to observe. Attending the meeting can be done synchronously or asynchronously. The contributor is asked to gather observations and questions from the meeting to share with their Guide during the next check-in.
The Guide will be available to the new contributor via Slack DM if any questions arise before their next check-in (this is an expectation between all subsequent check-ins).
The Guide and new contributor meet to discuss the self-guided onboarding process as well as their first Training Team meeting. They discuss any questions or concerns that arose during the process.
If the contributor did not decide upon an area of contribution after the first check-in, the Guide discusses the roles with the contributor to help guide them in finding how they can best apply their strengths and skills to the team.
The Guide gives an overview of the types of tasks in the contributor’s chosen area of contribution (using the Team Roles page as a reference). The Guide can show the contributor real examples of contributions through a screen share during a synchronous call.
Guides are expected to share a brief update on their activity with their new contributors and celebrate their contributions during Training Team meetings. This can be done asynchronously if the Training Team meeting is at an inconvenient time for the Guide.
Once the initial check-ins are completed, the Guide and Contributor can choose to continue regular check-ins and/or remain connected on the Making WordPress Slack.
It is recommended to check in again after three months to evaluate how their continued contributions are going and if they are interested in expanding their contributions (trying a new task or a different area of contribution). We will also create a survey for contributors to complete 3–6 months after concluding the Guide Program to gather feedback on their progress.