Writing a meeting request email

Open
#18 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
35/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Stale
Domain
content

Research direction

Create the Google Doc in your own Google Drive and write meeting-request emails for the three listed scenarios: setting context and an agenda, disagreeing with an idea, and asking about an assigned task. Check spelling and grammar, ensure reviewers can open and comment, then share the document link in a comment on the issue in your planner.

Written by the indexing model from the issue text.

Description

🏕 Priority Mandatory 🐇 Size Small 📅 Sprint 2 Core Module-Structuring-And-Testing-Data Submit:Issue
Learning Objectives
  • Write emails requesting meetings in different contexts.
Why are we doing this?

Being able to communicate effectively in writing is a very important skill. There are many different platforms where we might need to communicate in writing (eg. Slack, LinkedIn) and the way in which we do so may be slightly different for each. In this exercise we will practice writing emails to colleagues.

Write an email requesting a meeting with a colleague for each of these scenarios:

  • Booking a meeting and giving it context/agenda
  • Disagreeing with a team member’s idea
  • Asking a question about a task which has been assigned to you

Remember to check the spelling and grammar!

Maximum time in hours

1

How to submit

Create the Google Doc in your own Google Drive.
Ensure the document can be opened and commented on by reviewers - you can find out how to do that here.
Share the link to the document in a comment on this issue in your planner.

Dominant language
JavaScript
Stars
0
Forks
397
PR merge metrics
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from CodeYourFuture/Module-Structuring-and-Testing-Data

All issues in CodeYourFuture/Module-Structuring-and-Testing-Data

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.