Create templates for common communications

[nate-double-u]

Suggestion:

under the mentoring-wg/ folder, create a templates folder, put common templates there and create project specific folders for specific templates.

[nate-double-u]

/cc @jaytiaki @Riaankl @jberkus

As per discussion: https://github.com/cncf/mentoring/blob/main/mentoring-wg/2023-meeting-minutes.md#april-11-2023

[nate-double-u]

There's room for discussion about where and what types of templates should be created 🙂

[aliok]

It is a good idea!

I was creating links to the announcements we made in the GSoC admin guide. So that we can reuse their text next year.

Collecting these in a folder would be nice.

There's room for discussion about where and what types of templates should be created 🙂

I want to discuss the approach first 🙂

Can we do it as we go? Approach can be:

1. Check if the template exists for a communication you would like to make.
2. If it exists, use it.
3. If not, write the communication, get team feedback, make the communication, create a template out of it.

Writing communications in advance before need might be hard IMO.

create a templates folder, put common templates there and create project specific folders for specific templates.

I think being project specific is key! I like the idea here. Although, I think I would prefer having single folder with a file per program.

I think I would initially convert these into templates:

• GSoC - Call for ideas: Google Summer of Code 2023 CNCF Project Proposals #777
• GSoC - Acceptance announcement and call for more ideas: Google Summer of Code 2023 & CNCF #848
• GSoC - Contributor applications open: GSoC 2023 Applications are now open for contributors (mentees) #892
• GSoC - Contributor applications closed; mentors to review proposals: GSoC 2023: Contributor Proposal Review and Updates #918