Update the Google Calendar integration
Niloth-p opened this issue · 18 comments
The oauth2client library used in the google-calendar integration scripts has become deprecated. So, the script needs to be updated, to replace oauth2client with other libraries that Google is now using.
Refer to the quickstart example in the Google docs for what to use in the place of oauth2client.
Make sure that you update requirements.txt.
Set Up:
Refer to this integration doc for instructions to set up the integration. It's currently in the process of being updated as part of this PR, so until then you could refer to a screenshot of the updated version in that PR description.
Bonus tasks:
It would be nice to clean up the scripts as part of this.
And add a conventional example screenshot to the integration doc.
References:
For more on integrations, refer to these docs - Integrations Overview, and Non-webhook integrations.
Welcome to Zulip, @vats004! We just sent you an invite to collaborate on this repository at https://github.com/zulip/python-zulip-api/invitations. Please accept this invite in order to claim this issue and begin a fun, rewarding experience contributing to Zulip!
Here's some tips to get you off to a good start:
- Join me on the Zulip developers' server, to get help, chat about this issue, and meet the other developers.
- Unwatch this repository, so that you don't get 100 emails a day.
As you work on this issue, you'll also want to refer to the Zulip code contribution guide, as well as the rest of the developer documentation on that site.
See you on the other side (that is, the pull request side)!
The
oauth2clientlibrary used in thegoogle-calendarintegration scripts has become deprecated. So, the script needs to be updated, to replaceoauth2clientwith other libraries that Google is now using.Refer to the quickstart example in the Google docs for what to use in the place of
oauth2client.Refer to this integration doc for instructions to set up the integration. It's currently in the process of being updated as part of this PR, so until then you could refer to a screenshot of the updated version in that PR description.
Bonus tasks: It would be nice to clean up the scripts as part of this. And add a conventional example screenshot to the integration doc.
Hi @Niloth-p
Does this Google Calendar code use service account credentials?
@octocamocoder47 Can I still contribute to this issue?
@theofficialvedantjoshi - Yes, the issue is still open.
The linked PR does not conform to our guide on submitting a pull request, and needs to be updated before it is ready for a review.
Please go through our Contributing Guide before your first contribution to Zulip.
@zulipbot claim
@theofficialvedantjoshi This issue cannot be claimed, as someone else is already working on it. Please see our contributor guide for advice on finding an issue to work on. Thanks!
@zulipbot claim
@octocamocoder47 This issue cannot be claimed, as someone else is already working on it. Please see our contributor guide for advice on finding an issue to work on. Thanks!
@theofficialvedantjoshi I am still working on this issue.
@zulipbot claim
@octocamocoder47 This issue cannot be claimed, as someone else is already working on it. Please see our contributor guide for advice on finding an issue to work on. Thanks!
@theofficialvedantjoshi seems like most of the code is replicated from my pr.
@Niloth-p I have tested the issue end to end. below is link to demo.
https://drive.google.com/file/d/1isjB0xGirL0Bpn0SGRz0cO8RZS58rQFd/view?usp=sharing
please feel free to comment if link is not accessible.
I have also tested the bot script.
below is the public link to demo.
https://drive.google.com/file/d/1OvqqGw8jSNWe9iudZsoviqw9665E-9tw/view?usp=sharing
please feel free to comment if link is not accessible.
I submitted a PR for this issue a while ago, ensuring that all test cases passed and thoroughly validating the entire flow. I also provided testing video links as proof. However, despite having a well-tested PR in place, others continue contributing unnecessary changes, causing delays and inefficiencies. This not only wastes the time of contributors but also impacts users relying on this plugin. Could you please provide an update on when this PR will be merged?
pr link: #851