Migration to google calendars

mozillayvr / yvr-conf-free

Visualizes the availability status of conference rooms in the Mozilla Vancouver office

https://yvr-conf.paas.allizom.org/

Mozilla Public License 2.0

4 stars 9 forks source link

Migration to google calendars #12

Closed mozfreddyb closed 8 years ago

mozfreddyb commented 9 years ago

I used to run the mozilla berlin-office fork of this project and was trying to find out how to make it work with the new google calendaring system.

This is what I found out:

You can receive Room (aka 'calendar resource') information through the API
It needs to be authenticatedby the user with OAuth (we don't want to store personal user account/password in source code, I assume)

It returns XML :cry:. But there's also a python library, as shown in the example.

clarkbw commented 9 years ago

:crying_cat_face: I filed a Service Now request to see if they could open up the Free/Busy information for rooms to be publicly available like it used to be with Zimbra. I'll let you know what happens with that.

I've also split the back-end out into another project here: https://github.com/mozillayvr/conf-free-api If the permissions are changed we should be able to easily share the back-end code with only different forks for the front end code to display the information.

mozfreddyb commented 9 years ago

Ah, good idea. And thanks for splitting back-end off, that makes it even more convenient. Though I think I changed a few more things. But this should be discussed in another issue.

mozfreddyb commented 9 years ago

Just looked at my commits, doesn't seem like I touched server.js that much..

clarkbw commented 9 years ago

Got a disappointing response in my Service Now request from IT. Not sure we'll be able to move down that path, might have go the API route instead...

mozfreddyb commented 9 years ago

Could you CC me into the ServiceNow ticket? Maybe they could create a single-purpose user that has access to only the freebusy information for all rooms and we use this one in our backends (but not in git, of course)..

Or they share free/busy URLs for the respective rooms with us...

clarkbw commented 9 years ago

Tried, I'm not sure how to CC someone on those. After reopening the issue my request was denied again, :disappointed: seems we'll have to take another route.

mozfreddyb commented 9 years ago

I noticed that it works again. So, who did you bribe to get the YVR calendars public? It still doesn't work for me with the Berlin URLs

P.S. Repo description still points to the old paas URL.

clarkbw commented 9 years ago

So, who did you bribe to get the YVR calendars public? It still doesn't work for me with the Berlin URLs

I had to file a Service Now ticket, but the hard work is done. I did a security / privacy review already so it should be as simple as requesting your calendar URLs are made public.

mozfreddyb commented 8 years ago

Sorry, I forgot to follow up.I did get the calendar's public for the Berlin office, but I struggled with getting your gcal-rewrite working for Berlin. I finally took the time to do just that. It's now up and running at https://ber-conf.herokuapp.com/ - thanks!