New member communications plan

[ElenaFdR]

Have a plan to implement immediately each time a new member joins the Foundation. This should live in about/activities/communication.

It should include:

• an immediate response (eg updating publiccode.net/members, an announcement email to our mailing list and a tweet)
• a longer response that doesn't depend on the new member org (eg a blogpost announcing our exciting collaboration, focusing on specific codebases based on research we've already done)
• a longer response that does depend on the new member org (eg getting quotations from senior leaders, or setting out more detailed plans for what we'll do together in the months ahead) - agreed with the new member's communications team

[lscheske]

Great idea! Let's work on this together, @ElenaFdR

[ElenaFdR]

@bvhme/@nebster steer: frame as vote of confidence in public code, validating our approach and raison d'etre (we appreciate their recognition that the Foundation for Public Code supports their open source strategy), not emphasizing the effects this will have on our org.

[bvhme]

This doesn't need to be done all at once, and can be done in smaller iterations. Perhaps we can make a checklist out of the items in the issue?

Also, can this be the start of a activities/member-onboarding, so that we can keep that together and make sure those activities are shared between you?

[clausmullie]

@ElenaFdR some of this thinking may be useful for new partners joining, but I propose closing this issue for now as we are not doing member development.