-
-
Notifications
You must be signed in to change notification settings - Fork 116
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
Get better solution than Google groups to handle distribution list for meeting invites #171
Comments
oh my god 🤦🏼 I was always expecting a kind of anyway, would be good to have something vendor agnostic |
Talked to CNCF folks and also community managers from the slack workspace where we team up.
|
we need to speed up stuff here.
I was thinking, that maybe we just need https://www.teamup.com/ for calendar and some MailChimp-like solution for users to subscribe and provide emails that we could send invites too? I'm running out of ideas. Anyone has some thoughts. |
This issue has been automatically marked as stale because it has not had recent activity 😴 It will be closed in 120 days if no further activity occurs. To unstale this issue, add a comment with a detailed explanation. There can be many reasons why some specific issue has no activity. The most probable cause is lack of time, not lack of interest. AsyncAPI Initiative is a Linux Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model. Let us figure out together how to push this issue forward. Connect with us through one of many communication channels we established here. Thank you for your patience ❤️ |
solved by #245 |
Currently, we have this Google Group where people have to join if they want us to send them meeting invites.
Current issues related to this:
Possible solution: Get in touch with Linux Foundation, afaik they already host an alternative vendor-neutral solution for distribution lists - groups. But yeah, basically we should not now try to reinvent but rather just move to tools that are already there in the LF portfolio.
The text was updated successfully, but these errors were encountered: