Newsletter plan and execution #116
Loading…
Reference in New Issue
Block a user
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?
We have a mailing list that we are not using effectively, we need a plan to be agreed on and then we need to execute.
there needs to be a plan and people who get assigned to this plan to
see people who want to do them, we can start thinking to use INCA rewards
@despiegk OK but this is not really the point of the issue. Your points are being addressed in other issues, so I will move this one back out of the current sprint.
@Amanda Let's talk about this
As discussed I'll share my research and plan here.
Research:
**Not so very helpful.
TF Newsletter
Frequency:
1. I think once a month should work, maybe right after the project update call and on major updates that we get in between.
2. Don't suggest we do it often as we already have weekly community calls.
3. Can start our first after our upcoming project update community call.
Content-wise: Community calls, Blogs written, project updates, news articles.
We shall see how it works for about 3 months and move forward.
OK so we can close this story and make sure we incorporate it into the content calendar for May.