Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add Dec/Jan SC recaps to blog #249

Closed
1 of 16 tasks
theecrit opened this issue Feb 10, 2022 · 0 comments
Closed
1 of 16 tasks

Add Dec/Jan SC recaps to blog #249

theecrit opened this issue Feb 10, 2022 · 0 comments

Comments

@theecrit
Copy link
Collaborator

What are you submitting?

Place an x in the appropriate bracket:

  • Bug (something's broken)
  • Feature request or improvement
  • Content update
  • Question
  • Other

Description

Each month, we need to add a short recap of the most recent Steering Committee meeting to the blog. Ideally, this is done within a week of the meeting.

How to do it

  • Read the meeting minutes from the most recent meeting. These are located in the shared Google Drive.
  • Follow the instructions in the ReadMe to get the repo set up locally and create a new branch.
  • Create a new post in the /src/_posts folder by duplicating a previous SC recap post.
  • Change the front matter for accuracy (title, date, author, excerpt).
  • Replace the content with your recap (you can leave the featured image as-is).
  • Open a PR and request a review from any of the project admins.

What should be in the recap?

See previous recaps on the blog for how these are generally written. In the past, we've been a little wordy. We want to balance brevity with usefulness. Tell people the important decisions, discussions, and sentiment reflected in the minutes.

  • Brief intro summarizing that month's theme.
  • Key decisions made.
  • Key discussions and the points that were raised, including any open questions.
  • Key action items or next steps committed to.
  • Update the footer details with the next meeting date.

Thank you!

  • Please document your design and tech decisions in your pull request so others can follow along and understand why we've made the decisions we have.
  • If you'd like feedback, input, or help, share your thoughts or question in this issue's comments.
@theecrit theecrit self-assigned this Feb 10, 2022
@theecrit theecrit added this to Backlog in Ongoing improvements backlog via automation Feb 10, 2022
@theecrit theecrit moved this from Backlog to In progress in Ongoing improvements backlog Feb 10, 2022
@theecrit theecrit moved this from In progress to Done in Ongoing improvements backlog Feb 14, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

1 participant