tfgrid/circle_promotion
26
1
Fork 0
Code Issues 61 Pull Requests Packages Projects 4 Releases Wiki Activity

May Newsletter #170

New Issue
Closed
opened 2024-05-31 06:00:22 +00:00 by Amanda · 2 comments
Amanda commented 2024-05-31 06:00:22 +00:00
Member
Copy Link

Need to create a May newsletter and send it out

  • Create draft

  • Team to review

  • Send it out

The draft is here. Waiting to add yesterday's call recordings and the newsroom links for the community calls.

Need to create a May newsletter and send it out - [x] Create draft - [x] Team to review - [ ] Send it out The [draft ](https://docs.google.com/document/d/1BwNhIv3fC7PCGnP1F40uPwaY37NXpAxGqPvKeSALJvs/edit)is here. Waiting to add yesterday's call recordings and the newsroom links for the community calls.
Amanda self-assigned this 2024-05-31 06:00:32 +00:00
Amanda added this to the May 27 – June 09 project 2024-05-31 06:00:52 +00:00
gosam modified the project from May 27 – June 09 to June 10 – June 23 2024-06-10 14:44:04 +00:00
gosam commented 2024-06-11 12:28:29 +00:00
Owner
Copy Link

Hi @Amanda

The way it is written now is a bit hard to follow, there’s no introduction, it just goes straight into Community Updates and then a bunch of bullets, so it certainly needs some framing … Each section is like this ... It makes it a bit dry and a LOT of information

Maybe we should do a newsletter every ½ month, so somewhere around the 15th and somewhere around the end of the month, which covers those previous ±2 weeks ...

This can more or less summarize each news update that we send to the Telegram Channel (including summaries of the calls) and then maybe the new blogs (if they haven’t been highlighted in the news channel) and any relevant forum posts. This would make it a bit more straight-forward.

Let me know what you think. If you agree, we can close this issue and create a new one for a newsletter to be sent this Friday / next Monday, and you could start on that one.

If you disagree, please comment here!

Hi @Amanda The way it is written now is a bit hard to follow, there’s no introduction, it just goes straight into Community Updates and then a bunch of bullets, so it certainly needs some framing … Each section is like this ... It makes it a bit dry and a LOT of information Maybe we should do a newsletter every ½ month, so somewhere around the 15th and somewhere around the end of the month, which covers those previous ±2 weeks ... This can more or less summarize each news update that we send to the Telegram Channel (including summaries of the calls) and then maybe the new blogs (if they haven’t been highlighted in the news channel) and any relevant forum posts. This would make it a bit more straight-forward. Let me know what you think. If you agree, we can close this issue and create a new one for a newsletter to be sent this Friday / next Monday, and you could start on that one. If you disagree, please comment here!
gosam commented 2024-06-13 14:11:39 +00:00
Owner
Copy Link

We've decided on a new approach. New story coming for next sprint.

We've decided on a new approach. New story coming for next sprint.
gosam closed this issue 2024-06-13 14:11:39 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
  
Issue

   
Question

   
Roadmap

   
Story

   
Task

   
Urgent
No Label
Issue
Question
Roadmap
Story
Task
Urgent
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
June 10 – June 23
Assignees
Clear assignees
No Assignees
Amanda
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: tfgrid/circle_promotion#170
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?