Member Onboarding

Interested:

Registered some interest in the Foundation, but have not decided where to put their effort into.

A member is in the interested state when they completed our member signup form.

We then:

• Add them to our member database.

• Their organization representative has been informed this individual has registered.

• Added to the gsf-all, gsf-newsletter and gsf-announcement email lists.

• Send a welcome email with details of all the different groups/projects they could take part in amongst others.

• They receive a monthly email digest of the core activity in the Foundations Working Groups, Special Interest Groups and Projects.

• How we move them from Interested → Subscribed:

  • If something interests them they can click the link in the email to that WG/SIG/Project and follow the instructions to subscribe to that group.

Subscribed To Working Group or Project

Some part of the Foundation has captured their interest, be it a Working Group, a SIG or a Project. They have subscribed to their email list and want to find out what’s happening. At this point they are still just reading and looking around.

A member is in the subscribed state when they have filled out our member subscriber form and subscribed to either a WG/SIG or PROJECT.

We then:

• Update our member database and mark them as subscribed.

• Add the person to the relevant email list for that group.

• Send them a welcome email from that group.

• Send them regular emails regarding that group e.g. meetings agendas/minutes and/or regular weekly/monthly summary emails.

• The contents of these emails should mostly be GitHub discussions, issues, pull requests related to that group, we are using these emails to encourage people to take an action. The action could be as simple as a “like” or as complex as a “comment/review” etc… we should always have a very simple way for people to engage.

• We need to give people very small actions they can take to build up their confidence to take more complex actions later on.

How we move them from Subscribed → Engaged:

• If a Discussion, Issue or Pull Request (or some other action) captures their interest in the email they might click it and take an action (like, comment, approve etc…).

• As soon as someone takes an action on GitHub we consider them an Engaged member.

Engaged

Are actively engaging in a WG/SIG or PROJECT via GitHub consistently over a 3 month period.

A member is active when they perform an activity on GitHub that we can measure using our scripts, this usually means any activity on GitHub from liking a comment to creating a pull request.

To be engaged is to be active for at least 4 of the last 8 weeks.

Once people are engaged we want to continue to encourage that engagement and grow them into leaders.

Only engaged members can vote or nominate themselves for leadership positions.

We then:

• Update our member database and mark them as engaged.

• Send them an email congratulating them on their first engagement.

Uninterested

After a period of time have not subscribed or engaged in an aspect of the Foundation, we should check with these people every 6 months to see if they want to be removed from our database.

KR1.1:

80% of our individual members are subscribed by end of 2023.

As measured by the number of people who have subscribed to the mailing list of a Working Group, Special Interest Group or Project.

KR1.2

20% of our individual members are engaged by end of 2023.

As measured by the number of people who have performed at least one measurable activity on GitHub for 4 of the last 8 weeks, from liking a post to creating a pull request.

KR1.3

100% of our member organizations have at least 1 person in an engaged state by the end of 2023.