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

Save-The-Date Invitations #5

Closed
colin-kiegel opened this issue Jul 18, 2016 · 2 comments
Closed

Save-The-Date Invitations #5

colin-kiegel opened this issue Jul 18, 2016 · 2 comments

Comments

@colin-kiegel
Copy link
Collaborator

We use to send only ONE invitation before a meetup. This has often been delayed, because we waited for the final agenda or tweaked the text, etc.

I suggest to send the invitations in two steps:

  1. An early / preliminary "save-the-date" invitation without any "dependencies" on agenda, etc. We shouldn't fiddle to much with this text - but instead send it as quickly as possible. Ideally the day after the previous meetup. The most important information is the date and the opportunity to start a discussion (on meetup, or elsewhere).
  2. A final invitation 1-2 weeks before the meetup with an agenda (or alternatively cancellation or change-of-date).

@Florob @badboy @killercup What do you think?

@killercup
Copy link
Contributor

Sounds good to me. I'd really like to pin down the actual dates when we do this.

We should make the first announcements as short as possible (maybe even with the exact same text each time), so it's clear this is just a "save the date" thing. This one should always be send out at least 4 weeks before the next meetup, e.g., the day after the last meetup.

For the second invitation I'd suggest we send it as soon as

  • the final agenda is known,
  • or it's the Monday of the week before the meetup.

We can always send out more emails with refinements to the agenda, but I don't think that's really necessary (and it might bother people, since meetup.com seems to send out semi-random reminder emails anyway).

@colin-kiegel
Copy link
Collaborator Author

decision accepted

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants