Closed patcon closed 5 years ago
Your simple approach of having an ical feed that is just the result of calling out to Zoom’s API sounds great to me!
At first I was wondering if iCal would lead to standing calls not getting "upstreamed" to the org calendar, but now I think a seperate feed makes the most sense!
Assuming this would just be for the EDGI Zoom acct, as it is the only one halpy interfaces with?
Per our new stale issues policy:
This issue has been marked as stale because it has not had recent activity. It will be closed in seven days if no further activity occurs. If it should not be closed, please comment! Thank you for your contributions.
In the future, a robot will take care of this process!
Two cents :moneybag: : I think this is valuable! there are many issues in the halpy repo
: https://github.com/edgi-govdata-archiving/edgi-hubot-halpy/issues that could also align with improving access
I'll shop all the bot issues/ideas to our Sys Admin whenever they come onboard
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in seven days if no further activity occurs. If it should not be closed, please comment! Thank you for your contributions.
Currently, Zoom calls must be manually added the the EDGI organizational calendar. This is prone to being forgotten about, for many valid reasons.
There was some conversation around having halpy's call creation command (
zoom me
), auto-add things to calendar, but that's a little messy.There might be a more unixy approach: Write a tiny heroku app that uses the Zoom API key to rewrite event listings into an ical feed. That feed could then be renders as an HTML google calendar, or also passed to one of these general ical hubot scripts: https://github.com/edgi-govdata-archiving/edgi-hubot/issues/10#issuecomment-299395603
Related: https://github.com/edgi-govdata-archiving/edgi-hubot/issues/10
cc: @Mr0grog