cncf / mentoring

👩🏿‍🎓👨🏽‍🎓👩🏻‍🎓CNCF Mentoring: LFX Mentorship + Summer of Code
https://mentoring.cncf.io
Apache License 2.0
2.37k stars 612 forks source link

Create templates for common communications #930

Open nate-double-u opened 1 year ago

nate-double-u commented 1 year ago

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 commented 1 year ago

/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 commented 1 year ago

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

aliok commented 1 year ago

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: